Hide Forgot
Date of First Response: 2010-05-11 11:14:12 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/758543 Steps to Reproduce: Deploy the quickstart samples\quickstarts\publish_as_webservice Navigate to the jUDDI registry view: http://localhost:8180/uddi-console/uddibrowser.jsp Note that the service is not registered. project_key: SOA When a service is created which contains the HTTP gateway, the service is not registered within jUDDI.
Please provide a log file with DEBUG enabled, also a screen shot of what you believe to be the issue with the registry view.
Help Desk Ticket Reference: Removed: https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=758543 Added: https://enterprise.redhat.com/issue-tracker/758543
According to the referenced case you are using InVM transport for your service, these are never stored in the jUDDI registry. The jUDDI registry appears to be working as expected in that it is only supposed to contain EPRs which reference a physical transport. The jUDDI registry, certainly this part, is an internal aspect of the ESB and is not supposed to be consumed externally.
Kevin, please make a comment and reject this, as decided in SOA PM jira triage. Thanks!
Release Notes Text: Added: Earlier SOA-triage decided to close this, see ALT's comment.