[overlord-issues] [JBoss JIRA] Resolved: (SOAG-98) jpa hibernate classloader issues wtih overlord-cdl-runtime.esb
Jeff Yu (JIRA)
jira-events at lists.jboss.org
Sun Mar 29 12:56:22 EDT 2009
[ https://jira.jboss.org/jira/browse/SOAG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Yu resolved SOAG-98.
-------------------------
Fix Version/s: 1.0 MR2
Resolution: Done
I resolved it as removing all uneccesary libraries from the overlord-cdl-runtime.esb artifact. It only contain the overlord-cdl-runtime.jar & mvel.jar, as these two were not included in the JBossESB server.
> 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
> Fix For: 1.0 MR2
>
> 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
More information about the overlord-issues
mailing list