Re: Access request from tml / standard servlet api role support

t;users@tapestry.apache.org> > Subject: Re: Access request from tml / standard servlet api role support > > Hello, everyone! > > On Sat, Apr 28, 2018 at 8:45 AM, Dmitry Gusev <dmitry.gu...@gmail.com> > wrote: > > > As others pointed in this thread, the Tape

Re: Access request from tml / standard servlet api role support

: "Tapestry users" <users@tapestry.apache.org> > Subject: Re: Access request from tml / standard servlet api role support > > On Sat, Apr 28, 2018 at 7:51 AM, Luca Arzeni <l.arz...@iname.com> wrote: > > > Hi, > > > > Hello, Luca! (Ciao? :D ) > > > >

Re: Access request from tml / standard servlet api role support

rs" <users@tapestry.apache.org> > Subject: Re: Access request from tml / standard servlet api role support > > Hi Luca, > > Component parameters syntax is built about binding expressions [1], i.e. > "prefix:expression". > > By default the prefix is "

Re: Access request from tml / standard servlet api role support

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

Re: Access request from tml / standard servlet api role support

quot;pico.dev" <pico@gmail.com> > > To: "Tapestry users" <users@tapestry.apache.org> > > Subject: Re: Access request from tml / standard servlet api role support > > > > Hi, > > > > Maybe you can implement a new conditional component t

Re: Access request from tml / standard servlet api role support

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

Re: Access request from tml / standard servlet api role support

le Korhonen" <kalle.o.korho...@gmail.com> > To: "Tapestry users" <users@tapestry.apache.org> > Subject: Re: Access request from tml / standard servlet api role support > > Tapestry-security (http://www.tynamo.org/tapestry-security+guide/) supports > request.is

Re: Access request from tml / standard servlet api role support

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" <pico@gmail.com> > To: "Tapestry users" <users@tapestry.apache.org&g

Re: Access request from tml / standard servlet api role support

AM > From: "pico.dev" <pico@gmail.com> > To: "Tapestry users" <users@tapestry.apache.org> > Subject: Re: Access request from tml / standard servlet api role support > > Hi, > > Maybe you can implement a new conditional component that chec

Re: Access request from tml / standard servlet api role support

Tapestry-security (http://www.tynamo.org/tapestry-security+guide/) supports request.isuserInRole and provides components similar to the one suggested, i.e. SAVE DATA Kalle On Fri, Apr 27, 2018 at 3:41 PM, pico.dev wrote: > Hi, > > Maybe you can implement a new

Re: Access request from tml / standard servlet api role support

Maybe other alternative is create a base page class that has this and some/all application pages extends @Inject RequestGlobals m_requestGlobals; public boolean isUserAdmin() El sáb., 28 abr. 2018 a las 0:41, pico.dev () escribió: > Hi, > > Maybe you can implement a new

Re: Access request from tml / standard servlet api role support

Hi, Maybe you can implement a new conditional component that checks the role and render or not its body. Something like this: SAVE DATA See https://tapestry.apache.org/component-rendering.html Regards, El sáb., 28 abr. 2018 a las 0:12, Luca Arzeni () escribió: > Hi,