Interesting. We very rarely access the form bean from the JSPs, so I never
thought of doing that. After glancing over your code, I think my code could
be integrated without conflict. I submitted a Bugzilla report and attached
the two files I wrote to support the functionality I'm looking for:
http://issues.apache.org/bugzilla/show_bug.cgi?id=37301
Those are just what I came up with to be used as a kind of add-on to Struts. I
have an idea or two about integrating the code with Struts, but nothing
really solid yet.
> ----Original Message----
> From: [EMAIL PROTECTED]
> Date: Oct 28, 2005 3:08:31 PM
> To: dev@struts.apache.org
> Subj: Re: Interfaces for DynaActionForms
>
> I posted an enhancement recently [1] which does something very similar
> to what you describe here. My goal was to remove the requirement for
> writing ${form.map.property} instead of just ${form.property} in JSPs,
> so my code (which you can see on the Bugzilla ticket) dynamically
> generates the interface as well as its implementation.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
