Hello,

I just started using XFire. I'm using JiBX and Spring (although I don't think the fact that I'm using Spring pertains to this question). I've got some questions regarding the generated WSDL.

I've specified schemas in my spring bean XML file like this:

<bean id="xfireProductService" class="org.codehaus.xfire.spring.remoting.XFireExporter">
       <property name="serviceFactory" ref="jibxServiceFactory"/>
       <property name="xfire" ref="xfire"/>
       <property name="serviceBean" ref="productService"/>
<property name="serviceClass" value="com.pj.service.ProductService"/>
       <property name="style" value="document"/>
       <property name="use" value="literal"/>

       <property name="schemas">
           <list>
               <value>model.xsd</value>
               <value>bean.xsd</value>
           </list>
       </property>
   </bean>

Now, from what I can tell the model.xsd and bean.xsd files are inserted into schema elements in the generated WSDL. This is great and as I would expect it. Also generated in a schema element are lines like this:

<xsd:element name="findInventoryByUnitin0" type="xsd:int"/>

So my theory on this is that for all classes that do no have a JiBX binding, it creates default XSD types. Is this right?

I also get a bunch of messages with multiple parts. It's my understanding that this not not valid SOAP (I'm not 100% on this, however). I think I read that a SOAP body can have only one child. Here's an example of the message with multiple parts:

<wsdl:message name="deleteProductRequest">
<wsdl:part name="deleteProductin0" element="tns:deleteProductin0">
   </wsdl:part>
<wsdl:part name="deleteProductin1" element="tns:deleteProductin1">
   </wsdl:part>
</wsdl:message>

So I think I want to "wrap" this. How can I do that. Or is this okay?

What needs to be included in my schema files in order for this work correctly?

I don't mind digging into he code (in fact I prefer it). Any tips on what classes I should look at to figure this out?

Thanks,

Ian


---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to