Derek Hohls dijo: > Antonio > > Thanks, this is great - maybe we can open a Wiki > page and add this as an attachement (maybe refine > it to make a little more generic; or have a general > version and then variants for more speciifc cases). > > 2 questions - > > a. I assume Hibernate can be used in place > of JDO (and is it any better?)
Yep. <RT> BEAWARE: I am far to be a guru in this area. Currently, I found myself asking about the "viability" of using EJB for the overall task in some applications. Recently, Ralph's posts, triggered in my mind the idea of how will be the best approach to use J2EE (that include EJB) with Cocoon. I read some articles about that too. And there are diferent approach. Some articles tell you that Cocoon need to be used just as a publishing framework while using J2EE. But I think: This was before flow. But, now we have Flow and I don't like the idea of stripdown Cocoon wings when I know how much it can do and help.... Of course this is a very large discussion and a interesting one. What I understand is that you can use Hibernate, OJB or "JDO alone" inside EJB. There is currently a BIG discussion about O/R mapping tools vs. EJB CMP and I am on the JDO side. JDO is really great and simple seems to simplify many complexity that EJB need in order to work. If this is true, then the question is why we need to use EJB CMP in order to reach scalability? Maybe I am wrong, but there MUST be another simple path to this.... and JDO promise that. See: http://www.theserverside.com/news/thread.tss?thread_id=25695 JDO website: http://www.jdocentral.com/ </RT> > b. What are "transient" objects?? and what is their > role in the whole picture? In short, in the for DB developers: Transient Object: NOT stored on a Database. Not a DB Object. Persistent Object: It is sotred on a Database. It is a DB Object. A Formal description of the above: Transient Object: A transient object exists only in the memory of the process that creates it. When that process terminates, the transient object ceases to exist. This is diferent from a persistent object: Persistent Object: A persistent object is an object that continues to exist and retains its data beyond the duration of the process that creates it. Best Regards, Antonio Gallardo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
