Samuel Pessorrusso

Ranch Hand
+ Follow
since Jul 21, 2005
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
(keep public parts private until JForum day)
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt
Moderation Tools

Recent posts by Samuel Pessorrusso

Thanks a lot!

Do you know, did he also have this particular statement in the DB interface documentation? (This way I'll truly forget about this issue )

"If the specified record is already locked by a different client, the current thread gives up the CPU and consumes no CPU cycles until the record is unlocked"

[ November 18, 2008: Message edited by: Alecsandru Cocarla ]

I am the one who Roberto is talking about... Yes I have got this sentence in the assignment when I took this certification (2 years ago, I believe). I can not tell you the solution, all I can tell you is that YOUR ASSUMPTIONS are VERY important. You can implement almost anything if you have the correct assumption. Requirement gathering is also a requirement for this certification, you must prove that you know how to read and understand the list of requirements.
Just document your assumption. There were people who made it asynchronously and other made it synchronously.

Best regards


Originally posted by Adrian Irons:
Congrats Samuel !!

Could you tell me if you show in the component diagram all the user interfaces for the standalone application?.
I�m thinking to show only the business delegates and the rest in a unique component. What do you think about that?

There isn�t a recipe to do the Component Diagram. If you search a little bit you would realize that there aren�t too much information about Component diagrams.
So, that is up to you. Try to think as a developer, if you receive a component diagram, what would you expect and what would be better?
Just add a component when you think that it is really necessary to add more information to clarify your design.

My choice was to include all application components (Components, not classes). I used interfaces only where I thought that it was necessary, as I said, there isn�t a recipe.

Best regards

Originally posted by Anirudh Sonthalia:
Sam, do you think EJB is necessary, can't I just use siple MVC Architecture with Business Delegates, DAOs to persist the information.

I think EJB is REALLY necessary, not just to pass; the given assignment is one of the best scenarios to use EJB.
I would not use EJB just for small applications without a strong load.

Talking about load, just adding to my previous post, I used almost all J2EE Design Patterns (I can't tell more here).

Best regards
[ October 18, 2006: Message edited by: Samuel Pessorrusso ]
Thank you everybody;

My two cents:

Part One: Look for the Objectives in the sun web site and study each of the sections. I used the following books/material:
* SCEA Guide (Joseph Bambara)
* SCEA Guide (Mark Cade)
* HEAD FIRST Design Pattern
* GoF Design Patterns book
* My notes about SCWCD
* My notes about SCBCD (Just read the HEAD FIRST EJB)
* Notes from Javaranch user�s (I think it were Tim�s notes and John�s notes)
* Sun Architect course material (just the material, I didn�t attend to the course)
* Material related to security over the internet

Part Two:
* Core J2EE Patterns (this is a MUST)
* Design J2EE Applications (that PDF book from Sun)
* Petstore Documentation
* Javaranch�s posts

1- I read the assignment 3 or 4 times;
2- Draw the Class Diagram and write assumptions;
3- Draw the Component Diagram and write assumptions;
4- Draw the Sequence Diagrams and write assumptions;
5- Build your JAR, don�t forget to reduce your images� size (convert them to GIF and reduce the number of colors)
6- Check everything;
7- Check again!;
8- Check again!!!;

I had 20-22 classes, ~40 components and 7 sequence diagrams (Prepare, Change, Price, Pay[3] and one explaining my Framework). My doc had about 16 pages (HTML printed).

It is not too difficult; it just takes time (a lot of time in my case, ~150 hours).

Part Three:
Nothing, don�t worry about it. It is completely related to YOUR solution.

Best Regards and thank you againg!
[ October 18, 2006: Message edited by: Samuel Pessorrusso ]
Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061)
Grade: P
Score: 81
Comment: This report shows the total points that could have been awarded in each section and the actual amount of points you were awarded. This information is provided in order to give you feedback on your relative strengths on a section basis. The maximum number of points you could have received is 100, minimum to pass is 70.
Class Diagram (44 maximum) .......................... 37
Component Diagram (44 maximum) ...................... 32
Sequence/Colloboration Diagrams (12 maximum) ........ 12

I took the part 3 on september 20th and the result came today (october 16th).

In my opinion the whole thing is not too difficult but I spent almost 150 hours in part 2.
My advice is to not complicate things and just choose the simplest way and justify.

Thanks everybody!
Best regards

[ October 16, 2006: Message edited by: Samuel Pessorrusso ]
Congratulations and enjoy it!

Could you say when you did the part III exam ? (the date)

Thanks in advance
Best regards
Congratulations! Just wait and they will send the certificate to you.

Best Regards
Congratulations! Enjoy!

Best Regards.
Congratulations. Just wait and they will send the certificate to you.

Best Regards


Could you say when you did the part 3 (the date)?

Best Regards


Best Regards,

Originally posted by Cleuton Sampaio:

Well, you must provide only one JAR File, named after your prometric id (for example: sr1683652.jar).

If you name your jar file in this way you would fail. Using the prometric id sr1683652 it must be scea-sr1683652.jar

Read your instructions carefully, all the things you must do are there.

Part 3 is really easy. It is based on your assigment, it is just to prove that YOU have made it. Study your solution and go for it.

Best regards