-
1. Re: why must set SoapAction in http header ?
tomeicher Jul 21, 2010 7:15 AM (in response to smalla123)Maybe if you provide the SoapAction explicitly, it does not have to parse the message ?
In the action for the HttpRouter
<property name="MappedHeaderList" value="SOAPAction"/>
and in your code
message.getProperties().setProperty("SOAPAction", mySoapAction);
Cheers, tom.
-
2. Re: why must set SoapAction in http header ?
smalla123 Jul 21, 2010 9:57 PM (in response to tomeicher)hi tom
firstly, thanks for your reply. But, if the external webservice change its wsdl. we have to modify the code. Could you provide a method that resolve the issue by modifing the jboss esb config?
regards,
Jackie
-
3. Re: why must set SoapAction in http header ?
tomeicher Jul 22, 2010 5:14 AM (in response to smalla123)Hi, well, of course the code that sets the action, can in turn read the required value from it's own ConfigTree, so it's in your jboss-esb.xml. Cheers, Tom.
-
4. Re: why must set SoapAction in http header ?
dward Jul 28, 2010 11:33 AM (in response to tomeicher)Tom is correct. You can put a custom action class in the pipeline before the soapproxy, which sets the soapaction message property to a value configured in jboss-esb.xml.