[
https://jira.jboss.org/jira/browse/JBESB-2427?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2427:
-------------------------------------
Just realised that we have another issue with integrating jUDDI v3 into the ESB.
We now need to scope the jUDDI deployment as it uses JPA (configured through
META-INF/persistence.xml) and this cannot exist within a global scope. If it does then it
will cause problems for any other deployment using JPA.
A previous example of this issue was JBESB-2572, caused by the initial integration of
drools jars within the global scope. The solution in that instance was to remove the
drools jars which used JPA (we never needed them) but we obviously cannot do the same with
jUDDI.
I'll work on this today.
UDDIv3 support
--------------
Key: JBESB-2427
URL:
https://jira.jboss.org/jira/browse/JBESB-2427
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Registry and Repository
Reporter: Mark Little
Assignee: Tom Cunningham
Priority: Critical
Fix For: 4.7
We'd like this for SOA-P 5.0, so this may not be in ESB 4.6 but a later 4.x release.
--
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