This definitely works, you can look at the booking example for a functioning
example. I suggest that you set a breakpoint in your
authenticator.authenticate() method, then once its hit set another breakpoint
in BijectionInterceptor.aroundInvoke() (after invocation.proceed() is called)
to
Thank you for your response.
I will try debugging, but I'm anxious about the results becouse single access
or few multiple access is no problem.
I'm thinking now that the same cause of my another topic.
http://www.jboss.com/index.html?module=bbop=viewtopict=129224
Informtion:
I using JMeter
Bit off topic. But curious is the Identity no longer needed to do
authentication with?
I see you are injecting it but never setttng it. Is this then still going
through Seam security or your own?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4126149#4126149
Certainly, the Identity is never used.
My authentication process is three step.
1.Tomcat Authentication
used by FORM:org.jboss.web.tomcat.security.ExtendedFormAuthenticator
2.Seam Authentication
used by Identity:SessionManager class
3.Own application Authentication
used by RDB:Authenticator
What is the declaration of User?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4124313#4124313
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4124313
___
jboss-user mailing list
nickarls wrote : Well, if its not auto-create it will be null the first time
referenced. Add a create=true to the @In annotation.
public class RegisterAction {
| @In(create=true )
| private User user;
2008-1-29 16:54:00 com.sun.facelets.FaceletViewHandler handleRenderException
|
Hi,
Normally if you get exception like
@In attribute requires non-null value
then its something wrong with your configuration.
Change the DEBUG level in your log4j.xml (or whatever you use) and check the
complete log from application startup.
Also check whether you have seam.properties
Well, if its not auto-create it will be null the first time referenced. Add a
create=true to the @In annotation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4124253#4124253
Reply to the post :
seam is searching for a componenent called nomeEndereco.
Because it can't find one it throws an exception.
What did you expect to happen with @In
alex
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104085#4104085
Reply to the post :
This thread actually solved my problem, indirectly:
http://www.jboss.com/index.html?module=bbop=viewtopict=112375
The key is:
One other potential trap is that I have just upgraded from Seam 1.2.1 to 2.0b1
and managed-persistence-context has been moved from namespace core to
persistence. If
10 matches
Mail list logo
