[jira] Issue Comment Edited: (AXIS2-2845) Throwing exceptions causes 400 HTTP header appearing when running under Tomcat

[JIRA]

    [ 
https://issues.apache.org/jira/browse/AXIS2-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518229
 ] 

informaticu007-pfc edited comment on AXIS2-2845 at 8/7/07 12:40 PM:
-----------------------------------------------------------------

Hi Glen,

Now exceptions come with 500 HTTP header:

HTTP/1.1 500 Error Interno del Servidor
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; 
action="http://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault";charset=UTF-8
Transfer-Encoding: chunked
Date: Tue, 07 Aug 2007 19:36:42 GMT
Connection: close

346
<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
      <soapenv:Header>
         
<wsa:Action>http://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault</wsa:Action>
         <wsa:RelatesTo>urn:uuid:20F5EFD2CCF889D0FB1186515400973</wsa:RelatesTo>
      </soapenv:Header>
      <soapenv:Body>
         <soapenv:Fault>
            <soapenv:Code>
               <soapenv:Value>soapenv:Receiver</soapenv:Value>
            </soapenv:Code>
            <soapenv:Reason>
               <soapenv:Text xml:lang="en-US">Validation Fault</soapenv:Text>
            </soapenv:Reason>
            <soapenv:Detail>
               <ns3:ValidationFault 
xmlns:ns3="http://op_messages.medici_link/xsd";>
                  <ns3:description>System not validated. You must validate 
before invoking a method.</ns3:description>
               </ns3:ValidationFault>
            </soapenv:Detail>
         </soapenv:Fault>
      </soapenv:Body>
   </soapenv:Envelope>
0



In the client I can't see the exception description: 




java.rmi.RemoteException: Validation; nested exception is: 
        client.Validation: Validation
        at client.Medici_LinkStub.getPatientsByType(Medici_LinkStub.java:4187)
        at client.ClientUtilities.getPatientsTest(ClientUtilities.java:322)
        at client.Client.main(Client.java:53)
Caused by: client.Validation: Validation
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)Closing 
session...

        at java.lang.Class.newInstance0(Unknown Source)
        at java.lang.Class.newInstance(Unknown Source)
        at client.Medici_LinkStub.getPatientsByType(Medici_LinkStub.java:4173)
        ... 2 more
java.rmi.RemoteException: Validation; nested exception is: 
        client.Validation: Validation
        at 
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:4453)
        at 
client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:356)
        at client.Client.main(Client.java:59)
Caused by: client.Validation: Validation
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at java.lang.Class.newInstance0(Unknown Source)
        at java.lang.Class.newInstance(Unknown Source)
        at 
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:4439)
        ... 2 more
java.rmi.RemoteException: Validation; nested exception is: 
        client.Validation: Validation
        at client.Medici_LinkStub.logout(Medici_LinkStub.java:1056)

      was (Author: informaticu007-pfc):
    Hi Glen,

Now exceptions come with 500 HTTP header and the client works ok with them.
  
> Throwing exceptions causes 400 HTTP header appearing when running under Tomcat
> ------------------------------------------------------------------------------
>
>                 Key: AXIS2-2845
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2845
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Java 5 and 6, Tomcat 5 and 6, Windows XP SP 2
>            Reporter: Jorge Fernández
>            Assignee: Glen Daniels
>         Attachments: exception.txt
>
>
> When I integrate Axis2 with Tomcat and I try to throw any exception, the 
> response message is added a HTTP header meaning Bad Request and the exception 
> in the SOAP message is OK but when my client sees the HTTP header doesn' t go 
> on parsing the SOAP message.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]