| Summary: | jUDDI v3 services not available (inc. login to jUDDI console) in ER4 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Monitoring and Management | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.0.0 ER4 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.0.0 GA, 5.0.0 ER5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1625 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
ER4 build
|
|
| Last Closed: | 2009-12-11 18:11:51 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: | |
|
Description
Len DiMaggio
2009-11-21 04:18:57 UTC
Why is the console using non-existent WS endpoints? Why is it not using the local transport??? this has been fixed, a build patch works round this issue , the patch should be removed when the next esb merge is taken by the build So - in ER5 - these endpoints will be supported?
<!-- JAX-WS Transport
<proxyTransport>org.apache.juddi.v3.client.transport.JAXWSTransport</proxyTransport>
<custodyTransferUrl>http://${serverName}:${serverPort}/juddiv3/services/custody-transfer?
wsdl</custodyTransferUrl>
<inquiryUrl>http://${serverName}:${serverPort}/juddiv3/services/inquiry?wsdl</inquiryUrl>
<publishUrl>http://${serverName}:${serverPort}/juddiv3/services/publish?wsdl</publishUrl>
<securityUrl>http://${serverName}:${serverPort}/juddiv3/services/security?wsdl</
securityUrl>
<subscriptionUrl>http://${serverName}:${serverPort}/juddiv3/services/subscription?wsdl</
subscriptionUrl>
<subscriptionListenerUrl>http://${serverName}:${serverPort}/juddiv3/services/subscription-
listener?wsdl</subscriptionListenerUrl>
<juddiApiUrl>http://${serverName}:${serverPort}/juddiv3/services/juddi-api?wsdl</
juddiApiUrl>
-->
The webservices are a separate issue but have been done as part of JBESB-2983. We have our own implementation, because of a juddi deployment issue, and will provide all the services within the WSDL. /services/custody-transfer /services/inquiry /services/publish /services/replication /services/security /services/subscription /services/subscription-listener /services/valuesetcaching /services/valuesetvalidation The webservices are untested by us, however, as we do not make use of them. Link: Added: This issue related SOA-1632 Link: Added: This issue related SOA-1657 Verified in ER5 Link: Added: This issue related SOA-1775 Link: Removed: This issue related SOA-1775 |