If it is true that there could occur conflicts, then i guess the following documentation is not valid:
Reading from "Development Roles" http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Overview6.html :
"For example, in the application component development phase, an enterprise bean software developer delivers EJB JAR files. In the application assembly role, another developer combines these EJB JAR files into a J2EE application and saves it in an EAR file. In the application deployment role, a system administrator at the customer site uses the EAR file to install the J2EE application into a J2EE server."
Because there is no way for the "application assembly role" to _freely_ pick EJB JAR files from the "enterprise bean software developer". He will be getting global conflicts if an EJB JAR is assembled inside two EARs and deployed in the same server.
Do you see my point? Reusing EJB modules accross applications is not possible. Or have I misunderstood something obvious?
Cheers,
-Kristoffer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959627#3959627
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959627
About the CMS integration with Portal. I agree with you that those are two separate concerns.
However JBoss Portal as a *product* ships with a CMS.
It is totally possible to remove the CMS and only keep the aggregation capabilities of the portal if you don't need CMS :
1/ delete portal-cms.war
2/ remove cms related stuff : portlets, instances and portlet windows
If you look at jboss-service.xml you can even change how the URL decoding is performed :
1/ remove the PrefixDelegatingCommandMapper
2/ set the PortalObjectCommandMapper as the next of the DefaultPortalCommandMapper service
this way you should have /a/b/c act the same as /portal/a/b/c
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959624#3959624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959624