-
1. JBoss sends empty SOAPAction
asoldano Jan 28, 2011 4:25 AM (in response to izgur)Hi,
the code that sets the SOAPAction header relies on the metadata you see having that info; http://anonsvn.jboss.org/repos/jbossws/stack/native/tags/jbossws-native-3.2.1.GA/modules/core/src/main/java/org/jboss/ws/core/jaxws/binding/SOAPBindingJAXWS.java .
Can you double check you're not overwriting the soapAction thorugh the message context? Also, addressing might play a role in this.
Generally speaking, also consider trying a more recent jbossws version.
-
2. JBoss sends empty SOAPAction
izgur Jan 28, 2011 4:46 AM (in response to asoldano)Can you please specify more in details...
How can i check I'm not overwriting the soapAction through message context ?
Can I change the addressing ?
This is the last WS I have to call, everything else works...
So I hope I'll get some ideas...
And if it really doesn't work with 3.2.1, I will upgrade the next week...
-
3. JBoss sends empty SOAPAction
izgur Jan 28, 2011 5:59 AM (in response to izgur)I installed jbossws-native-3.2.2.GA... nothing changes...
-
4. JBoss sends empty SOAPAction
asoldano Feb 8, 2011 3:56 AM (in response to izgur)Are you still having issues, or the upgrade of Riftsaw solved this too? http://community.jboss.org/message/585121#585121
If you still see this issue, it might really help having a small testcase to reproduce.
-
5. JBoss sends empty SOAPAction
izgur Feb 8, 2011 5:29 AM (in response to asoldano)Ooo... noithing changed with the upgrade to jbossws-native-3.2.2.GA.
I saw it's a bug in Riftsaw 2.1 calling a .NET WS -
(see https://issues.jboss.org/browse/RIFTSAW-279)
But then I installed jbossesb4.9(4.8 before) and RiftSaw2.2.0.Final.
Works well ...
The issue is solved...
If you have some time, please look at http://community.jboss.org/message/585997 . Other issue...
-
6. JBoss sends empty SOAPAction
asoldano Feb 14, 2011 4:36 AM (in response to izgur)OK, regarding the other issue, please open a new thread, providing more ws specific details; for instance, you might want to check/capture what exactly goes on the wire when calling the remote endpoint using SoapUI and using your (RiftSaw) client.