can accept different type of soap request payloads (for different soap
> actions).
>
> We discovered an issue with a Soap 1.1 client that is sending a SOAPAction
> HTTP header to the endpoint. When the SOAPAction HTTP header is present
> the following soap fault is returned:
>
>
ap11_HTTP/KnowledgeDatabaseConsultationLogEntryCreation
> does not match an operation.
>
> As there is no WSDL associated with the endpoint (the endpoint is running
> in payload mode) how can the SOAPAction HTTP header ever be matched ?
>
> What is the proper way to handle
sultationLogEntryCreation
does not match an operation.
As there is no WSDL associated with the endpoint (the endpoint is running in
payload mode) how can the SOAPAction HTTP header ever be matched ?
What is the proper way to handle this ?
--
View this message in context:
http://camel.465427.n5
