[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Refactoring on delegates

[clebert.suconic@jboss.com]

anonymous wrote : 
  | I don't want to see any state or delegates methods remainaing - that's a half way hack. There should just be ConnectionFactory, Connection, Session and Consumer classes in the agnostic layer - all the code from the delegate, state and aspect classes should end up in those classes.
  | 

that's ok...  but looking at the code now (with all the fields we have on states) it seems that would be reasonable to keep separated data for Connection, Session.. etc... like SessionData, ConnectionData and so on...  This wouldn't be like the SessionState we have now.. just a separated POJO. 

anonymous wrote : I don't think we have need of any interceptors (apart from * see below), ClosedInterceptor can be easily implemented without being an interceptor.
  | 
  | Failover doesn't need interceptors either. We just have a simple valve on Jeff's dispatcher send methods. So no need for a factory or anything else to create any proxies.
  | 

That's exactly what I thought one hour after I sent the post/finished the doc (I just  think about the Customer's needs on interceptors tough). I thought I would be able to send another post before you wake up in London (6 hours time difference) but apparently you never sleep :-)


anonymous wrote : The current wiki page describes various intermediate versions. That's fine, but I'm not so interested in the intermediate ones, but really the end goal. I think it's a bit confusing describing intermediate stages.
  | 


I was more concerned about how to get on the final model, than the final model itself.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108287#4108287

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108287