Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Chris Mylonas
I'll check out both in any event. Yes, it's crazy! :p It shouldn't be hard to make it work in your environment. Fixed. open another terminal and run `mvn clean package` reload page, viola. took me a 2nd go at live class reloading troubleshooting - "build automatically in your ide" sor

Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Thiago H de Paula Figueiredo
On Tue, 07 Oct 2014 11:48:55 -0300, Chris Mylonas wrote: You had to put an extreme case of URL rewriting as an example for v2! Subdomains and tag mappings!!! /s v2 is actually exactly the same as v1, but without the outgoing (generated) URL rewriting, as LinkTransformer is better as it.

Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Chris Mylonas
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

Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Thiago H de Paula Figueiredo
On Tue, 07 Oct 2014 08:53:17 -0300, Chris Mylonas wrote: hi tapestry users, Hi Questions/observations/notes/feedback-or-guidance a) LinkTransformer - looks like PageRenderLinkTransformer would be an easier thing to implement b) URLRewrite v2 from thiago - there a naming convention inv

Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Chris Mylonas
Yeah very good point, I've not been a fan of naming conventions since first looking at tapestry and @Annotations were new to me when I first touched deving again - handy "new" thing in java indeed :) I'm on a deadline for this Friday so it'll have to be put into the scratch-the-itch bag unt

Re: tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Lance Java
I'd probably use an explicit @ProvidesMenu annotation rather then naming convention magic. Much nicer for the next poor developer who has to maintain the code :) On 7 Oct 2014 12:53, "Chris Mylonas" wrote: > hi tapestry users, > > whatever responses i get i'll tack onto here [1] > > i have a page

tapestry-5.4 way of url -> page that is not page class name

2014-10-07 Thread Chris Mylonas
hi tapestry users, whatever responses i get i'll tack onto here [1] i have a page, with context, but i want to access it from another url? e.g. localhost:8080/normalname/5 localhost:8080/differentname/5 or more accurately localhost:8080/services/ethernet localhost:8080/products/antivirus the