Examples of SAXRecordingImpl

• com.volantis.xml.sax.recorder.impl.recording.SAXRecordingImpl
  A thread safe recording that is safe to cache.

  This stores the recording in three parts, an array of unique strings used for those events that take {@link String}s and also for attribute strings, an array of characters used for content, an {@link AttributesContainer} and last but not least an array of ints used torecord the main information about the event stream.

  Each event is stored as a sequence of ints in the {@link #intArray}, starting with the index of the event type followed by some event specific information.

  This recording stores each event type as follows, where a value is stored as a String what is actually stored is an index into the string array:

  setDocumentLocator

  1. Public ID - as string.
  2. System ID - as string.

  startDocument

  1. Forward reference to matching endDocument event.

  endDocument

  Nothing stored.

  startElement

  Note: The startPrefixMapping events are not treated separately, rather they are treated as an intergral part of the startElement event (which is as it should be).

  1. A count of the number of startPrefixMapping events.
  2. For each startPrefixMapping event the following is stored:
     1. Prefix - as string.
     2. URI - as string.
  3. Namespace URI - as string.
  4. Local Name - as string.
  5. QName - as string.
  6. Offset to start of attributes in the container.
  7. Length of window within the attributes container.
  8. Forward reference to matching endElement event.

  endElement

  Note: The endPrefixMapping events are not treated separately, rather they are treated as an intergral part of the endElement event (which is as it should be).

  1. Namespace URI - as string.
  2. Local Name - as string.
  3. QName - as string.
  4. A count of the number of endPrefixMapping events.
  5. For each endrefixMapping event the following is stored:
     1. Prefix - as string.

  characters

  Note: Consecutive characters event are coalesced into a single event, this typically occurs if the input stream is being produced by a parser that splits the content up into lines and generates an event for each line.

  1. Offset of start of characters in the characters array.
  2. Length of characters.

  ignorableWhitespace

  Note: Consecutive ignorableWhitespace event are coalesced into a single event, this typically occurs if the input stream is being produced by a parser that splits the content up into lines and generates an event for each line.

  1. Offset of start of characters in the characters array.
  2. Length of characters.

  processingInstruction

  1. Target - as string.
  2. Data - as string.

Examples of com.volantis.xml.sax.recorder.impl.recording.SAXRecordingImpl