[
https://issues.apache.org/jira/browse/AXIS2-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486193
]
Tim Buss commented on AXIS2-2446:
---------------------------------
I am no longer able to reproduce the "minOccurs" problem described above so I
suspect it was caused by an odd condition on my machine. Nothing really
changed as far as I am aware except that I downloaded the 3.0.1 commons-http
client so I could debug. The tests as so far descibed involving minOccurs now
work with the exception of the "any" test which I am still working on.
The string length issue is reproducible.
There is another "minOccurs" problem I am trying to characterize where
"minOccurs="0"" seems to be required when it shouldn't be.
> Schema constraints generate incorrect code
> ------------------------------------------
>
> Key: AXIS2-2446
> URL: https://issues.apache.org/jira/browse/AXIS2-2446
> 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
> Attachments: Axis2RPCLiteralTest.wsdl
>
>
> 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 param){
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
