> Hmm. Can't say that I've ever perceived REST as much more than a
> buzzword
One of these things that started out as an architectural pattern, and
got hijacked for a thousand different interpretations. If it 'has'
REST, it's gotta be good ;-)
Eelco
--
On 10/12/07, Roland Weber <[EMAIL PROTECTED]> wrote:
> > I'd keep server side separate, but a rest-centric server side stack
> > (with no attempts to support WSDL) would be appealing, though restlets
> > exist for that purpose.
>
> Hmm. Can't say that I've ever perceived REST as much more than a
Hi Steve, Niclas,
>>> Any Java stack that does SOAP or REST should be using
>>> HttpClient
>>
>> That seems to indicate that it should be a TLP in its own right.
>
> you want that, you get my support.
Thanks for your encouragement. I'm currently drowned in work,
but I intend to kick off the (hop
Niclas Hedhman wrote:
On Monday 08 October 2007 18:37, Steve Loughran wrote:
Any Java stack that does SOAP or REST should be using
HttpClient
That seems to indicate that it should be a TLP in its own right.
you want that, you get my support.
Besides WS, we have;
- Maven do the http clien
On Monday 08 October 2007 18:37, Steve Loughran wrote:
> Any Java stack that does SOAP or REST should be using
> HttpClient
That seems to indicate that it should be a TLP in its own right.
Besides WS, we have;
- Maven do the http client stuff... the naive version??
- Ivy would be in the same bo
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
t
