Sorry for the delay. Jira AXIS2-767 created.
Regards,
Michele
Deepal Jayasinghe wrote:
> can u pls create a JIRA , I think this is a bug.
>
> Michele Mazzucco wrote:
>
>> example1/MyService:
>>
>> 1) no headers added:
>> HTTP/1.1 200 OK
>> Server: Apache-Coyote/1.1
>> Set-Cookie: JSESSIONID=CF2
can u pls create a JIRA , I think this is a bug.
Michele Mazzucco wrote:
>example1/MyService:
>
>1) no headers added:
>HTTP/1.1 200 OK
>Server: Apache-Coyote/1.1
>Set-Cookie: JSESSIONID=CF2A6A3A366706087FBBD8818E91A62C; Path=/axis2
>Content-Type: multipart/related;
>boundary=MIMEBoundaryurn_uuid_
example1/MyService:
1) no headers added:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=CF2A6A3A366706087FBBD8818E91A62C; Path=/axis2
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_1CAAD3F62EB8F21F2011478815557861;
type="application/xop+xml";
start="<0.urn:uuid:[E
I'm sorry, but where can I find the 'axis2-soapmonitor.jar' file
mentioned here: http://ws.apache.org/axis2/1_0/soapmonitor-module.html?
Michele
Davanum Srinivas wrote:
> What do you see on the wire? can u please try tcpmon or some other
> mechanism to look at the actual soap messages?
>
> thank
What do you see on the wire? can u please try tcpmon or some other
mechanism to look at the actual soap messages?
thanks.,
dims
On 5/17/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Hi all,
I noticed that the calls ServiceClient.addStringHeader() and
ServiceClient.addHeader() cause the messa
Hi all,
I noticed that the calls ServiceClient.addStringHeader() and
ServiceClient.addHeader() cause the message to be not received.
Any idea?
Michele
