| Summary: | juddiv3.war doesn't get deployed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | jUDDI - within SOA | Assignee: | trev <tkirby> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 5.0.0 ER6 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.0.0 GA, 5.0.0 ER7 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-1775 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-01-28 10:24:34 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
Jiri Locker
2010-01-06 15:42:33 UTC
Link: Added: This issue is related to JBESB-2983 Link: Added: This issue is related to SOA-1625 Link: Added: This issue is related to SOA-1632 Link: Added: This issue is related to JBPAPP-3291 Attachment: Added: server.log Link: Removed: This issue is related to SOA-1632 Link: Removed: This issue is related to JBESB-2983 Link: Removed: This issue is related to JBPAPP-3291 There are two issues that need fixing in the integration
- deployment of the war file
- correction of the jbossws-entities file
For the first, change the war jboss-web.xml to the following and then place it in the deploy directory (no longer in the jbossesb-registry.sar directory)
<jboss-web>
<class-loading>
<loader-repository>jboss.esb:loader=jbossesb-registry.sar</loader-repository>
</class-loading>
<context-root>/juddiv3</context-root>
<depends>jboss.esb:service=JuddiRMI</depends>
</jboss-web>
For the second, edit the jbossws-entities.properties file and remove the trailing space from the xmldsig entry.
With both of these done, the services are once again deployed and can be seen through the http://localhost:8080/jbossws/services console.
This should have been picked up as part of the evaluation of SOA-1625 but was missed.
Link: Added: This issue depends JBESB-3101 Trev, assigning to you as there are a couple of integration tasks - war should now be placed in deploy directory (explicit scoping information is now included in the war) - need to remove the space from the property file. Kev Sorry, correct issue should have been SOA-1632 and not SOA-1625. Link: Removed: This issue is related to SOA-1625 Link: Added: This issue is related to SOA-1632 build fixes checked in r4685 esb war fix will be in next merge, leaving open until merge happens Related affect of this JIRA is that these URLs are broken in the console: http://localhost:8080/juddiv3/services/subscription?wsdl http://localhost:8080/juddiv3/services/custody-transfer?wsdl http://localhost:8080/juddiv3/services/inquiry?wsdl http://localhost:8080/juddiv3/services/publish?wsdl http://localhost:8080/juddiv3/services/publisher?wsdl http://localhost:8080/juddiv3/services/security?wsdl http://localhost:8080/juddiv3/services/subscription?wsdl http://localhost:8080/juddiv3/services/subscription-listener?wsdl Verified in ER7. |