This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 69114 - Add AS 8.2 action changes derby.system.home
Summary: Add AS 8.2 action changes derby.system.home
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ ludo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-22 15:35 UTC by Martin Schovanek
Modified: 2007-02-06 17:21 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schovanek 2005-11-22 15:35:52 UTC
[#200511211900, jdk1.5.0]

When the AS 8.2 is added to Nb with already installed Derby from UC, it changes
the derby.system.home (AKA Database Location) but it breaks all previoulsy
created Derby connections and user losts contact with these database.

I would suggest to use current derby.system.home to avoid users from this
experience.
Comment 1 _ ludo 2005-11-22 16:32:48 UTC
derby module issue I think.
Comment 2 _ ludo 2005-11-22 16:33:42 UTC
Again, the derby from AU center is NOT in the NetBeans 5.0 plan, so I would say,
not a bug if the bug was assigned to me :-)
Comment 3 _ ludo 2005-11-22 17:04:13 UTC
not sure at all about fix-in-50 status...
AUC derby is not in the plan
Comment 4 Petr Jiricka 2005-11-22 17:37:43 UTC
Agree the autoupdate module is not in the plan, no committment to fix this. I
suggest removing fix-in-50 and adding the NO50 keyword to indicate this does not
affect the release.
Comment 5 Martin Schovanek 2005-11-22 17:54:45 UTC
I can reproduce it with manually downloaded/reistered Derby and Derby Support
module from daily builds and it is supported scenario from my point of view.
Comment 6 Petr Jiricka 2005-11-23 10:03:00 UTC
In that case I agree that this is a valid bug and should be addressed in the
Derby module somehow.
Comment 7 Andrei Badea 2005-11-24 12:58:22 UTC
Not a bug in the Derby support module:

1. The Derby support module only provides the API to change derby.system.home.
It's up to the API client how it uses this API and the Derby support module
can't do anything about it.

2. The appserver plugin doesn't need to change derby.system.home anymore, since
only reason for it was to register its sample databases.
Comment 8 _ ludo 2005-11-24 21:04:33 UTC
Fixed
Comment 9 Martin Schovanek 2007-02-06 17:21:34 UTC
v.