You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Jesper Söderlund <Je...@smarttrust.com> on 2002/09/12 17:05:03 UTC

Feature request - WSDL2Java - enforcing Schema - restrictions

Wouldn't it be really cool if Axis supported the XML Schema constraints that you can specify in you WSDL-file during WSDL2Java generation? That would really fulfill the vision of WebService programming, define your constrains on a logical level and then generate an API that enforces these so that you WebService doesn't have to deal with all that error checking which we all know can take up the bulk of your code.
 
I don't think that a simple implementation would be that hard. It seems that you should be able to save the schema into the WSDL2Java generated files and then use that to verify the SOAP-message (letting the XML-parser do the job) when it arrives at the server. Sure it might not give you a very detailed error message, beeing limited to what the SAX-parser would emitt as an error text but it beats not having any checks.
 
Are there any Axis developers out there that has any oppions on the topic? Any user seconding this request?
 
Regards,
/Jesper

Re: Feature request - WSDL2Java - enforcing Schema - restrictions

Posted by doug <um...@yahoo.com>.

Jesper Söderlund wrote:
> Wouldn't it be really cool if Axis supported the XML Schema constraints 
> that you can specify in you WSDL-file during WSDL2Java generation? That 
> would really fulfill the vision of WebService programming, define your 
> constrains on a logical level and then generate an API that enforces 
> these so that you WebService doesn't have to deal with all that error 
> checking which we all know can take up the bulk of your code.
>  
> I don't think that a simple implementation would be that hard. It seems 
> that you should be able to save the schema into the WSDL2Java generated 
> files and then use that to verify the SOAP-message (letting the 
> XML-parser do the job) when it arrives at the server. Sure it might not 
> give you a very detailed error message, beeing limited to what the 
> SAX-parser would emitt as an error text but it beats not having any checks.
>  
> Are there any Axis developers out there that has any oppions on the 
> topic? Any user seconding this request?
>  
> Regards,
> /Jesper

i've requested this via bugzilla.  see 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10872