The ideal way to be setting the cause on the LoginException, but this is a 1.4.x extension to the exception base classes that will not work with jdk 1.3 which we still support at least for compilation. I could look at reflectively adding this info when the runtime supports it.
The problem with introducing a JBossLoginException that supports nested exception is non-standard code for something that does exist in jdk 1.4.x. Is this something you need with jdk 1.3 or could you look to the LoginException cause in a 1.4.x runtime?
yes I am still on jdk 1.3, which is hopefully going to change soon. I would like it if the cause could be set if one is running a 1.4 runtime. One more reason to finally upgrade :)