Originally posted by Ajith Kallambella:
Here is my two cents worth...
It all depends on what *your* career aspirations are. If you want to be an expert in WebLogic product suite, you must plan to take product certifications offered by BEA. However, if you want to tout yourself as an Enterprise Java Arcitect, SCEA should be your goal.
Although as you have noted WebSphere and WebLogic dominate today's J2EE implementations, I have seen plenty of job openings calling for skills in a third-party app server( Sun, Pramati, JBoss, OracleAS etc). IMO vendor certifications (obviously) focus more on product specifics whereas SCEA tends to be product agnostic. Specs, best practices, patterns, UML, SDLC process - all these constitute the repertoire of a seasoned architect and *none* of these are specific to product implementations. I am not trying to undercut the importance of "knowing your app server", but as a hiring manager, if I know that you( as a candidate) know core J2EE and all of these things, I will be willing to accept your limited(or lack of) knowledge of a particular app server. After all, how long does it take for one to read a product manual and learn the basics? Therefore, I personally value SCEA more than vendor certifications. Ofcourse, I will certainly prefer somone having both
Originally posted by Hai Lin:
Vitaliy,
If based on what you said, Bean provider only provide the abstract getter/setter, then why in HFEJB, Page 318, Complete code for the CustomerBeanCMP class, the bean proveider also gave us the concrete implemtation of all the abstract getter/setter?
Waiting for your reply.
Thanks a lot.
Hai
Originally posted by Hai Lin:
Hi All, I got a question about mock question in HFEJB, Page 367,
Question 1:
What's true for a bean provider when creating an entity bean using container-managed persistence? (Choose all that apply).
A. Container-managed persistent fields must be defined in the entity bean class.
B. Container-managed relationship fields must be defined in the entity bean class.
C. When implementing a one-to-many relationship, the java.util.List interface must not be used.
D. Accessor methods for container-managed relationship fields must be exposed in the bean's remote component interface.
The answer given by the book is: C. But why A, B is not right?
(I know as for option C. Only collection or Set can be used, so C is right,
as for option D, should be local component interface, not remote component interface. Why A, B are not right? )
Please help me clarify this question?
Thanks a lot.
Originally posted by sarah Marsh:
'Remote interface of bean A' could be the correct answer also, right?
Originally posted by sarah Marsh:
question:
A container-managed persistence (CMP) entity bean A has a one-to-many unidirectional relationship (CMR) to another container-managed persistence (CMP) entity bean B. Which interface can expose the methods related to this relationship?
The answer is 'Only local interface of bean A'.
Why have to be local interface?
Thanks a lot!
Originally posted by Nicholas Cheung:
Congrad!!!
You did a cool job!!!
What's next?
Nick
Originally posted by Vishy Anand:
Waiting for the reply on the above question. Any EJB expert out there, reading this?
Originally posted by Valentin Crettaz:
Alex,
I'm glad you made it work
Vitaliy,
Unfortunately, when the spec says that the session bean class has to be public, it really means it and expects that container providers enforce the rule
Originally posted by Valentin Crettaz:
Your example does not conform to what the spec mandates in section 7.10.2, namely that session bean classes must be declared public.
I know this does not answer your question, but everything that does not conform to the spec is not worth investigating anyway
Originally posted by Sujatha Kumar:
When a Bean instance is associated with a trasaction, it
cannot be Passivated
Originally posted by mini mehta:
Hi
Sorry it should SessionContext Object.
But amazingly answers given at the SCBCD revising site are 2, 3 , 5.
Mini