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 "Victor Volle (JIRA)" <ji...@apache.org> on 2006/03/31 09:14:29 UTC
[jira] Created: (AXIS2-536) CLONE -validate request and response
with Schema
CLONE -validate request and response with Schema
------------------------------------------------
Key: AXIS2-536
URL: http://issues.apache.org/jira/browse/AXIS2-536
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Victor Volle
Priority: Minor
Currently the content (SoapBody) is not validated against the Schema definition in the WSDL.
I propose to add a Handler that can be added to the request and/or the response handling on the server (or even on the client). I think
this would simplify many problems when developing a client.
The request validation might even be switched on in production
environments to reduce the risk af malicious requests or
to reduce the load on the backend in case of DoS attacks
(assuming that Axis is used as a sort of Proxy/Broker that
forwards the (transformed) request to another system).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-536) CLONE -validate request and response
with Schema
Posted by "Victor Volle (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-536?page=comments#action_12372641 ]
Victor Volle commented on AXIS2-536:
------------------------------------
The original request has been closed with a "won't fix".
The only thing I am asking for, is a reason, why this issue has been "resolved" as "won't fix"
> CLONE -validate request and response with Schema
> ------------------------------------------------
>
> Key: AXIS2-536
> URL: http://issues.apache.org/jira/browse/AXIS2-536
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Reporter: Victor Volle
> Priority: Minor
>
> Currently the content (SoapBody) is not validated against the Schema definition in the WSDL.
> I propose to add a Handler that can be added to the request and/or the response handling on the server (or even on the client). I think
> this would simplify many problems when developing a client.
> The request validation might even be switched on in production
> environments to reduce the risk af malicious requests or
> to reduce the load on the backend in case of DoS attacks
> (assuming that Axis is used as a sort of Proxy/Broker that
> forwards the (transformed) request to another system).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-536) CLONE -validate request and response
with Schema
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-536?page=comments#action_12372669 ]
Davanum Srinivas commented on AXIS2-536:
----------------------------------------
Victor,
If you wish to help and can contribute a patch then i'll keep this open. please let us know. from experience with Axis1, this kind of request just stays in the system *forever*.
thanks,
dims
> CLONE -validate request and response with Schema
> ------------------------------------------------
>
> Key: AXIS2-536
> URL: http://issues.apache.org/jira/browse/AXIS2-536
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Reporter: Victor Volle
> Priority: Minor
>
> Currently the content (SoapBody) is not validated against the Schema definition in the WSDL.
> I propose to add a Handler that can be added to the request and/or the response handling on the server (or even on the client). I think
> this would simplify many problems when developing a client.
> The request validation might even be switched on in production
> environments to reduce the risk af malicious requests or
> to reduce the load on the backend in case of DoS attacks
> (assuming that Axis is used as a sort of Proxy/Broker that
> forwards the (transformed) request to another system).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-536) CLONE -validate request and response
with Schema
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-536?page=all ]
Deepal Jayasinghe resolved AXIS2-536:
-------------------------------------
Resolution: Won't Fix
Hi Victor,
If we are trying to validate req/res with schema then all the time we have to build the tree and I dont think that is not a good idea at all. We have introduced AXIOM which will not build the incoming message until some one ask for that so this will break that :( .
I know the requirement can be easily implemented by adding two handlers. It will be great that if you can help us to implement this since that will benefit you and any other user who are waiting for such a feature.
> CLONE -validate request and response with Schema
> ------------------------------------------------
>
> Key: AXIS2-536
> URL: http://issues.apache.org/jira/browse/AXIS2-536
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Reporter: Victor Volle
> Priority: Minor
>
> Currently the content (SoapBody) is not validated against the Schema definition in the WSDL.
> I propose to add a Handler that can be added to the request and/or the response handling on the server (or even on the client). I think
> this would simplify many problems when developing a client.
> The request validation might even be switched on in production
> environments to reduce the risk af malicious requests or
> to reduce the load on the backend in case of DoS attacks
> (assuming that Axis is used as a sort of Proxy/Broker that
> forwards the (transformed) request to another system).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira