Hi Ken, I got your example working by doing some small changes. First I made the service and endpoint names easier and made sure they match in the http and jsr definition. Btw. I wonder why it worked at all with the original definitions. But perhaps I don´t completely understand servicemix here.
But the thing that really made the difference is that I used the namespace of your java package in the xmlns:serviceNS. It seems like a complex object is only included in the wsdl if it is in the same namespace as the service itself. I think this could be a bug in servicemix or xfire. Perhaps Guillaume can comment on this. Best regards Christian <?xml version="1.0" encoding="UTF-8"?> <beans xmlns:http="http://servicemix.apache.org/http/1.0"; xmlns:serviceNS="http://service.edgenet.com";> <http:endpoint service="serviceNS:OrderService" endpoint="soap" role="consumer" locationURI="http://localhost:8080/Order"; defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; soap="true"/> </beans> <?xml version="1.0" encoding="UTF-8"?> <beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"; xmlns:serviceNS="http://service.edgenet.com";> <classpath> <location>.</location> </classpath> <jsr181:endpoint service="serviceNS:OrderService" endpoint="soap" pojoClass="com.edgenet.service.SubmitOrderService" serviceInterface="com.edgenet.service.SubmitOrder" style="wrapped"/> </beans> Ken Berthelot schrieb:
Thanks for the response, but still no luck. I added a SubmitOrder interface (and had SubmitOrderService implement it) and referenced it in the jsr181 config:
-- Christian Schneider --- http://www.liquid-reality.de
