Packaging struts business logic and action classes

[Vinay <vi...@mdp.net>]

Can somebody please clarify or explain the following 

1. Business Objects (BO's)
2. Data Access Objects (DAO's)
3. Value Objects (VO's)
4. Data transfer objects (DTO's)

All of the  above I know is part of the Model(M) in MVC architecture.I think that Value Objects and DTO's are the same , and they have setters and getters.Correct me if I am wrong.

What is the general way of packaging a struts application?
like if my companyname is www.companyname.neti will probably have an application or context as applicationname as its name. 
I would like my business logic to be independent from the struts specific controller(action classes) . 

 I also know the package should start with    net.companyname.applicationname.

Thanks in advance.

Help appreciated.

Re: Packaging struts business logic and action classes

[Nicolas De Loof <ni...@cgey.com>]

I think "Value Object" is the J2EE BluePrint name of "Data transfer objects"
design pattern. This is a way to transfert multiple datas as a simple bundle
(so you doesn't need to make multiple getter calls, especially on remote
obects).

"Data Access Objects" (DAO) is a pattern to encapsulate ressource access
(database). This is used for example to put all SQL code in specialized
classes, so that business logic is not mixed with database access.

"Business Objects" is a name for objetcs (javabeans, EJB ...) that has a
meaning in the business model that the application is using. This can be
datas (EJB entity for example) or process / behaviour (EJB session).


Nico.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>