You told us I have created an embedded database … and added data to it. Thus, this database must be visible in Netbeans Services. NO ;create=true ! You should connect with the same URL you see in the properties. Nothing more. Expand Database URL or look at the bottom. con = DriverManager.getConnection(“jdbc:derby:C:/Dokumente und Einstellungen/Administrator/.netbeans-derby/sample”,”app”,”app”); In … Read more
Apache Derby db-derby-10.9.1.0-src / Eclipse 4.2.1 (Juno) / Java 7 Some kind of fix. Needs more research but this will work. References: db-derby-10.9.1.0-src/BUILDING.html db-derby-10.8.1.2-src/plugins/eclipse/Readme.txt Download the Apache Derby source zip. Extract the zip. Change to the source directory. db-derby-10.9.1.0-src Perform the following ant targets. ant -quiet clobber ant -quiet buildsource ant -quiet buildjars Build the … Read more
Three common reasons for “table does not exist” when you think you’ve already created the tables: You are connecting to a different database than you think you were connecting to, and since you specified “create=true” on the Connection URL, Derby quietly created a new empty database for you. You are using the “in-memory” configuration of … Read more
Create the table, catch the SQLException and check SQL status code. The full list of error codes can be found here but I couldn’t find Table <value> already exists; it’s probably X0Y68. The code you need is X0Y32. Just run the code once and print the error code. Don’t forget to add a test to … Read more
You need a ResourceLink in your META-INF/context.xml file to make the global resource available to the web application. <ResourceLink name=”jdbc/mydb” global=”jdbc/mydb” type=”javax.sql.DataSource” />
Apache Derby is just like other databases that provide interface through JDBC. You don’t need a specific plugin to connect with Derby. Just use the usual JDBC routines. Basic steps: If you want to use the latest Derby version, first you need to download it from here You need to include the jar in your … Read more
I can’t see anything obviously wrong, but perhaps a different approach might help you debug it? You could try specify your datasource in the per-application-context instead of the global tomcat one. You can do this by creating a src/main/webapp/META-INF/context.xml (I’m assuming you’re using the standard maven directory structure – if not, then the META-INF folder … Read more
java.sql.SQLException: No suitable driver found for jdbc:derby://localhost:1527/ This exception has two causes: The driver is not loaded. The JDBC URL is malformed. In your case, I’d expect to see a database name at the end of the connection string. For example (use create=true if you want the database to be created if it doesn’t exist): … Read more