I've proposed a patch.
Please don't blame me, it's my first one for Tapestry ;-)
Nicolas Bouillon a écrit :
Done.
https://issues.apache.org/jira/browse/TAPESTRY-2763
I've enclosed a test project.
Howard Lewis Ship a écrit :
I think you are right; there is definitely some interference between
@Secure and your activation context. Please add an issue.
On Thu, Mar 25, 2010 at 11:50 AM, Nicolas Bouillon
<nico...@bouil.org> wrote:
Hi,
I have a major (i'm close to putting my app in production) issue
with the
@Secure.
I have a page with the following onActivate :
public void onActivate(String domainName, Integer domainId)
i have the corresponding on passivate
public Object[] onPassivate() {
return new Object[] { domainName, domainId };
}
The parent class of my page is annoted with @Secure
When i get
httpS://localhost/myPage/bouil.org/42 everything is fine
when i get http://localhost/myPage/bouil.org/42 (non https),
I got a 302 redirected to
http://localhost/myPage/$N/$N
So the context is lost !
I'm running Tapestry 5.1.0.5
Any help will be greatly appreciated.
Nicolas.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
