Well, it generally depends on what you're doing and how happy you are with the urls, e.t.c. It's true that you can use the page service along with getRequestCycle().getParameter() to get parameters in whatever order they may appear - and if that's what you're after, fine!
ExternalPages do require the params in a specific order - however those params can be of any type, not just strings. Also: - dataSqueezers are used to decode-encode to strings making the process transparent to the developer (you can add your own squeezers, since for complex objects the whole instance is serialized) - ServiceEncoders are easy to writer + make nicer urls On Nov 29, 2007 11:21 PM, Ulrich Stärk <[EMAIL PROTECTED]> wrote: > Hi List, > > I don't really understand when one should use the ExternalService and what > exactly it is good for. > According to the JavaDocs and TiA the external service enables me to bookmark > pages and pass > parameters to them. > But according to my understanding I can create a bookmark to every page in a > Tapestry application > regardless of whether it implements IExternalPage or not. And for the > parameters: If I rely on the > mechanisms provided by the ExternalService the URL parameters to this page > have to be in an exact > order. If I instead used getRequestCycle().getParameter() I can work with > named parameters. > > So where is the difference between a "normal" page that doesn't implement > IExternalPage and doesn't > get accessed through the external service and one that is? > > Cheers, > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
