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 158245 - Should not allow to delete Glassfish V3 directory if still registered
Summary: Should not allow to delete Glassfish V3 directory if still registered
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 02:56 UTC by davisn
Modified: 2012-11-22 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
errorMessage (8.56 KB, text/plain)
2009-02-10 02:57 UTC, davisn 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2009-02-10 02:56:54 UTC 
-User is allowed to delete a registered V3 server directory while is not allowed to delete Glassfish V2 registered directory
-It should be consistent among servers at least on WinXP

Steps To Reproduce
1. Install NB 7.0 Dev, dated Feb 08, 2008 from http://bits.netbeans.org/download/trunk/nightly/latest/
2. From Plugin dialog, select to activate Glassfish V3 Prelude and Glassfish V2/V1 Server
3. From a window explore, select to delete the bundled Glassfish V2 server directory
Note:
   You're not allowed
4. Select to delete the Glassfish V3 Prelude bundled Server
BUG:
   -You can delete it 
   -After deleted GF V3 server, I try to start the Glassfish V3 Prelude from Servers list menu, an irrelevant error
message appears to say "can start server...Associate jdk ..." please see the attached file for the full message
Comment 1 davisn 2009-02-10 02:57:24 UTC 
Created attachment 76769 [details]
errorMessage
Comment 2 Vince Kraemer 2009-02-11 05:20:17 UTC 
you cannot delete v2 because the IDE is using jars that are in the server directory....

the v3 plugin does not use jars out of the installation directory... so it can be deleted. Putting in a false usage of
one of the jars might address this (on Windows only)... 

I do not see a huge pay-off for adding such a hack.
Comment 3 TomasKraus 2012-11-22 16:41:52 UTC 
I do not see this as a NetBeans issue. People can delete files on their file systems and they should know that doing so can break something.

User can delete asadmin because NetBeans code does not use it at all, user can delete remote GlassFish server and blame NetBeans that it did allowed him to do so.

I would like to avoid doing such a hack. People using NetBeans are developers and they should have some basic knowledge about computers and operating systems.