Exposing deployments services through the xml deployment descriptor of the
jar/sar/war/ear
------------------------------------------------------------------------------------------
Key: AS7-1769
URL:
https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: EJB, JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Assignee: Carlo de Wolf
Following scenario:
Web application which is assembled by 4 different jars/wars:
(1)myapp-model.jar -> contains the model + persistence.xml containing the definition of
a CMT.
(2)myapp-buisness.jar -> contains buisness EJB3's Spring Beans, whatever you can
think of.
(3)myapp-messaging.jar -> Contains MDB's for sending messages to several queues.
(4)myapp-console.war -> Contains the web interface of the app.
Now the -> define a dependency from a project to another to function,i.e. A->B means
that A project has a dependency in B. Now the graph of dependencies between projects are:
(4)->(2)->(1).
Currently in jboss as 7 you are able to deploy your application either as module exposing
several services(even though there is no clear documentation on how you do that.You follow
the old way, you have to do something else?Nowhere in any documentation isn't that
documented.) or you can use the deployments folder and copy everything there.Given the
previous scenario if we deploy the module(2) then even if we have as dependency in the
jboss-deployment-structure.xml the reference to the module(1) then we will get an
exception saying that the persistence unit defined isn't accessible or undefined for
the module(2). Now with the new version of jboss that allow us to manipulate the
dependencies using the module mechanism and the well defined deployment and dependencies
between projects it would be really useful if.
When we define a dependency from one module to another, in my example from (2)->(1),
also the mcs services defined are also exported in the target deployment, thus allowing
access to the pu with the name for example is deployed. I don't know if this can be
applied for the module architecture also.
regards
Nick
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira