axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guus Gerrits (JIRA)" <>
Subject [jira] Kommentiert: (AXIS-119) WSDL2Java doesn't honor restrictions in schema
Date Wed, 13 Jul 2005 09:51:22 GMT
    [ ] 

Guus Gerrits commented on AXIS-119:

A lot of work is often done to define such kind of restrictions in XSDs, currently only ending
up as a good documentation of the used DataTypes. At least  these DataTypes get some more
attention/thought during the development/design process (which usually pays out at the end).
But as time and budgets are tight in projects,  such "extra work"  is hard to legitimate to
our bosses and customers.

As the JAX-RPC 1.1 Final (JSR101) defines all facets as required, are there plans to add support
for these restriction facets in Axis-1.x or Axis-2.x (or maybe somebody is already working
on this)?

> WSDL2Java doesn't honor restrictions in schema
> ----------------------------------------------
>          Key: AXIS-119
>          URL:
>      Project: Apache Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: beta-2
>  Environment: Operating System: Windows NT/2K
> Platform: PC
>     Reporter: Joe Riess
>     Assignee: Axis Developers Mailing List

> The Java bean class which is generated via WSDL2Java using the following WSDL 
> schema section:
> <wsdl:schema targetNamespace="">
>   <xsd:simpleType name="simpleRestrictionType">
>     <xsd:restriction base="xsd:integer">
>       <xsd:minInclusive value="1" /> 
>       <xsd:maxInclusive value="10" /> 
>     </xsd:restriction>
>   </xsd:simpleType>
> </wsdl:schema>
> does not contain any range checking with regards to the minInclusive and 
> maxInclusive values.  The bean class accepts any valid integer value which is 
> contradictive to the schema.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message