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

https://github.com/ocpsoft/rewrite/tree/master/integration-gwt

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

~Lincoln


On Tue, Mar 4, 2014 at 12:26 PM, Christian Sadilek <csadilek@redhat.com> wrote:
Hi,

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

Cheers,
Christian

On 2014-02-19, at 6:33 AM, Eric Wittmann <eric.wittmann@redhat.com> 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:
>
> http://example.org/myapp#/CustomerABC/orders/order-17
>
> Does anyone else desire something like this?
>
> -Eric
> _______________________________________________
> errai-dev mailing list
> errai-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/errai-dev


_______________________________________________
errai-dev mailing list
errai-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/errai-dev



--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."