[JBoss JIRA] Created: (AS7-1769) Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear
3:44 p.m.
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
8:52 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1769) Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-1769:
------------------------------
Assignee: (was: Carlo de Wolf)
Component/s: (was: EJB)
Affects: (was: [Documentation (Ref Guide, User Guide, etc.), Interactive
Demo/Tutorial, Compatibility/Configuration, Release Notes])
Forum Reference: http://community.jboss.org/message/625854#625854 (was:
http://community.jboss.org/message/625854#625854)
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: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
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
1:13 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas updated AS7-1769:
------------------------------
Summary: PU Injection across JARs (separate DeploymentUnits) (was: Exposing
deployments services through the xml deployment descriptor of the jar/sar/war/ear)
Description:
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it was
used to load perfectly in all previous versions...i know about the new loading way so i
am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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
was:
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
Forum Reference: http://community.jboss.org/message/625854#625854 (was:
http://community.jboss.org/message/625854#625854)
I updated as Scott requested.
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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
2:20 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas updated AS7-1769:
------------------------------
Forum Reference: http://community.jboss.org/message/625854#625854 (was:
http://community.jboss.org/message/625854#625854)
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:22 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
Scott i am adding your comment...
I think that there are two parts to this. Taking care of the classloader dependencies
(whether by MANIFEST.MF Class-Path entries or using jboss-deployment-structure.xml). The
other part requires some small code changes (I think).
I think we should try a small change to
PersistenceUnitSearch.resolvePersistenceUnitSupplier(). Or more specifically, to private
method PersistenceUnitSearch.PersistenceUnitMetadata getPersistenceUnit(DeploymentUnit
current, final String absolutePath, String puName).
The code change will be something like:
PersistenceUnitSearch.java ....
// add persistenceUnitName to method signature (local var in
resolvePersistenceUnitSupplier method)
private static PersistenceUnitMetadata getPersistenceUnit(DeploymentUnit current,
final String absolutePath, String puName, String persistenceUnitName) {
for (ResourceRoot resourceRoot : resourceRoots) // search in current deployment
...
}
// end of for for (ResourceRoot resourceRoot : resourceRoots) loop
// see if we can reference another deployement for the persistence unit definition
// get the MSC service registry so we can attempt lookup of the pu service
ServiceRegistry serviceRegistry = current.getServiceRegistry();
String puServiceName = persistenceUnitName;
ServiceName targetPuServiceName = JPAServiceNames.getPUServiceName(puServiceName);
// lookup the pu service
ServiceController serviceController =
serviceRegistry.getService(targetPuServiceName);
Service<PersistenceUnitServiceImpl> service =
(Service<PersistenceUnitServiceImpl>) serviceController.getService();
if (service != null) {
return service.getPersistenceUnitMetadata();
}
// give up, throw not found error...
throw MESSAGES.deploymentUnitNotFound(absolutePath, puName, current)
// file PersistenceUnitServiceImpl.java
// add getter for pu instance variable
public PersistenceUnitMetadata getPersistenceUnitMetadata() {
return pu;
}
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
Scott i have spend yesterday in following the code of loading the pu.I think for me the
solution isn't adding the puName at the end , cause you already have it.But instead of
handling the substring(0,i) as
a dummy filepath rather check if that's reflect also a dependency in the
jboss-deployment-structure.xml
of the deployment.If that's hold true then retrieve that deployment and inject the pu
in the current deployment that depends.That part of the code i have identified that needs
to be added in the class we discuss PersistenceUnitSearch.java in the line where we
iterate over the resources.If the resources fail.Then as a final solution we should check
it the path..even for example a puname defined as "1/mcube-model.jar#puName" can
later on be resolved which means that if the path matches a dependency
in the deployment-structure.xml then that dep needs to be looked up there and
injected?Waiting for
your valuable input.
kind regards
Nikos
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:59 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
Hi Scott,
I have the impression also that the JPAService class needs to be altered a bit for
searching the pu to be looked up there.
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1769:
-----------------------------------
One additional change that we need to worry about, where will the entity classes live?
I think that they probably should be in the application that has the persistence unit
definition (persistence.xml). In which case, we are talking about sharing classes across
deployments also (not just the PU definition).
I think we can expect the applications to handle the class sharing on their own (as
mentioned in the description of this jira).
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1769:
-----------------------------------
Another iteration of what sounds to be the same use case is
[here|https://community.jboss.org/message/743521#743521].
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Bruno Borges commented on AS7-1769:
-----------------------------------
Yes Scott, I think it's the same problem as [I posted in the
forum|https://issues.jboss.org/browse/AS7-1769].
And in my opinion, I think that the classes should reside together with the
persistence.xml as well, and let applications request for a dependency through either
MANIFEST.MF or jboss-deployment-structure.xml.
Would be nice to have a fix for this as soon as possible.
In any case, the WORKAROUND is to put all Entity classes (only) in a JAR and set that as a
resource of "org.hibernate" module (if the user is using Hibernate as an
EntityManager provider).
Second, the user must have a JAR with only the persistence.xml and a dependency on the
"org.hibernate" module (jboss-deployment-structure.xml), and deploy this skinny
JAR. If I'm correct, the persistence.xml must set all classes (with <class>) one
by one, because the package Class scanner won't work here.
Then, whenever one wants to have access to this persistence unit, they must declare a
dependency on the "org.hibernate" module as well, and get the
EntityManagerFactory from JNDI as it must to.
My post has more info about this. I'm voting on this issue and watching it from now
on.
Thanks
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Bruno Borges commented on AS7-1769:
-----------------------------------
Oh, and this issue affects 7.1.1-Final too.
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:28 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
The workaround suggested by Bruno works also for me but I don't think is a clear
solution.
Scott, I think the entity classes must leave in a jar with the
persistence.xml/orm.xml(since we would like to have backwards compatibility).The
application that want's to have
access to that pu, must have a declaration in the jboss-deployment-structure.xml or in the
MANIFEST.MF. On the other hand, that raises an issue..that we start having the immitation
of an hierachical classloader, which is also the root of many classloading problems...in
the past.The clear solution would sound as follows.
I deploy my jar and it creates a persistence unit.References to that persistence unit
from other wars/jars/ears will have to declare a deployment.dependency to be injected.Thus
we keep
closer to the module notion.Currently my time is more free but some problems with my
laptop doesn't allow me to work to much.I will go back to that issue.
regards
Nick
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:26 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Bruno Borges commented on AS7-1769:
-----------------------------------
The problem is that, what will happen if I have a module X under my jboss/modules that
needs to access Entity classes? How to manage this kind of dependency?
deployment.mypersistence --
deployment.myapp1 -- depends on: com.mycompany.infra, deployment.mypersistence
delpoyment.myapp2 -- depends on: com.mycompany.infra, deployment.mypersistence
modules/com/mycompany/infra/module.xml has some classes that are shared accross myapp1 and
myapp2, and need to access Entity classes.
This is the scenario that must be fixed, IMO.
In other words, how to have a jboss module dependent on a possible, future deployment
(like deployment.mypersistence)?
I think this is the root of this problem and what must be fixed to have real Global shared
Persistence Units
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 p.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Bruno Borges commented on AS7-1769:
-----------------------------------
The workaround so far, like I said before, but with more details here, is:
1) have a persistence.jar with all mapped classes with @Entity and their dependents, under
modules/org/hibernate/main (and add a resource-root to module.xml)
2) have a persistence-unit.jar with only a META-INF and a persistence.xml with every class
defined here with a <class>
It will work, until Scott or someone else finds a better way :-)
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-1769:
-----------------------------------
I was talking to David Lloyd at JBoss Judcon (Boston) last night about the idea of
introducing a DataAccessObjectShare service that could perhaps scratch this itch (David
suggested that following the current singleton dependency model implementation might be
easiest).
I'm open to what the best approach might be. I think that we need to identify exactly
which components in the DAO need to be annotated to be shared (e.g. mark a persistence
unit as shared the make the persistence unit globally available). As well as some way on
the other application deployments to indicate a direct reference to the globally shared
persistence unit.
Internally, if the deployment with the DataAccessObjectShare service is undeployed, the
other applications that depend on it, will also be undeployed (since the
DataAccessObjectShare service will not be available anymore). The applications should
become available when the DataAccessObjectShare service is redeployed again.
I'll think some more about this and break it into subtasks that could help someone do
the work (whether its me or someone else).
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas updated AS7-1769:
------------------------------
Affects Version/s: 7.1.1.Final
7.1.0.Final
Forum Reference: http://community.jboss.org/message/625854#625854 (was:
http://community.jboss.org/message/625854#625854)
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final, 7.1.0.Final, 7.1.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
Hi both,
I agree with Bruno but on my head the implementation to be done must be able to
distinguish wither a dependency comes from a standard JEE 6 deployed app(.war,.ear)
complying 100% with the JEE 6 Specification, in which case the above problem doesn't
exist or is something coming as a dependency from outside the world of the
application.Then the sharing of classloader issue will rise once again.For me a nice trick
would be if you define it as a module or as a deployment(this is the initial report i did)
to be able in the deployment descriptor of the project that depends from the pu to make it
aware that if it tries to load it from it's own classloader will fail but rather
injection must take place,aka that is comes from the "outside" world of the
application.This would help also the dependency injection not to search extensively
everything and scan dozen of file to inject classes. That was my initial thought. The only
problem when i spend 1-2 days debbuging the classes is that I couldn't found the code
where the parsing of the jboss-deployment.xml takes place.
@Scott count me as a work unit if it's decided to implement a solution on that.
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final, 7.1.0.Final, 7.1.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Bruno Borges commented on AS7-1769:
-----------------------------------
It is important to note that the <package> scanner on orm.xml doesn't work when
the classes are not inside the JAR containing persistence.xml and orm.xml. So maybe this
problem could be solved starting from here?
# About the DAOS idea:
This is how we tell JBoss to set the PU as global:
<!-- Global Persistence Unit at JBoss -->
<property name="jboss.entity.manager.jndi.name"
value="java:/myPersistenceUnit" />
<property name="jboss.entity.manager.factory.jndi.name"
value="java:/myPersistenceUnitFactory" />
Must we do something else to set a PU as global? I don't think so. I rather keep doing
this way. So the problem comes back to ClassLoading and intra-TL-deployment dependency. A
PU module that aims to be shared must not export its META-INF, and a developer should not
add anything to it except XML files related to the persistence unit, to avoid loading
extra PUs. JBoss could be smart about implicit excluded path at the exports though.
I couldn't figure out how this DAOS would be defined in my pu-module.jar, but I think
it shouldn't at all. I already provide enough information to JBoss (properties) that
tells it to share my PU.
Please let me know if I'm out of my mind...
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final, 7.1.0.Final, 7.1.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [JBoss JIRA] (AS7-1769) PU Injection across JARs (separate DeploymentUnits)
[
https://issues.jboss.org/browse/AS7-1769?page=com.atlassian.jira.plugin.s...
]
Nikos Ballas commented on AS7-1769:
-----------------------------------
Hi Bruno,
can you please explain what you mean when you say "developer should not add anything
to it except XML files related to the persistence unit, to avoid loading extra PU". I
will explain my setup and then it will make clear the scope of this JIRA issue
created.Imagine I have standalone deployments.Thus I have a mypu.jar, which contains
orm.xml , persistence.xml and the entity classes.This if you deploy it in jboss as
standalone deployment it creates a pu.Now the debate is what type of entity model we
want.If we want to have an anemic model that we only have the pojos, then DAOS must be
defined in the mybusiness.jar where somehow the pu generated by the previous deployment
will be injected.Imagine now that the mybusiness.jar contains some Facades I will use for
myapp-console.war.Then a new application, myapp-console2.war comes..I want to be able to
deploy it and add a reference to the deployment descriptor and inject the pu.I don't
want to put the pojos again inside that war..because 1)I am repeating code 2)The pu
isn't only the persistence.xml but also the entities, thus the injection must imply
that the myapp.jar that has a dependency to that pu, the entity classes must also be
injected to that jar when is deployed.I used to put the DAOS in the business side,but
frankly nowadays i don't understand the existance of a DAO class without a model
behind it.But still some people like to put logic in the DAO classes
that's why Scott i think the DAOS will exist not in the .jar containing the definition
of the pu(for me a definition contains the classes + the persistence.xml file _+
orm.xml).
PU Injection across JARs (separate DeploymentUnits)
---------------------------------------------------
Key: AS7-1769
URL: https://issues.jboss.org/browse/AS7-1769
Project: Application Server 7
Issue Type: Feature Request
Components: JPA / Hibernate
Affects Versions: 7.0.1.Final, 7.1.0.Final, 7.1.1.Final
Environment: Linux, Window, MacOS, *BSD
Reporter: Nikos Ballas
Labels: new_and_noteworthy
the following architecture of jars/wars doesn't load correctly in JBossAS 7 but it
was used to load perfectly in all previous versions...i know about the new loading way so
i am explaining the scenario:
myjar-model.jar : Contains entities and the persistence.xml which defines also a
persistence unit inside the META-INF folder.
myjar-buisness.jar: Contains EJB's and Spring beans that uses the model.There is
an annotation with @PersistenceContext(name="mypu") on this EJB's for the
entity manager to work. The jboss-deployment-structure.xml has declared dependency in the
deployment.mcube-model.jar.
I am copying both of these files first the model and then the buisness in the standalone
profile in deployments folder.The first one is loaded successfully.The second one that
also uses classes from the previous one can see the classes but not the pu need it for the
db operations.The exception follows:
[code]
10:33:49,369 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed
to start service jboss.deployment.unit."myjar-buisness.jar".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mcube-buisness.jar".INSTALL: Failed to process phase
INSTALL of deployment "myjar-buisness.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at
org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Component
class ***.**.GenericDAOImpl for component MyBean has errors:
Can't find a deployment unit named myjar-persistence at deployment
"myjar-buisness.jar"
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:133)
at
org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:52)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:129)
at
org.jboss.as.ee.component.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:122)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
[/code]
Following scenario/arcs:
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5086
days inactive
5375
days old
18 comments
5 participants
participants (5)
-
Bruno Borges (JIRA) -
Nikos Ballas (Commented) (JIRA)
-
Nikos Ballas (JIRA)
-
Nikos Ballas (Updated) (JIRA)
-
Scott Marlow (JIRA)