> I'm also very, very! much interested in persistence and transaction > management in Avalon/Merlin. I just got the opportunity to build a > technical prototype for a huge enterprise project, which I will build on > Merlin.
We have very close goals :-) I'm in charge of build a framework from persistence layer to persistence... This framework should not depends on any technology like EJB, Hibernate or any other. Each project has its own reality - sometimes the customer doesn't want to work with EJB for example - so I must propose something that this kind of facility could be plugged on or off. > capabilities, so that "persistence" is transparent and not only > transactions. Yes, this is fine. I'd like to provide transaction handling on POJO just like xdoclet does for EJBs, so the developer only need to learn one thing. > trx = UserContext.startTransaction(); > trx.insert(businessObject); > trx.commit(); I think this is a bit intrusive :-\ I'm thinking about a simple (or complex) object model that each entity exposes a save/remove and delegate this work to a EntityPersistence for each model. We are in Avalon world, so a EntityPersistence will be pluggable. For sometimes this would use EJB, sometimes a plain DAO or Hibernate... What do you think? regards, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
