James, Sounds like you did some nice work with the DBMessageResources - I can't wait to use it!
Jason -----Original Message----- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 1:04 PM To: Struts Users Mailing List Subject: RE: Servlte-level Resource Files It doesn't actually 'suck in' the data. I've implemented a database call for getMessage() based on a few predetermined variables (current module, bundleKey, etc). This way you won't ever have to ask for 'reload' capabilities, because it is never 'loaded' to begin with. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the "Open Minded Developer Network" http://www.open-tools.org/struts-atlanta > -----Original Message----- > From: Eddie Bush [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 10, 2002 3:57 PM > To: Struts Users Mailing List > Subject: Re: Servlte-level Resource Files > > > Sub-applications may have their own resources. That's not quite as > fine-grained as you are talking about, but it's a lot finer-grained than > it used to be. Also, James Mitchell has recently completed a > DBMessageResources which will "suck in" your resources from a DB table > (you could use basically any JDBC-capable DBMS to store them; that's an > assumption based off the fact that he's using OJB). > > Regards, > > Eddie > > Billy Ng wrote: > > >Hi folks, > > > >I don't know if anybody is doing this. I want to move the > resoruces to the servlet level which means each servlet has its > own resources instead of putting the entire app's subtitutes in > ApplicationResources.properties. If you have the mechanism like > this, would you please give me some points for how to do it. > > > >Thanks! > > > >Billy Ng > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
