Hi,
this is an idea, but I was hoping to have direct access to the request.
In tapestry3 there was a direct way to access the Visit Object, and the ognl
was well documented, but it seems that there is no more similar in tapestry5.
Thank you,
larzeni
> Sent: Saturday, April 28, 2018 at 12:41 AM
Yeah, that was my old way of doing this thing, but it ties classes too much, so
I discarded that code.
Thank you,
larzeni
> Sent: Saturday, April 28, 2018 at 12:49 AM
> From: "pico.dev"
> To: "Tapestry users"
> Subject: Re: Access request from tml / standard servlet api role support
>
> Maybe o
Hi Kalle,
we are forced to use spring security, and cannot migrate to shiro.
Beside it, I don't like the idea to glue my code to external libraries, using
annotations or other code that may have a different lifecycle.
I can wait as I want to update my code, but, if there is a security issue, I
m
Hi Luca,
Component parameters syntax is built about binding expressions [1], i.e.
"prefix:expression".
By default the prefix is "prop:", unless explicitly overridden for specific
parameter [2].
You can find detailed explanation for property expressions, including its
BNF grammar, in official Tap
On Sat, Apr 28, 2018 at 7:51 AM, Luca Arzeni wrote:
> Hi,
>
Hello, Luca! (Ciao? :D )
> this is an idea, but I was hoping to have direct access to the request.
> In tapestry3 there was a direct way to access the Visit Object, and the
> ognl was well documented, but it seems that there is no mor
Hello, everyone!
On Sat, Apr 28, 2018 at 8:45 AM, Dmitry Gusev
wrote:
> As others pointed in this thread, the Tapestry way of dealing with your
> requirement is to create a new component,
> similar to `t:If`, that would accept a role name as it's parameter so you
> could render it's body conditi
