[
https://jira.jboss.org/jira/browse/SOAG-98?page=com.atlassian.jira.plugin...
]
Jeff Yu commented on SOAG-98:
-----------------------------
Hi Jeff Delong,
Are you using the SOA-P 4.3 embedded version or standalone one? Not sure how you install
the SOA-G M1 libraries, using ant deploy in the $CDL/install folder, which means both
install the cdl-runtime and validator module. But if you deploy these two module, you
would get error like 'No ClassLoaders found for org.jboss.mq.server.jmx.Topic;',
as I just found that both the embedded one and standalone one are using the JBoss Messaing
instead of JBoss MQ as JMS provider.
I agreed that I should remove the jpa/hibernate related jars from the
overlord-cdl-runtime.esb, which I will fix it soon. Another thing is that I'd think
that I won't expect other artifacts, unless depends on the cdl-runtime.esb, will
access to the hibernate libraries in the overlord-cdl-runtime.esb.
Can you provide a bit detail on ur test case or even better, just attach the artifact that
you've used to help me to produce this error.
Thanks
Jeff Yu
jpa hibernate classloader issues wtih overlord-cdl-runtime.esb
--------------------------------------------------------------
Key: SOAG-98
URL:
https://jira.jboss.org/jira/browse/SOAG-98
Project: SOA Governance
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: WS-CDL
Affects Versions: 1.0 MR1
Environment: SOA-P 4.3 with SOA-G CDL M1sars and esb archives added
Reporter: Jeff DeLong
Assignee: Jeff Yu
There are classloader issues if you deploy a JPA component (packaged as a jar) into the
same server (in my testing a SOA-P 4.3 server) with SOA-G CDL components added. I believe
this is because of conflicts between the hibernate / jpa jars already available on the
classpath and those added by overlord-cdl-runtime.esb. I saw MethodNotFoundExceptions in
my esb service that accessed my JPA component that are not present if
overlord-cdl-runtime.esb is not present in the deploy directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira