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.
| Summary: | [navigator] provide XML navigator for JSPX and TLD files | ||
|---|---|---|---|
| Product: | xml | Reporter: | Marek Fukala <mfukala> |
| Component: | Text-Edit | Assignee: | issues@xml <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | jkovalsky |
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
Marek Fukala
2005-12-02 15:52:36 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. 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. Reassigning to default owner of selected subcomponent. New owners are gladly welcomed. 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 <br> <br> i.e. exactly the unimportant part of the file. A collapsible view of the XML would be very helpful for erm, navigating, the pages. 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. |