0 Replies Latest reply on Nov 14, 2002 2:12 PM by bctboss

    JCA JDBC Overly Complex

    bctboss

      Between JDBC versions (DeviceManager and DataSource), and the JCA connectors, there seems to be a myriad of ways to interact with a simple JDBC compliant database. There is no clear documentation on how to leverage the transaction management facilities in JBoss for pooling, security, etc. for a simple JDBC resource. Can someone please point me to a single example of using a JDBC resource through the JCA facilities in JBoss 3.0.x. My understanding is that JBoss 3.0.x comes with a a JCA-JDBC wrapper, but it's not clear how to use it.

      I would like to see how the '*-service.xml' file is setup (for any JDBC compliant database), and the corresponding EJB source code for interacting with that resource through the JCA facilities including looking up the JNDI resource, getting a connection, setting up the interaction SQL statements, executing them, and iterating through the result set.

      Thanks for any help.

      Just an aside. This level of complexity and myriad of options is exactly what killed CORBA/C++. I would hate to see the same mistakes made with J2EE/Java especailly with .NET breathing down our necks.