axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandro Monteiro de Souza (JIRA)" <>
Subject [jira] Updated: (AXIS2-3931) Adb generates non compilable code
Date Mon, 21 Jul 2008 21:45:31 GMT


Sandro Monteiro de Souza updated AXIS2-3931:


I attached a propose of correction. I tested and seems to work nicely.

There are three correction points with comments START Correction. You can also make a diff
with revision 648561 (trunk).

> Adb generates non compilable code
> ---------------------------------
>                 Key: AXIS2-3931
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.4
>            Reporter: Sandro Monteiro de Souza
>         Attachments: Bug.wsdl,
> When generate client code for the attached WSDL file, it generates the following non
compilable code line in a ADBBean:
> object.setAddContractFileOut(
>                                                     org.apache.axis2.databinding.utils.ConverterUtil.convertToAddContractFileOut_type0(content));
> Conditions:
> This error occurs when all of the following conditions are true:
> . There are several schemas defined in the WSDL (not in external files);
> . There are a multi-level schema imports; (one imported schema imports another)
> . There is a element in the second level of imports that references the schema self target
namespace ( is this case <xsd:element name="filename" type="tns:filenameType"/>);
> . There are multiple references of the same type in the main schema;
> Possible causes (all found in SchemaCompiler class):
> . The compile method does not compile internal exports, only the external ones;
> . The method getParentSchema and getParentSchemaFromIncludes compiles the included schemas
without the isPartOfGroup flag setted to true;
> . The method finalizeSchemaCompilation cleans up the generated types and further references
to these types are messed up in JavaBeanWriter class (metainf.getSchemaQNameForQName(name)
is null).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message