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 33825 - Cancel RMI action doesn't change object executor and debugger
Summary: Cancel RMI action doesn't change object executor and debugger
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: rmi (show other bugs)
Version: -S1S-
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-22 10:43 UTC by Marek Fukala
Modified: 2009-12-21 07:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 Marek Fukala 2003-05-22 10:43:31 UTC 
[nevada rc4, #030516, jdk1.4.1_02]
Try to create an UnicastRemoteObject from
template. Then perform 'Tools/Cancel RMI' action
(be sure that the 'Confirm Marking' RMI setting is
set to true). The object is not an RMI object
longer, but it's executor is set to an RMI
Executor and debugger to an RMI Debugger. The
properties should be set to 'External Execution'
and 'Default Debugging'.
Comment 1 Marek Fukala 2003-05-22 10:45:51 UTC 
Similar problem happens when you explicitly set the executor and
debugger for a java class and then mark it as an RMI object. The
values remains and are not changed to the RMI Executor and RMI Debugger.
Comment 2 Quality Engineering 2009-12-21 07:11:12 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team