This is not a request, Wes.  I can't help you if you don't provide
your code and configuration files!  All I can say is "Gosh, that's weird,
you must be doing something wrong because that doesn't happen for me."
So, please throw me a bone and maybe I can figure out what's happening!
        BTW, I'm curious as to why PoolManager is involved at all...  Are
you saying that you're using DriverManager.getConnection(...) instead of
looking up a DataSource like below?  If so, why?

Aaron

On Tue, 14 Nov 2000, Wes Mckean wrote:
> I got this working using the JNDI example:
>
> javax.sql.DataSource ds = (javax.sql.DataSource)
> ctx.lookup("java:/mysource");
> Connection conn = ds.getConnection();
>
> So, I know I set jBoss up correctly.  The problem would appear to be that
> the class org.jboss.minerva.datasource.PoolDriver and my own vendor's jar
> file are not accessible to the driver manager as called upon by the EJB.
>
> Wes
>
> -----Original Message-----
> From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 14, 2000 1:29 PM
> To: jBoss
> Subject: RE: [jBoss-User] Minerva Question
>
>
>       Perhaps you could provide your complete jboss.conf, jboss.jcml,
> and jboss.properties files.  The PoolDriver is loaded in the constructor
> for XAPoolDataSource, so I'm inclined to believe that you do not have an
> XAPoolDataSource configured correctly.
>
> Aaron
>
> On Mon, 13 Nov 2000, Wes Mckean wrote:
> > I have configured the jboss.conf and jboss.jcml properly.  However, when I
> > try to open a connection via the connection pool, I am getting a
> > ClassNotFoundException as follows:
> >
> > Class.forName("org.jboss.minerva.datasource.PoolDriver");
> >
> > When I leave this out, the DriverManager.getConnection throws a no
> suitable
> > driver exception.
> >
> > The jboss.properties file is loading the drivers correctly, because I can
> > see the confirmation when jboss starts.
> >
> > As a minimum, I don't understand why
> org.jboss.minerva.datasource.PoolDriver
> > is not available as a class to my EJB, since I can see the JAR file being
> > added to the CLASSPATH when jboss loads.  I also don't understand why my
> > vendor's driver isn't available to my EJB since I put the JAR file in the
> > lib\ext directory.
> >
> > Wes
> >
> > -----Original Message-----
> > From: Scot Bellamy [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, November 13, 2000 1:48 PM
> > To: jBoss
> > Subject: Re: [jBoss-User] Minerva Question
> >
> >
> >
> > Make sure you specify the fully qualified class name (including the
> > package) of your JDBC driver in the jdbc.Driver= property of
> > jboss.properties file.
> >
> > Also, make sure that your MLET entry in the jboss.conf includes the name
> > of the jar file containing your JDBC driver.
> >
> > Hope this helps.
> >
> > Scot.
> >
> > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> >
> > On 11/13/00, 12:37:31 PM, Wes Mckean <[EMAIL PROTECTED]> wrote
> regarding
> > [jBoss-User] Minerva Question:
> >
> >
> > > I am stumped.  I added my vendors JAR file to the lib/ext directory.
> > When I
> > > try to load the driver, I get a class not found exception.  I created a
> > > connection pool using the driver.  As far as I can tell, the connection
> > pool
> > > loads fine.  There are no errors on start up, and I can see it being
> > bound
> > > properly.  When I try to create a connection using the PoolDriver (
> > > org.jboss.minerva.datasource.PoolDriver), am again getting a
> > > ClassNotFoundException.
> >
> > > Can anyone point me in the right direction as to what I am doing wrong?
> >
> > > Wes
> >
> >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe:        [EMAIL PROTECTED]
> > > To unsubscribe:      [EMAIL PROTECTED]
> > > Problems?:           [EMAIL PROTECTED]
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
>



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to