Does EJB 2.0 Guarantees Dirty Detection Mechanisms

[Anand Wadhwani]

Please refer HF-EJB book objective #2 at pg. 60 (First chapter)

It mentions that EJB 2.0 does not guarantees the dirty detection mechanisms. But this seems to be contradicting the specs (Pg. 26, first bullet on top of the page).

Please advice.

Also, Do I really need to know what's "new" in EJB 2.0 on top of EJB 1.1/1.0? Somehow I dont like the first chapter mock question #3.

Thanks!!
[ October 26, 2005: Message edited by: Anand Wadhwani ]

[Peer Reynders]

Originally posted by Anand Wadhwani:
It mentions that EJB 2.0 does not guarantees the dirty detection mechanisms. But this seems to be contradicting the specs (Pg. 26, first bullet on top of the page).

The section in question is

To support more efficient vendor implementations leveraging lazy loading and dirty
detection mechanisms; to reduce memory footprints; to avoid data aliasing problems;
etc.

Support isn't the same as guarantee. The specification was changed to create some opportunities for the vendors to implement these features if they are so inclined - the specification does not mandate the implementation of these features.

Originally posted by Anand Wadhwani:
Do I really need to know what's "new" in EJB 2.0 on top of EJB 1.1/1.0? Somehow I dont like the first chapter mock question #3.

That question is in line with the Testing Objectives:

EJB Overview:
Identify the use, benefits, and characteristics of Enterprise JavaBeans technology, for version 2.0 of the EJB specification

[ October 27, 2005: Message edited by: Peer Reynders ]

[Anand Wadhwani]

Thank you very much Peer! Your posts are really quite helpful.