[
http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-681:
-------------------------------------
We should remove AOP usage from the standard stack, and use java.lang.reflect proxies as
EJB3 does to allow users to specify a stack of interceptors on both client and server
side.
The functionality currently in the client side JMS aspects should be moved into a set of
standard classes:
ConnectionFactory, Connection, Session, Consumer.
Note that this *do not* correspond to JMS connection factory, connection, consumer
classes. These are a simpler abstraction.
We maintain the standard JMS object implementations which should delegate to these
classes.
Consolidate JMS related aspects into one JMS aspect
---------------------------------------------------
Key: JBMESSAGING-681
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-681
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta 1
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.
--
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