Bug 151646 - smarter 'start db' functionality
smarter 'start db' functionality
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Code
6.x
All All
: P2 (vote)
: TBD
Assigned To: Nitya Doraisamy
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-28 21:57 UTC by Vince Kraemer
Modified: 2009-02-19 23:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Kraemer 2008-10-28 21:57:45 UTC
Currently, the v2 plugin will start java db when you start the app server IF the option is checked.

the v3 plugin doesn't support started java db at all.

In a perfect world... the java db would start IFF there was an app deployed on the server which is going to use it....
The app server would probably need to be 'the one' to do this.

In a less than perfect world, the IDE might be able to make a better guess about when to start the java db, by looking
at the datasources that an app that is being deployed will use... if a CP in the list going to use java db, we may want
to make sure the db is started.

A naive implementation (that extends the driver deployment feature) seems to work... but this probably requires an API
change to do right.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo