Hi Dan,
Still does not fix the problem. (ArrayOfString definition is still not
generated)
This is the configuration file I use (had to modify the one that you sent)
1. The JaxbServiceFactory namespace was incorrect
2. JaxServiceFactory does not have a constructor that takes the transport
manager and binding provider
<bean
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="urlMap">
<map>
<entry key="/EchoService">
<ref bean="echo" />
</entry>
</map>
</property>
</bean>
<bean id="xfire.myjaxbServiceFactory"
class="org.codehaus.xfire.jaxb2.JaxbServiceFactory" singleton="true">
<constructor-arg index="0">
<ref bean="xfire.transportManager" />
</constructor-arg>
</bean>
<!-- Declare a parent bean with all properties common to both
services -->
<bean id="echo" class="org.codehaus.xfire.spring
.remoting.XFireExporter">
<property name="serviceFactory">
<ref bean="xfire.myjaxbServiceFactory" />
</property>
<property name="xfire">
<ref bean="xfire" />
</property>
<property name="serviceBean">
<ref bean="echoBean" />
</property>
<property name="serviceClass">
<value>org.codehaus.xfire.spring.example.Echo</value>
</property>
<property name="namespace">
<value>http://www.abc.com/myproject </value>
</property>
</bean>
With this change I had to make use of JSR 181 @WebService annotation on the
Echo interface which I want to avoid (I can live with this though)
Does this configuration generate the required "ArrayOfString" definition at
your end?
Regards,
Swami
--
View this message in context:
http://www.nabble.com/Any-Workarounds-for-XFIRE-739%3A-wsdl%3A-doesn%27t-describe-pojos-in-xsd---tf2839974.html#a8554901
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
