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 92053 - Consistent external reference customizer supporting cross-project XML references
Summary: Consistent external reference customizer supporting cross-project XML references
Status: RESOLVED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: XSLT (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks: 89562
  Show dependency tree
 
Reported: 2007-01-08 21:22 UTC by Nam Nguyen
Modified: 2007-02-02 16:37 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 Nam Nguyen 2007-01-08 21:22:20 UTC 
XSL editor custimizer for external XML file reference need to use the same
ExternalReferenceCreator defined in xml/xamui to provide consistent user
experience as other editors (Schema, WSDL,...) and also to automatically get
support for cross-project XML file reference.

For more info see section "Adding Support for Cross-Project References" on this
page
http://xdesign-tools.czech.sun.com:8080/JSPWiki/Wiki.jsp?page=XmlFileRefsOnepager
Comment 1 Vladimir Yaroslavskiy 2007-01-09 13:10:08 UTC 
Nam, please provide details:
which external reference wizards in bpel module are incorrect?
what classes in xml suite should I use?
Comment 2 Vladimir Yaroslavskiy 2007-01-12 13:07:36 UTC 
Nikita, please do changes in your choosers.
Comment 3 Nam Nguyen 2007-01-22 21:22:30 UTC 
The common import wizard to use is ExternalReferenceCreator in xml/xamui .
Comment 4 Nikita Krjukov 2007-02-02 15:26:48 UTC 
I can't understand what to apply this issue for. 
Nam, you have said me before that it relates the XSLT editor. 
But I don't see any imports there and there is another issue #92051, 
which is more specific.
Comment 5 Nam Nguyen 2007-02-02 16:37:41 UTC 
Now that I see the XSL editor, there is no UI's for xsl:import or xsl:include,
agree to close as invalid.