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

[timfox]

"clebert.suconic at jboss.com" wrote : 
  | 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. 
  | 

We're going for an OO approach - let's just keep it simple and have one object with data and behaviour - standard OO approach.

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

Let's concentrate on the goal first, if you want to add extra pages on how to get there, that's fine, but these aren't central - this is a design document not a roadmap.

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

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