[
https://issues.apache.org/jira/browse/AXIS2-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohamed el habib updated AXIS2-3851:
------------------------------------
Attachment: SchemaCompiler.java
Hello everybody,
I'm using axis2 (1.4.1) to generate a web service client with the ADB. I have
the same problem: when wsdl contains an imported schema with an empty target
name space, I get a null pointer exception into
SchemaCompiler.isComponetExists(). You can find here a fix I done. I work for
me.
By
> adb-codegen no longer accepts schemas without targetNamespace
> -------------------------------------------------------------
>
> Key: AXIS2-3851
> URL: https://issues.apache.org/jira/browse/AXIS2-3851
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.4
> Environment: Java by sun 1.5.0.14 (amd64)
> Eclipse SDK
> Version: 3.2.1
> Build id: M20060921-0945 (Debian version: 3.2.1-4)
> Reporter: Xavi Drudis Ferran
> Fix For: 1.3
>
> Attachments: SchemaCompiler.java
>
>
> With Axis1.3 I can generate code with an ant task for wsdl2java , from an
> wsdl file
> that contains an schema with targetNamespace="" (to describe the
> namespaceless xml I get in a RESTful service).
> With Axis1.4 I can no longer generate it.
> There's an exception originating at :
> [java] Caused by: java.lang.NullPointerException
> [java] at
> org.apache.axis2.schema.SchemaCompiler.isComponetExists(SchemaCompiler.java:2723)
> [java] at
> org.apache.axis2.schema.SchemaCompiler.getParentSchemaFromIncludes(SchemaCompiler.java:2670)
> [java] at
> org.apache.axis2.schema.SchemaCompiler.getParentSchema(SchemaCompiler.java:2644)
>
> This is apparently because of commit
> http://svn.apache.org/viewvc?view=rev&revision=627710
> Revision 627710
> Jump to revision: Previous Next
> Author: amilas
> Date: Thu Feb 14 11:30:40 2008 UTC (3 months, 3 weeks ago)
> Log Message: when resolving schemas target namespaces must be matched
> Aparently the namespace from the schema is null.
> Maybe it should be "" or maybe the added condition should accept both
> namespaces being null.
> I'm not sure what else has changed from Axis2 1.3 to 1.4 and whether fixing
> this would introduce
> some other error with empty namespaces, but it seems a regression, hopefully
> easy to fix. I'm sorry
> I can't try to fix it now.
> (the function name is misspelt, it lacks an n before the last t of
> "component", btw, but that's irrelevant).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
