]
Clebert Suconic updated JBMESSAGING-681:
----------------------------------------
Attachment: (was: patch.diff)
Refactor client side model
--------------------------
Key: JBMESSAGING-681
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-681
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 2.0.0 Alpha
Attachments: backup-r3568.patch
Currently, client side JMS functionality is implemented in a set of aspects:
SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have
these as separate aspects since we either provide all the jms functionality or none of
it.
Having the functionality distributed across several aspects makes it hard to communicate
between them meaning the code is messy and hard to follow.
We should consolidate into one aspect, from which hang a set of classes Session,
Connection, Consumer etc which implement the jms functionality in a nice OO way. This will
make the code simpler and easier to understand and possibly more performant since we would
avoid unnecessary calls through the stack.
The classes should be chosen to represent generic messaging, not just JMS (e.g. no need
for a producer).
We also need to have an extension point so customers can add their own vanilla
interceptors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: