I think you might be right, but that seems kinda crazy to me. The unified classloader is ok, but it seems to depart from the encapsulation concept.
The main reason I want to do this is so I can produce a client jar for my client that will not include DAO/JDBC code, etc, etc. I want to be strict with enforcing what the clients can invoke and thus want to encapsulate all of the business code and objects behind a Facade implemented using a remote stateless session bean. This facade then resides in it's own ear out on the system, but is accessible only through the remote interface. With unified classloader, it seems everything is out on the system for anybody to access as they please. It seems like the client-jar and ejb-jar is not a concept that is often used with JBoss? Any ideas? Examples? on how to use the scoped ears in the manner described above would be appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840360#3840360 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840360 ------------------------------------------------------- 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
