Someone correct me if I'm wrong, but the l10n service loads localization properties as resource bundles, so that means they need to be in the class path.
Work-around if you are using Tomcat: You should be able to override the resource bundle in the jar by putting one of your own that matches the package and name of the one in jetspeed.jar into the WEB-INF/classes directory. From my experiences Tomcat's webapp classloader will always load a resource, be it a class or not, from WEB-INF/classes directory before it checks WEB-INF/lib. Another approach is to modify the ant build scripts to NOT place resource bundles in the jar and instead, put them into WEB-INF/classes as to make for easy modification. Scott > -----Original Message----- > From: Vlachogiannis Evangelos [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 1:16 PM > To: '[EMAIL PROTECTED]' > Subject: Localization files location > > Hi all, > I was wondering why does jetspeed localization files are in jar file. > Shouldn't be more useful to be in the conf directory. Can I do that > easily? > Is there a reson for not doing smt like that? > > Thnx > Vangelis > > -- > To unsubscribe, e-mail: <mailto:jetspeed-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:jetspeed-dev- > [EMAIL PROTECTED]>
