[ http://issues.apache.org/jira/browse/WSIF-64?page=all ]
Aleksander Slominski resolved WSIF-64:
--------------------------------------
Fix Version: current (nightly)
Resolution: Fixed
Assign To: Aleksander Slominski
I think it is now resolved as part of (WSIF-68) "schema parsing
incorrect/incomplete for <element>"?
http://issues.apache.org/jira/browse/WSIF-68?page=all
> improper handling of <element ref=qname>
> ----------------------------------------
>
> Key: WSIF-64
> URL: http://issues.apache.org/jira/browse/WSIF-64
> Project: Axis-WSIF
> Type: Bug
> Components: Basic Architecture
> Versions: current (nightly)
> Environment: Windows 2000 SP4, j2sdk1.4.2_05
> Reporter: Jeff Greif
> Assignee: Aleksander Slominski
> Fix For: current (nightly)
>
> Given these types:
> <element name="createAccountWithLogin"
> type="tns:CreateAccountWithLogin"/>
> <complexType name="CreateAccountWithLogin">
> <sequence>
> <element name="username" type="xsd:string"/>
> <element name="password" type="xsd:string"/>
> <element ref="tns:createAccount"/>
> <!-- <element name="createAccount" type="tns:CreateAccount"/>
> -->
> </sequence>
> </complexType>
>
> and a doc/lit operation called createAccountWithLogin whose input message has
> a single part defined by a createAccountWithLogin element,
> WSIFPort.createOperation(operationName, null, null)
> fails in org.apache.wsif.providers.ProviderUtils.unwrapPart complaining that
> "sequence element has no type name". This occurs because the wsif.schema
> stuff does not handle <element ref="..."> properly. If the line above
> mentioning ref= is replaced by the one below it, the problem does not occur.
> This applies to all builds I tried between 2.0 and one just made from cvs.
--
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
