axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "footh (JIRA)" <>
Subject [jira] Created: (AXIS-2035) isOnlyLiteralReferenced flag improperly set
Date Thu, 02 Jun 2005 21:36:17 GMT
isOnlyLiteralReferenced flag improperly set

         Key: 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

I have observed that the isOnlyLiteralReferenced flag is not properly set in certain situations.

Example, in this 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:

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:
For more information on JIRA, see:

View raw message