> From: Richard Sayre <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <user@struts.apache.org>
> Date: Tue, 26 Feb 2008 14:08:18 -0330
> To: Struts Users Mailing List <user@struts.apache.org>
> Subject: Re: Struts 2 and SOA
>
> Could you elaborate a bit. Would the POJO contain the Business logic
> for calling My DAO and other classes? Would the POJO replace the
> action functionality? Then my action would use a POJO to do all of
> the work? So any logic in MyAction.save() would go into POJO.save()
> which would then be called form my action? That way My POJO could be
> accessed from my struts application and any other clients that need it
> functionality? I dont see any need for .NET interoperability in the
> future, but it would hurt to have that option. The main reason for
> this is we are designing a new J2EE Application seprate from our
> current system. In the future we want to beable to access certian
> functionality of each of these systems. So System A will be asking
> System B for info and doing some work based on that info.
What you are describing here is essentially the standard MVC pattern. The
business object doesn't have to be a POJO. In general there should be no
business logic in your action, it should be in some external class such as a
POJO, EJB or web service of some sort.
Randy
This email and any attachments ("Message") may contain legally privileged
and/or confidential information. If you are not the addressee, or if this
Message has been addressed to you in error, you are not authorized to read,
copy, or distribute it, and we ask that you please delete it (including all
copies) and notify the sender by return email. Delivery of this Message to any
person other than the intended recipient(s) shall not be deemed a waiver of
confidentiality and/or a privilege.
