axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Buss (JIRA)" <>
Subject [jira] Commented: (AXIS2-2446) Schema constraints generate incorrect code
Date Sat, 31 Mar 2007 00:30:25 GMT


Tim Buss commented on AXIS2-2446:

Note that these tests are "rpc-Literal"

It seemt aht adding minOccurs="0" to any element - simple or complex results in a bad message
whether or not the element is present. For example

			<xsd:complexType name="MinOccursSimpleType">
					<xsd:element minOccurs="0" name="AString" type="xsd:string"/>

set as follows in the generated test client

           minOccursSimpleOperation124.setMinOccursSimpleOperationRequest(new MinOccursSimpleType());

results in the following message

POST /axis2/services/Axis2RPCLiteralTest HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Axis2
Transfer-Encoding: chunked

with the following reply

HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 30 Mar 2007 19:21:07 GMT
Connection: close

<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:wsa="" xmlns:soapenv="">
            <faultstring>Invalid chunk</faultstring>
            <detail />

It seems there is code that expects to handle minOccurs="0" (ie the "setting tracker").  The
same test without minOccurs="0" works with not problmes.

I have attached the test WSDL I am using.

> Schema constraints generate incorrect code
> ------------------------------------------
>                 Key: AXIS2-2446
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.1.1
>         Environment: Java 1.5, Tomcat 5.5, Axis2 1.1.1 and more recent  Axis and Axiom
SNAPSHOTs, Axis2 Eclipse codegen plugin 1.1.1, Eclipse 3.2, WTP 1.5.1, Windows 2003 server
>            Reporter: Tim Buss
> This problem was originally found in Axis 1.1.1 but is stil present in AXIS SNAPSHOT
3/21 and Axiom SNAPSHOT 3/23
> A schema constraint that attempts to limit a string to a particular "maxLength"  generates
code that instead eforces the given size as a "minLength".  eg:
> The schema type
> 			<xsd:simpleType name="ConstrainedSimpleType">
> 				<xsd:restriction base="xsd:string">
> 					<xsd:maxLength value="36"/>
> 				</xsd:restriction>
> 			</xsd:simpleType>
> generates
>                              /**
>                                * Auto generated setter method
>                                * @param param ConstrainedSimpleType
>                                */
>                                public void setConstrainedSimpleType(java.lang.String
>                                             if (  (java.lang.String.valueOf(param).length()
>= 36)  ) {
>                                                 this.localConstrainedSimpleType=param;
>                                             }
>                                             else {
>                                                 throw new java.lang.RuntimeException();
>                                             }
>                                }
> As you can see the ">" is reversed.  It should be "<".   I have only tested this
case so far so I don't know if the bug is isolated to this case.
> I am having some other issues with minOccurs=0 (or its omission) where the generated
code does not behave as expected but I am still trying th characterize that.

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:
For additional commands, e-mail:

View raw message