This is more or less the way that I'm doing it, except that I use a loop that keeps on retrieving the parent cause (with the getCause() method) until the message (from the getMessage() method) starts with 'checkSecurityAssociation'. This way, I remove a dependency in the application client on certain classes. The client doesn't have any references to JBoss classes in it, although it references jbossall-client.jar in the JNLP descriptor (it is launched from Java WebStart).
I agree that it's not elegant, and handling an exception by actively looking at its cause(s) is not considered proper programming, but I see no other way. - Peter View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870933#3870933 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870933 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
