Provide client side WS-RM API
-----------------------------
Key: JBWS-2047
URL: http://jira.jboss.com/jira/browse/JBWS-2047
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
The client WS-RM api will enable users to:
* attach to not closed sequences
* to obtain sequence id so it can be used after client restart
* to pick up all not yet delivered response messages but already available in client RMStore
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite client side RM implementation to ensure QoS
---------------------------------------------------
Key: JBWS-2045
URL: http://jira.jboss.com/jira/browse/JBWS-2045
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RM on client side must be recoverable from client restarts and clients must be able to attach to not closed sequences
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite initial RM implementation to ensure HA and QoS
------------------------------------------------------
Key: JBWS-2048
URL: http://jira.jboss.com/jira/browse/JBWS-2048
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
We have to ensure HA and QoS to make RM production ready.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Refactor server side RM handler to be used by RMReceiver
--------------------------------------------------------
Key: JBWS-2043
URL: http://jira.jboss.com/jira/browse/JBWS-2043
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RMServerHandler:
* will be refactored to behave like message Filter
* will be used by RMReceiver
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite RMDeploymentAspect
--------------------------
Key: JBWS-2041
URL: http://jira.jboss.com/jira/browse/JBWS-2041
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RMDeploymentAspect:
* will de/register endpoint with RMProxy
* will provide QoS policy description to be ensured by RMProxy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite Server side file system based RM store
----------------------------------------------
Key: JBWS-2044
URL: http://jira.jboss.com/jira/browse/JBWS-2044
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
Server side RMStore:
* will store RMProxy registered endpoints
* will store exchanged messages
* will store sequence metadata
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite WS-RM protocol messages de/serialization
------------------------------------------------
Key: JBWS-2042
URL: http://jira.jboss.com/jira/browse/JBWS-2042
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
WS-RM protocol message de/serialization:
* will be based on Input/Output streams
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Implement RMEndpointInvoker
---------------------------
Key: JBWS-2040
URL: http://jira.jboss.com/jira/browse/JBWS-2040
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RMEndpointInvoker:
* will be used from RMReceiver
* will be able to handle local/remote endpoint invocations
* will use addressing logical address for informations
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite RMReceiver to survive server restarts and handle QoS correctly
----------------------------------------------------------------------
Key: JBWS-2039
URL: http://jira.jboss.com/jira/browse/JBWS-2039
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RMReceiver
* will use RMStore to re/store messages, states, sequences
* will use RMEndpointInvoker to invoke remote or local endpoints
* will ensure AtLeastOnce, AtMostOnce, ExactlyOnce, InOrder delivery quality
* will have registered callback to RMProxy (to listen for endpoints de/registered events) and will persist this information
* will be well tested via automatic tests
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rewrite server side RM implementation to ensure HA and QoS
----------------------------------------------------------
Key: JBWS-2037
URL: http://jira.jboss.com/jira/browse/JBWS-2037
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Assigned To: Richard Opalka
Fix For: jbossws-native-2.0.5
RM on server side must be HA and must survive server restarts
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira