Just ruling out a few things.
1. It still happens if you use Http 1.0 or Http 1.1.
2. It still happens if I deploy my service in WebSphere, which
implements JAX-RPC and is not an Axis based web service.
 
So 2 above that tells me it is not just Axis, but some sort of standard
behavior. (It is possible that .NET may indeed be expecting the xml
declaration on responses, but that it is a Microsoft anomaly and they
shouldn't be expecting it. The other possibility is that Microsoft is
indeed correct, and the Java world is lax in not providing the xml
declaration on responses).
 
The other train of thought I had is that this is SOAP 1.2 behavior, and
I am using Soap 1.1.
So, what version of .NET and SOAP are you using?
-jeff
 
  _____  

From: Luposlip [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 17, 2007 10:39 AM
To: [email protected]
Subject: Re: XML-declaration in WSDL2Java generated SOAP service



        I don't know if it's standard or not.
        My problem is that my AXIS2-service should be "digestable" from
a .NET application that requires the XML declaration. .NET based SOAP
services seems to include the XML declaration at top. 
        
        Does anyone know how to make AXIS2 include the XML declaration
at top of responses?
        
        
        
        2007/10/17, Walker, Jeff <[EMAIL PROTECTED] >: 

                I too have noticed this. (I use Axis1 1.4, but from what
you say, it also occurs in Axis2). 

                

                My requests looks like:

                POST /fmr-pdk-pag-soaservices/services/PaGWebService
HTTP/1.0

                Content-Type: text/xml; charset=utf-8

                Accept: application/soap+xml, application/dime,
multipart/related, text/*

                User-Agent: Axis/1.3

                Host: 127.0.0.1:1234

                Cache-Control: no-cache

                Pragma: no-cache

                SOAPAction: ""

                Content-Length: 1731

                 

                <?xml version="1.0" encoding="UTF-8"?>
                <soapenv:Envelope ..some huge xml string..

                 

                and my responses look like:

                HTTP/1.0 200 OK

                Content-Type: text/xml; charset=utf-8

                Content-Language: en-US

                Content-Length: 1482

                Set-Cookie: JSESSIONID=0000W_MwQ1tM9VkElguugWBApVz:-1;
Path=/

                Date: Wed, 17 Oct 2007 14:05:32 GMT

                Server: WebSphere Application Server/6.1

                Expires: Thu, 01 Dec 1994 16:00:00 GMT

                Cache-Control: no-cache="set-cookie, set-cookie2"

                

                 

                <soapenv:Envelope ..some huge xml string..

                 

                

                Notice how the request has the <?xml version="1.0"
encoding="UTF-8"?> line but the response does not. Is this standard web
service behavior?
                -jeff

                 

                
  _____  

                From: Luposlip [mailto:[EMAIL PROTECTED] 
                Sent: Wednesday, October 17, 2007 4:27 AM
                To: [email protected]
                Subject: XML-declaration in WSDL2Java generated SOAP
service
                
                
                

                        HI there gurus,
                        
                        I've generated a SOAP based service with
WSDL2Java (AXIS2 1.2). The issue is that it doesn't include a XML
declaration as the first line in the response documents.
                        Could you please tell me how to do this? 
                        
                        Thanks a bunch! 


Reply via email to