InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Christian

I don't have the Tomcat code handy - have you verified that the exception
being generated can only happen on the Class.forName(...)?

Maybe the driver is loading OK (although I would have expected to see the
InstantDB copyright banner on stdout if it is). It could be that the
database url or something is misconfigured.

Regards

Pete

--

Peter Hearty                         peter.hearty@lutris.com
Lutris Technologies (UK)        http://www.lutris.com
----- Original Message -----
From: "Christian Cryder" <christian.cryder@lutris.com>
To: <instantDB@enhydra.org>
Sent: Thursday, November 16, 2000 5:16 PM
Subject: RE: InstantDB: IDB Driver name


> Well, I have verified that it's not a classpath error. Consider the
> following:
>
> I am running this in a servlet. When instantiating the servlet, I need to
> set up an Enhydra application (see java.txt for the relevant code
snippet).
> After getting the discRack.conf file, I call
>
> app.startup(conf)
>
> and this is where I see the error message in question (see output.txt for
> error message plus stack trace).
>
> Now, what I've done in this example is gone and manually tried to
> instantiate the idbDriver class right before I call app.startup(). If this
> really is a classpath error I should get the error there as well.
>
> But I don't.
>
> I instantiate the driver both directly and via newInstance()...
>
>    idbDriver driver = new idbDriver();
>    Debug.println (this, 0, "Made it to here!!!!!");
>    try {
> Class cl = Class.forName("org.enhydra.instantdb.jdbc.idbDriver");
> Debug.println (this, 0, "Got class");
> Object instance = cl.newInstance();
> Debug.println (this, 0, "Got instance");
>    } catch (Exception e) {
> Debug.println (this, 0, "Got error:"+e);
>    }
>
> When I do this I get all the messages indicating success. So I know this
> puppy is in my classpath, right? Or am I missing something here?
>
> Any suggestions appreciated...
>
> Christian
> ------------------------------------------------
> Christian Cryder
> Software Engineer, Rocks
> Lutris Technologies, Inc.
> christianc@lutris.com
> ------------------------------------------------
>        "What a great time to be a Geek"
> ------------------------------------------------
>  http://www.lutris.com ~ http://xmlc.enhydra.org
>
>
> > -----Original Message-----
> > From: owner-instantDB@enhydra.org [mailto:owner-instantDB@enhydra.org]On
> > Behalf Of george stewart
> > Sent: Thursday, November 16, 2000 7:50 AM
> > To: instantDB@enhydra.org
> > Subject: RE: InstantDB: IDB Driver name
> >
> >
> > Hi Christian
> > --- Christian Cryder <christian.cryder@lutris.com>
> > wrote:
> > > Hi Helge,
> > >
> > > Actually it should. The Servlet 2.2 spec states that
> > > any .jar file in the
> > > /lib directory will be loaded when the web app
> > > starts. I have verified that
> > > idb.jar is in this directory (and that the jar does
> > > in fact contain the
> > > driver class).
> >
> > I would try Helge's suggestion.  Either add to the
> > classpath environment or modify the tomcat startup
> > scipt to add InstantDB to the class path.  Tomcat will
> > echo the classpath on startup.
> >
> > >I also have another jar file in the
> > > lib directory, and it is
> > > getting loaded, so I'm 99.9% sure it is in fact
> > > already in the classpath.
> > >
> >
> > It probably doesn't help to have the InstantDB jar in
> > context.  My experience with Tomcat is Class.forName()
> > fails for classes in the context unless you provide
> > Tomcats's class loader.
> >
> > Regards, george
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Calendar - Get organized for the holidays!
> > http://calendar.yahoo.com/
> > ------------------------------------------------------------------
> > -----------
> > To unsubscribe from this mailing list, send email to
majordomo@enhydra.org
> > with the text "unsubscribe instantdb" in the body of the email.
> > If you have other questions regarding this mailing list, send email to
> > the list admin at owner-instantdb@enhydra.org.
>

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.