[
https://issues.apache.org/jira/browse/AXIS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS-1495:
----------------------------------
Description:
Error Summary:
Anonymous types are named in the SymbolTable with the ANON_TOKEN prefix (">").
This causes a problem for the makeTypeElement method invoked by writeType.
Initial Diagnostic:
There seems to be a contradiction here, makeTypeElement doesn't allow anonymous
types outside of a containing element, whereas writeType invokes
makeTypeElement specifying "null" as the containing element.
makeTypeElement code snippet:
// Can't have an anonymous type outside of a containing element
if (anonymous && (containingElement == null)) {
throw new AxisFault(Messages.getMessage(
"noContainerForAnonymousType", qName.toString()));
}
writeType code snippet:
if (!makeTypeElement(type, qName, null)) {
return null;
}
How to reproduce the error:
Use WSDL2Java to create client and server-side bindings (with skeleton) from
the attached files.
Compile the javas and deploy the jar to your application server (JBoss in my
case).
Deploy the Web Service using the deploy.wsdd
Try to obtain the WSDL from the deployed service. The following error results:
Fault - makeTypeElement() was told to create a type
"{urn:anontype}>AnonRequest", with no containing element
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
"{urn:anontype}>AnonRequest", with no containing element
faultActor:
faultNode:
faultDetail:
Workaround:
Make sure types are named (note that this is not always a possible solution,
for example for third-party WSDLs, hence Priority=Major).
See Related Issues:
AXIS-1453
AXIS-1431
AXIS-1295
AXIS-1284
AXIS-1277
was:
Error Summary:
Anonymous types are named in the SymbolTable with the ANON_TOKEN prefix (">").
This causes a problem for the makeTypeElement method invoked by writeType.
Initial Diagnostic:
There seems to be a contradiction here, makeTypeElement doesn't allow anonymous
types outside of a containing element, whereas writeType invokes
makeTypeElement specifying "null" as the containing element.
makeTypeElement code snippet:
// Can't have an anonymous type outside of a containing element
if (anonymous && (containingElement == null)) {
throw new AxisFault(Messages.getMessage(
"noContainerForAnonymousType", qName.toString()));
}
writeType code snippet:
if (!makeTypeElement(type, qName, null)) {
return null;
}
How to reproduce the error:
Use WSDL2Java to create client and server-side bindings (with skeleton) from
the attached files.
Compile the javas and deploy the jar to your application server (JBoss in my
case).
Deploy the Web Service using the deploy.wsdd
Try to obtain the WSDL from the deployed service. The following error results:
Fault - makeTypeElement() was told to create a type
"{urn:anontype}>AnonRequest", with no containing element
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
"{urn:anontype}>AnonRequest", with no containing element
faultActor:
faultNode:
faultDetail:
Workaround:
Make sure types are named (note that this is not always a possible solution,
for example for third-party WSDLs, hence Priority=Major).
See Related Issues:
http://nagoya.apache.org/jira/browse/AXIS-1453
http://nagoya.apache.org/jira/browse/AXIS-1431
http://nagoya.apache.org/jira/browse/AXIS-1295
http://nagoya.apache.org/jira/browse/AXIS-1284
http://nagoya.apache.org/jira/browse/AXIS-1277
> WSDL2Java Anonymous Types cause problems for fromJava
> -----------------------------------------------------
>
> Key: AXIS-1495
> URL: https://issues.apache.org/jira/browse/AXIS-1495
> Project: Axis
> Issue Type: Bug
> Components: WSDL processing
> Affects Versions: 1.1, 1.2 Beta
> Environment: Any J2EE Server
> Reporter: Tom Crossland
> Assignee: Ias
> Attachments: anon.wsdl, anon.xsd
>
>
> Error Summary:
> Anonymous types are named in the SymbolTable with the ANON_TOKEN prefix
> (">"). This causes a problem for the makeTypeElement method invoked by
> writeType.
> Initial Diagnostic:
> There seems to be a contradiction here, makeTypeElement doesn't allow
> anonymous types outside of a containing element, whereas writeType invokes
> makeTypeElement specifying "null" as the containing element.
> makeTypeElement code snippet:
> // Can't have an anonymous type outside of a containing element
> if (anonymous && (containingElement == null)) {
> throw new AxisFault(Messages.getMessage(
> "noContainerForAnonymousType", qName.toString()));
> }
> writeType code snippet:
> if (!makeTypeElement(type, qName, null)) {
> return null;
> }
> How to reproduce the error:
> Use WSDL2Java to create client and server-side bindings (with skeleton) from
> the attached files.
> Compile the javas and deploy the jar to your application server (JBoss in my
> case).
> Deploy the Web Service using the deploy.wsdd
> Try to obtain the WSDL from the deployed service. The following error results:
> Fault - makeTypeElement() was told to create a type
> "{urn:anontype}>AnonRequest", with no containing element
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> faultSubcode:
> faultString: makeTypeElement() was told to create a type
> "{urn:anontype}>AnonRequest", with no containing element
> faultActor:
> faultNode:
> faultDetail:
> Workaround:
> Make sure types are named (note that this is not always a possible solution,
> for example for third-party WSDLs, hence Priority=Major).
> See Related Issues:
> AXIS-1453
> AXIS-1431
> AXIS-1295
> AXIS-1284
> AXIS-1277
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
