Hello,
I have the same problem getting the exact exception cause on the client side.
If you are lucky your client will run on the same VM that the logincontext
does. In that case you might use
Object exception =
org.jboss.security.SecurityAssociation.getContextInfo("org.jboss.security.exception");
System.out.println("exception:"+exception);
The exception obtained is the original exception thrown by the LoginModule and
you can insert your own code based upon that exception (rethrow it for example).
In my case i use ejb services accessed from a remote machine and that exception
is not available on the remote client :(.
As requested by Scott i have opened a Jira requesting this feature for the
client. Please vote for it so that they can correct it.
http://jira.jboss.com/jira/browse/JBAS-47
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858748#3858748
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858748
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
