Thanks for your reply.
I actually had the get and set methods for my properties (2), but could not get the properties set. Even on Tomcat.
No How. No Way. Until...
I fell back and punted.
- Started with a blank custom ActionMapping class.
- Put in a "private String paramOne" field
and a "public void setParamOne(String paramOne)" method with a S.o.p("...")
- Put a "<set-property property="paramOne" value="Use Me!"/>" element in my struts-config.
- Started up Tomcat.
- IT WORKED! - showed the message on load-up.
- Put in a "public String getParamOne()" method
- Started up Tomcat.
- IT WORKED! - showed the message on load-up.
- Put in a "public boolean isParamOne()" method (it's ultimately a boolean)
- Started up Tomcat.
- IT DID NOT WORK! - no message on load-up, and no property set in the app, either.
So here's my conclusion:
In order to be able to subclass ActionMapping and use <set-property .../> to configure and use custom Mapping properties, one:
MUST
----
extend ActionMapping
implement a "public void set{ParamName}(String param)" method
MAY
----
implement a "public String get{ParamName}()" method
MUST NOT
--------
implement a "public boolean is{ParamName}()" method
- doing so will prohibit the set{ParamName} method's invocation via the <set-property ...>
This is all very odd, I haven't spent that much time with Digester, but think it might be worthwhile digging into it to figure out what's going on.
Thanks again.
Chris G
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
