You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2010/01/20 13:21:02 UTC
Client tries to use GET?
I just delivered a CXF service to a customer. They created a client
with something (I don't know, yet, what), and tried to use it.
Bad things happen:
org.apache.cxf.interceptor.Fault: No such operation: (HTTP GET
PATH_INFO: /rex-ws/Extraction)
Now, the service's parameters are pretty simple, so I don't know why
it couldn't handle a get, but it doesn't.
Shouldn't the wsdl be describing the binding so as to prevent this? On
the other hand, is there something simple I could do to turn it on? Or
am I misunderstanding what's going on here.
Re: Client tries to use GET?
Posted by Benson Margulies <bi...@gmail.com>.
Yes. Someone passed a URL without the ?wsdl to a client constructor
that wanted the WSDL.
On Wed, Jan 20, 2010 at 7:32 AM, Sergey Beryozkin <sb...@progress.com> wrote:
> Can it be that the client is attempting to get a WSDL but no WSDL has not
> been found yet, that is the CXF QueryHandler handling ?wsdl requests was not
> able to satisfy a ?wsdl query and allowed the request to continue ?
> Though may be they use some clients that do SOAP GETs (thus ignoring the
> binding information in a wsdl)
>
> cheers, Sergey
>
>> I just delivered a CXF service to a customer. They created a client
>> with something (I don't know, yet, what), and tried to use it.
>>
>> Bad things happen:
>>
>> org.apache.cxf.interceptor.Fault: No such operation: (HTTP GET
>> PATH_INFO: /rex-ws/Extraction)
>>
>> Now, the service's parameters are pretty simple, so I don't know why
>> it couldn't handle a get, but it doesn't.
>>
>> Shouldn't the wsdl be describing the binding so as to prevent this? On
>> the other hand, is there something simple I could do to turn it on? Or
>> am I misunderstanding what's going on here.
>
>
Re: Client tries to use GET?
Posted by Sergey Beryozkin <sb...@progress.com>.
Can it be that the client is attempting to get a WSDL but no WSDL has not been found yet, that is the CXF QueryHandler handling
?wsdl requests was not able to satisfy a ?wsdl query and allowed the request to continue ?
Though may be they use some clients that do SOAP GETs (thus ignoring the binding information in a wsdl)
cheers, Sergey
>I just delivered a CXF service to a customer. They created a client
> with something (I don't know, yet, what), and tried to use it.
>
> Bad things happen:
>
> org.apache.cxf.interceptor.Fault: No such operation: (HTTP GET
> PATH_INFO: /rex-ws/Extraction)
>
> Now, the service's parameters are pretty simple, so I don't know why
> it couldn't handle a get, but it doesn't.
>
> Shouldn't the wsdl be describing the binding so as to prevent this? On
> the other hand, is there something simple I could do to turn it on? Or
> am I misunderstanding what's going on here.