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 23025 - Infrastructure for using schema2beans in settings architecture
Summary: Infrastructure for using schema2beans in settings architecture
Status: RESOLVED INCOMPLETE
Alias: None
Product: ide
Classification: Unclassified
Component: Schema2Beans (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: schema2beans-issues@ide
URL:
Keywords:
Depends on: 17924
Blocks:
  Show dependency tree
 
Reported: 2002-05-02 08:57 UTC by Jaroslav Tulach
Modified: 2011-09-19 22:53 UTC (History)
1 user (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 Jaroslav Tulach 2002-05-02 08:57:49 UTC 
The schema2beans seem to be natural and useful
extension for usage in NetBeans settings
management (issue 17924). Please provide the
infrastructure for using schema2beans in settings
architecture so modules can easily register their
DTDs and their settings files will be
automatically presented as objects.
Comment 1 Jaroslav Tulach 2002-05-02 09:02:37 UTC 
The module should either implement Environment.Provider or
org.netbeans.api.settings.Convertor (part of issue 17924) and allow
other modules to just register their DTD and generate their beans and
the system should handle the conversion automatically.
Comment 2 _ cliffwd 2003-07-19 01:37:38 UTC 
Is this request obsolete at this point in time?  If not, please
provide more details on what needs to be done to help out.
Comment 3 Jaroslav Tulach 2003-07-21 09:36:20 UTC 
This should be rethinked in context of new settings infrastructure.
CCing David to express his opinion and leave open/close this issue.
Comment 4 David Konecny 2003-07-21 11:45:28 UTC 
Give me some time. I need to look first at what schema2beans module does.
Comment 5 David Konecny 2003-08-07 13:46:18 UTC 
At the moment I do not see much usage for this in regard to  Convertor
API. I do not see how it should work and simplify user's job with
Convertor API. Looks like obsolete issue to me.