[JBoss JIRA] Created: (JBESB-3437) EBWS endpoints missing in jUDDI when there are no listener definitions in jboss-esb.xml.
5:50 a.m.
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.8, 4.7 CP2, 4.7 CP1
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBESB-3437:
-------------------------------------
I thought we already had an issue which covered this, will try to dig it out.
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBESB-3437:
-------------------------------------
This applies to any contract at the moment, as the contract application incorrectly relies
on the registry entries to determine whether the local endpoint exists.
This is also likely to be the reason why non-EPRs were put into the registry, to
workaround this defect.
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBESB-3437:
-------------------------------------
BTW The title of this issue is incorrect, as InVM EPRs will never exist in jUDDI.
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 a.m.
New subject: [JBoss JIRA] Commented: (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 commented on JBESB-3437:
-------------------------------------
Just tested this and the WSDL is available through the contract application, I modified
publish-as-webservice to remove the JMS listener and use an InVM scope.
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
5:52 a.m.
New subject: [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
5112
days inactive
5228
days old
5 comments
2 participants
participants (2)
-
Kevin Conner (JIRA) -
Marek Baluch (JIRA)