Gregor
> Are there known access-problems? Is there a user or schema concept in
> instantdb at all?
Nope - in fact usernames and passwords are just ignored.
> Do I have to use the rmijdbc-driver? I think that I should because jee2
uses
> rmi. But which url-format is used with rmijdbc?
The url format is:
jdbc:rmi://<rmiHostName[:port]>/<jdbc-url>
So an RmiJdbc url for IDB would be something like:
jdbc:rmi://localhost/jdbc:idb:/home/pete/idb/sample.prp
See TestClient.java in the RmiJdbc download for an example (I think it's
buried inside the jar file if I remember rightly).
Regards
Pete
--
Peter Hearty peter.hearty@lutris.com
Lutris Technologies (UK) http://www.lutris.com
----- Original Message -----
From: "Frey, Gregor Karl" <gregor.karl.frey@sap.com>
To: "'Peter Hearty'" <peter.hearty@lutris.com>
Sent: Thursday, November 02, 2000 7:48 AM
Subject: RE: JSDK2EE-Problems with InstantDB
> Hello Pete,
> meanwhile I found in the logfiles of jdkee a more "speaking" error
message.
> I says that there is an access problem. But to me it's surprising, because
I
> have all my jar-files coming with instantdb in the jre/lib/ext directory.
> I tried then the rmijdbc-driver, but got the problem that jee2 estimates
> that driver as not suitable.
> Are there known access-problems? Is there a user or schema concept in
> instantdb at all?
> Do I have to use the rmijdbc-driver? I think that I should because jee2
uses
> rmi. But which url-format is used with rmijdbc?
> Thanks a lot for all your friendly help!
> ... I just got a mail from Dion Truder, who first posted that problem. He
> says that finally he gave up and took another opensource-db(InterBase).
> Regards,
> Gregor Frey
>
> -----Original Message-----
> From: Peter Hearty [mailto:peter.hearty@lutris.com]
> Sent: Thursday, November 02, 2000 5:59 AM
> To: Frey, Gregor Karl
> Subject: Re: JSDK2EE-Problems with InstantDB
>
>
> Gregor
>
> The:
>
> "Enhydra InstantDB - Version 3.21
> ...
> Reserved."
>
> bit is coming from InstantDB. That means that it's finding InstantDB OK
and
> it's starting up. Something must be going wrong after that though and any
> IDB exception is maybe getting lost.
>
> The:
>
> "Cannot find principal mapping information for data source with JNDI name
> jdbc/InstantDB"
>
> bit is probably the JSDKEE message. Try setting traceLevel=6, to see if
you
> get any more output to stdout, or to 255 if even that doesn't work.
>
> Regards
>
> Pete
>
> --
>
> Peter Hearty peter.hearty@lutris.com
> Lutris Technologies (UK) http://www.lutris.com
> ----- Original Message -----
> From: "Gregor Frey" <Gregor.Frey@t-online.de>
> To: <peter.hearty@lutris.com>
> Sent: Wednesday, November 01, 2000 7:26 PM
> Subject: JSDK2EE-Problems with InstantDB
>
>
> > Hi Peter,
> > thanks for your answer to my mail concerning the problems connecting
> > from the SUN-Reference-Implementation of J2EE to InstantDB.
> > You asked which JDBC-Version is required by JDKEE. The manual says that
> > it should work with 1.x and 2.x versions of jdbc. I think it should work
> > with InstantDB too.
> > Actually the error-message is not clear concerning the question, which
> > tools runs the error. I get the message on the terminal where I run the
> > j2ee-server. It says:
> >
> > Cannot find principal mapping information for data source with JNDI name
> > jdbc/InstantDB
> > Enhydra InstantDB - Version 3.21
> > The Initial Developer of the Original Code is Lutris Technologies Inc.
> > Portions created by Lutris are Copyright (C) 1997-2000 Lutris
> > Technologies, Inc.All Rights
> > Reserved.
> >
> > I'm not quite sure wether this message comes from InstantDB or not. Does
> > it?
> >
> > Regards,
> > Gregor
> >
> > PS: Please send your response to
> > gregor.frey@t-online.de
> > and
> > gregor.karl.frey@sap.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.
|