Got it. It was unable to call my method as it was not included in the web.inf
as SJSAS requires EJBs to be declared.
It now works but:
I traced down with the debugger and it generated some exception down there
which did not surface (which, IMHO, would rather be thrown/logged). It simply
adds a
You can override the messages. See this post:
http://www.jboss.com/index.html?module=bbop=viewtopict=101074
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030409#4030409
Reply to the post :
In my last message, I sound like the problem was solved but that is not the
case. I still have the problem.
It looks like it goes through some default/stock authenticator instead of what
I described. I cannot tell if this is the case. And my only reference is the
reference manual. Could I look
Set a breakpoint in SeamLoginModule.login() and see if it gets invoked. Also
check the MethodBinding variable in this method to confirm it correctly refers
to your authentication method.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030027#4030027
Reply to
Seems like it is OK. I am including the full output in case you notice
something weird. BTW I am using SJSAS 9 and I tried with both Seam 1.1.6 and
1.2.0 p1.
Thank you for the help.
authenticateMethod #{otantikamator.otantikmi}
| class class
Can you verify (using debug.seam) what the authenticateMethod valid is on the
instance of identity in the session?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4028990#4028990
Reply to the post :
