On Sunday 02 November 2003 07:28, Niclas Hedhman wrote: > If you would make, for instance, Merlin EJB/CMP-like, you are facing a much > larger challenge than having a Persistable interface. > You need to introduce runtime modifiable dependency links and likewise > Configuration. You would need to define a transaction system and many other > intricate mechanisms straight into Avalon Framework. > You basically need a JDO/Hibernate/OJB/whatever implementation right in the > core.
Dude this is just a RT. I'm just trying to see if we could have a simple approach. A tradeof beetween EJB & JDO & Avalon. BTW as some (& you) have sugested, a component could be defined to handle persistence. This already exist and seems quite obvious. > I don't think that is feasible, even by leveraging something like > Hibernate, it requires massive changes, and for those who MUST HAVE it, I > seriously think they should look at above links. Dont be pessimist, we are here to raise challenges. And sometime there are simple and small solution. > Compared to a PersistenceManager as a Component (whether coming via > ServiceManager, Context or container extensions) is a lot easier to deal > with. No prob, it is just that I'm trying to see beyond this, to maybe get some magical model, maybe inside component manager or Merlin Extension. > I hope my negativism doesn't hamper your creativity. negativism is not good for health. I'm not claiming creativity, but just trying to see if there is some good idea from this thread that could enhance component model or Merlin management. take care. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
