cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3657) Incorrect message routing for missing operation
Date Thu, 21 Jul 2011 20:54:58 GMT

     [ https://issues.apache.org/jira/browse/CXF-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-3657.
------------------------------

       Resolution: Not A Problem
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


This is working completely per spec.   When using a JAX-WS provider, the @WebParam/@WebResult/@WebMethod
annotations are irrelevant.  Per spec, any message that comes into the service should be sent
directly to the invoke method.


> Incorrect message routing for missing operation
> -----------------------------------------------
>
>                 Key: CXF-3657
>                 URL: https://issues.apache.org/jira/browse/CXF-3657
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.4.1
>            Reporter: Alexey Markevich
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: Invalid
>
>         Attachments: CustomerService.wsdl, CustomerServicePort.wsdl, Provider.java, soapui.txt
>
>
> I created provider implementation (Provider.java) based on CustomerService.wsdl .
> CustomerServicePort.wsdl is provider generated.
> When I send request for missing operation using SoapUI (soapui.txt) my provider called
in despite of another operation implementation.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message