Hola Martin:

I tried what you said but the problem is the same. Furthermore, those 
characters remain appearing even commenting every Transfer-Encoding parameter.

 I think that it's something related to Tomcat because the code 400 on HTTP 
header only appears when deploying Axis2 under Tomcat. 

"Saludos y muchas gracias" again,

Jorge Fernandez


Martin Gainty <[EMAIL PROTECTED]> escribió:       undecipherable characters 
(specifically 3a2)  is being introduced before the beginning xml tag which 
neither the servlet or  the client stub can interpret
 I have seen this happen with Chunked  encoding
 
try to disable <parameter  name="Transfer-Encoding" (commenting out the 
<parameter  name="Transfer-Encoding" from axis2.xml)
and re-deploy
  
 Saludos
 M--
 This email message and any files transmitted with it contain  confidential
information intended only for the person(s) to whom this email  message is
addressed.  If you have received this email message in error,  please notify
the sender immediately by telephone or email and destroy the  original
message without making a copy.  Thank you.

    ----- Original Message ----- 
   From:    Jorge Fernandez 
   To: [email protected] 
   Sent: Thursday, June 21, 2007 3:40    PM
   Subject: HTTP/1.1 400 Bad Request
   

Hi again,

I was trying to get some information on this    problem but I couldn't know 
what is happening so I'm trying again.

Does    anybody know anything about how can I fix this???

Thanks a    lot,

Jorge Fernández

Jorge Fernandez <[EMAIL PROTECTED]>    escribió:   Hi      all,

I'm having problems only when throwing exceptions. I'm getting      "bad 
request". This problem appeared since I moved to axis2 1.2, using it      with 
Tomcat. If I use axis as standalone server there's no problem.      

The messages are apparently the same except for some minimal changes      in 
the order of HTTP header, the prefix for the description element      namespace 
and that the final character after envelope in one case appears in      the 
following line. This are the messages:

The correct one with      standalone axis:

HTTP/1.1 500 Internal server error
Date: Wed, 13      Jun 2007 08:22:37 GMT
Content-Type: application/soap+xml;      
action="http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault";
Server:      Simple-Server/1.1
Transfer-Encoding: chunked
Connection:      Close

3a2
<?xml version='1.0'      encoding='UTF-8'?>
   <soapenv:Envelope      xmlns:wsa="http://www.w3.org/2005/08/addressing";      
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
           <soapenv:Header>
              
<wsa:Action>http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault</wsa:Action>
              
<wsa:RelatesTo>urn:uuid:B2AFE74A4124DE7BFF1181722957402</wsa:RelatesTo>
           </soapenv:Header>
           <soapenv:Body>
              <soapenv:Fault>
                 <soapenv:Code>
                    <soapenv:Value>soapenv:Sender</soapenv:Value>
                 </soapenv:Code>
                 <soapenv:Reason>
                    <soapenv:Text      
xml:lang="en-US">ValidationFaultException</soapenv:Text>
                 </soapenv:Reason>
                 <soapenv:Detail>
                    <ns4:ValidationException      
xmlns:ns4="http://op_messages.medici_link/xsd";>
                       <ns4:ValidationFault>
                          <s2:description 
xmlns:s2="http://faults.medici_link/xsd";>User not      validated. You must 
validate before invoking a      method.</s2:description>
                       </ns4:ValidationFault>
                    </ns4:ValidationException>
                 </soapenv:Detail>
              </soapenv:Fault>
           </soapenv:Body>
        </soapenv:Envelope>0


The bad one with      tomcat:

HTTP/1.1 400 Petición incorrecta
Server:      Apache-Coyote/1.1
Content-Type: application/soap+xml;      
action="http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault";charset=UTF-8
Transfer-Encoding:      chunked
Date: Wed, 13 Jun 2007 08:12:50 GMT
Connection:      close

3a2
<?xml version='1.0'      encoding='UTF-8'?>
   <soapenv:Envelope      xmlns:wsa="http://www.w3.org/2005/08/addressing";      
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
           <soapenv:Header>
              
<wsa:Action>http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault</wsa:Action>
              
<wsa:RelatesTo>urn:uuid:61931C3AAB6FF83F181181722371001</wsa:RelatesTo>
           </soapenv:Header>
           <soapenv:Body>
              <soapenv:Fault>
                 <soapenv:Code>
                    <soapenv:Value>soapenv:Sender</soapenv:Value>
                 </soapenv:Code>
                 <soapenv:Reason>
                    <soapenv:Text      
xml:lang="en-US">ValidationFaultException</soapenv:Text>
                 </soapenv:Reason>
                 <soapenv:Detail>
                    <ns4:ValidationException      
xmlns:ns4="http://op_messages.medici_link/xsd";>
                       <ns4:ValidationFault>
                          <s1:description 
xmlns:s1="http://faults.medici_link/xsd";>User not      validated. You must 
validate before invoking a      method.</s1:description>
                       </ns4:ValidationFault>
                    </ns4:ValidationException>
                 </soapenv:Detail>
              </soapenv:Fault>
           </soapenv:Body>
        </soapenv:Envelope>
0






     
     
---------------------------------
     
LLama Gratis a cualquier PC del      Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
      

---------------------------------
   
¡Descubre una nueva forma de obtener respuestas    a tus preguntas!
Entra    en Yahoo! Respuestas.


       
---------------------------------

¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.

Reply via email to