[jboss-user] [JBoss Seam] - Seam design

[monkeyden]

I'm in the process of designing a new, and much larger Seam application and had some design questions.  First, here are a few things I'd like to have in my next Seam implementation:

1.  Provide some separation of interests without committing to the onerous DAO pattern
2.  Provide some way to implement non-persistent business methods. These might be state-sensitive mutators (e.g. modifying some entity attribute when some other entity attribute crosses a threshold) 
3.  Provide a lightweight object to interact with in the SLSB, rather than the entity itself, without having to duplicate all of the entities methods.

My first thought was to have my business objects extend their respective entities, to make use of it's methods and implement finders and non-persistent business methods, but then I lose EJB 3.0 persistence, so that's out of the question.

>From my first implementation of DAOs, I felt as though I was writing (generating) a lot more boilerplate code than I should.  Has anyone discovered a way to get reasonable separation without having to replicate the entire entity interface?



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

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