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 64457 - LifecycleManager.restart()
Summary: LifecycleManager.restart()
Status: RESOLVED DUPLICATE of bug 168257
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@platform
URL:
Keywords: API
: 64390 (view as bug list)
Depends on:
Blocks: 60279 62053
  Show dependency tree
 
Reported: 2005-09-15 15:45 UTC by _ pkuzel
Modified: 2012-04-20 19:03 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 _ pkuzel 2005-09-15 15:45:22 UTC 
There are infrastructure modules (i.e. vcscore) that can provide very generic
services (here filesystem). Such services are typically used by many, many,
many, ... clients. It's unlikely that all clients release their references to
module service objects while disabling the service modules. Original service
module zombies remain and can clash with newly enabled services.

I think that IDE restart makes sense here (private implementation must exist
it's used by IDE updater....).

Should be addressed in 5.0 timeframe.
Comment 1 _ pkuzel 2005-09-15 16:11:00 UTC 
Another (probably better) alternative is to add a "restartOnDisable" attribute
into module manifest. This attribute would be handled by module manager. This
approach is similar to existing "needsRestart" attribute.
Comment 2 Jan Chalupa 2005-09-15 16:46:43 UTC 
Sorry, won't be addressed in 5.0 timeframe. We're several weeks after the
feature freeze.
Comment 3 Jan Chalupa 2005-09-16 09:10:09 UTC 
Regardless of what priority you assign to this issue, it won't be implemented
for 5.0.

Has this feature been consulted with HIE?
Comment 4 Marian Mirilovic 2006-03-28 11:49:34 UTC 
*** Issue 64390 has been marked as a duplicate of this issue. ***
Comment 5 markiewb 2012-04-20 19:03:21 UTC 
Duplicate. Its already fixed since 6.8.

*** This bug has been marked as a duplicate of bug 168257 ***