Brian K. Wallace wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So what I'm gathering from this is: 1. Defaulting friendly URLs from a user perspective is a plus but has a drawback of current implementation in both a hivemodule and web xml.
"drawback of breaking backwards compatibility" and having to update configuration files
3. Somewhat off-topic, the need for multiple types of links is not clear. (ideally, I'd like to see a single @Link and have Tapestry figure out what kind it needs to be by parameters, URL, or other identifying marker.
This is a bad summary. We were just talking about PageLink/Service and ExternalLink/Service. They are essentially the same: loadPage, initPage, renderPage, returnPage. The only difference is if you have any parameters to pass the page for it to initialize itself with.
There is no talk (I am not qualified to talk) of confusing this very straight forward behavior with ActionLink or DirectLink, which deal with more complicated scenarios and doing callbacks on particular components within a page, blah blah blah.
If I create an Page/ExternalLink I am fully aware that the page has only as much information as I pass to it through the parameters, nothing more. That's the whole point. I think we can work on refactoring these together without having to deal at all with the issues of rewind or state management.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
