If you are after full SOAP web service support it might make more sense to wire in a framework like Axis or Glassfish Metro directly into web.xml and not tie it to Tapestry pages per se.
Which does raise a follow up question... has anyone successfully wired Tapestry IOC with a web service framework, so we can have Tapestry control the lifecycle of the web service implementation, inject other services into it, etc, etc? Thanks, Alfie. -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 19 May 2009 22:47 To: Tapestry users Subject: Re: again on webservices Em Tue, 19 May 2009 15:57:36 -0300, Andrea Chiumenti <kium...@gmail.com> escreveu: > I have a simple question: > may a T5 page behave like a webservice (soap) ? Yes. Why not? :) You can use Tapestry's templating engine to generate the answer or use another code or framework to generate the answer and return it as a StreamResponse. -- Thiago H. de Paula Figueiredo Consultor, desenvolvedor e instrutor em Java http://www.arsmachina.com.br/thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
