[jboss-user] [J2EE Design Patterns] - Components based application

Hello. I'm very new to EJB3 and JBoss but going over the materials, it seems like it is a solution to what I'm trying to accomplish. I have a very dynamic situation (who doesn't!) and I want to build the backend of the application in a "componentized" way. So I have Entity objects that can be persisted with Hibernate. I would like to use container managed persistence (not required but seems like it would be good to use that). I have various components: - Contacts and addresses maintenance - Invoicing - Inventory - etc Each component may need to use services from the other. Like invoicing needs data from inventory and contacts/addresses. But I want to be able to build/deploy each component on its own (assuming it does not need a more recent API from a component that hasn't been deployed). E.g.: I want to be able to add new features to the Invoicing component without having to deploy anything new from Contacts. Is EJB3 and JBoss the solution or part of the solution? I was looking at that and I thought that I would make a project for each and deploy each as their own EAR but then I'm not sure how to get data from Contact from the Invoicing code. Anybody could give me some pointers? Etienne View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188634#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...