I tend to use bulk setters on the helper classes to transfer everything
from the ActionForm at once, e.g.
public void setString(
String property0, String property1, String property2, String
property3
) throws SQLException {
values.updateString("property0",property0);
values.updateString("property1",property1);
values.updateString("property2",property2);
values.updateString("property3",property3);
}
The helper class can then expose the properties to the EJB, or other
data access object, in their native type.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
"Assenza, Chris" wrote:
>
> We are doing so right now - all we had to do was create an additional class
> that has all the getters/setters of the ActionForm for a particular screen
> or set of screens. Then call all the sets from the Action and pass the
> object along to the EJB. That's it. :) No tangible performance loss/gain.
>
> (BTW, any better ways of doing this for future reference?) :)
>
