Skip to main content

SCEA 5 Step 1

I have prepared from the following materials

EJB in Action
GOF Design patterns
J2EE Design patterns
JEE 5 tutorial from (EJB, JAX-WS)

Real exam was different than what I've learned from the above books, SCEA 5 exam was challenging, its an Enterprise Architect Certification so the focus was on solving architectural problems (Scalability, Availability, Maintainability, Picking right technology, & Patterns)

So the above materials covered 60-70% of the objectives, rest of the questions I had to answer from my experience, and most of the answer choices were pretty close.


However i can't post the real question so I'm providing this from my own

Pick the right technology for sending XML based reliable message to another system.
D: Stateless bean

as you can see A, B, C are all correct i.e. we can send an XML message to another system reliably

My Advice:
However I would cross all those choice which doesn't seem appropriate for the given scenario, and most of the time you will be left with two close choices so what I would suggest is see previous and next question to identify the current context (i.e. are they focusing on JAX-WS or JMS) that will help you solve the question

I guess I've already hinted like how to prepare for this exam, here are few more points to remember
1. No need to remember code and syntax (I've spend some time remembering EJB, JMS, JAX-WS, TrAX annotations and api, waste of time)
2. No Design diagrams are asked (When preparing for patterns I've spend substantial time on design diagrams they are of no use for step 1)
3. Key is understand when to use (Stateless, Statefull, JMS, JAX-WS, Servlets, JSP, JSF etc) technologies
4. Understand which is the most appropriate technology to use for a given problem
5. Spend some time on the following concepts (Availability, Maintainability, Scalability etc)
6. Patterns ( I realized they mostly focus on most used patterns ) so spend more time on the famous one's.


Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax.

Example 1: Stores list of Strings in an Entity

public class Users implements Serializable {

    private static final long serialVersionUID = 1L;
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    private List<String> certifications = new ArrayList<String>();

    public Long getId() {
        return id;

    public void setId(Long id) { = id;

    public List<String> getCertifications() {
        return certifications;

    public void setCertifications(List<String> certifications) {
        this.certifications = certifications;

        Users u = new Users();
        u.getCertifications().add("Sun Certified Java Programmer");

Generated Tables

Column --> ID
    Row             1


ArrayList vs LinkedList vs HashSet Performance Comparision

ConclusionsInserting & Reading sequentially from Collection prefer LinkedList/ArrayListInserting & Reading/Deleting by Search/equals from Collection prefer HashSetInserting, ArrayList & LinkedList performs best while HashSet takes double the timeReading, HashSet performs best while ArrayList & LinkedList are marginally lessDeleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet
Inserting/Reading/Deleting integer's from zero till countJDK7Collectionactioncounttime msArrayListInsert1000/1LinkedListInsert1000/1HashSetInsert1000/1ArrayListInsert100005LinkedListInsert100004HashSetInsert100007ArrayListInsert10000011LinkedListInsert10000011HashSetInsert10000021ArrayListGet/Read1000LinkedListGet/Read1000HashSetGet/Read1000ArrayListGet/Read100004LinkedListGet/Read100003Has…

Validating CSV Files

What is CsvValidator ?
  A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
  You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
  Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.

What is the license clause ?

Are there any JUnit test cases for me checkout ?
 Yes, source

How to integrate in my existing project ?

Just add the Jar which can be downloaded from here CsvValidator.jar and you are good.

Instantiate CsvValidator constructor which takes these 3 arguements

         // filename is the the file to be validated and here is a sample         // list - defines all the fields in the above csv file ( a field has index, type, isOptional, rege…