[esb-issues] [JBoss JIRA] Closed: (JBESB-3437) EBWS endpoints missing in jUDDI when there are no listener definitions in jboss-esb.xml.
[
https://jira.jboss.org/browse/JBESB-3437?page=com.atlassian.jira.plugin.s...
]
Kevin Conner closed JBESB-3437.
-------------------------------
Resolution: Rejected
Talked with Marek and we are rejecting this issue, the test was checking within jUDDI but
inVM endpoints are never stored there.
EBWS endpoints missing in jUDDI when there are no listener
definitions in jboss-esb.xml.
----------------------------------------------------------------------------------------
Key: JBESB-3437
URL: https://jira.jboss.org/browse/JBESB-3437
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository, Rosetta, Web Services
Affects Versions: 4.7 CP1, 4.7 CP2, 4.8
Reporter: Marek Baluch
For ESB to publish EBWS services to jUDDI there must a provider and listener defined in
jboss-esb.xml for that service. IMHO this may be valid for non EBWS endpoints but as soon
as a service becomes EBWS then it's WSDL contract should be exposed no matter what.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira