[ http://issues.apache.org/jira/browse/AXIS-2035?page=all ]
Tom Jordahl resolved AXIS-2035:
-------------------------------
Fix Version: 1.2.1
Resolution: Fixed
I believe I fixed this on June 03 2005 with the following check in:
http://marc.theaimsgroup.com/?l=axis-dev&m=111783743602099&w=2
Please reopen if the fix doesn't work for you.
> isOnlyLiteralReferenced flag improperly set
> -------------------------------------------
>
> Key: AXIS-2035
> URL: http://issues.apache.org/jira/browse/AXIS-2035
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: 1.2RC3
> Environment: Windows XP, Java SDK version 1.4.2_07
> Reporter: footh
> Priority: Minor
> Fix For: 1.2.1
>
> I have observed that the isOnlyLiteralReferenced flag is not properly set in
> certain situations.
> Example, in this WSDL:
> http://www.ripedev.com/webservices/ZipCode.asmx?WSDL
> 1.) I read it into a SymbolTable. Then I get the operation parameters via
> the getOperationParameters method call (in this example, using the
> "ZipCodeToCityState" operation).
> 2.) Then, I iterate through the parameters. In this case, there is just one
> input parameter referring to the ZipCodeToCityState element in the message
> part.
> 3.) I call the getType method on the Parameter object to retrieve the
> TypeEntry object. Then, I get this TypeEntry's referenced type by calling
> the getRefType method on it.
> 4.) This leads me to the TypeEntry object that I believe should have the
> literalReference flag set to true, but instead is false.
> As a contrasting example, take this WSDL:
> http://ws2.serviceobjects.net/pt/PackTrack.asmx?WSDL
> Using the UPS_GetTrackingInfo operation, one can see that the input message
> has one part which refers to the UPS_GetTrackingInfo element. Going over to
> this element, it has a very simlar format to the first WSDL (except two child
> parameters as opposed to one). However, using the procedure outlined above,
> the literalReference flag is set to true.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
