[ 
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

        

Reply via email to