Rajesh Kartha [EMAIL PROTECTED] writes:
Jonas wrote:
Hello.
I'm trying to use Derby 10.2.2 with IBM WSDD and it does not work for me.
I always get a
java.lang.NoClassDefFoundError: java.math.BigDecimal
at java.lang.Class.verifyImpl(Native Method)
at
hello,
i looked in the documentation and searched the web without any luck on
how to run an external sql script from inside a java program - this
means without using the interactive shell ij (run
'/path/to/script.sql';) since 'run' is an ij command only.
i'm thinking (at least hoping) since the
Hi,
I'm building a gwt app using derby db under eclipse.
I'm looking for simple step-by-step instructions for deploying this
app via tomcat.
So far, I have managed to deploy the gwt app via tomcat excluding derby db.
Amir
Here's what I did:
Have the db data live in a separate directory, totally outside of the
Tomcat deployment dir. Just make sure that whatever service you are
running Tomcat as has access to that dir. The derby libarary jars
should live either in Tomcat Shared libs or in your application's
I'm looking for simple step-by-step instructions for deploying this
app via tomcat.
Here's a nice article about using Derby via Tomcat:
http://db.apache.org/derby/integrate/DerbyTomcat5512JPetStor.html
thanks,
bryan
Hi,
I can't start the derby server outside of Eclipse properly.
Using the startNetworkServer command, I get this error:
ij select * from links;
ERROR 42Y07: Schema 'AMICHAIL' does not exist
But using the corresponding menu item in Eclipse works fine.
Any hints on how to fix this?
Amir
On
On 12/27/06, Amir Michail [EMAIL PROTECTED] wrote:
Hi,
I can't start the derby server outside of Eclipse properly.
Using the startNetworkServer command, I get this error:
ij select * from links;
ERROR 42Y07: Schema 'AMICHAIL' does not exist
This turned out to be a db path problem. The path
On 12/27/06, Amir Michail [EMAIL PROTECTED] wrote:
...
I also had a security problem with the connect that I solved like this:
http://forum.java.sun.com/thread.jspa?threadID=653424messageID=3840697
And yet another security problem (this one unrelated to derby db)
fixed like this:
