-
Bug
-
Resolution: Fixed
-
P2
-
1.0.2
-
1.4
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2153436 | 7 | Joe Wang | P2 | Closed | Fixed | b14 |
JDK-2144028 | 6u2 | Santiago Pericasgeertsen | P2 | Closed | Won't Fix |
When a XMLStreamReader whose current event type (for eg:) is START_ELEMENT is wrapped with XMLStreamFilter . The newly created XMLStreamReader returns getEventType as -1 instead of START_ELEMENT.
test provided by santiago:
public void testTwo(){
try {
XMLStreamReader reader =
factory.createXMLStreamReader(new StringReader(XML));
reader.next(); // advance to START_ELEMENT
XMLStreamReader filter =
factory.createFilteredReader(reader, new Filter());
assertTrue(filter.getEventType() != -1);
}
catch (Exception e) {
e.printStackTrace();
fail("Unexpected Exception: " + e.getMessage());
}
}
test provided by santiago:
public void testTwo(){
try {
XMLStreamReader reader =
factory.createXMLStreamReader(new StringReader(XML));
reader.next(); // advance to START_ELEMENT
XMLStreamReader filter =
factory.createFilteredReader(reader, new Filter());
assertTrue(filter.getEventType() != -1);
}
catch (Exception e) {
e.printStackTrace();
fail("Unexpected Exception: " + e.getMessage());
}
}
- backported by
-
JDK-2144028 Filtered XMLStreamReader returns -1 when getEventType is called
-
- Closed
-
-
JDK-2153436 Filtered XMLStreamReader returns -1 when getEventType is called
-
- Closed
-