Hello all,

 

Thank you for the help.  A couple comments on the solution:

 

1) Although the wsdl2java converter placed my schema in the resources
directory, the Axis2 Service Archiver did not add the schema into the
archive web service file (*.aar).  I resorted to manually copying the schema
into the AAR file (the AAR file is just a ZIP file) each time I ran the
archiver wizard.

2) I played around with the various schemaLocation and namespace attributes
in my WSDL, but I don't know if this caused any problems in the end.
Despite its appearance, the simple namespace "HW" is a valid URI; it's just
a relative one, not absolute.

 

Regards,

 

Matt

 

  _____  

From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 19, 2007 4:57 AM
To: [email protected]
Subject: Re: Problems with Schemas and WSDL in Axis2

 

Can you have a look at with a nighly build.

when generating the code with wsdl2java there is a folder created named as
resources.

under this folder you should have your wsdl and xsd file.

wsdl file should referto the xsd file there. 

i.e it should have and entry like 

<xs:import namespace="HW" schemaLocation="HelloWorldSimple.xsd"/>

Amila.

On 10/19/07, Matthew Fadoul <[EMAIL PROTECTED]> wrote:

Hello all,

 

I'm having trouble using my own schemas in WSDL.  Part of it may be related
to the Axis2 code generation.

 

So, I've made my own "HelloWorld" example.  Here's my process:

 

1) Make WSDL file (attached)

2) Process with Axis2 code generation to build client/server code.  Fill in
a little of the skeleton code.

3) Build inside Eclipse using Ant

4) Package with the Axis2 Service Archiver.

 

I've attached my WSDL and Schema.  The schema has little more than a type
definition based on "xs:string".

 

I've placed my XSD file on a local server.  This is reflected in the
attached WSDL here:

 

< xs:import namespace=" HW" schemaLocation="
http://strawberry/schema/HelloWorldSimple.xsd
<http://strawberry/schema/HelloWorldSimple.xsd> " />

 

By the time the service gets placed on the Axis server, the reference to the
schema in "HelloWorldExternalSchemaService?wsdl" becomes:

 

< xs:import namespace=" HW"
schemaLocation="HelloWorldExternalSchemaService?xsd=
http://strawberry/schema/HelloWorldSimple.xsd"; /> 

 

Unfortunately, Axis can't seem to resolve my schema with the "xsd" option.
Because of this, the schema and all of its types are unresolved.

 

As a side note, I've also toyed with locale schema (i.e. the XSD file is in
the same directory as the WSDL file), though I haven't had much success with
that route either.

 

Questions.  Are there:

Any ideas or advice for integrating schemas with WSDL?  

Any ideas why the code generator is changing the schema location? 

Any glaring mistakes (e.g. namespace problems or DOC/RPC stuff) in my
WSDL/XSD?

 

 

Thank you!

 

Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED]






-- 
Amila Suriarachchi,
WSO2 Inc. 

Reply via email to