So in relation to the JAAS context (where my application is searching for roles
in the facescontext) I just have to wait, but it will be available right?
I still have a few moths until deployment and I'll wait.
In the mean time I'll use those components you mentioned (s:hasRole and
s:hasPermiss
anonymous wrote :
| 2.) I tried using a custom principal class (UserInformation implements
Principal) by specifying the principalClass option for my login module and it
was used throughout the login process. however in my web app I always got a
SimplePrincipal object, when doing
|
You hav
Very nice, thanks! I just spent 2 days trying to do things the other way around.
Is your component IsUserInRole working fine?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988015#3988015
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posti
Right forgot to update that jar in one place.
Thanks for the quick reply.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986266#3986266
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986266
Here's the stack trace (I'm using JBoss 4.0.5 and seam 1.1.0 BETA2)
| 18:12:38,270 INFO [SeamExceptionFilter] killing transaction
| 18:12:38,320 ERROR [SeamExceptionFilter] uncaught exception handled by Seam
| javax.servlet.ServletException: org/jboss/seam/util/Validation
| at javax.
I can't seam to find this class anywhere.
I made an update from the CVS just minutes ago.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986260#3986260
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986260
The last version (from CVS) has this problem solved (I think, I'm getting
anotherone now)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986258#3986258
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986258
Hi I'm having the same problem.
Been around this problem for days (I have so much respect for Jboss people I
never supected a bug :))
I think you can solve the problem by looking up the EJB programatically
(ctx.lookup) instead of relying on Jboss to inject it for you.
Any ideas when this will
