I'm trying to determine what the least awful J2EE/EJB pattern is for the following:
I have a large, read-only resource. There should be one in a server. It provides a common service. There is JNI under it, so it has to be in one, common, classloader. I've successfully deployed it in plain old Tomcat by putting the implementation in the shared classloader and setting up a JNDI name for it via Tomcat's global resource declarations. In J2EE-land, should this be JCA, or can it be a singleton EJB of some kind? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871837#3871837 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871837 ------------------------------------------------------- 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
