The java database (jdbc) derby with GlassFish 3.0.1 is used in the project. The problem occur when the default schema APP is set to default on service panel but the properties of database is remain unchanged.

The following steps could be done to reproduce the problem:

1. Create Java DB under service panel, and set database name as test, username and password as ADMIN.
2. Right click the "test" database under Java DB and choose connect.
3. Under the Databases, double click the newly created jdbc:derby://localhost:1527/test [admin on ADMIN].
4. Right click on APP and set as Default Schema.
5. Right click the database file jdbc:derby://localhost:1527/test [admin on ADMIN] and the schema is remained ADMIN.

When the schema remained as ADMIN, I've tried to go on my project and create a new entity class from database. Database Connection is chose correctly and there is no Available Tables in the list (Note that I have created few tables).

If, on the creation of database, the username is set as APP, then the database created will be using APP schema by default. Then create a new entity class from a project and choose the database with schema APP and the tables under Available Tables list is shown correctly.

This bug seems like the scheme of database is depend solely on the username, and the option to set another schema as default is not worked (can be seen from the properties of the database under "Schema")

And another bug is that, schema is depend on the username, i.e, ADMIN, the schema list under database do not have ADMIN as the new schema. So another question come, we are not possible to create a new schema? Only the schema listed can be used?