It depends on what you want to archieve.
It the aim of your software is providing an address service, then it should be enough to have a single AddressbookServiceBean.
But if those entities are just picked out of a lot other beans beeing part of a very complex enterprise application, there might be circumstances that justify creation of a single session facade for each.
Architecture should follow the project target, so there is no silver bullet for all programs.
Regards
Markus
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Montag, 26. Mai 2008 07:05
To: users_at_glassfish.dev.java.net
Subject: Session beans and entity beans - which is best practice?
If these are some of my entity beans:
Contact
Group
Company
Should I have a session bean for each:
ContactServicesBean
GroupServicesBean
CompanyServicesBean
or use one for all:
AddressbookServicesBean
Thanks
//Marius
[Message sent by forum member 'mariusw' (mariusw)]
http://forums.java.net/jive/thread.jspa?messageID=276508
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net