Never mind. I found a work-around (sort of). James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the "Open Minded Developer Network" http://www.open-tools.org/struts-atlanta
> -----Original Message----- > From: James Mitchell [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 03, 2002 6:10 PM > To: Struts Developers List > Subject: RE: [MessageResources] loading bundle from db > > > No comments? > > James Mitchell > Software Engineer\Struts Evangelist > Struts-Atlanta, the "Open Minded Developer Network" > http://www.open-tools.org/struts-atlanta > > > > > > -----Original Message----- > > From: James Mitchell [mailto:[EMAIL PROTECTED]] > > Sent: Monday, September 02, 2002 4:11 AM > > To: Struts Developers List > > Subject: [MessageResources] loading bundle from db > > > > > > I've got JDBCMessageResources working, but in my attempts to make > > this more > > flexible I've come across a peculiar problem. > > > > I was wondering if there was a reason that the MessageResources > > implementations > > are not given a reference to MessageResourcesConfig or any > other resources > > (e.g. Datasources configured through the struts-config). > > > > I could be wrong (after all...its 4AM), but this makes it > > impossible to pass > > any properties configured via set-property in the > struts-config. The only > > way I can do this is to use 'parameter' from message-resources. > > (I need to > > pass more than one parameter) > > > > > > > > > > > > Am I way off in left field here? > > > > Is it even feasible to change the framework to do something like this: > > > > <plug-in > > className="org.apache.struts.util.PropertyMessageResourcesPlugin"> > > <set-property > > property="parameter" > > value="org.apache.struts.webapp.example.ApplicationResources"/> > > </plug-in> > > > > > > > > James Mitchell > > Software Engineer\Struts Evangelist > > Struts-Atlanta, the "Open Minded Developer Network" > > http://www.open-tools.org/struts-atlanta > > > > > > > > > > -- > > 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]>
