user.setCity(rs.getString("city"));
> user.setCounty(rs.getString("county"));
> user.setPhone(rs.getString("phone"));
> user.setEmail(rs.getString("email&qu
Why not use TAPESTRY-SECURITY by Kalle :)
this is more advanced...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4460330.html
Sent from the Tapestry - User mailing list archive at Nabble.com
On 06/06/2011 01:58 PM, Thiago H. de Paula Figueiredo wrote:
On Mon, 06 Jun 2011 14:34:20 -0300, robnangle
wrote:
Eh I dont understand what you mean here. Am i not setting the user when
somebody logs in with a valid username and password?
I'm sorry, I overlooked the only place user is set.
am sure it does just cant quite figure out where I am going wrong. If
the admin user logs in first, it works 100%.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4459422.htm
On Mon, 06 Jun 2011 14:34:20 -0300, robnangle wrote:
Eh I dont understand what you mean here. Am i not setting the user when
somebody logs in with a valid username and password?
I'm sorry, I overlooked the only place user is set. Having been using
Tapestry since 5.0.5, almost four years ago
l: users-h...@tapestry.apache.org
>
Eh I dont understand what you mean here. Am i not setting the user when
somebody logs in with a valid username and password?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4459326.html
Sent from the
Have you noticed your page code doesn't set the user field anywhere? I
guess you have a logic issue somewhere.
Your JDBC usage is far from recommended. You're opening a connection in
the constructor and reusing it. If you're using Tapestry 5.2+, you'll end
up having two requests using the s
en the working and broken states?
>
Well what I thought was correct. When the admin user logs in, he can view
one correct page. After this any navigation to an admin page will print
false, i.e. he has not passed the admin test,
On 06/06/2011 12:48 PM, robnangle wrote:
Rich M wrote:
Most likely your page is not loading and assigning the adminUser boolean
like you are expecting, and after your initial login, it's not calling
any of that code anymore and thus your privileges appear to regress to a
normal user, when really
thod, as I have used it elsewhere.
However it does not solve the issue. The user seems to be completely
reverting to the previous logged in user after navigating through more than
one page.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4
On Mon, 06 Jun 2011 13:35:01 -0300, Rich M wrote:
Well does it have to be persisted? I call the adminUser() in every class
where it is necessary. The updatePoints() is the constructor so it will
be called when the page is loading?
Absolutely no.
You might want to refresh your knowledge of
ress. The logged in user
display name reverts to the previous logged in user..
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4459203.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
---
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
>
> Yes I agree with you that it is pointless recalculating whether
>
Yes I agree with you that it is pointless recalculating whether its an admin
user or not. However that constructor is defientley being called as the
transfers display in a sidebar and if it was not being called the transfers
would not display (also them transfers being persisted would make more sense
On 06/06/2011 12:20 PM, robnangle wrote:
Rich M wrote:
On 06/06/2011 12:04 PM, robnangle wrote:
No didn't seem to make a difference im afraid. I cant think of anything
that
would revert the user back to the previous logged in user?
My updated code now looks like:
@SessionState(creat
minUser;
>> }
>>
>> public void setAdminUser(boolean adminUser) {
>> this.adminUser = adminUser;
>> }
>>
>> public Object onSubmitFromLogout() throws Exception {
>> user = null;
>> S
if (session != null) {
session.invalidate();
}
return index;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4459081.html
Sent from the Tapestry - User m
public Object onSubmitFromLogout() throws Exception {
user = null;
Session session = request.getSession(false);
if (session != null) {
session.invalidate();
}
return index;
}
--
View
t page will load but after this
> it seems to revert back to the previous user and you will then be unable to
> view admin pages (even though I just logged in as an admin user).
>
> It seems to be setting itself to the previous user for some reason?
>
>
> --
> View th
e will load but after this
it seems to revert back to the previous user and you will then be unable to
view admin pages (even though I just logged in as an admin user).
It seems to be setting itself to the previous user for some reason?
--
View this message in context:
http://tapestry.1045711.
On Mon, 06 Jun 2011 10:18:20 -0300, robnangle wrote:
However it still does not seem to be working.
The problem is that it still does not seem to be clearing.
I have admin pages that only an admin user can view. The code behind
that is working as when i login at first it determines that it is
I have admin pages that only an admin user can view. The code behind that is
working as when i login at first it determines that it is an admin user and
grants them access. The problem arises when I log in as a normal user, then
logout and try log in as an admin user. It will not grant them acces
On Mon, 06 Jun 2011 09:26:26 -0300, robnangle wrote:
Hi All,
Hi!
I create have a @SessionState on my user but when I try logout it is not
fully clearing the session.
@SessionState
private User user;
Setting a @SessionState field to null will remove it from the session, but
just it. And
Essentially i want to destroy the session..
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4458598.html
Sent from the Tapestry - User mailing list archive at Nabble.com
.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4458593.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h
the session.
>
> @SessionState
> private User user;
>
> onSubmitFromLogout(){
> user = null;
> return index;
> }
>
> Is there a specific way to do it?
> Cheers
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Clearing-SessionSta
FromLogout(){
> user = null;
> return index;
> }
>
> Is there a specific way to do it?
> Cheers
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4458525.html
> Sent
his message in context:
> http://tapestry.1045711.n5.nabble.com/Clearing-SessionState-tp4458525p4458525.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: u
.n5.nabble.com/Clearing-SessionState-tp4458525p4458525.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h
29 matches
Mail list logo
