Same here - would have preferred #1 but implemented #2 because it was much
simpler
On Wed, 17 Feb 2010 13:09:25 +0100, Peter Stavrinides
wrote:
Hi Uli,
I opted out of 3, since I don't use Spring, so thought it would be overkill
bringing too much baggage. I would love to see an actual examp
ginal Message -
From: "Piero Sartini"
To: "Tapestry users"
Sent: Tuesday, 16 February, 2010 22:59:51 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: integrating a web services stack
> That would be for RESTful web services only. Did you ever have to expos
> That would be for RESTful web services only. Did you ever have to expose a
> service via SOAP?
You are right, this is useful for RESTful services only. Never had to
expose a SOAP service within a pure tapestry application, but a few
where I am doing this from an EJB backend. But that's overkill
That would be for RESTful web services only. Did you ever have to expose a
service via SOAP?
Uli
On 16.02.2010 20:40 schrieb Piero Sartini:
Which solution are you using and why? Are there others I haven't thought of?
I am using tapestry-resteasy if I need to make a service available.
> Which solution are you using and why? Are there others I haven't thought of?
I am using tapestry-resteasy if I need to make a service available.
Piero
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
Fo
Hi folks,
I'd like to know how you are integrating a web services stack to expose services used by your pages
as a web service. For me there are several options:
1. Most stacks come with a servlet that handles requests to the web services. One could write a
wrapper around that servle
