You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Michal Hlavac <hl...@hlavki.sk> on 2005/08/31 16:32:18 UTC

protected page and tapestry 4

hello,

I have tapestry3 webapp... I want to rewrite it into tapestry4.
I have in tapestry3 BasePage and ProtectedPage

Every descendant of ProtectedPage need to be logged in. In not logged
in, then login.page is shown.
Every descendant of BasePage is ok without login too...

is this philosophy also good for tapestry4?

thanks, miso

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: protected page and tapestry 4

Posted by Kevin Menard <km...@servprise.com>.
On Aug 31, 2005, at 12:29 PM, Michal Hlavac wrote:

> Kevin Menard wrote:
>
> what does it mean "should be"? is there some better way???

It means it worked for me and I see no reason why it won't work for  
you.  But I make no guarantees ;-)

-- 
Kevin

Re: protected page and tapestry 4

Posted by Michal Hlavac <hl...@hlavki.sk>.
Kevin Menard wrote:
> Michal Hlavac wrote:
> 
>> is this philosophy also good for tapestry4?
> 
> Yes, you should be fine.  I did have an issue setting a callback
> property on a page instance however.  Using an abstract setter method
> and marking the field persistent fixed the issue.

what does it mean "should be"? is there some better way???

thanks, miso

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: protected page and tapestry 4

Posted by Kevin Menard <km...@servprise.com>.
Michal Hlavac wrote:

> is this philosophy also good for tapestry4?

Yes, you should be fine.  I did have an issue setting a callback
property on a page instance however.  Using an abstract setter method
and marking the field persistent fixed the issue.

-- 
Kevin

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org