ster, if memory servers, was that the session is
still somewhat valid in the context of using the request object after a call to
session.invalidate().
good luck
hoth256
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933476#3933476
Reply to the
Thanks Scott! I have to say you are really on top of things, I see your posts
all over these forums.
I am able to reproduce the intended behavior in 4.0.2 - the same as 4.0.1sp1.
Is this behavior specified in the newer servlet spec? Just wondering why the
results were different in JBoss 3.2.5?
New infomation:
I was NOT able to reproduce the issue in [3.2.5 (build: CVSTag=JBoss_3_2_5
date=200406251954)]
I am able to reproduce the issue in [4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1
date=200502160314)]
Downloading 4.0.2 right now - wll post the results.
View the original post :
http
Hello this is a duplicate posting of
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67511 (my apologies
for the duplicate - but I believe this forum is more apporpriate).
Background
I'm using j_security_check for form based auth. using a custom login module.
Problem:
Upon logging
Hello all,
I think I might need to get a handle to the LoginContext to logout as well...
Background
I'm using j_security_check for form based auth. using a custom login module.
Problem:
Upon logging in using the custom login module, things work as expected -
however, upon logging out by invalid
Correction:
In the last post I say that I get an exception in JBoss 3.2.2. Actually, the exception
is thrown in JBoss 3.2.3.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3828760#3828760
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=post
Background:
Axis provides a way to use pluggable providers - excerpt from
org.apache.axis.deployment.wsdd.WSDDProvider (Axis source code) for method: private
static void loadPluggableProviders()
| /**
| Look for file META-INF/services/org.apache.axis.deployment.wsdd.Provider
| in all the
