This seems like a servlet-filter type of thing. A legacy servlet recieves the original request and transforms it into a Tapestry request. Does the HTTP query parameter parsing and builds a new request that is in a format that can be used by a Tapestry engine service.
Use RequestDispatcher.forward() to let Tapestry handle the request from there. Problems: that initial request sets the implicit base address for relative URLs (to static resources) ... may not be the right base. In that case, send a redirect and let the client start a second round trip. -- [EMAIL PROTECTED] http://tapestry.sf.net > We work with an ordering system that's been around for a long time. > (Fat-Client Java. yeah!) > > Way back, (waaay before I ever heard of Tapestry), we built a simple > servlet-based reporting tool that > would pull and display orders and thier line items. Used URLs like: > > (show an order) > http://192.168.0.4:8080/l3_iw/COReport?ORDER_NUMBER=828661&REVISION=7 > (potentially show a list of orders) > http://192.168.0.4:8080/l3_iw/COReport?ORDER_NUMBER=828661 > (show a list of orders that match) > http://192.168.0.4:8080/l3_iw/COReport?TELCO_CIRCUIT_NUMBER=AD3456-345 > > Over time the ordering system has been integrated with Vitria Businessware > (process engine) and > part of that was passing in the URLs we use for the report into Vitria. This > enabled users in other systems around the > company to quickly have a look at any orders in our system. We also offered > to provide enough info to the Vitria side > to build the URLs on the fly, but they were not interested in that. > > Turns out that out there in Vitria-space, they are storing these URLs and > using them often (1000 hits/day). This was not > supposed to happen. Which brings me to the point of my message. > > Been toying with the idea of converting the reports (JSP based) to the > Tapestry way. The old report system has expanded greatly > and is ripe to be "tapestrized". But, the new system still needs to respond > to the old URLs pumped in from Vitria-space. > > Been looking at Engine Services but I believe that the URLs produced and > understood by Tapestry are not compatible with > the old URLs. right? > > I could make some servlets that recieve the old URLs and transform them into > Tapesrty friendly request parameters, then forward, but I'm wondering how > hard it would be to avoid this. > > Oh yeah, I'm using Tapestry 2.1 ('cuz Spindle 1.1alpha1 isn't done! yet.) > > Any thoughts? > > Geoff > > Geoffrey Longman > Intelligent Works Inc. > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
