The Map idea got me thinking. The ExternalService, IExternalPage & ExternalLink could act as an integration point between a Tapestry apps and Servlet/JSP apps. Even when running in the same Servlet context.
This was how I was using the ExternalService. I had JSP's calling Tapestry in the same Servlet context. <servlet-mapping> <servlet-name>TapestryServlet</servlet-name> <url-pattern>/tap/app</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>LegacyServlet</servlet-name> <url-pattern>/jsp/legacy</url-pattern> </servlet-mapping> If we were to go down this approach I think we should make the external service URL as normal as familiar as possible for Servlet/JSP users, ie: //localhost/app/pagename?param1=value1¶m2=value2 We could have Tapestry presume the service is external if the 'service' parameter is not defined. With the parameters in think they should go through as Strings and not use the DataSqueezer, as external apps wont have access to this stuff. With IExternalPage: public void setup(Object[] params, IRequestCycle cycle); rename: public void initPage(Map params, IRequestCycle cycle); _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
