Sun's cooperation development of EJB3 and JDO2 in September last year entered the substantive stage, in addition to the EJB3 expert group, in addition to the members of 6 JDO2 expert group entered the EJB3 expert group, the EJB3 will be released regularly to the JDO expert group. At present, EJB3 is developing an EJB3 API in a non-J2EE (ie, J2SE Environment). The non-J2EE-API of EJB3 will primarily draw on the standard and experience of JDO2, so the non-J2EE-API of EJB3 is responsible for leading from JDO2 Patrick Linsy.
The current EJB3 specification must rely on the J2EE container to run, one but also allow EJB3 to operate outside the container, EJB3 will be both a data persistence of J2EE, or a data persistence of J2SE. JDO2 is currently preparing to publish API packages and TCK tests, which can foresee the JDO implementation of TCK compatibility test before JavaOne. Relative to the lag of EJB3, JDO2 is still driven by the active JDO2 development community. The problems and recommendations found in use are considered and adopted, maybe there is JDO3?
The Red Industrial Park will release its own EJB3 preview versions and ready to perform JDO2 compatible tests in the near future.
