Hi Anne,
Thanks for looking into this. I am not sure if I know how to fix it... I
copied/saved the WSDL file by going to the my service URL
("http://localhost:8080/.../MyService?wsdl";). At that time I had no wsdl
defined in my .aar file. So I what I got was an axis2 generated wsdl. I turned
around and bundled the same wsdl file in my next version of the .aar file.
So, if I want to include my own wsdl file in the .aar file, what is the process
for that? Should not I be able to take the axis2 generated/default wsdl file
and bundle that in my service? I may be missing something here.
I tried the same experiment with the AddressBook example and had the exact same
error. I think the main issue here is creating/using a user-generated wsdl in
the service.
Thanks,
-- MK
----- Original Message ----
From: Anne Thomas Manes <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, October 19, 2007 6:45:47 AM
Subject: Re: Error: Unexpected subelement responseCode
I found some errors in your WSDL. You have three schemas, each with a
separate namespace, and they reference each other, but you neglected
to import the namespaces.
Your second schema references types from the third schema, but it
doesn't import the namespace. Likewise, the third schema references
types from the first schema, but it doesn't import the namespace.
Anne
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
