Just want to share my experiences, hopefully it'll help someone. 1. Overall the exam was considerably easier than I expected, but not exactly trivial. 2. I have read people been seeing initial 10 question being "warm-up" easy question. That was not the case. 3. Not too many Exhibit questions ...maybe 5-7. 4. Descriptors questions are very high-level, I feel kinda stupid for spending lot of time memorizing DTDs. But, you must understand DD elements purpose for being. 5. Had a question involving Template Method design pattern. Have no idea what it is - I think I missed it, otherwise patterns are relatively easy. 6. Tags are a big part of the test. Many questions on return values and related behaivor. No questions on advanced stuff like JSP tag objects, methods of pageContext, buffered outputs, nothing of that nature. Dont let this discorage you from studying it though. 7. Distributed apps was tricky piece. Asked if URL rewriting was prohbited in distributed mode, that seemed like the most reasonable option in multiple choice -- still dont know if thats true. I figured diff apps may have different methods of session traking and cookie would be the lowest common denominator. 8. Java beans - too easy. 9. Threading -- easy , but read closely. in general I found it very useful to mark a question if you not sure and come back to it later, i think i fixed 2-3 answers like this. Plenty of time. Also, dont be fooled be practical experience u may have, this test is mostly academic.
Thanks to all who contributed to this forum. Javaranch has been great, this is my third cert and I've gotten much help especially for project-oriented certifications.
7. Distributed apps was tricky piece. Asked if URL rewriting was prohbited in distributed mode, that seemed like the most reasonable option in multiple choice -- still dont know if thats true. I figured diff apps may have different methods of session traking and cookie would be the lowest common denominator.
I had a similar qstn. I think I lost on this qstn. Mine was more pertinent to SRV.7.7.2. - satya
Take a Minute, Donate an Hour, Change a Life
Actually it does make sense. In a clustered environment you must have a hardware and software proxy-loadbalancer. Those who works in a large company must've heard of things like Cisco LocalDirector, DNS round robin, or something like Weblogic proxy-loadbalancer. If I am not mistaken hardware loadbalancers support "passive cookie" loadbalancing mechanism to route requests but not URL-rewriting. I think that is the reason URL-rewriting is not allowed in distributed environments, although I didnt find anything in servlet spec. Thoughts anyone?