Are you generating your service from wsdl? Or are you generating your
xmlbeans then writing your service class using those?
If XFire is "cleaning" the imports for you (i.e. removing the
schemaLocation), you might want to set the "wsdlBuilder.cleanImports"
property to "true". In spring form:
<bean clas="...ServiceBean">
<property name="properties">
<map>
<entry>
<key>wsdlBuilder.cleanImports</key><value>true</value>
</entry>
</map>
</property>
This is obscurely documented here and highlights a need for a
documentation reorganization :-)
http://xfire.codehaus.org/services.xml+Reference
Does that help at all?
- Dan
Tim Robertson wrote:
Hi,
I have a WSDL with an xsd:import bringing in another schema in a
different namespace.
I XMLBeans it, write some methods and expose them using XFire.
My generated WSDL is importing the namespace but not the schema – is
there a way to force it to do this?
What I get out is:
<xsd:import
namespace="http://digir.net/schema/conceptual/darwin/2003/1.0"/>
But I’d either like it to include the Schema inline or have a
<xsd:import namespace="http://digir.net/schema/conceptual/darwin/2003/1.0";
schemaLocation="http://digir.net/schema/conceptual/darwin/2003/1.0/darwin2.xsd"/>
Is there anything I can add to the XFire Spring config to force this?
(The Configurator seems to be removed.
http://docs.codehaus.org/display/XFIRE/Generating+WSDL+with+Schema+for+XMLBeans?decorator=printable)
I pretty sure this is user error on my part…
Thanks,
Tim
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
