I think there is a better way, we just call the ejb from the action servlet
and fill in the appropriate data. The best architect for entity beans is to
have session beans in front of them anyway, so any methods you need you put
in a session bean, and call with the appropriate fields.
-----Original Message-----
From: Assenza, Chris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 1:27 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Struts Questions
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?) :)
Chris
-----Original Message-----
From: George, Carl [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 1:14 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Struts Questions
Yes, I've done this. Difficult is a relative term. If you know ejb and you
know struts, no it's not difficult.
-----Original Message-----
From: Matt Raible [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 11:42 AM
To: [EMAIL PROTECTED]
Subject: Struts Questions
Has anyone implemented Struts with EJBs for business logic. If so, was it
difficult? Also, does anyone know of any performance statistics for Struts?
Thanks,
Matt
