ahmed fayed

Greenhorn
+ Follow
since Aug 28, 2010
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by ahmed fayed

I would recommend Head First Design Patterns by Freeman, and Core J2EE patterns books to start with, it will help you allot in the certificate and in your actual work.
Delegate layer has many forces besides isolating the presentation from the business tiers, like exception translation, hiding the details of service creation, reconfiguration, and invocation retries from the clients...etc.

Although JSF can use EJB 3 annotation to call the session beans directly, but the other delegate forces makes it worth to use than the annotation option.

From my readings in this forum and other users' experience, the more patterns you include in your design the more points you get, also there are questions in part three about the used patterns and the reason of using it, and so it will be a good point to mention there.
For a summary about those parts you can read JEE 5 tutorial and try out the mentioned examples.
I've found another way to keep the direct relation between the two domain entities by using a Map ElementCollection feature of JPA 2.0; I've tested it on the quantity attribute and found it working.
it's because he assumed that the user data will be maintained in LDAP server, so it's not represented as entities.
Thanks Jeanne for your reply; I'm changing in the shape of existing relation in the domain model which was direct many to many but I injected the joined table in between (it's still many to many but the diagram is changed), after seeing some threads I think I'll remove it as loosing some points for not handling quantity attribute is better than loosing them all for changing in their holy domain model.

what do you think about the desing problem itself, am I right and the built in manytomany anotation in JPA can't handle this alone?
I have a many to many relation which requires additional attribute to be persisted in the join table, for example Order and Product relation with quantity attribute.

to use JPA, that join table should be implemented as entity, and the relation is broken into many to one and one to many, I saw in many threads that I have to reserve the given domain relations without a change, I heard that many people lost points because of changes in the given domain model.

Should I reserve the given model as is (how to persist quantity in this case?), or can I change the given mode without a problem?
I recommend using this study guilde Adel Al-moshaigah http://www.scribd.com/doc/25297376/Java-5-Architect-Exam, it's much better than the cade one, and it covers all of the objectives, I've used the Cade's study guide but it didn't help me allot in the exam, I was reading from Adel's book bits and pieces but I regret not reading all of it.

Also recommend you to read and try the APIs using JEE 5 tutorial.
***************
SCJP, SCWCD, SCEA
I totally agree with you Rajiv, the three practice exams are worthless, it all repeated from the learning mode, I scored up to 95% in the practice exams, but I've passed today with 75% only, I found that the level of questions in the actual exam is much harder and more in depth than what I got trained on in whizlap simulator, even there was a task style questions which has no similar style in whizlaps simulator.

whizlaps helped me a bit but its a low value for the paid money, and I wouldn't recommend it if you target a high score.