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 27182 - Adapt form editor to classpath defined by project
Summary: Adapt form editor to classpath defined by project
Status: RESOLVED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on: 27180
Blocks: 26422 27181
  Show dependency tree
 
Reported: 2002-09-10 17:01 UTC by Tomas Pavek
Modified: 2003-12-11 14:21 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Pavek 2002-09-10 17:01:58 UTC
Form Editor can no longer use
FileObject.getPackageName for deriving class names
from files. This is used on several places (code
generator, persistence manager, component
palette). The case of Component Palette is tracked
separately in issue 27181. New classpath API
defined by java module should be used.

Another implication of new projects is that
TopManager.currentClassLoader will no longer work.
It is used for loading classes of beans placed in
the form. Instead, a class loader reflecting
classpath of a project should be used. Will be
provided probably by java module. This requires to
know the project the form belongs to - see issue
27180. See also issue 27112.
Comment 1 Jan Jancura 2003-03-27 15:48:37 UTC
Can you update keyword for planning, please?
Comment 2 Tomas Pavek 2003-04-15 15:46:11 UTC
Basically, the form editor needs a classloader to be able to load
custom user beans from resources and from compiled sources of given
project. We need to clarify the definition of the classloader and how
it would be accessible (using ClassPath API) - in cooperation with
java module.
Comment 3 Tomas Pavek 2003-04-15 16:26:25 UTC
The first try was presented in issue 27826. However, global
classloader is not good idea, the classloader should be project
specific. See issue 27181 for how the palette will work with that.
Comment 4 Tomas Pavek 2003-11-26 15:36:08 UTC
As described in
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss
the current work on projects prototype has been stopped.