Hi, I was reading the introduction to "Java Data Objects" in the book store and it seems that JDO is supposed to take the place of EJB's. I don't really hear much about EJB's any more, at least not like I used to. I was wondering if anyone has comments about what the current trend is, and has anyone used JDO in a real project. thanks, Barry
JDOs started out as a standard for mapping objects to either OODBs or RDBs. The initial version of JDO had some design features that made working with an OODB easier but working with an RDB harder (like no support for the Object-Relational mapping). Much of that has been addressed in later specs, but the main commercial vendors of JDO products continue to include OODB companies. There are a number of "best of breed" object-relational mapping products that address the performance issues of EJBs without requiring JDOs. EdgeXtend from Persistence Software and Toplink from Oracle are two such products. Some links for more information on this include: <vendor stuff> 1. Persistence object-relational mapping (BMP or POJO) 2. Persistence distributed object caching - chris
Roland Barcia
author
Ranch Hand
Joined: Apr 15, 2004
Posts: 177
posted
0
JDO is an alternative only to Entity Beans, not EJB as a whole. You can use Session Beans and Message Driven Beans with JDO. Please do not say JDO vs. EJB. Say JDO vs. ENtity Beans
Roland Barcia<br />STSM - ISSW Lead Web 2.0 Architect
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
0
