You do need to add the oracle driver to the line in
jboss.properties. The JdbcProvider simply loads the drivers in
jboss.properties, and you probably will not need to change the imports
there since everything in lib/ext gets loaded into the classpath at an
earlier step, but it can't hurt. Then you must add either a
DataSourceImpl or the Minerva pool equivalent in order to start a data
source that uses your Oracle driver.
Once all that is done you should see a line in the JdbcProvider
output stating that your driver was loaded, and then a line in the
DataSourceImpl or Minerva pool output saying the specific data source was
loaded. Then you need to make sure that the jboss.xml has a resource
manager entry referring to the JNDI name of the data source, and a
resource entry that links the ejb-jar.xml name of the resource to the
resource manager name of the resource (and it's easier if you make some of
these names the same!).
If those are all hooked up correctly, your bean should be able to
reference the name as java:comp/env/<ejb-jar.xml name>, so you'd have to
make the ejb-jar.xml name "jdbc/employeedb" if you want it to appear to
the bean as java:comp/env/jdbc/employeedb. If that is set correctly but
nothing is in JNDI, double check the resource/resource manager settings in
jboss.xml.
If you still can't get it to work, send an e-mail with your
ejb-jar.xml, jboss.xml, jboss.conf, and jboss.jcml.
Aaron
On Fri, 7 Jul 2000, Richard Backhouse wrote:
> Hi,
>
> I've just started playing with jboss and I have a couple of questions :
>
> 1. Is BMP working yet ? I have read through alot of the mail archivesand
> I can't find a definitive answer.
>
> 2. I'm trying to set up a new Oracle datasource in jboss.conf. Do I need
> to add the oracle zip file name to the JdbcProvider MLET tag as :
>
> <MLET CODE = "org.jboss.jdbc.JdbcProvider"
> ARCHIVE="jboss.jar,classes111.zip" CODEBASE="../lib/ext/">
> </MLET>
>
> or add it to the DataSourceImpl MLET tag as :
>
> <MLET CODE = "org.jboss.jdbc.DataSourceImpl"
> ARCHIVE="jboss.jar,classes111.zip" CODEBASE="../lib/ext/">
>
> 3. Do I need to add the oracle driver name to jboss.properties.
>
> 4. I tried deploying some ejb's that I have already written and have
> running with suns j2ee ri. They seem to deploy ok but I don't see any
> references to the jdbc/db names being bound. I do see that the EJBs
> themselves are being bound ok. When I try and run a test against any of
> the ejbs I get the following exception :
>
> java.rmi.ServerException: Exception occurred; nested exception is:
> javax.ejb.EJBException: Cannot lookup
> java:comp/env/jdbc/employeedb[javax.naming.NameNotFoundException: jdbc
> not bound
>
> I have setup a Resource Manager in my jboss.xml to point to the Oracle
> datasource. I have also setup each of the datasource references for each
>
> bean to point to the named resource manager.
> Any Ideas ?
>
> Thanks
> Richard Backhouse
> Oak Grove Software
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
