SPRINGSOURCE -Core Spring (based on Spring 3.2) Set 3

Traditional RMI requires the client to catch RemoteExceptions, but Spring's approach does not ✘ Traditional RMI requires implementing java.rmi.Remote, but Spring's approach does not ✘ Both approaches require you to extend the UnicastRemoteObject class on the server side ✘ Both approaches require method parameters and return values to implement java.io.Serializable ✔

To drive authentication ✘ To enforce authorization of web requests ✘ To provide a logout capability ✘ All of the above ✔

The URLs are specified in the XML configuration using the tag, with the most specific match first and the least specific last ✘ The URLs are specified in the XML configuration, with the least specific match first and the mostspecific last ✘ The URLs are specified in a special properties file, used by Spring Security ✘ The URLs can only be specified in web.xml as part of the Servlet mapping ✔

It provides a strict implementation of the Java EE Security specification ✘ Authentication data can be accessed using a variety of different mechanisms, including databases andproperties files ✘ Security can be configured at the method level ✘ Tag libraries are provided for displaying security context information in JSP pages ✔

To provide a mechanism for applying security to Spring Web Services ✘ To allow certain URLs to be tagged as requiring secure access ✘ To provide functionality in JSP pages, such as hiding certain sections based on roles ✘ To allow Spring Security to be applied to XHTML ✔

Spring cannot use a standalone JMS provider ✘ Spring can use the JMS resources provided by an application server ✘ The ConnectionFactory cannot be standalone ✘ The ConnectionFactory cannot be retrieved from JNDI ✔

The JmsTemplate manages resources transparently (e.g. Connections, default Queue...) ✘ The JmsTemplate converts checked JMSExceptions to runtime equivalents ✘ The JmsTemplate provides convenience methods and callbacks ✘ All of the above ✔

setDefaultDestination ✘ onMessage (asynchronous call) ✘ convertAndSend ✘ receiveAndConvert (synchronous call) ✔

Spring will automatically receive messages from the order.queue.destination ✘ The orderListener bean has to implement javax.jms.MessageListener or Spring'sSessionAwareMessageListener interface ✘ The application needs to run in an application server that provides a JMS implementation out of the box ✘ Spring will automatically send a response message ✔

Multiple parameters can be dependency injected into a constructor ✘ Using XML configuration, the constructor-arg element may be omitted if the constructor requires asingle parameter ✘ One single bean cannot mix constructor injection with setter injection ✘ All of the above ✔