On Sun, 27 Jan 2013 10:47:08 -0200, John wrote:
So, I can pick up the /UserName in my index page and forwards to the
required page, although of course that will limit me to only handling 1
parameter linked to 1 page.
Actually, you can have as much parameters as you want:
onActivate(Event
in the url. Is there some
way to reference the root context in my layout paths?
John
- Original Message -
From: Thiago H de Paula Figueiredo
To: Tapestry users
Sent: Sunday, January 27, 2013 12:35 PM
Subject: Re: handling parameters passed through the url path
On Sun, 27
On Sun, 27 Jan 2013 10:13:33 -0200, John wrote:
is there a root page then, do I need to program this in my Index page,
or am I better something like this
The Index page is the root page.
somedomain.com/p/JackSmith
Where p is a page and JackSmith is the username?
If you'll need more stuff
, January 27, 2013 11:45 AM
Subject: Re: handling parameters passed through the url path
On Sun, 27 Jan 2013 09:39:36 -0200, John wrote:
> Suppose I want to pass a parameter like this:
> http://somedomain.com/JohnSmith
> instead of http://somedomain.com?username=JohnSmith
On Sun, 27 Jan 2013 09:39:36 -0200, John wrote:
Suppose I want to pass a parameter like this:
http://somedomain.com/JohnSmith
instead of http://somedomain.com?username=JohnSmith
so the parameter looks like a subdirectory.
Can a tapestry page plus some kind of service hande this?
That's the pa
Easy, I would go as far as to say that this is the preferred way in
Tapestry. See:
http://tapestry.apache.org/page-navigation.html
for examples of onActivate() and onPassivare().
/Mats
Mats AnderssonRonsoft AB -
Fridhemsvägen 8 - 372 25 RonnebyTel. 073
