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.
[#200511211900, jdk1.5.0] When the AS 8.2 is added to Nb with already installed Derby from UC, it changes the Derby Location and Driver File(s) for registered drivers, to Derby folder from the AS. We should display a Warning dialog that this changes happen.
to reproduce: ------------- 1) install Derby from Update Center 2) chose Customize from 'Databases > Drivers > Appache Derby (Net)' driver node NOTE: derbyclient.jar cames from Derby from UC 3) add AS 8.2 server into Nb 4) chose Customize from 'Databases > Drivers > Appache Derby (Net)' driver node NOTE: derbyclient.jar cames from Derby from AS 8.2 ERROR: the .jar location was changed without a warning
Might not be possible in some case when we do automatic server regsitration (cobundle case) when the call can happen even if Netbeans is not fully started (i.e no ui to emit the warning). We could emit something in the conseole (or log file)? Also, I am not sure about the Derby db from UC. Is is part of NetBeans 5.0 plan? Not really, so I would not say currently that this is a P3 bug... Please add your comments. Enhancement? Or maybe the warning should come from the Derby module?
In case of automatic (cobundle) registration is not a reason to display a warning, because there will not be a previous driver/connection registration. It should be done only in case when we are changing existing driver/connection registration. To UC Derby: I can reproduce it with manually downloaded/reistered Derby and Derby Support module from daily builds and it is part of NetBeans 5.0 plan. There is only one difference, at first there is both drivers registrations, from my own location and from AS. After Nb restart situation is the same. Only drivers from AS and my previously registered drivers disappeared. To display the warning from the Derby module makes no sense for me, the Add AS wizard looks like much better place for me.
there will be no derby implementation on AU. So no duplication or confusion.
Sorry to say this but it does not depend on AU. It is reproducible with manually downloaded/reistered Derby as well. See my previous comment.
The AS does not change anything now if things are already configured.
Reproducible in #200511291900
Well, given the fact that the way to manually register own instance of Derby through system options is not easily discoverable, I would argue that not many users will run into this issue and this is not too important to fix for NB 5.0 - we have bigger fish to fry. Also, is it really an issue that the Derby install path changes? If future versions of the Appserver keep up with latest versions of Derby, then the user will get the latest Derby in Appserver, and will not need to manually download better versions.
I discussed it with Peter J. and agree this issue is not so clear now, so I describe the problem again. Current status: ---------------- When the AS 8.2 is added to Nb with already installed Derby, it changes the Derby Location (place where Derby's jar files are kept) and Driver File(s) for registered drivers to AS Derby location. It causes two problems: 1) Derby stops working when the AS is physically uninstalled 2) user starts using another Derby without any warning or info Desirable state: ---------------- As Ludo suggested, does not change anything if Derby Location is already configured. Justification: -------------- - AS bundles 'Derby 10.1.1.0' but Latest Official Release is 'Derby 10.1.2.1' so users can use the latest version. - Probably all of J2SE developers which only try and uninstall the AS, run into this issue.
/cvs/serverplugins/sun/appsrv81/src/org/netbeans/modules/j2ee/sun/ide/j2ee/db/RegisterPointbase.java,v <-- RegisterPointbase.java new revision: 1.16; previous revision: 1.15
v.