Em Fri, 16 Oct 2009 04:28:57 -0300, Alexander Reelsen
escreveu:
This is exactly what I want. But why does this not go "in line" with my
url rewriting question? If I have three parameters for the onactivate,
where else instead of the url are those constructed of?
That's what Tapestry calls t
Hi Igor
> On Thu, Oct 15, 2009 at 11:11 PM, Alexander Reelsen
> wrote:
>> @RequestMapping(value="/{tenant}/{user}/reservations/{id}",
>> method=RequestMethod.GET)
>>
> URL rewrittng is indeed not covered by the book. It is not possible in
> Tapestry to map different methods of a page to differen
Hi Alexander,
On Thu, Oct 15, 2009 at 11:11 PM, Alexander Reelsen wrote:
> Hi,
>
> after reading the new german book on Tapestry I am thinking to take a
> closer look at it. It is a very nice and clean structured book, which
> can be read quite easily at a rainy weekend. Very well done.
>
It's
Em Thu, 15 Oct 2009 18:11:04 -0300, Alexander Reelsen
escreveu:
Hi,
Hi!
One question I could not figure out from the book is a question
regarding complex url redirects. With complex I mean injecting certain
properties based on the url (like spring 3 supports with its
requestmapping annota
Hi,
after reading the new german book on Tapestry I am thinking to take a
closer look at it. It is a very nice and clean structured book, which
can be read quite easily at a rainy weekend. Very well done.
One question I could not figure out from the book is a question
regarding complex url redire
