11:03 p.m.
Sato Tadayoshi created JBESB-3789:
-------------------------------------
Summary: SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3789:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=815183
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3789:
-------------------------------------------
Bugzilla Update: Perform
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan reassigned JBESB-3789:
-----------------------------------
Assignee: Magesh Bojan
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan commented on JBESB-3789:
-------------------------------------
Tadayoshi,
Thanks for reporting this issue. The fix however is not the way as suggested by you.
Please mention only the issue and not any suggestion for fix as this could confuse the
issue at hand.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:57 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
SBS JIRA Integration updated JBESB-3789:
----------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=815183 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=815183)
Forum Reference: https://community.jboss.org/message/349805#349805
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan edited comment on JBESB-3789 at 4/24/12 8:32 AM:
--------------------------------------------------------------
Tadayoshi,
Thanks for reporting this issue. The fix however may not be the way as suggested by you.
Please mention only the issue and not any suggestion for fix as this could confuse the
issue at hand.
was (Author: mageshbk):
Tadayoshi,
Thanks for reporting this issue. The fix however is not the way as suggested by you.
Please mention only the issue and not any suggestion for fix as this could confuse the
issue at hand.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
midnight
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan closed JBESB-3789.
-------------------------------
Fix Version/s: 4.11 CP1
Resolution: Done
At revision: 38059
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan reopened JBESB-3789:
---------------------------------
Reopening to add this fix to 4.10.CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan updated JBESB-3789:
--------------------------------
Fix Version/s: 4.10 CP2
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=815183 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=815183)
Forum Reference: https://community.jboss.org/message/349805#349805 (was:
https://community.jboss.org/message/349805#349805)
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3789:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=815183 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=815183)
Forum Reference: https://community.jboss.org/message/349805#349805 (was:
https://community.jboss.org/message/349805#349805)
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3789:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=815183,
https://bugzilla.redhat.com/show_bug.cgi?id=817747 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=815183)
Forum Reference: https://community.jboss.org/message/349805#349805 (was:
https://community.jboss.org/message/349805#349805)
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan closed JBESB-3789.
-------------------------------
Resolution: Done
At revision: 38069 on 4_10_CP branch.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:57 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Sato Tadayoshi reopened JBESB-3789:
-----------------------------------
Reopened because the fix is incomplete.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Sato Tadayoshi commented on JBESB-3789:
---------------------------------------
Thanks Magesh for quick fixing. But unfortunatelly I tested the fix and found it's not
complete.
Explaining based on the reproducing step above, the WSDL contract actually becomes to be
published by the fix but the WSDL /definitions/service/port/soap:address/@location (XPath
notation for convenience) points to the original Web service
(http://127.0.0.1:8080/Quickstart_webservice_producer_esb/GoodbyeWorldWS). What is
expected here should be the http-gateway endpoint on ESB
(http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCatego...)
because otherwise a client ends up calling the original Web service directly.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> updated the status of jira JBESB-3789 to Reopened
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
At revision: 38069 on 4_10_CP branch.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
Reopening to add this fix to 4.10.CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Sato Tadayoshi <tasato(a)redhat.com> made a comment on jira JBESB-3789
Reopened because the fix is incomplete.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Sato Tadayoshi <tasato(a)redhat.com> updated the status of jira JBESB-3789 to
Reopened
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> updated the status of jira JBESB-3789 to Closed
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Sato Tadayoshi <tasato(a)redhat.com> made a comment on jira JBESB-3789
Thanks Magesh for quick fixing. But unfortunatelly I tested the fix and found it's not
complete.
Explaining based on the reproducing step above, the WSDL contract actually becomes to be
published by the fix but the WSDL /definitions/service/port/soap:address/@location (XPath
notation for convenience) points to the original Web service
(http://127.0.0.1:8080/Quickstart_webservice_producer_esb/GoodbyeWorldWS). What is
expected here should be the http-gateway endpoint on ESB
(http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCatego...)
because otherwise a client ends up calling the original Web service directly.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:12 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan commented on JBESB-3789:
-------------------------------------
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_10_CP branch
At revision: 38082 on 4_11_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:16 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan edited comment on JBESB-3789 at 5/9/12 9:15 AM:
-------------------------------------------------------------
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_11_CP branch
At revision: 38082 on 4_10_CP branch
was (Author: mageshbk):
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_10_CP branch
At revision: 38082 on 4_11_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_10_CP branch
At revision: 38082 on 4_11_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_11_CP branch
At revision: 38082 on 4_10_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
tcunning(a)redhat.com changed the Status of [bug
815183|https://bugzilla.redhat.com/show_bug.cgi?id=815183] from NEW to MODIFIED
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Sato Tadayoshi <tasato(a)redhat.com> made a comment on jira JBESB-3789
Thanks Magesh for quick fixing. But unfortunatelly I tested the fix and found it's not
complete.
Explaining based on the reproducing step above, the WSDL contract actually becomes to be
published by the fix but the WSDL /definitions/service/port/soap:address/@location (XPath
notation for convenience) points to the original Web service
(http://127.0.0.1:8080/Quickstart_webservice_producer_esb/GoodbyeWorldWS). What is
expected here should be the http-gateway endpoint on ESB
(http://127.0.0.1:8080/Quickstart_webservice_producer/http/MyServiceCatego...)
because otherwise a client ends up calling the original Web service directly.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_10_CP branch
At revision: 38082 on 4_11_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Magesh Bojan <mageshbk(a)jboss.com> made a comment on jira JBESB-3789
Terribly sorry! Fixed it, let me know any issues before closing it.
At revision: 38081 on 4_11_CP branch
At revision: 38082 on 4_10_CP branch
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Sato Tadayoshi <tasato(a)redhat.com> updated the status of jira JBESB-3789 to
Reopened
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Sato Tadayoshi <tasato(a)redhat.com> made a comment on jira JBESB-3789
Reopened because the fix is incomplete.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
(md5sum for unsigned jar)
9a1e2534bb8df393b63bcd07f3fb73bb jbossesb-soap.jar
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:31 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -15,7 +15,8 @@
This means that for enpoints exposed via http-provider do not have a WSDL published in
the 'contract' application, which lists the esb deployments, and their contracts.
ie localhost:8080/contract
MANUAL INSTALL INSTRUCTIONS:
- TODO
+ To install this patch replace the following with the jar included in this patch:
+ $SOAP_HOME/jboss-as/server/<profile>/deploy/soap.esb/jbossesb-soap.jar
COMPATIBILITY:
TODO
DEPENDENCIES:
@@ -25,6 +26,6 @@
SUPERSEDED BY:
TODO
CREATOR:
- Jason Shepherd
+ Jason Shepherd, Tadayoshi Sato
DATE:
- May 1st, 2012+ May 10th, 2012
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:07 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3789:
------------------------------------------------
Toshiya Kobayashi <tkobayas(a)redhat.com> made a private comment on [bug
817747|https://bugzilla.redhat.com/show_bug.cgi?id=817747]
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Sato Tadayoshi commented on JBESB-3789:
---------------------------------------
Magesh, thanks for the prompt correction! It works fine, and you can close it.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan closed JBESB-3789.
-------------------------------
Resolution: Done
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:56 p.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Jason Shepherd reopened JBESB-3789:
-----------------------------------
From a sample, wrapped endpoint URL:
http://myTestServer/myapp-esb/http/myapp?wsdl
I get a WSDL back;
<wsdl:import location="http://esb.mycompany.cub/schemas/Errors.wsdl"
namespace="http://css.mycompany.com/ws/errors/v1/">
</wsdl:import>
<wsdl:types>
<xsd:schema xmlns:err="http://css.mycompany.com/ws/errors/v1/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://css.mycompany.com/ws/sc/myapp/v1/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd"
/>
</xsd:schema>
</wsdl:types>
where the original is
<!-- Base Service Messages -->
<wsdl:import namespace="http://css.mycompany.com/ws/errors/v1/"
location="http://esb.mycompany.cub/schemas/Errors.wsdl" />
<!-- Data types definition -->
<wsdl:types>
<xsd:schema>
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="myapp.xsd" />
</xsd:schema>
</wsdl:types>
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
midnight
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Jason Shepherd edited comment on JBESB-3789 at 5/15/12 12:58 AM:
-----------------------------------------------------------------
From a sample, wrapped endpoint URL:
http://myTestServer/myapp-esb/http/myapp?wsdl
I get a WSDL back with a reference to a schema on the wrapped web service. The schema
should be hosted relative to the WSDL, on the ESB instance.
<wsdl:import location="http://esb.mycompany.cub/schemas/Errors.wsdl"
namespace="http://css.mycompany.com/ws/errors/v1/">
</wsdl:import>
<wsdl:types>
<xsd:schema xmlns:err="http://css.mycompany.com/ws/errors/v1/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://css.mycompany.com/ws/sc/myapp/v1/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd"
/>
</xsd:schema>
</wsdl:types>
where the original is
<!-- Base Service Messages -->
<wsdl:import namespace="http://css.mycompany.com/ws/errors/v1/"
location="http://esb.mycompany.cub/schemas/Errors.wsdl" />
<!-- Data types definition -->
<wsdl:types>
<xsd:schema>
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="myapp.xsd" />
</xsd:schema>
</wsdl:types>
was (Author: jshepher):
From a sample, wrapped endpoint URL:
http://myTestServer/myapp-esb/http/myapp?wsdl
I get a WSDL back;
<wsdl:import location="http://esb.mycompany.cub/schemas/Errors.wsdl"
namespace="http://css.mycompany.com/ws/errors/v1/">
</wsdl:import>
<wsdl:types>
<xsd:schema xmlns:err="http://css.mycompany.com/ws/errors/v1/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://css.mycompany.com/ws/sc/myapp/v1/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp.xsd"
/>
</xsd:schema>
</wsdl:types>
where the original is
<!-- Base Service Messages -->
<wsdl:import namespace="http://css.mycompany.com/ws/errors/v1/"
location="http://esb.mycompany.cub/schemas/Errors.wsdl" />
<!-- Data types definition -->
<wsdl:types>
<xsd:schema>
<xsd:import namespace="http://css.mycompany.com/ws/sc/myapp/v1/"
schemaLocation="myapp.xsd" />
</xsd:schema>
</wsdl:types>
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:41 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan commented on JBESB-3789:
-------------------------------------
Jason,
The SOAPProcessor is an action that exposes only Webservice endpoints that are internally
hosted in the same container via JBossWS. This JIRA was created to mimic the behavior of
JBR gateway in the new HTTP gateway. That has been done along with the endpoint address
rewrite. Please do not overwhelm the issue here.
Just rewriting schema urls alone will not work, as such the resources like
http://myTestServer/myapp-esb-myapp-esb-ws-0.7.0-SNAPSHOT/myapp?xsd=myapp... do not exist
in the server. The schema or WSDL imports will always point to the original
Webservice's location only as done by JBR gateway. This needs to be handled in a
separate JIRA. This encloses rewriting all JBR, HTTP gateway schema import urls and
caching the schemas. Whether this feature will be acceptable or not we need to validate
that separately. Users can inline their schema for the time being.
Tadayoshi,
The SOAP1.2 support is not there in SOAPProcessor/SOAPProxy as of now. The linked issue
only states one small portion of re-writing that is not happening. That is definitely not
related to this schema re-writing issue at all although they may touch the same files.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 a.m.
[
https://issues.jboss.org/browse/JBESB-3789?page=com.atlassian.jira.plugin...
]
Magesh Bojan closed JBESB-3789.
-------------------------------
Resolution: Done
Additional issue raised by Jason is handled here JBESB-3802.
SOAPProcessor doesn't publish WSDL when used with HTTP Gateway
--------------------------------------------------------------
Key: JBESB-3789
URL: https://issues.jboss.org/browse/JBESB-3789
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.11
Reporter: Sato Tadayoshi
Assignee: Magesh Bojan
Fix For: 4.10 CP2, 4.11 CP1
SOAPProcessor can publish WSDL when it is used with JBR Gateway as demonstrated in
webservice_producer. But if it is used with HTTP Gateway, it cannot publish WSDL. (For
comparison, SOAPProxy publishes WSDL with both JBR and HTTP gateways.)
The reason is clear that whereas SOAPProxy's annotated publisher
(SOAPProxyWsdlContractPublisher) implements ContractProvider interface as well as
ActionContractPublisher, SOAPProcessor's annotated publisher
(JBossWSWebserviceContractPublisher) implements only ActionContractPublisher. And HTTP
Gateway works only with ContractProvider when publishing a WSDL contract.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4409
days inactive
4438
days old
40 comments
5 participants
participants (5)
-
Jason Shepherd (JIRA) -
Magesh Bojan (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Sato Tadayoshi (JIRA)
-
SBS JIRA Integration (JIRA)