Yes, I like this idea too.

Is there any chance of reusing path parameter stuff from errai-jaxrs? I feel like it would be nice if Errai Navigation used the same syntax (and impl!) as JAX-RS for doing this.

As for URL rewriting, I also like that idea. I guess itís somewhat related to Ericís proposal, but it will also depend on using HTML5 history.pushState() in order to remove the hash on browsers that support it. Johannes Barop has an implementation of this that claims to be mostly compatible with GWTís History class:

I think it should be possible to tackle path parameters with hashes, then hash elimination (rewrite-and-pushState support) as a separate follow-on item. Does that make sense?


On Mar 4, 2014, at 1:48 PM, Lincoln Baxter, III <> wrote:

Yes, this would be extremely useful. Also take a look at this:

I think it could be useful to integrate (or do something like) this.


On Tue, Mar 4, 2014 at 12:26 PM, Christian Sadilek <> wrote:

I think this would be a great addition. Other frameworks (i.e. Angular.js) support that.


On 2014-02-19, at 6:33 AM, Eric Wittmann <> wrote:

> Hey guys.  I was wondering if anyone else would be interested in
> expanding the page navigation path support.  Currently I think
> @Page(path="blah") only supports relatively basic tokens.  Additionally,
> the @PageState feature expresses the state values similar to query params.
> What I would like to do is something like this:
> @Templated
> @Page(path="/{customerId}/orders/{orderId}")
> public class OrderDetailsPage extends Composite {
>   @PageState String customerId;
>   @PageState String orderId;
> }
> This would allow a very flexible system for generating interesting URLs.
>  So the URL for my app might look like:
> Does anyone else desire something like this?
> -Eric
> _______________________________________________
> errai-dev mailing list

errai-dev mailing list

Lincoln Baxter, III
"Simpler is better."
errai-dev mailing list