Your WSDL and schema look okay, except that "HW" is not a valid URI. Namespace names must be a valid URI. I don't know if this might be your problem, though.
Anne On 10/18/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"; > /> > > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
