[jira] Created: (WSIF-64) improper handling of <element ref=qname>
| Newsgroups | gmane.comp.apache.webservices.wsif.devel |
|---|---|
| Message-ID | <1753959667.1096034311939.JavaMail.apache@nagoya> |
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSIF-64
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSIF-64
Summary: improper handling of <element ref=qname>
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-WSIF
Components:
Basic Architecture
Versions:
current (nightly)
Assignee:
Reporter: Jeff Greif
Created: Fri, 24 Sep 2004 6:57 AM
Updated: Fri, 24 Sep 2004 6:57 AM
Environment: Windows 2000 SP4, j2sdk1.4.2_05
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira