schemas.configuration.wsrm-manager.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of cxf-bundle-minimal Show documentation
Show all versions of cxf-bundle-minimal Show documentation
Apache CXF Minimal Bundle Jar
This schema defines features and beans to configure the CXF Reliable Messaging components.
This feature enables and controls the use of WS-Reliable Messaging.
It ensures that the reliable messaging interceptors are added to the interceptor chains,
and allows to configure behaviour of the reliable messaging infrastructure
that goes beyond what can be described by the attributes in the RMAssertion type.
Note that addition of the addressing interceptors is not part of this feature. It should
therefore always be used in conjunction with the addressing feature.
The RMAssertion to be used.
The parameters of this RMAssertion element supercede those specified
in policy attachments.
The delivery assurance to be used by the reliable messaging manager.
The source policy to be used by the reliable messaging manager.
The destination policy to be used by the reliable messaging manager.
The WS-Addressing namespace to be used for WS-ReliableMessaging 1.0.
For the client, this determines the addressing namespace used when sending
requests to the server. Both client and server will accept either namespace
in incoming messages.
The store to use when persisting messages.
The child element of this element must be a bean whose bean class implements
org.apache.cxf.ws.rm.persistence.RMStore, or a reference to such a bean.
By default, messages are only persisted in memory, and thus delivery cannot be
guaranteed in the presence of application crashes.
Deprecated. To support the older spring:property element that is no longer used
The JDBC driver class name.
The optional datasource reference to be used.
The connection URL.
The username.
The password.
The default schema name.
The SQL state to verify a vendor specific table-exists condition.
The SQL error code to verify a vendor specific table-exists condition.
Indicates if the connection is kept by the store.
The initialy delay before attempting to reconnect to the database. The subsequent
delay follows the exponential backoff algorithm. This attribute is only
relevant when the connection is kept by the store.
The maximum number of attemps taken to reconnect to the database after a connection error.
The value of 0 indicates no attempt, while a negative value indicates no limit.
This attribute is only relevant when the connection is kept by the store.
activationType is a workaround to reuse the Tactivation type from blueprint schema.