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 example of 1, it could be interesting... but I settled for a version of 2, from what I understood this was the simplest approach to get working.
Cheers, Peter -- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Please visit http://www.albourne.com/email.html for important additional terms relating to this e-mail. ----- Original Message ----- From: "Piero Sartini" <li...@pierosartini.de> To: "Tapestry users" <users@tapestry.apache.org> 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 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 if you don't have it in place already. Piero --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
