The desire to limit access to the DAOs, etc is more from a design perspective, not a security one. Your approach is essentially the same, except that I have always bundled my "lib" classes in with the "ejb" jar descriptors. This approach has always worked in weblogic and I assumed it would work in JBoss. The whole portable application thing. :-)
I will try your "lib" approach, although I am not sure why bundling the ejb implementations into a "lib" directory as opposed to the ejb.jar itself would work since they will reside in the same ear. Do you know if this works with scoped ears on JBoss? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840385#3840385 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840385 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
