| Summary: | jUDDI error on boot after installing CXF - javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=juddiv3,endpoint=ReplicationService | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||
| Component: | jUDDI - within SOA, EDS | Assignee: | tcunning | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.2.0dev2 | CC: | kevin.conner, kurt.stam, tcunning | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.2.0 ER1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-3155 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
RHEL6
5.2 DEV2 build - with EDS and CXF installed
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.39.1.9.8.el6_1-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
|
|||||
| Last Closed: | 2011-08-25 18:45:29 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Len DiMaggio
2011-07-07 20:56:15 UTC
Attachment: Added: SOA-3155_server.log This looks like it is an issue in the ESB scripts, probably with a knock-on effect on the platform. TomC should look at this. Prior to the juddi update ESB was responsible for providing a clean deployment of the juddi webservices. We provided endpoints for all the services, including replication, but it looks like the juddi implementation of replication is no longer a webservice (no annotation). Correct, we removed the (optional) endpoint that are not implemented (yet). So I guess the bean.xml or web.xml in soa-p is still referencing it, this should be removed. --Kurt Agreed, which is why I suggested TomC look at it. It is coming from the ESB codebase. What I wasn't sure about was whether the platform team had a version in their scripts, which eneds checking. needs checking even Taking this one to investigate. Link: Added: This issue relates to JBESB-3634 Release Notes Text: Added: Removed ReplicationService from the web.xml. tcunning@localhost:product]$ svn commit Sending product/rosetta/war/resources/WEB-INF/web.xml Transmitting file data . Committed revision 37256. Removed ReplicationService from the web.xml. tcunning@localhost:product]$ svn commit Sending product/rosetta/war/resources/WEB-INF/web.xml Transmitting file data . Committed revision 37256. Release Notes Text: Removed: Removed ReplicationService from the web.xml. tcunning@localhost:product]$ svn commit Sending product/rosetta/war/resources/WEB-INF/web.xml Transmitting file data . Committed revision 37256. Link: Added: This issue relates to SOA-3185 Verified fixed in ER3 build. |