adamy's Journal: EJBs vs JDO

I really need to get my mind around this JDO thing. The problem is I don't want to introduce yet another technology. The counter problem is that I don't want to reinvent JDO, and most of our optimizations seem to be leading that way.

Radnom Musings: Do JDO and Entity EJB solve different problems? Should we Wrap JDO with Entity beans in certain cases? Shoud we completely disregard Enitity beans and only Use JDO?

The problem with JAWS (JBoss CMP EJB implementation) is that Populating an entity is incredibly time expensive, on the border of 1/2 a second or so. For beans that that are short lived, this is not acceptable.

Still need to look into JBoss 3 to see if they've solved this. Bulk loading of entities is vital for better performance.