Spring Framework Quiz # 5

SecurityContextLoader

SecurityContextHolder

InMemoryDaoImpl

UserDetailsService

The password-parameter specifies the HTTP parameters of password that Spring Security will use to authenticate the user.

The login-page attribute specifies where Spring Security will redirect the browser if a protected page is accessed and the user is not authenticated.

The authentication-failure-url attribute specifies the page that Spring Security will redirect if Spring cannot find the login page.

The username-parameter specifies the HTTP parameters of username that Spring Security will use to authenticate the user.

TestContextManager is the main entry point into the Spring TestContext Framework, but is NOT responsible EITHER for managing a single TestContext OR for signaling events to all registered TestExecutionListeners

TestContextManager is the main entry point into the Spring TestContext Framework, which is responsible for managing a single TestContext and signaling events to all registered TestExecutionListeners

TestContextManager is NOT the main entry point into the Spring TestContext Framework, but is responsible for managing a single TestContext and signaling events to all registered TestExecutionListeners

TestContextManager is the main entry point into the Spring TestContext Framework and is responsible for managing a single TestContext but NOT for signaling events to all registered TestExecutionListeners

<map>

<set>

<collection>

<props>

<list>

Singleton Pattern

Post/Redirect/Get

Factory Pattern

Proxy Pattern

Spring-WS require Spring 2.x or higher

Provides flexible XML Marshalling

Supports WS-Security

Supports integration with Acegi Security

@Repeat(5): This indicates that a test method has to run 5 times.

@Timed: This indicates that a test method must complete in a specified time period

@IfProfileValue:specifies testing environment of the testing method. Only one environment can be specified

@ExpectedException: This indicates that test method suppose to throw certain exception

None of these

Using the destroy method

We cannot destroy, JVM takes take of it

Referencing as null

Return a Callable from the @RequestMapping method

Return a DeferredResult from the @RequestMapping method

Inject a TaskExecutor and pass it to the Session

Spring ORM

Spring context

Spring AOP

Spring Bean Factory

FreeMarker

Hibernate

Velocity

XSLT

When configuring Application Context, Spring supports defining beans either through XML file or annotations starting from Spring 2.5

ApplicationContext is an interface and is an extension to BeanFactory interface.

ApplicationContext provides dependency Injection services and AOP service, but NOT transaction services.

In a web container environment, Spring bootstraps ApplicatonContext via the ConextLoaderListner.

TestExecutionListeners

ReflectionTestUtils

TestContextManager

SpringJUnit4ClassRunner

@Service is to identify that this class is a spring component providing business services.

@Transactional annotations describes transaction attributes of the class.

@PersistenceContext is a Spring annotation which instructs Spring to inject a SessionFactory

@Repository instructs Spring to translate the vendor-specific exceptions to Springs's DataAccessException hierachy.

Transactions uses less memory and improves performance

Read only transactions prevent Hibernate from flushing session

There are no transactions in Hibernate

None of these

BeanFactory factory = new XmlBeanFactory(new FileInputStream(“beans.xml”));

BeanFactory factory = new BeanFactory(new FileInputStream(“beans.xml”));

BeanFactory factory = new XmlBeanFactory(“classpath:beans.xml”);

BeanFactory factory = new BeanFactory(“beans.xml”);

the default value of readOnly attribute is true

The timeout attribute defines the number in seconds for transaction time out.

The rollbackFor attribute defines which exception class will cause the transaction to roll back

If not specified the default value of propagation attribute is Propagation.REQUIRED

The Spring Framework gives you an opportunity to customize transactional behavior, using AOP

The Spring Framework support propagation of transaction contexts across remote calls

The Spring Framework provide a simpler API for programmatic transaction management than a number of complex transaction APIs such as JTA

The Spring Framework offers declarative rollback rules

Use the @ContentType annotation

Use the 'contentType' attribute of @RequestMapping

Use the 'produces' attribute of @RequestMapping

Use the @ContentType annotation

Use the 'consumes' attribute of @RequestMapping

Use the 'contentType' attribute of @RequestMapping

GrantedAuthority

Authentication

UserDetails

UserDetailsService

This annotation will inject the SpringJUnit4ClassRunner bean in the test class

This annotation is indicating the test where to get the context files containing the bean definitions

This annotation means that tests are going to be able to get hold of instantiated beans as defined in the Spring context files

This annotation will facilitate the test to get hold of the ApplicationContext

as part of testing, making sure some code is executed before the transaction is started

as part of Spring AOP, defining what to execute before the transaction is started

as part of Spring OXM, what to serialize before the transaction is started

Gets the the value of the "complete" attribute of the session.

Submits the form input from the user.

Expires the session Data of a controller.

Sets the attribute the session as "complete".

None of them

Both of them

@Transactional(readOnly = true)

@Transactional(propagation = Propagation.NEVER)

byName

byType

autodetect

byClass

The security context is established by calling SecurityContextHolder.getContext().setAuthentication(...), passing in the returned authentication object

The username and password are obtained and combined into an instance of UsernamePasswordAuthenticationToken

The AuthenticationManager returns a fully populated Authentication instance on successful authentication

The UsernamePasswordAuthenticationToken is passed to an instance of AuthenticationManager for validation

createPreparedStatement(Connection)

createPreparedStatement(Datasource)

createPreparedStatement()

createPreparedStatement(Database)

Extending Spring’s ActionSupport classes and getting applications spring-managed beans using getWebApplicationContext() method

Struts - Spring integration is not supported as of Spring 3.x

Any of the given approach can be used to integrate the two

Using ContextLoaderPlugin, configuring spring app to manage actions as beans and then setting their dependencies in a spring context file

processCallback(ResultSet)

processRow(ResultSet)

handleRowCallback(ResultSet)

processRowCallback(ResultSet)