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 50296 - ISE: Next cannot be the same as current element
Summary: ISE: Next cannot be the same as current element
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: Text-Edit (show other bugs)
Version: 4.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-12 20:19 UTC by Jesse Glick
Modified: 2009-12-21 04:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack trace (1.71 KB, text/plain)
2004-10-12 20:20 UTC, Jesse Glick 		Details
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 Jesse Glick 2004-10-12 20:19:48 UTC 
041011, JDK 1.5. Have
nbbuild/javadoctools/apichanges.xsl opened in
editor. Had tried some code completion to make
sure it was working (it was). Found some repeated
exceptions in my log file afterward.
Comment 1 Jesse Glick 2004-10-12 20:20:18 UTC 
Created attachment 18232 [details]
Stack trace
Comment 2 Jesse Glick 2004-10-12 20:21:05 UTC 
The XML source in question is

        <xsl:if test="$is-first">
            <h2>
                <xsl:apply-templates select="api"/>
            </h2>
            <!-- Need to use the slinky disable-output-escaping
because we do not close the ul here: -->
            <!-- ** HERE ** --><xsl:text
disable-output-escaping="yes">&lt;ul&gt;</xsl:text>
        </xsl:if>
Comment 3 Marek Fukala 2004-10-26 10:56:03 UTC 
There is a problem with XMLSyntaxSupport.getElementChain(...) method.
If there is an entity (e.g. &lt;) item in a XML document, the method
returns bad syntax element around the offset of the entity element. To
be more specific the some syntax element is returned for two offsets
where the second offset > first offset + token length. 

The fix has to be done in the syntax support but since many things
rely on it I do not want to risk to change it now, a few days before
high resistance. So I am going to simply comment out the code which
makes the informational exception and leave this issue opened. Then we
can fix it better for next release.

Checking in SyntaxElement.java;
/cvs/xml/text-edit/src/org/netbeans/modules/xml/text/syntax/SyntaxElement.java,v
 <--  SyntaxElement.java
new revision: 1.11; previous revision: 1.10
done
Comment 4 Petr Jiricka 2005-02-22 12:09:05 UTC 
Let's reevaluate this.
Comment 5 Marek Fukala 2005-03-29 12:34:33 UTC 
a change to xml syntax support seems to be too dangerous and not worth of the
effect.
Comment 6 Marek Fukala 2005-10-12 13:40:03 UTC 
The informational exception is not thrown anymore and there aren't any other
user complains about the XML CC => downgrading to P4.
Comment 7 Marek Fukala 2007-02-16 14:43:34 UTC 
Reassigning to default owner of selected subcomponent. New owners are gladly
welcomed.
Comment 8 Quality Engineering 2009-12-21 04:45:06 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team