I need javax.sql.DataSource in my deployment in order to assembly a list of Value Objects via JDBC instead of query the database through EJB-QL.
I also need certain degree of isolation because our deployment lives with legacy releases of our application in the same container. We never had problem in JBoss 3.0.3, but we have in JBoss 3.2.3. I don't want any javax.* inside my EAR, neither does my system administrator because of extra replicated megabytes of infrastruture stuff. Don't you think would be better practice to share common infrastructure resources through ClassLoaders? Thanks, Eduardo Gouvea. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839003#3839003 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839003 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
