Roland Weber wrote:
A fallback option is to move from Jakarta to WebServices, exchanging one umbrella for another. That wouldn't move us forward, and the impression we got from Jakarta is that umbrellas are not in favour at the board. As a TLP, we will have a fighting chance to grow the project to the point where it no longer depends on just the two of us. Until that is achieved, we'll be one of those projects that Niall referred to, with community issues because they didn't pass through the Incubator. That's why I thought it was a good occasion to ask for suggestions. The new HttpComponents as well as the old HttpClient we maintain are being used by Apache projects, so coming into the Incubator is not an option for HttpComponents.
I dont consider http support in webservices as a general purpose umbrella. Any Java stack that does SOAP or REST should be using HttpClient unless they are naiive fools who believe that there is someone that actually maintains java.net.HttpUrl, and that persion has actually read the HTTP RFCs.
1. it is used in Axis, XFire, Alpine. I think the only mainstream stack that doesnt use it is the Sun one, but they have the ability to fix bits of java.net, and/or the naiive optimism I mentioned earlier.
2. It would be a good way of kickstarting more pure RESTy stuff in the WS group.
3. this has been raised on ws pmc, we'd love to have the HttpComponents/HttpClient team(s) on board if you want to join.
-steve (still on the WS PMC, incidentally) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
