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 "Dino (JIRA)" <ji...@apache.org> on 2010/11/21 19:30:13 UTC
[jira] Created: (AXIS2-4891) Handle bad client requests better
Handle bad client requests better
---------------------------------
Key: AXIS2-4891
URL: https://issues.apache.org/jira/browse/AXIS2-4891
Project: Axis2
Issue Type: New Feature
Components: kernel
Affects Versions: 1.4.1, 1.5, 1.5.1, 1.5.2, 1.5.3
Reporter: Dino
We are getting a lot of parsing exceptions from clients (more rouge than legit) hitting our axis2 soap services incorrectly.
For example:
2010-11-21 16:17:47,309 ERROR [http-httpd-10380-162$1212637080] org.apache.axis2.engine.AxisEngine : javax.xml.stream.XMLStreamException: :3:247 expected '>' at 0xffffffff
We have no control over the processing since the AxisEngine logs the error directly (e.g log.error(e.getMessage(), e)).
Axis2 should provide a way to override the error handling either by using an interceptor or having a delegating method that can be overwritten. It can default to logging the error but allow developers to overwrite this behavior easily.
Not sure the easiest approach but look for guidance from the Axis2 dev team to provide a solution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4891) Allow the ability to handle bad client
requests
Posted by "Dino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dino updated AXIS2-4891:
------------------------
Summary: Allow the ability to handle bad client requests (was: Handle bad client requests better)
> Allow the ability to handle bad client requests
> -----------------------------------------------
>
> Key: AXIS2-4891
> URL: https://issues.apache.org/jira/browse/AXIS2-4891
> Project: Axis2
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4.1
> Reporter: Dino
>
> We are getting a lot of parsing exceptions from clients (more rouge than legit) hitting our axis2 soap services incorrectly.
> For example:
> 2010-11-21 16:17:47,309 ERROR [http-httpd-10380-162$1212637080] org.apache.axis2.engine.AxisEngine : javax.xml.stream.XMLStreamException: :3:247 expected '>' at 0xffffffff
> We have no control over the processing since the AxisEngine logs the error directly (e.g log.error(e.getMessage(), e)).
> Axis2 should provide a way to override the error handling either by using an interceptor or having a delegating method that can be overwritten. It can default to logging the error but allow developers to overwrite this behavior easily.
> Not sure the easiest approach but look for guidance from the Axis2 dev team to provide a solution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4891) Allow the ability to handle bad
client requests
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4891.
------------------------------------
Resolution: Won't Fix
Because of deferred parsing, if the client sends XML that is not well formed, the exception may occur anywhere inside Axis2. There is no central place where this type of exception could be intercepted. However, you have the option to register a modified SOAPBuilder that would add a wrapper around the XMLStreamReader obtained from Axiom. This wrapper could then implement some custom error reporting if it gets an exception from the underlying parser.
> Allow the ability to handle bad client requests
> -----------------------------------------------
>
> Key: AXIS2-4891
> URL: https://issues.apache.org/jira/browse/AXIS2-4891
> Project: Axis2
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4.1
> Reporter: Dino
>
> We are getting a lot of parsing exceptions from clients (more rouge than legit) hitting our axis2 soap services incorrectly.
> For example:
> 2010-11-21 16:17:47,309 ERROR [http-httpd-10380-162$1212637080] org.apache.axis2.engine.AxisEngine : javax.xml.stream.XMLStreamException: :3:247 expected '>' at 0xffffffff
> We have no control over the processing since the AxisEngine logs the error directly (e.g log.error(e.getMessage(), e)).
> Axis2 should provide a way to override the error handling either by using an interceptor or having a delegating method that can be overwritten. It can default to logging the error but allow developers to overwrite this behavior easily.
> Not sure the easiest approach but look for guidance from the Axis2 dev team to provide a solution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org