Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Exam differences : SCBCD 1.3 X 5 ?

 
Steven Colley
Ranch Hand
Posts: 290
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks,

I'm preparing myself to take SCBCD1.3 soon..after I'm supposed to tae SCBCD 5 test as well.

My question is..how different is this test regardless the new JPA api ?

I meant...:

1) is the session bean questions the same? (is there any changes in the session bean specs?)

2) will entity beans be required in the test? (is there any change?)

3) what about transactions and security parts?

Please..for those who already took both tests, advice!!!

Tks so much!!!
 
Camilo Morales
Ranch Hand
Posts: 92
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just took the SCBCD 5 test, but i had a few previous experience with J2EE 1.3 so I'm going to try to answer a copuple of your questions:

Originally posted by Felipe Pittella:

My question is..how different is this test regardless the new JPA api ?

JPA is the major change in JEE 5 ... it is TOTALLY re-design... completely different ... entities are no longer components ... they are POJO's ... do not need any interfaces to be accessed ... can live outside of the container. etc. EntityManager and Persistence Context concepts are introduced in order to manage the new type of entities.



2) will entity beans be required in the test? (is there any change?)

Yes, and yes there are A LOT of changes.

Regards,
 
Steven Colley
Ranch Hand
Posts: 290
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

2) will entity beans be required in the test? (is there any change?)
Yes, and yes there are A LOT of changes.



As far this question..when you meant A LOT of changes ..did you mean changes for entity beans contract, right???

And what about transactions, exception and security?

Tks ;-)
 
Camilo Morales
Ranch Hand
Posts: 92
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
( Sorry about the "Regardless" JPA in the first question,,, didn't notice that until after I posted the reply. )

Yes, everything changed about entities ... now is the EntityManager with an attached Persistence Context the one that is responsible of manage the Entity lifecycle at runtime ... not the container as with Sessions and Message-Driven Beans. You don't have to use the Home interface in orden to "crate" (or load from database) an entity ,,, now you can just create a new instance like instanciating any other java class with the NEW operator, and then you can use the EntityManager to attach the entity to a Persistence Context and at commit time save it to a database.

I guess people that is familiar with the J2EE 1.3 version won't find it too hard to understand the changes about Session Beans and Message-Driven Beans because almost all of these changes are made in order to make the developement easier ... also the JPA changes ... but the changes in this area ar far more deep than the changes of the other components of the architecture. (I find JPA-Hibernate oe TopLink or any of these OR Frameworks VERY VERY VERY nice )

Regards,
 
Steven Colley
Ranch Hand
Posts: 290
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK Camilo, Tks so much!!!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic