My personal opinion is that the old URL Rewriter API is easier to use for incoming URLs (requested ones), while LinkTransformer is better for outgoing ones (generated by Tapestry).

c) ComponentEventLinkEncoder - [2], description sounds good, impl looks followable

LinkTransformer works by decorating or advising ComponentEventLinkEncoder. Old URL Rewriter by adding a RequestFilter, so Tapestry itself (actually, the dispatchers) doesn't even see the original requested URL, just the already rewritten one.


Yeah i read your article on v2 about easiness of v1 - also your opinion on using external tools, which i agree with. I'll give Lance's a shot first because it looks a bit easier for me to follow and I think I'll be able to mangle it easier. You had to put an extreme case of URL rewriting as an example for v2! Subdomains and tag mappings!!! /s



Further, if I wanted to build an application with Pages that had a naming convention like PageName1ProvidesMenu, ComponentModeProvidesMenu and using the PageCatalog with some kind of filter that @Matches("*ProvidesMenu") to jam the bootstrap-navbar with these pages, with a bit of URL rewriting magic, sounds like it would allow me to get out of the way of page curation chores more often, no?

Yep. For live class reloading to work with this new annotation you'll create, you'll need to create a ComponentClassTransformWorker and set one entry in the class metadata map (<string, string).

I'm not using live class reloading with my current dev env, not in eclipse, and yeah i know, crazy! But thanks for the pointer, I've used @EJB long enough I should have thought about looking at it's implementation for a howto. ComponentClassTransformWorker2 actually ;)

I had a peek at org.apache.tapestry.services package to see what else was there to poke around with.

The mailing list will get the odd lay question from me, if you're not already accustomed to them already :D

Thanks for replies
CM

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to