[GLASSFISH-20666] Start Derby with start-domain (like WLS) Created: 26/Jun/13  Updated: 05/Jan/14

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: reza_rahman Assignee: michael.y.chen
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

A very useful feature included in Java EE 7 is the default data source. It is especially useful for demo applications and beginners. However, in order for the default database to work in GlassFish, you need to start Derby separately from the domain. Via asadmin, it looks like this:

asadmin start-domain
asadmin start-database

The problem is that it is easy for a beginner to miss this. It is also painful to deal with from tools like Apache Cargo (very useful for demos and smallish standalone applications a la the "containerless" buzzword) which call start-domain under the hood but not start-database.

I think it would significantly improve usability given the default database feature to simply start Derby with start-domain.

Sahoo (sanjeeb.sahoo@oracle.com) made this comment on the matter:
"I have always felt that GlassFish should either start Derby as part of start-domain (just like WLS) or use embedded Derby to make life of developers easier".

Do let me know if anything needs to be explained further - I am happy to help.

Please note that these are purely my personal views and certainly not of Oracle's as a company.



 Comments   
Comment by arjan tijms [ 05/Jan/14 ]

+100 for this issue!

For the default data source to work as intended its imperative that it's started by default. Note that this request was already stated in the issue that led to the addition of the default data source in the first place:

To make use of this platform default data source, the user should not have to configure anything and should not have to manually start the embedded database separately from starting the application server.

See: JAVAEE_SPEC-4

It's very unfortunate that this vital requirement was somehow missed when the spec was made final.

Generated at Mon Apr 24 05:02:31 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.