Hi,
I experienced the same problem you had with a pojo service I exposed
like you did it.
You have to change two things to make it work. First you should define
an interface your service implements. The next thing is to configure
this interface in the jsr181 endpoint declaration.
I hope I could help. Please report back if it worked for you.
greetings
Christian
public interface SubmitOrderService {
public Order submitOrder(String description, double price);
}
public class SubmitOrderServiceImpl implements SubmitOrderService {
public Order submitOrder(String description, double price) {
Order order = new Order(description, price);
return order;
}
}
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";
xmlns:serviceNS="http://edgenet.com";>
<classpath>
<location>.</location>
</classpath>
<jsr181:endpoint service="serviceNS:Local_OrderService" endpoint="Local_OrderService-10ebf2af9aa-478322"
pojoClass="com.edgenet.service.SubmitOrderServiceImpl" serviceInterface="com.edgenet.service.SubmitOrderService"
style="wrapped"/>
</beans>
--
Christian Schneider
---
http://www.liquid-reality.de
KBerthelot schrieb:
I've created a simple pojo that I'm exposing as a web service using the http
and jsr181 components. The service consists of one operation (submitOrder)
that returns an Order object (which is a basic java bean exposing 3
properties).
The wsdl generated is missing the definition of the complex type "Order".
The definition of the submitOrderResponse correctly refers to "ns1:Order",
but that type is not defined in the wsdl and causes the web service client
generation to fail.
