You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aleksandar Balaban (Created) (JIRA)" <ji...@apache.org> on 2012/01/18 13:57:39 UTC
[jira] [Created] (CXF-4040) WS-Notification's operation
"Unsubscribe" not avaliable via SOAP call
WS-Notification's operation "Unsubscribe" not avaliable via SOAP call
---------------------------------------------------------------------
Key: CXF-4040
URL: https://issues.apache.org/jira/browse/CXF-4040
Project: CXF
Issue Type: Bug
Components: Services
Affects Versions: 2.5.1
Environment: Apache Karaf 2.2.5
Reporter: Aleksandar Balaban
The WS-notification service doesn't expose SOAP endpoint with operation Unsubscribe. It is not listed in the WSDL retrieved via URI and an invocation (for example, using SoapUI) will end up with an SOAP exception. it seems like the only operations supported are those from the WS-BrokeredNotification where the basic notification operations are not avaliable via SOAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4040) WS-Notification's operation
"Unsubscribe" not avaliable via SOAP call
Posted by "Aleksandar Balaban (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandar Balaban updated CXF-4040:
------------------------------------
Description: None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. Th eoperation is not listed as part of published WSDL document and an invocation (for example, using SoapUI) will therefore end up with an SOAP exception. it seems like the only operations supported are those from the WS-BrokeredNotification where the basic notification operations are not avaliable via SOAP. (was: The WS-notification service doesn't expose SOAP endpoint with operation Unsubscribe. It is not listed in the WSDL retrieved via URI and an invocation (for example, using SoapUI) will end up with an SOAP exception. it seems like the only operations supported are those from the WS-BrokeredNotification where the basic notification operations are not avaliable via SOAP.)
> WS-Notification's operation "Unsubscribe" not avaliable via SOAP call
> ---------------------------------------------------------------------
>
> Key: CXF-4040
> URL: https://issues.apache.org/jira/browse/CXF-4040
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5.1
> Environment: Apache Karaf 2.2.5
> Reporter: Aleksandar Balaban
> Labels: cxf,, service,, ws-notification, wsn
>
> None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. Th eoperation is not listed as part of published WSDL document and an invocation (for example, using SoapUI) will therefore end up with an SOAP exception. it seems like the only operations supported are those from the WS-BrokeredNotification where the basic notification operations are not avaliable via SOAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4040) WS-Notification: Operation
"Unsubscribe" not avaliable via SOAP endpoints
Posted by "Aleksandar Balaban (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandar Balaban updated CXF-4040:
------------------------------------
Description: None of WS-Notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation "Unsubscribe". The operation isn't listed in the WSDL document and an invocation (for example via SoapUI) will end up with SOAP exception. It looks like the only operations exposed via SOAP endpoint are those from the WS-BrokeredNotification - the basic notification operations are not avaliable via SOAP. (was: None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. The operation isn't listed in the WSDL document and an invocation (for example via SoapUI) will end up with SOAP exception. It looks like the only operations exposed via SOAP endpoint are those from the WS-BrokeredNotification - the basic notification operations are not avaliable via SOAP.)
Summary: WS-Notification: Operation "Unsubscribe" not avaliable via SOAP endpoints (was: WS-Notification's operation "Unsubscribe" not avaliable via SOAP call)
> WS-Notification: Operation "Unsubscribe" not avaliable via SOAP endpoints
> -------------------------------------------------------------------------
>
> Key: CXF-4040
> URL: https://issues.apache.org/jira/browse/CXF-4040
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5.1
> Environment: Apache Karaf 2.2.5
> Reporter: Aleksandar Balaban
> Labels: cxf,, service,, ws-notification, wsn
>
> None of WS-Notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation "Unsubscribe". The operation isn't listed in the WSDL document and an invocation (for example via SoapUI) will end up with SOAP exception. It looks like the only operations exposed via SOAP endpoint are those from the WS-BrokeredNotification - the basic notification operations are not avaliable via SOAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4040) WS-Notification's operation
"Unsubscribe" not avaliable via SOAP call
Posted by "Aleksandar Balaban (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandar Balaban updated CXF-4040:
------------------------------------
Description: None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. The operation isn't listed in the WSDL document and an invocation (for example via SoapUI) will end up with SOAP exception. It looks like the only operations exposed via SOAP endpoint are those from the WS-BrokeredNotification - the basic notification operations are not avaliable via SOAP. (was: None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. Th eoperation is not listed as part of published WSDL document and an invocation (for example, using SoapUI) will therefore end up with an SOAP exception. it seems like the only operations supported are those from the WS-BrokeredNotification where the basic notification operations are not avaliable via SOAP.)
> WS-Notification's operation "Unsubscribe" not avaliable via SOAP call
> ---------------------------------------------------------------------
>
> Key: CXF-4040
> URL: https://issues.apache.org/jira/browse/CXF-4040
> Project: CXF
> Issue Type: Bug
> Components: Services
> Affects Versions: 2.5.1
> Environment: Apache Karaf 2.2.5
> Reporter: Aleksandar Balaban
> Labels: cxf,, service,, ws-notification, wsn
>
> None WS-notification services (NotificationBroker, CreatePullPoint) expose a SOAP endpoint with operation Unsubscribe. The operation isn't listed in the WSDL document and an invocation (for example via SoapUI) will end up with SOAP exception. It looks like the only operations exposed via SOAP endpoint are those from the WS-BrokeredNotification - the basic notification operations are not avaliable via SOAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira