Jim: <egg-on-face>Yes that worked. I actually read ".. which will all have been called before the init() method is invoked." as "which will have to be called before the init() method is invoked." and got stumped.. </egg-on-face>
Thank you so much! Geeta P.S> I can see now why writing to the list before googling is so tempting..! > From > http://struts.apache.org/api/org/apache/struts/action/PlugIn.html > I read: > Configuration can be accomplished by providing standard > JavaBeans property setter methods, which will all have been > called before the init() method is invoked. > > I can assume that something like this would work: > > public class SomeLogicalClassName implements Plugin { > private String aWellNamedPropertyFieldYouWantToSet; > public void get... > public void set... > } > > and in your config: > <plug-in className="package.path.to.SomeLogicalClassName"> > <set-property > property="aWellNamedPropertyFieldYouWantToSet" value="A > configuration value" /> > </plug-in> > > and voila! your plugin is configured. Maybe... I could be > talking out of my hat here. But that seems logical. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
