You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jorge Fernández (JIRA)" <ji...@apache.org> on 2007/08/07 21:35:59 UTC
[jira] Issue Comment Edited: (AXIS2-2845) Throwing exceptions
causes 400 HTTP header appearing when running under Tomcat
[ 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:35 PM:
-----------------------------------------------------------------
Hi Glen,
Now exceptions come with 500 HTTP header and the client works ok with them.
was (Author: informaticu007-pfc):
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org