Hi Andy,
I hope that answered the question. Love Linux. Hate Windows. But
sometimes it's still the best solution after all is said and done.
Yeah, the JDBC driver is NetDirect's Type 3 JDataConnect-- so part's on
Linux, part's on Windows. And our other applications are all Linux->Win2k
as well.
In the meantime, I think I found the problem. In the old docs, it says to
specify the JData2_0.jar right after the jboss.jar file in jboss.conf, but I
noticed that InstantDB didn't do that... so when I took it out and restarted
it, seemed to bind the datasource ok. That is, I got this:
...
[WRSQL] Starting
[WRSQL] XA Connection pool WRSQL bound to java:/WRSQL
[WRSQL] Started
...
Looks right huh?
Thanks again,
Rian
----- Original Message -----
From: Andy "Mad" Schaefer <[EMAIL PROTECTED]>
To: jBoss <[EMAIL PROTECTED]>
Sent: Sunday, December 10, 2000 5:02 PM
Subject: Re: [jBoss-User] SQL Server and jBoss, one last time...
> Hi
>
> I was just wondering why you use Linux and M$ SQL-Server.
>
> I assume that you used the JDBC driver also on Linux box, did
> you.
>
> The problem from your stack trace indicates that the MBeanServer
> (which loads and instantiate the DataSource) does not find the specific
> class. Could you please give me jboss.conf or jboss.jcml (if you use the
> latest code from JBoss).
>
> Have fun - Mad Andy / Better Pizza
>
> Senior Java Developer
> eBuilt Inc. (www.ebuilt.com)
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
