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 72588 - Move class doesn't move the class in MobPack MVD
Summary: Move class doesn't move the class in MobPack MVD
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-13 07:26 UTC by ieising
Modified: 2008-05-05 12:14 UTC (History)
0 users

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 ieising 2006-02-13 07:26:10 UTC 
Hi,

When I move a custom component's class to another package, the new location is
not propagated to the MVD file, so after reloading of the file, the class can't
be found and references to it are deleted. Another (already reported) issue, is
that the generated code of MobPack uses FQN which prevents the class from being
moved in the MVD's corresponding .JAVA file.

Iwan
Comment 1 Jan Becicka 2006-02-13 07:40:48 UTC 
J2ME modules must implement their refactoring plugin.
Comment 2 David Kaspar 2006-02-13 15:06:44 UTC 
This is not supported in current version of VMD.
The palette is static right now. When an user is adding a component/Java_class
into the palette, its abstraction is registered only. This abstraction does not
synchronize with the original class and stays in the palette unchanged even when
a class file is deleted.

Lowering priority to P3 and changing to an ENHANCEMENT.
Comment 3 Lukas Hasik 2006-06-23 14:42:57 UTC 
moving to mobility component
Comment 4 David Kaspar 2006-08-21 09:14:29 UTC 
This issue requires "Live Palette" feature which is planned as optional for
NetBeans 6.0.

Lowering the issue to P3 enhancement. Setting Target Milestone to "Dev".
Comment 5 David Kaspar 2007-07-11 09:10:19 UTC 
Designer 1 has been removed. Therefore reassigning to Designer 2 module. Probably this issue will be resolved in the future.
Comment 6 David Kaspar 2007-09-17 13:09:52 UTC 
Required "Live Palette" feature has be removed from 6.0 plan.
Very likely it will not be implemented in NB 6.0.