Package EJB & DAO classes

[PN Kumar]

The concept of a DAO(Data Access Object) as i understand is to decouple the business logic and data access mechanism, so that any change to the data access mechanism can be done independent of the business logic changes. Doesnt this mean that the DAO class and the ejb classes should be a part of two different jar files each of which can be independently deployed?

[Slava Imeshev]

Generally it does not unless you ship jar with DAO seprately from EJBs.

[PN Kumar]

My question here is - doesnt the packaging of DAO classes and the ejb jars together defeat the very purpose of DAO classes ?

[kundan varma]

No it will not defeat the purpose of DAO. WE make DAO for the ease of maintainability and extensibility.Packaging both together will still make them two different class.And it also depend on your project architecture.I dont think you will be using same Database for two different project.
Ultimately its your architecture decision.But it will not defeat the purpose of DAO
Regards,
kundan

[Natarajan Shankar]

Hello,
DAO should be seperate from EJB package as logically speaking. Since normally while pakaging all EJB are put in one jar for applciation server to load all EJB's while starting the application server. But DAO classes whould be under ../WEB-INF/classes, so for this reason we should seperate DAO/ EJB classes jar file.

Still for the question, it is not defating the purpose of DAO but as per standard it is not advisable.