Thread: EclipseLink Derby database problem

Hi all,
I need some guidance please as I'm new to the subject of data binding.

I'm building a Java SE application (using Embedded Apache Derby and EclipseLink 2.1) of a catalogue of music albums. However, when I try to bind data from the embedded Derby database table to a Swing JTable and Run the project, I don't see any of the data from the database table. Also, the SE application is only for viewing - it is not a CRUD.

Here is the code in the 'persistence.xml' file:

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns: xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence
http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="MyGUIApp_forTesting_1PU" transaction-type="RESOURCE_LOCAL">
<provider>org.eclipse.persistence.jpa.PersistenceP rovider</provider>
<class>org.me.myimageapp.Catalogue</class>
<properties>
<property name="eclipselink.target-database" value="Derby"/>
<property name="javax.persistence.jdbc.url" value="jdbc:derby:sitw;create=true"/>
<property name="javax.persistence.jdbc.password" value="DCproject"/>
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="javax.persistence.jdbc.user" value="DCproject"/>
<property name="eclipselink.logging.level" value="ALL"/>
<property name="eclipselink.ddl-generation" value="create-tables"/>
<property name="eclipselink.ddl-generation.output-mode" value="database"/>
<property name="javax.persistence.schema-generation.database.action" value="create"/>
</properties>
</persistence-unit>
</persistence>

What am I doing wrong?

What am I doing wrong?

Could be any number number of things, from connecting to the database, to querying, to displaying the data. Perhaps someone else can come along and somehow guide you, but from where I sit the lack of code, exceptions stack traces (if any), and context on what might be the cause doesn't leave us much to help you with. Your best bet: post an SSCCE that demonstrates the problem.