View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3821547#3821547
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3821547 1) You need to do whatever it takes to make the dlls available on your platform. This typically requires them to be in the path of the os. Dlls suck, maybe you can introduce an ipc mechanism that can work with a pure java side. 2) If your not using JAAS the CallbackHandler can be ignored. 3) SubjectSecurityManager is now the required interface as the JAAS Subject is the standard representation of the authenticated identity. 4) You need to have a Subject representation. This needs to be populated following the contract defined in chap 8 of the admin/devel guide. Everything uses the security manager so you have to be able to deal with all of the authentication requests. The JCA layer which you are showing here expects some JCA specific info to be added to the Subject. If your going to replace the security manager you either need to throw out layer you don't need, or think about a delegation strategy. 5) Show the stack traces for the two creation attempts. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
