Class SoapConfig
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringSets the context path for JAXB marshalling and unmarshalling.static final StringColon-separated list of XML Schemas to validate against in case validation is enabled.static final StringDefines if outgoing messages should contain a comment with SDCri version information.static final StringDefines a mapping of namespace prefixes to namespace URIS.static final StringDefines if SOAP message validation is enabled (true) or not (false). -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
JAXB_CONTEXT_PATH
Sets the context path for JAXB marshalling and unmarshalling.Internal context path elements will be added automatically. This configuration item uses the same String format as used in
JAXBContext.newInstance(String).- Data type: String
- Use: optional
- See Also:
-
JAXB_SCHEMA_PATH
Colon-separated list of XML Schemas to validate against in case validation is enabled.Please note that the order of the files matters. If schema X uses schema Y, then schema Y is required to be listed before schema X.
The defined paths are resource paths. XML Schemas used by DPWS are added automatically. Recognized namespaces are
- http://www.w3.org/2003/05/soap-envelope
- http://www.w3.org/2005/08/addressing
- http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
- http://schemas.xmlsoap.org/ws/2004/08/eventing
- http://schemas.xmlsoap.org/ws/2004/09/mex
- http://schemas.xmlsoap.org/ws/2004/09/transfer
- http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01
- http://schemas.xmlsoap.org/wsdl/
- http://www.w3.org/XML/1998/namespace
- Data type: String
- Use: optional
- See Also:
-
NAMESPACE_MAPPINGS
Defines a mapping of namespace prefixes to namespace URIS.The configuration key is used to define custom namespace prefixes and optimize namespace usage. The application will use the mappings on the root element in generated XML instances in favor to let JAXB define where to append a namespace, which can lead to repeated usage and herewith inflating documents.
Some DPWS-specific prefix-to-namespace mappings are predefined:
- XML Schema instance declarations: {xsi:http://www.w3.org/2001/XMLSchema-instance}
- WS-Addressing: {wsa:http://www.w3.org/2005/08/addressing}
- WS-Eventing: {wse:http://schemas.xmlsoap.org/ws/2004/08/eventing}
- WS-Discovery: {wsd:http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01}
- WS-MetadataExchange: {wsm:http://schemas.xmlsoap.org/ws/2004/09/mex}
- WS-Transfer: {wst:http://schemas.xmlsoap.org/ws/2004/09/transfer}
- DPWS: {dpws:http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01}
- SOAP 1.2: {s12:http://www.w3.org/2003/05/soap-envelope}
Internally, the prefix-to-namespace mappings are stored as a namespace to prefix-namespace map, which allows you to overwrite prefixes by customizing the namespace in the config. Configuration metadata:
- Data type: String
- Use: optional
-
VALIDATE_SOAP_MESSAGES
Defines if SOAP message validation is enabled (true) or not (false).- Data type: Boolean
- Use: optional
- See Also:
-
METADATA_COMMENT
Defines if outgoing messages should contain a comment with SDCri version information.- Data type: Boolean
- Use: optional
- See Also:
-
-
Constructor Details
-
SoapConfig
public SoapConfig()
-