Vinod Iyer

Ranch Hand
+ Follow
since Apr 13, 2006
Merit badge: grant badges
For More
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 Vinod Iyer

santosh arroju wrote:Congratulations Vinod , cant stop myself from asking this.. how many years of work experience do you have ??



4.5 years but I have been lucky with my projects, always had tremendous scope and down to earth architects who have groomed me

Hi Ranchers,

I clear SCEA Level 1 wth 87 %.

There are many people I would like to thank
Mikalai Zaikin for his superb notes ( Its incomplete agreed but thats the first thing one should read )
Ranhers for patiently answering my dumb questions ( specially JJ Wright )


Now coming to how I prepared
I read MZ's notes - really helpful to start
Read through most of the specs ( not fully but 20 - 25 % of each one ) - well there is a short cut to exam read 100% and write the exam but it is really impossible ( atleast for me ) to read all the specs fully
Read through Sun Certified Enterprise Architect for Java EE Study Guide, Second Edition - Rough Cut ( Not very useful at this stage since it is no where near what it should be ( my personal comment, might be wrong , again it is similar to MZ's notes but since I had to pay 30$ for it , I found it disappointing for the sheer quality of coverage)
JAVA EE Tutorial from Sun - Very Very good - Essential
JWS White paper - Essential
Java SE Security - Sun website - Essential
Took Sun's Mock Exam and Whizlab's Mock Exams. Both were relatively easy compared to real exam, so they are not very useful, but it is a must to give mock test. It makes you think like the person who set the questions. Most of us who do not care to give mock test miss out on filling the gap between our knowledge and examiner's perspective
All through the exam be conscious that this is a Sun Exam. Technologies like JSF / JPA always wins


Ok I will add more later, right now I want to relax and enjoy.

PS : I prepared only for 2 weeks for this exam and I think if one is good in Architecture this is sufficient



Hi,
In JWS White Paper there are two statements which confuses me

1. In Sandbox mode The application cannot access the local disk.
2- Using the (Java™ Network Launching Protocol (JNLP) API - Work with files on the computer

Ultimately does it mean that in Sandbox mode application can not directly access the local disk but can do so by using JNLP Api's ?

Can someone please confirm this

J J Wright wrote:It's always worth searching the forum to see if your question has been raised previously.

Unfortunately I never received a response from Sun regarding any of the mistakes I found n their practice exam questions.

You may also find the following threads of interest:

Sun ePractice Examination Errors - JMS
Practical Software Estimation




My Apology I have exam tomorrow and I was in a real hurry to get my questions answered , didnt strike that I can search . Missed it in hurry.

But thanks for taking pains to give the link.

Also Sun's Mock Exam has atleast 4-5 wrong answers Pretty disappointing
Thanks wright. I was going to read that book today, your reply in other topic just saved my time. I also cited more than 10 references in Sun Mock test.

J J Wright wrote:The following is from one of Sun's SCEA ePractice questions.

Your application sends three messages with no delivery failures to a JMS destination, where two consumers consume messages from the destination.

How do both consumers ensure they receive all messages?

A) Consumers listen to a JMS queue without message selectors
B) Consumers listen to a JMS queue with message selectors
C) Consumers subscribe to a JMS topic with message selectors
D) Consumers subscribe to a JMS topic without message selectors

Answer

Option C is correct
Options A, B are incorrect because consumers subscribe to a JMS topic
Option D is incorrect because consumers subscribe to a JMS topic with message selectors

This seems completely wrong! The JMS 1.1 specification contains the following description of a selector:

�A JMS message selector allows a client to specify, by message header, the messages it�s interested in. Only messages whose headers and properties match the selector are delivered. The semantics of not delivered differ a bit depending on the MessageConsumer being used.�

Section 6.11 of the specification, TopicSubscriber, goes on to say:

�Messages filtered out by a subscriber�s message selector will never be delivered to the subscriber. From the subscriber�s perspective, they simply don�t exist.�

Has any one else come across any other errors in the SCEA ePractice questions from Sun? This is second one I�ve found. I guess it�s not a bad thing if it causes you to think a little harder but then again it�s pretty disappointing after having paid good money for these questions.



This particular question has been corrected. Now it says durable subscriber !

dharmendra gahlot wrote:I don't why is this confusion?

JAXP provides API for XML processing. JAXP does not provide API for attachment.
SAAJ is SOAP with Attachment API for java. It means SAAJ attach an attachment with SOAP messaging capability.
so surely SAAJ is the correct option.



Yeah correct I just messed up big time. Dont know what was going on in my mind, I was reading JAXP and thinking JAX-WS.

Thanks anyways
"Servlet 2.4 spec.
Option C is correct because the default behavior for JSPs is for the service method to be synchronized in the resulting servlet.
" - Sun Mock Exam Explanation

I am very sure this is untrue. Can some one confirm

Hi Ranchers,


I came across below qstn in a mock test

Your organization is interested in building an application that will allow users to query and read volumes of statistical data for analysis. They anticipate high volumes of traffic and want the most scalable solution. This application will be distributed in a cluster and deployed as an enterprise archive. Components should be designed so that they can be accessed remotely by other Java applications.

What Java EE component type and remote access technology is correct for this architecture?

A Servlet accessed using HTTP.
B Message-driven bean accessed using JMS.
C Stateless session bean accessed using RMI.
D Stored procedures and DAO's.


I woud suggest option C is most scalable solution. Since Session beans are pooled and also they support remote invocation . But D is given as correct option.

I am unable to digest why not C.

Anyone can throw some light on this
Hi I came across below question in a mock test

You need to implement a Java attachments API that will enable developers to produce and consume messages conforming to the SOAP 1.1 specification and SOAP with attachments.

Which is the correct API to implement?

A JAXB
B StAX
C SAAJ
D JAXP

The answer provided is SAAJ but I doubt it, if i understand the question correctly it states that developers needs to produce and consume messages conforming to SOAP1.1 and SOAP with attachments.

JAXP uses SAAJ internally and it is more capable to handle SOAP messages, from what I understand is SAAJ is only for attachment support in SOAP. Hence JAXP is more appropriate according to me.

Am i missing something very obvious ?




Kumar Ala wrote:I do agree that we can use JNI to connect to C++, Can anyone explain why not the choice C.


yes corba can be used but won't it be an overkill for solving the current problem ??
From SCEA exam point view or even generally when is a website called high traffic website ( which needs a scalable EJB solution not just simple MVC with DAO ).

I thought 50/100 concurrent hits is a high number.

But i have come across in mock exams from javabeat that 50/100 concurrent hits is not a candidate for high traffic website !

Could someone please provide some clarity on this

Kumar Ala wrote:As per my understanding we can not make calls to C++ application only through RMI, we should use IDL(through CORBA) or RMI IIOP. So Option C might be suitable in this case.



JNI can be used to make calls to C++

sriram sankar wrote:Yes Option D is better since if you deploy the c++ application in one location and access it from RMI server, it makes lot of things easier like

1) We don't need to make JNI calls from every client, since this will be done at the server end.

2) Security will be major issue when accessed from applets.

3) Use your web application to communicate with RMI instead of applet.



Thanks Sriram, very reasonable explanation. I am now convinced
I like your way of answering , you never give answers just give directions !

Even I could boil down to Builder and Factory Method Pattern.

But not able to decide between these two. Factory Method looks a bit closer but not 100% sure