|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||
java.lang.Objectorg.cyberneko.pull.XMLEvent
org.cyberneko.pull.event.TextDeclEvent
An XMLDecl or TextDecl event. This event is used to communicate both the XML declaration at the beginning of XML instance documents and text declarations appearing at the beginning of external parsed entities.
REVISIT: [Q] Should these be separate events? -Ac
| Field Summary | |
java.lang.String |
encoding
The value of the "encoding" pseudo-attribute. |
java.lang.String |
standalone
The value of the "standalone" pseudo-attribute. |
java.lang.String |
version
The value of the "version" pseudo-attribute. |
boolean |
xmldecl
True if this event is used for XMLDecl; false if used for TextDecl. |
| Fields inherited from class org.cyberneko.pull.XMLEvent |
augs, CDATA, CHARACTERS, COMMENT, DOCTYPE_DECL, DOCUMENT, ELEMENT, GENERAL_ENTITY, next, PREFIX_MAPPING, PROCESSING_INSTRUCTION, TEXT_DECL, type |
| Constructor Summary | |
TextDeclEvent()
Default constructor. |
|
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
public boolean xmldecl
public java.lang.String version
public java.lang.String encoding
public java.lang.String standalone
REVISIT: This is why I'm thinking that the XMLDecl should be separate from the TextDecl. It just seems wrong to have unused fields based on the type.
| Constructor Detail |
public TextDeclEvent()
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||