Geronimo Web Service Stack

Goals

• JAX-RPC
• JSR 109 (link to EWS proposal http://wiki.apache.org/ws/FrontPage/Proposals/EnterpriseWebServices)

What We have Now

A Web Service is modled by two GBeans , POJOWSGBean or EJBWSGBean. The Configuration Builder generate the Configuration for deployed Web Service.

(TODO fix the configuration Builder to ususal interface.)

Decisions / we need to discuss following

problem 1:How to pass the SOAP request from geronimo Web container to Axis

• Axis uses a one servlet to serve all the Web Service requests, then it is not very clear how the information in the web.xml should be handled. If we go for using number of Servlets it is not clear how the Axis keep the deployment configurations. This is the basic problem stand against making each Web Service up/down using a GBean. I saw three approches.

I should be able to write a EngineConfiguration (Axis specific) maintained by Geronimo so we start and run Axis completly in Geronimo control. As #2 approch shows Dummy Servlet will direct the incoming message to AxisGbean but we have to decide on our goals for the WS- stack.

problem 2:How to store the deployed Gbean configurations in Axis GBean

The current implementation is stateless - AxisGBean forgets the Web Services deployed when shutdown. The Axis GBean should keep track of the configurations and start them.

TODO

1. Get the EJB Web Service test up
2. Get the complex type test runing