Developer's Guide
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages

P6DOMXMLFLAGS.

Generic component flags,

P6DOMXML_NOFLAGS - no component preferences set, user can pass in their own SAX/JSON parser

P6DOMXML_TRACEON - show a detailed parsing trace to server.log file.

P6DOMXML_USEJSON - JSON is expected as input data rather than XML (do not set with P6DOMXML_USERPARSER)

P6DOMXML_USERPARSER - the caller will pass in their own parser via one of the setSAXParser() or setJSONParser() methods

P6DOMXML_USEJSONML - JsonML (see http://www.jsonml.org) is expected as input data rather than XML (do not set with P6DOMXML_USERPARSER)

P6DOMXML_USEKMIP - P6R's KMIP 1.0 parser (p6IKMIPDecoder) is used to parse messages encoded by the standard: Key Management Interoperabilty Protocol Specification 1.0", 15 June 2010, http://docs.oasis-open.org/kmip/spec/v1.0/cd06/kmip-spec-1.0-cd-06.doc

P6DOMXML_USEKMIPEX1 - is the same as P6DOMXML_USEKMIP with P6R's parsing extension to treat the following items with KMIP tags: (0x00420088, Server Information), (0x0042009C, Vendor Extension), and 0x0042002D, Custom Attribute) as encoded as binary strings. These particular items are ambiguous and can be encoded anyway a client decides to encode them. Treating them like binary strings allows an application above P6R software to decode them directly as an application extension.

P6DOMXML_USEKMIPXML - parse the XML dialect used by KMIP into our DOM tree. OASIS, KMIP Additional Message Encodings Version 1.0, 10 August 2013

P6DOMXML_USEKMIPJSON - parse the JSON dialect used by KMIP into our DOM tree. OASIS, KMIP Additional Message Encodings Version 1.0, 10 August 2013

Definition at line 96 of file p6domxmltypes.h.