[
https://jira.jboss.org/jira/browse/SOAG-98?page=com.atlassian.jira.plugin...
]
Jeff DeLong commented on SOAG-98:
---------------------------------
Jeff,
I deployed the cdl archives by changing the JBossMQ queue/topics to JBossMessaging
queues/topics, and copying the deployment archives to
jboss-soa-p.4.3.0/jboss-as/server/default/deploy. I had also copied by
PolicyQuoteEntity.jar to the deploy directory. When I started the server, I got the
exceptions. If I removed overlord-cdl-runtime.esb, the exceptions went away.
Jeff
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
Attachments: PolicyQuoteEntity.jar
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