THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
To enable persistence, you must specify the object implementing the persistent store for RM. You can develop your own, or use the JDBC based store that comes with CXF (class org.apache.cxf.ws.rm.persistence.jdbc.RMTxStore). You can configure the latter using a custom jdbcStore bean (namespace http://cxf.apache.org/ws/rm/manager
) . It inside the wsrm-mgr:reliableMessaging element. The jdbcStore bean supports the attributes:
Attribute Name | Type | Default |
|---|---|---|
dataSource | String | null |
driverClassName | String | org.apache.derby.jdbc.EmbeddedDriver |
initialReconnectDelay | long | 0 |
keepConnection | boolean | false |
maxReconnectAttempts | int | 0 |
passWord | String | null |
tableExistsCode | int | 0 |
tableExistsState | String | null |
schemaName userName | String | null |
passWord userName | String | null |
url | String | jdbc:derby:rmdb;create=true |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<wsrm-mgr:jdbcStore xmlns:wsrm-mgr="http://cxf.apache.org/ws/rm/manager" id="myStore" driverClassName="org.apache.derby.jdbc.ClientDriver"/> url="jdbc:derby://localhost:1527/rmdb;create=true"/> password="password"/> |
See the jdbcStore element definition in the RM Manager schema for more details of the attribute usages.
Adding the Reliable Messaging Interceptors Manually
...