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 69762 - [navigator] provide XML navigator for JSPX and TLD files
Summary: [navigator] provide XML navigator for JSPX and TLD files
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Text-Edit (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: issues@xml
Depends on:
Reported: 2005-12-02 15:52 UTC by Marek Fukala
Modified: 2008-01-18 04:48 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Marek Fukala 2005-12-02 15:52:36 UTC
...both are XML documents.
Comment 1 Marek Fukala 2005-12-02 16:46:24 UTC
JSP documents (JSPX) has the same mime type as JSP in standart syntax. So there
is no way to distinguis them easily. Either mimetype has to be set to a
different one or NavigatorLookupHint has to be put into the TC of the JSP
documents. Both are potentilly dangerous now a few days before HR.

The TLD files has no set content type at all, so the same as for JSP document
applies for them.
Comment 2 Marek Fukala 2006-08-04 12:34:07 UTC
The fix is not that easy - even I introduce a new composite mimetype for these
files, I still cannot make the navigator working for them since the XML
navigator requires the underlying document to be parsed by XMLSyntax. JSPX and
TAGX files are xml-based, but the IDE implementation of them is based on JSP
syntax with embeded html syntax. This issue should be taken into account in 6.0
j2ee editor redesign.
Comment 3 Marek Fukala 2007-02-16 14:41:15 UTC
Reassigning to default owner of selected subcomponent. New owners are gladly
Comment 4 cayhorstmann 2008-01-16 03:08:28 UTC
Please do something about this. When editing JSPX files in source mode (which are, for example, produced by the Visual
Web Editor), right now the Navigator shows something like


i.e. exactly the unimportant part of the file. A collapsible view of the XML would be very helpful for erm, navigating,
the pages. 
Comment 5 Marek Fukala 2008-01-18 04:48:23 UTC
That is what this isssue is about. The navigator shows just the html content for JSP/Xs. The ideal solution is to have
separate navigators - "views" of the document - JSP View, HTML View.