Based on your previous posts here, I would say that you are ready to take the exam. I don't feel that part I is very difficult and most people seem to overprepare for it. You are probably one of those people. You should schedule your exam for a week from today. Print out the notes found on this site and the yahoo group if you haven't already. Read through each set a few times. Go pass the exam.
I know I didn't study nearly as hard as you did. I'll bet you'll score around 90%. Some others here, I worry about how they will do, because their knowledge is not yet complete. And sometimes, they pass anyway, though with a low score. You're definitely not one of those people.
Because it would be fun. As weird as that may sound. And I really wasn't that happy with my original score. Not that with 161 questions ,some with errors in it, will I really hope to do better, but I have learned so much more since then, and I'd like to see what happens. Plus I can help Sun out. Mark
Mark and I have been together through scjd and scwcd. I know Mark as a bright guy, I really dont understand why so hesitent, Mark? I am reasonbly sure you'll pass it. Worst comes to worst you lose $150 but gain valueable experience, pass it next time. It's not like you taking CPA or Bar exam - no stain on your record. [ May 01, 2002: Message edited by: Gennady Shapiro ]
For messaging they ask rediculously simple questions like: is JMS synchronous or asynch? things of that nature. But then they they might give you a real life scenatio involving JMS and you need to understand it, but its all very high level you dont need to know JMS API. In fact, all you have to know about JMS is that its asynchronous messging and you can figure out answers from there.
Hi folks, I thought JMS was both! Before going crazy I had to look at the Java JMS tutorial and found this: "Messaging products are inherently asynchronous in that no fundamental timing dependency exists between the production and the consumption of a message. However, the JMS Specification uses this term in a more precise sense. Messages can be consumed in either of two ways: Synchronously. A subscriber or a receiver explicitly fetches the message from the destination by calling the receive method. The receive method can block until a message arrives or can time out if a message does not arrive within a specified time limit. Asynchronously. A client can register a message listener with a consumer. A message listener is similar to an event listener. Whenever a message arrives at the destination, the JMS provider delivers the message by calling the listener's onMessage method, which acts on the contents of the message" From my point of view, you can't say that it's either way, it depends on how you use. Or? /Enrico
Enrico, you are missing an important point. The producers and receivers exchange messages asynchronously. A producer does not have to block until his receiver gets the messge and acknowledges it. In this sense JMS is asynch. Specific ways of receiving messages - listeners or blocking calls to queues -- are not that important. Think of it this way. When you make a phone call you either connect or you dont, in either case you know the outcome of your call. When you send a letter you really don't know whether the receipient ever gets it, you just drop it and go by your business. The receiver may seat by his mail box (blocking call) and wait for the letter doing nothing else or 'monitor' box's status periodically (listener). In either case the mail is still asynchronous. Here's a great example of asynchronous message that failed to be delivered. A guy gets a parking ticket, sends his payment, the city never receives the check, the city suspends his driver license, at some point later somebody rearends HIM, police comes, police runs his license -- it comes back suspended, the guy spends a night in jail. Real story.