users@glassfish.java.net
Who is putting the Header in the soap message
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
]
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]
From
: Mauro Almeida <
malmeida_at_localmatters.com
>
Date
: Sat, 22 Nov 2008 07:24:35 -0700
Here is a brief description.
I have A WS client and server. If the client and server are running in the same machine. They work great.
(Sailfin b59 on linux with java6 32bits)
The soap message received by the server is:
<S:Envelope xmlns:S="
http://schemas.xmlsoap.org/soap/envelope/
">
<S:Header/>
<S:Body>
<ns2:init xmlns:ns2="
http://webservice.yy.xx.aa.com/
">
<qualifier_id>id</qualifier_id>
<wsdl>
http://funk:8080/xx-yy/WS?wsdl</wsdl
>
</ns2:init>
</S:Body>
</S:Envelope>
Now if a run the server in a remote box. It does not work. And the server receives a soap message with the following header.
So it basically fails.
(Client - Sailfin b59 on linux with java6 32bits)
(Server - glassfish on AIX with java5 64bits)
<S:Envelope xmlns:S="
http://schemas.xmlsoap.org/soap/envelope/
">
<S:Header>
<CoordinationContext xmlns="
http://schemas.xmlsoap.org/ws/2004/10/wscoor
" xmlns:ns3="
http://schemas.xmlsoap.org/soap/envelope/
" xmlns:ns2="
http://schemas.xmlsoap.org/ws/2004/08/addressing
" ns3:mustUnderstand="true">
<Identifier>uuid:WSCOOR-SUN-4124b51e-3f3b-47c6-8f6d-e9e669d0d969</Identifier>
<CoordinationType>
http://schemas.xmlsoap.org/ws/2004/10/wsat</CoordinationType
>
<RegistrationService>
<ns2:Address>
https://funk.isxinc.com:8181/__wstx-services/wscoor/coordinator/register</ns2:Address
>
<ns2:ReferenceParameters>
<jaxws:objectId xmlns:jaxws="
http://jax-ws.dev.java.net/xml/ns/
" xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing
">3dabbfc6-e916-4fca-8c33-271231cdd989</jaxws:objectId>
</ns2:ReferenceParameters>
</RegistrationService>
</CoordinationContext>
</S:Header>
<S:Body>
<ns2:init xmlns:ns2="
http://webservice.yy.xx.aa.com/
">
<qualifier_id>id</qualifier_id>
<wsdl>
http://funk:8080/xx-yy/WS?wsdl</wsdl
>
</ns2:init>
</S:Body>
</S:Envelope>
Finally, I've seen this behavior with the WS Testing tool as well. Sometimes the message sent would contain the header, ( and it would fail)... Sometimes it would contain the header and it works...
Thanks !!!
Mauro Almeida
mailto:malmeida_at_localmatters.com <mailto:malmeida_at_localmatters.com>
This message
: [
Message body
]
Next message
:
glassfish_at_javadesktop.org: "Not able to create cluster on my Windows XP SP3"
Previous message
:
glassfish_at_javadesktop.org: "Re: Stateful Session Bean [One instance per client ? Really ?]"
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]