|
Thanks, Frances -- I've checked the case pretty carefully and it seems to be okay. foo.properties results in the MissingResourceException, foo_en_US.properties works around the problem. As I said, the properties file is kept in the same .jar as my code. This works fine on both WinNT and OS/390 but the exact same .jar file doesn't work on the 400. So much for "write once, run everywhere". Oh well, I'll wait for the PTFs to be applied. If that doesn't work, I'll try to switch to jdk 1.2 and see if that makes a difference. Thanks, Gary francess@us.ibm.com wrote: > > This should work just fine. Certainly having the latest PTFs will help, > but based on what you describe below (about renaming the _en_us and having > it work), I wonder if it is not possible that you are running into a case > sensitivity problem. > > For instance, I just recreated your problem by creating the properties file > with the name Foo.properties instead of foo.properties (the latter worked > fine). I used Wordpad and a mapped drive to create the file each time. > > Frances Stewart > Java II and Applications Enablement +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.