This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
which two cannot directly cause a thread to stop executing? A. exiting from a synchronized block B. calling the wait method on an object C. calling the notify method on an object D. calling a read method on an InputStream object E. calling the setPriority method on a thread object The answer is "CE" But I think the answer is "AC".Because I think "exiting from a synchronized block" can do nothing to stop a thread.Am I right?
I think the answers are A, C and E, although the option E is ambiguous. It does not say if setPriority is called on the current thread or another thread, nor does it say if the priority is increased or decreased. If you found this in a mock exam, you can always send and email to the author. HTH
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com