[
https://issues.apache.org/jira/browse/AXIS2-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486246
]
Amila Chinthaka Suriarachchi commented on AXIS2-2446:
-----------------------------------------------------
your first issue is already fixed with a later build. So please have a look at
with the RC1 or the RC2 which is due to release soon.
For minOccurs='0' problem I think you have to check the request rather than
response.
try to use the following code to do and adb testing with the element you want
to test.
NewOperation newOperation = new NewOperation();
newOperation.setNewOperationRequest("test");
OMElement omElement = newOperation.getOMElement(NewOperation.MY_QNAME,
OMAbstractFactory.getOMFactory());
try {
String omElementString = omElement.toStringWithConsume();
System.out.println("OM String ==> " + omElementString);
XMLStreamReader xmlReader = StAXUtils.createXMLStreamReader(new
ByteArrayInputStream(omElementString.getBytes()));
NewOperation result = NewOperation.Factory.parse(xmlReader);
} catch (Exception e) {
}
here you can see first it gets the xmlString from the object structure and then
get the Object structure from the xml string. In this way you can properly test
the generated adb code easily and correctly.
I have done a lot of testing with the minOccures='0'. So I belive it should
work with any case.
> 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]
