Dave and Laurie:
So I am complicating things, as usual, by over thinking them. Say I
have an AccountAction. Then it's as simple as having an AccountUtil
class (or several classes depending on need) that will contain most of
the logic that will need to be performed by the Account Action. The
Action simply pulls in the data off the form, maintains the Struts2
Framework and integrity, but passes that data off to my Util class
methods for process and obtaining results, and then passes that
information back to the front via the standard Struts2 means.
I already have my DAO for the actual data layer retrieval via our
webservices and that has worked out great, as per the CRUD demos and
Mailreader.
I could learn to like this.
Thanks,
Skip.
Laurie Harper wrote:
Err, no, the idea is for the POJO facade classes to form a completely
decoupled service layer -- i.e. they should know nothing about Struts,
HTTP, etc. The service layer provides a platform-agnostic API for
invoking business functionality, which your actions (or anything else)
can then call.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
