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 Sun.com
JavaPassion.com (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.

Example

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

Question:
Pick the right technology for sending XML based reliable message to another system.
A: JMS
B: JAX-WS
C: RMI
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.

Comments

Post a Comment

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

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 @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.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");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more