Replying to the dev list if you don't mind ;-) On 4/26/07, Thomas TERMIN <[EMAIL PROTECTED]> wrote:
Is this HttpProviderEndpoint an replacement for the ProviderProcessor? http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderEndpoint.java?view=markup&pathrev=508584
This is a work I began some time ago to better support soap, split the provider endpoints from the consumer endpoints This is clearly unfinished.... The goal was to rewrite the HTTP endpoints so that they are easier to extend. There are some derived endpoints that use the new soap2 module for a better SOAP support. The server side is in a workable state, but the client side has not been finished. I have also worked on integrating Apache CXF (which is the "next" version of XFire) ... And it seems to be quite usable so we have two components that I checked in this week. The main point is that it should bring a better jax-ws support, including on the tooling side, and also add support for WS-RM on the BC side. I don't think maintaining the soap2 module is a good idea given that CXF provides a better support and has a load of developers to support it. At the same time, the work that has been done on HTTP and JMS endpoints is good. I don't think CXF has enough support for HTTP / JMS when not using SOAP. Thoughts ? -- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
