Sorry for the thread revival, however I am coming up against the same
problem.
I have a page needs to be served via https for some customers and http
for others.
If I request the page via https without the @Secure annotation, all ajax
event urls are incorrectly altered to:
Hi Lenny
Thanks for your answer. I guess my description was somehow incomplete...
OnActivate from the unauthorized page is not called, that's surprising to me.
The user has permission to view the page in general but misses certain
functionality permissions triggered by event callback
I do believe your assumption is correct.
On Oct 28, 2013, at 2:51 AM, mailingl...@j-b-s.de mailingl...@j-b-s.de
wrote:
Hi Lenny
Thanks for your answer. I guess my description was somehow incomplete...
OnActivate from the unauthorized page is not called, that's surprising to
me.
I think you are running into this issue:
https://issues.apache.org/jira/browse/TAP5-2080
Seems due to political issues it will not be fixed,
But the workaround in the issue should work for you.
I feel your pain because I had to implement a similar workaround as well.
On Oct 28, 2013, at 2:35
Thanks Lenny that is exactly it and the solution works great.
Agree with the bug poster and would vote for the issue if it weren't
closed already.
p.
On 28/10/2013 6:05 PM, Lenny Primak wrote:
I think you are running into this issue:
https://issues.apache.org/jira/browse/TAP5-2080
Seems due
Hi,
the If component doesn't have a parameter context. What you need to do
is the following:
1) set parameter row in your grid component (which you probably
already did with property bestellung):
t:grid t:row=bestellung ... /
@Property
private Bestellung bestellung;
2) create a
Hi Nathan,
Am 28.10.13 11:07, schrieb Nathan Quirynen:
Hi,
the If component doesn't have a parameter context. What you need to do
is the following:
1) set parameter row in your grid component (which you probably
already did with property bestellung):
t:grid t:row=bestellung ... /
Hi Andreas!
If you make use of @Property annotation tapestry creates get and set methods
for you. if you mix it with self-written methods you have to set read and
write annotation params to false accordingly to avoid creation. Just have a
look at the @Property documentation.
Jens
Von meinem
On Sun, 27 Oct 2013 11:44:42 -0200, Lenny Primak lpri...@hope.nyc.ny.us
wrote:
I don't think Tapestry-Security works for Ajax requests.
I think it's geared more of blocking access to pages for initial load.
I wouldn't say that before checking the source first.
How can you have AJAX
On Oct 28, 2013, at 8:09 AM, Thiago H de Paula Figueiredo wrote:
On Sun, 27 Oct 2013 11:44:42 -0200, Lenny Primak lpri...@hope.nyc.ny.us
wrote:
I don't think Tapestry-Security works for Ajax requests.
I think it's geared more of blocking access to pages for initial load.
I wouldn't say
Sorry to bring up an old thread, I'm just reading it now - to my
entertainment and learning :)
I've created a JIRA - https://issues.apache.org/jira/browse/TAP5-2210
For the purpose of suggesting an Alternatives section for the tapestry
features that would be commonly used and how to initiate NOT
11 matches
Mail list logo
