A Walking Tour of (almost) all of Springdom

A Walking Tour of Spring

Josh Long
Spring Developer Advocate
SpringSource, a Division of VMware
http://www.joshlong.com || @starbuxman || josh.long@springsource.com

© 2009 VMware Inc. All rights reserved

About

 SpringSource is the organization that develops the Spring
framework, the leading enterprise Java framework

 SpringSource was acquired by VMware in 2009

 VMware and SpringSource bring you to the cloud and
deliver on the mission of “build, run, manage”
• established partnerships with the major players in the business, including
Adobe, SalesForce, and Google to help deliver the best experience for
Spring users across multiple platforms

 Leading contributor to projects like
Apache HTTPD and Apache Tomcat

2

About Josh Long

Spring Developer Advocate
twitter: @starbuxman
josh.long@springsource.com

3

SPRING: a WALKING TOUR

Introduction

4

Why Are We Here?

“ Software entities (classes,
modules, functions, etc.) should
be open for extension, but closed
for modification.
”
-Bob Martin

5

Why Are We Here?

do NOT reinvent
the Wheel!

6

Spring’s aim:
bring simplicity to java development
data
web tier
batch integration & access
& service tier mobile
processing messaging / NoSQL /
RIA
Big Data

The Spring framework
the cloud: lightweight traditional
WebSphere
CloudFoundry tc Server
JBoss AS
Google App Engine Tomcat
WebLogic
Amazon BeanStalk Jetty (on legacy versions, too!)

7

Not All Sides Are Equal

8

The Spring Framework

Framework Description

Spring Core The foundation

Spring @MVC the web leading framework (comes with the core framework)

Spring Security Extensible framework providing authentication, authorization

Spring Webflow An excellent web framework for building multi-page flows

Spring Web Services Contract-first, document–centric SOAP and XML web services

Spring Batch Powerful batch processing framework

Spring Integration Implements enterprise integration patterns

Spring BlazeDS Support for Adobe BlazeDS

Spring AMQP interface with AMQP message brokers, like RabbitMQ

Spring Data NoSQL options: HBase, MongoDB, Redis, Riak, CouchDB, Neo4J, etc.

Spring Social integrate Twitter, Facebook, Tripit, MySpace, LinkedIn, etc.

Spring Hadoop Provides a POJO-centric approach to building Hadoop applications
provides first-class support for service
Spring Mobile, Spring Android
creation and consumption for iPhone, Android
Spring GemFire Provides the easiest interface for the GemFire enterprise data grid technology

9

The Spring ApplicationContext

 Spring Manages the beans you tell it to manage (Implicitly, Explicitly)
• use annotations (JSR 250, JSR 330, native)
• XML
• Java configuration
• component scanning

 You can of course use all of them! Mix ‘n match

 All configuration styles tell the ApplicationContext how to manage
your beans

10


 Annotations (component-scanning)
• best when you want Spring to sort it all out in the wash, no need for explicit configuration
 Java Configuration
• type-safe, and explicit - all configuration is centralized. Provides a good birds-eye view of
your application
 XML
• explicit - namespaces still provide the most punch in a lot of cases
 All together
• use Java configuration for your regular third party beans (like a DataSource)
• XML namespaces for DSLs and higher level functionality (Spring Integration, Batch, etc.)
• annotations for your components (a @Service, or a Spring MVC @Controller)

11


public class Main {
public static void main(String [] args) throws Throwable {
ApplicationContext ctx =
new AnnotationConﬁgApplicationContext( ServicesConﬁguration.class );
CustomerService serviceReference = ctx.getBean( CustomerService.class );
Customer customer = serviceReference.createCustomer( "Juergen", "Hoeller");
}
}

12

Spring Makes Building Applications Easy...

Not confidential. Tell everyone. 13

I want Database Access ... with Hibernate 4 Support
@Service
public class CustomerService {

public Customer createCustomer(String ﬁrstName,
String lastName,
Date signupDate) {
...
}

}


@Service

@Inject
private SessionFactory sessionFactory;

String lastName,
Date signupDate) {
Customer customer = new Customer();
customer.setFirstName(ﬁrstName);
customer.setLastName(lastName);
customer.setSignupDate(signupDate);

sessionFactory.getCurrentSession().save(customer);
return customer;
}

}


@Service

@Inject

@Transactional
String lastName,
Date signupDate) {

return customer;
}

}


I want Declarative Cache Management...
@Service

@Inject

@Transactional
@Cacheable(“customers”)
String lastName,
Date signupDate) {

return customer;
}
}


I want a RESTful Endpoint...
package org.springsource.examples.spring31.web;
..

@Controller
public class CustomerController {

@Inject
private CustomerService customerService;

@RequestMapping(value = "/customer/{id}",
produces = MediaType.APPLICATION_JSON_VALUE)
public @ResponseBody Customer customerById(@PathVariable("id") Integer id) {
return customerService.getCustomerById(id);
}
...
}


DEMO
• the 80% case!

Not confidential. Tell everyone.

...But Where’d the SessionFactory come from?


A Quick Primer on Configuration in Spring 3.1

....
<beans>

<tx:annotation-driven transaction-manager = "txManager" />

<context:component-scan base-package = "org.springsource.examples.spring31.services" />

<context:property-placeholder properties = "conﬁg.properties" />

<bean id = "txManager"
class = "org.springframework.orm.hibernate3.HibernateTransactionManager">
<property name = "sessionFactory" ref = "sessionFactory" />
</bean>

<bean id = "sessionFactory"
class = "org.springframework.orm.hibernate4.LocalSessionFactoryBean">
...
</bean>

</beans>


A Quick Primer on Configuration in Spring 3.1

@Configuration
@PropertySource("/config.properties")
@EnableTransactionManagement
@ComponentScan(basePackageClasses = {CustomerService.class})
public class ServicesConfiguration {

@Bean
public PlatformTransactionManager txManager() throws Exception {
return new HibernateTransactionManager(this.sessionFactory());
}

@Bean
public SessionFactory sessionFactory() { ... }

}


DEMO
 introduce the tool chain
 how to “setup” Spring
 basic dependency injection
• annotations (JSR 250, JSR 330, native)
• xml
• java configuration


Working with many beans


Working with many beans

 Low Level
• BeanPostProcessor
• BeanFactoryPostProcessor

 Higher Level
• AOP


DEMO
 Demos:
• Bean*PostProcessor
• AspectJ


The Life of a Bean


Life Cycles

 Life Cycles for different folks
• “safe and consistent” - use the interfaces
• InitializingBean, DisposableBean
• correspond to init-method and destroy-method attributes
• Simple and component-centric : use the annotations
• @PostConstruct, @PreDestroy
• correspond to init-method and destroy-method attributes
• More power: SmartLifecycle
• gives you the ability to dynamically start and stop beans in a certain order as well as to query
whether the bean’s been started or not.


Scopes

 Spring beans have scopes
• default: singleton
• can be:
• prototype
• HTTP session
• HTTP request
• HTTP application (servlet, basically)
• “step” in Spring batch
• thread-local
• Spring Web Flow “flow” scoped
• Spring Web Flow “conversation scoped”
• Spring Web Flow “view” scoped (in JSF)
• Activiti BPMN2 process-scoped


Scopes

• Implement o.s.beans.factory.config.Scope
• register the scope with a o.s.beans.factory.config.CustomScopeConfigurer

public interface Scope {

Object get(String name, ObjectFactory<?> objectFactory); map-like lookup of
beans in a given
Object remove(String name); scope

void registerDestructionCallback(String name, Runnable callback);
well known beans like the
Object resolveContextualObject(String key); HttpServletRequest ‘request’ for
‘request’ scope
String getConversationId();
}
null, or storage specific
‘conversation’ ID


DEMO
 Demos:
• life cycle callbacks
• scopes
• using
• creating your own


Getting Beans from Strange Places



 FactoryBeans
 Spring Expression Language
• convenient way to get at values and inject them
 Spring environment specific beans (profiles)
• introduced in Spring 3.1
• make it easy to conditionally define an object based on some sort of runtime condition



 FactoryBeans
• interface that’s used to provide a reusable definition of how to create a complicated
object with many dependencies
• Related: Java configuration, and builders
• prefer both over FactoryBeans where possible



 Spring Expression Language
• convenient way to get at values and inject them
• Andy Clement’s a genius
• like the Unified JSF EL, on steroids
• Can be used in Java, XML
• @Value(“#{ ... }”) or value = “#{ .. }”



 Spring profiles
• @Profile(“production”) @Configuration ...
• <beans profile = ‘production’> ... </beans>
• Use System properties or simply specify the active profile on the environment
• Use ApplicationContextInitializer in web applications



...
<beans ....>

 In Development = “default”>
<beans proﬁle
<ds:embedded-database id= "dataSource" type = “H2” />
</beans>
 <beans proﬁle = “cloud”>
In Production

<cloud:data-source id="dataSource"/>
</beans>

</beans>



...
<beans ....>

<beans proﬁle = “dev”>
<ds:embedded-database id= "dataSource" type = “H2” />
</beans>

<beans proﬁle = “cloud”>
<cloud:data-source id="dataSource"/>
</beans>

</beans>


Environment Configuration



 Associating specific bean definitions with specific environments
• XML 'profile' attribute on <beans> element
• @Profile annotation on configuration classes
• @Profile annotation on individual component classes




 Activating specific profiles by name
• e.g. through a system property
• -Dspring.proﬁles.active=development
• or other means outside of the deployment unit
• according to environment conventions




 Activating specific profiles by name
• e.g. through a system property
• -Dspring.proﬁles.active=development
• or other means outside of the deployment unit
• according to environment conventions

 Ideally: no need to touch deployment unit across different stages/
environments


Environment Abstraction



 Grouping bean definitions for activation in specific environments
• e.g. development, testing, production
• possibly different deployment environments
 Custom resolution of placeholders
• dependent on the actual environment
• hierarchy of property sources




 Injectable environment abstraction API
• org.springframework.core.env.Environment




 Injectable environment abstraction API
• org.springframework.core.env.Environment
 Unified property resolution SPI
• org.springframework.core.env.PropertyResolver



 An ApplicationContextInitializer

public interface ApplicationContextInitializer
<C extends ConﬁgurableApplicationContext> {

void initialize(C applicationContext);
}


DEMO
 Demos:
• FactoryBeans
• SpEL
• Profiles
• ApplicationContextInitializers


Other Things Core Spring Supports

 transparent service remoting
 seamless JMX support, both consuming and exposing
 transaction management
• (which we’ll look at shortly)
 job scheduling
 thread management
 object to XML marshalling


Spring Roo

 provides domain driven design and RAD for your enterprise Java
applications
 Needs to be seen to be believed, so...


DEMO
 Spring Roo

 ALSO: come see my talk on Spring Roo applications!


The Cloud

 Spring works reliably on many, many clouds.
 Cloud Foundry is an ideal place for your Spring applications to run
• they’ll be well fed and cared for
• lots of nice services to play with (Redis, RabbitMQ, MySQL, PostgreSQL, MongoDB)
• there are nice Spring API integrations for all of those!


DEMO
 Setting up a Redis-caching, PostgreSQL-using Spring app on MCF

 ALSO: come see my talk on building Cloud Foundry applications!



The Service Side

59

Spring’s Transaction Management Hierarchies


Spring’s Transaction Support

 Rooted at PlatformTransactionManager
• Many middleware services expose common notions about units of work:
• begin
• do work (N times)
• commit
• if error when committing, rollback
• end
• The devil’s in the details
• Hibernate’s got its Session API
• JTA has its own API (and server lock-in problems)
• JPA has its EntityManager API
• JDBC has the Connection and PreparedStatement APIs
• JMS has its Session API



 PlatformTransactionManager encompasses common concerns
across transactional resources

package org.springframework.transaction;

public interface PlatformTransactionManager {

TransactionStatus getTransaction(TransactionDeﬁnition deﬁnition)
throws TransactionException;

void commit(TransactionStatus status) throws TransactionException;

void rollback(TransactionStatus status) throws TransactionException;

}


Many Implementations



 TransactionTemplate exposes low-level support for working with
PlatformTransactionManager

ﬁnal JdbcTemplate jdbcTemplate = new JdbcTemplate(ds);

DataSource ds = .... ;

PlatformTransactionManager platformTransactionManager =
new DataSourceTransactionManager( ds);

TransactionTemplate transactionTemplate =
new TransactionTemplate( platformTransactionManager ) ;

Customer result = transactionTemplate.execute( new TransactionCallback<Customer>() {
public Customer doInTransaction(TransactionStatus status) {
RowMapper <Customer> rowMapper = ... ;
return jdbcTemplate.queryForObject( "select * from CUSTOMERS", rowMapper) ;
}
}) ;



 Use Spring’s Declarative Transaction Management Instead

@Configuration
@EnableTransactionManagement
public class ServiceConfiguration {
@Bean
public PlatformTransactionManager jpaTransactionManager (){ ... }
}

@Service
@Transactional
public Customer createCustomer( String firstName, String lastName) {
// ....
}
}


Spring’s Cache Support


Cache Abstraction

67

Cache Abstraction
 CacheManager and Cache abstraction
• in org.springframework.cache
• which up until 3.0 just contained EhCache support
• particularly important with the rise of distributed caching
• not least of it all: in cloud environments

67

Cache Abstraction

 Backend adapters for EhCache, GemFire, Coherence, etc
• EhCache adapter shipping with Spring core
• JSR-107 a.k.a. JCache support coming in Spring 3.2

67

Cache Abstraction

 Backend adapters for EhCache, GemFire, Coherence, etc
• EhCache adapter shipping with Spring core
• JSR-107 a.k.a. JCache support coming in Spring 3.2

 Specific cache setup per environment – through profiles?
• potentially even adapting to a runtime-provided service

67

Declarative Caching

68

Declarative Caching
@Cacheable
public Owner loadOwner(int id);

68

Declarative Caching
@Cacheable

@Cacheable(condition="name.length < 10")

68

Declarative Caching
@Cacheable

public Owner loadOwner(String name);

68

Declarative Caching
@Cacheable


@CacheEvict

68

Declarative Caching
@Cacheable


@CacheEvict
public void deleteOwner(int id);

68

JDBC


JDBC Support with Spring

 DataSourceTransactionManager
• implements transaction support for JDBC
 JdbcTemplate
• provides convenient one-liner template methods for common JDBC calls
 JDBC command objects (like SimpleJdbcInsert)


JdbcTemplate convenience

// inserts
RowMapper<Customer> customerRowMapper = new RowMapper<Customer>() {
public Customer mapRow(ResultSet resultSet, int i) throws SQLException {
long id = resultSet.getInt("id");
String firstName = resultSet.getString("first_name");
String lastName = resultSet.getString("last_name");
return new Customer(id, firstName, lastName);
}
};
}

// reads
Long id = 23L;
jdbcTemplate.queryForObject(
“select * from customers where id = ? “, customerRowMapper, id);


JDBC Inserts with SimpleJdbcInsert

Map<String, Object> args = new HashMap<String, Object>();
args.put("ﬁrst_name", fn);
args.put("last_name", ln);

SimpleJdbcInsert simpleJdbcInsert = new SimpleJdbcInsert(jdbcTemplate);
simpleJdbcInsert.setTableName("customer");
simpleJdbcInsert.setColumnNames(new ArrayList<String>(args.keySet()));
simpleJdbcInsert.setGeneratedKeyName("id");

Number id = simpleJdbcInsert.executeAndReturnKey(args);


DEMO
• Looking at, and running, a JDBC-based client


JPA


JPA Support with Spring

 JpaTransactionManager
• implements transaction support for JPA
 LocalContainerEntityManagerFactoryBean
• installs support for using @EntityManager and @EntityManagerFactory to inject
EntityManager(Factory) references
 EntityManager access is transparently thread-safe
 Requires no XML
• no persistence.xml, or orm.xml


Configure JPA Support Easily

HibernateJpaVendorAdapter jpaVendorAdapter =
new HibernateJpaVendorAdapter();
jpaVendorAdapter.setGenerateDdl(true);

LocalContainerEntityManagerFactoryBean emfb =
new LocalContainerEntityManagerFactoryBean();
emfb.setDataSource(dataSource());
emfb.setPackagesToScan(Customer.class.getPackage().getName());
emfb.setJpaVendorAdapter(jpaVendorAdapter);


Consuming JPA from your Services

@PersistenceContext
private EntityManager entityManager;

@Transactional(readOnly = true)
public Customer getCustomerById(long id) {
return this.entityManager.ﬁnd(Customer.class, id);
}


DEMO
 Demos:
• Looking at, and running a JPA based client


Hibernate


Hibernate Support with Spring

 Supports Hibernate 3 and 4
 Requires no XML
 LocalSessionFactoryBuilder, LocalSessionFactoryBean
 Supports thread-local based Hibernate Session access transparently


Easy to Use in Code

@Transactional(readOnly = true)
public List<Customer> getAllCustomers() {
Session session = sessionFactory.getCurrentSession();
List<Customer> customers =
session.createCriteria(Customer.class).list();
return customers;
}


DEMO
 Demos:
• Looking at Spring 3.1’s refined XML-free and fluid Hibernate 4 support


Batch Processing


Why we’re here...


...So, What’s the Problem?


Job and Step

Job
* Step
*
JobInstance

Step Scope
*
JobExecution
* StepExecution


Getting Started

Application
Developer
implements ItemProcessor (optional)

input output (optional)
configures
ItemReader ItemWriter

Job

* StepExecutor concerns
Step

RepeatOperations ExceptionHandler


Spring Batch

 Supports Batch API...
• Jobs have Steps
• Steps have Readers, and optional Processors and Writers
• Readers read data
• Processors process data coming into them, optionally transforming it. Optional.
• Writers write data out


ItemReader

public interface ItemReader<T> {

T read() throws Exception,
UnexpectedInputException,
ParseException,
NonTransientResourceException;

}

Returns null at end of dataset

delegate Exception handling to framework


ItemProcessor (Optional)

public interface ItemProcessor<I, O> {
O process(I item) throws Exception;
}

Delegate Exception handling to framework


ItemWriter

public interface ItemWriter<T> {

void write(List<? extends T> items) throws Exception;

}

expects a “chunk”

delegate Exception handling to framework


All Together...

<job id="skipJob" incrementer="incrementer"
xmlns="http://www.springframework.org/schema/batch">

<step id="step1">
<tasklet>

<chunk reader="ﬁleItemReader"
processor="tradeProcessor"
writer="tradeWriter"
commit-interval="3" skip-limit="10">
</chunk>
</tasklet>

<next on="*" to="step2" />
<next on="COMPLETED WITH SKIPS" to="errorPrint1" />
<fail on="FAILED" exit-code="FAILED" />

</step>

</job>

DEMO
 Demos:
• Processing File Data with Spring Batch


Integration with Messaging in Spring (generally)


Common Idioms in all of Spring’s Messaging Support

 (Amqp|Jms)Template
• eliminates tedious resource acquisition, setup, management, and destruction
• provides easy one-liner template methods that facilitate sending, and receiving
messages
• receiving messages is synchronous
 MessageListenerContainers
• provide a clean, POJO-centric, asynchronous way to receive messages
 Plays nicely with the PlatformTransactionManager SPI impls
 MessageConverters
• transparently transform message payloads into canonical data formats like JSON, XML
• MLCs, *Templates both support MessageConverters for sending and receiving
 Lots of Options
• JMS, AMQP, Redis, GemFire


Integration with JMS


Anatomy of a JMS Application


Spring’s JMS support makes JMS easy

 JmsTemplate reduces tedious boilerplate code to one liners
 JMS MessageListenerContainer SPIs make it easy to
asynchronously respond to messages
• POJO centric
• Same idiom’s available across the entire framework


Easy to Configure

@Bean
public MessageConverter messageConverter() {
MarshallingMessageConverter marshallingMessageConverter =
new MarshallingMessageConverter();
marshallingMessageConverter.setMarshaller(this.oxmMarshaller());
marshallingMessageConverter.setTargetType(MessageType.TEXT);
marshallingMessageConverter.setUnmarshaller(this.oxmMarshaller());
return marshallingMessageConverter;
}

@Bean
public JmsTemplate jmsTemplate() throws Exception {
JmsTemplate jmsTemplate = new JmsTemplate(connectionFactory());
jmsTemplate.setMessageConverter( messageConverter()); // optional
return jmsTemplate;
}


Easy to Use in Code

Customer customer = new Customer("Mario", "Gray");
String queue = "customers";
jmsTemplate.convertAndSend(queue, customer);

Customer ogCustomer =
(Customer) jmsTemplate.receiveAndConvert(queue);


DEMO
 Demos:
• Sending and Receiving Data with Spring’s JMS support


Integration with AMQP


AMQP is not the ORIGINAL “Cloud Scale Messaging”
....but close enough!

103

RabbitMQ – Messaging that Just Works

Robust
High-performance
Easy to use
AMQP LEADER

Why AMQP?

A Protocol, not an API
•A defined set of
messaging capabilities
called the AMQ model
•A network wire-level
protocol, AMQP

On commodity hardware
•10-25 thousand
messages per second is
routine *
•The NIC is usually the
bottleneck

* Non-persistent messages
17

Anatomy of an AQMP Application


AMQP Architecture

café deliveries

queue

café NA deliveries

queue

café WW deliveries

queue

20

AMQP Architecture

café deliveries

M1 M2 M3
queue

café NA deliveries

M1 M2 M3
queue

café WW deliveries

M1 M2 M3
queue

20

AMQP Architecture

new.order

queue

19

AMQP Architecture

new.order
new.order

binding queue

19

AMQP Architecture

new.order
new.order new.order

routing key binding queue

19

AMQP Architecture

all_drinks

queue

21

AMQP Architecture

all_drinks

queue

cold_drinks

queue

21

AMQP Architecture

all_drinks

queue

cold_drinks

queue

hot_drinks

queue

21

AMQP Architecture

all_drinks

queue

.*
drink
cold_drinks

queue

hot_drinks

queue

21

AMQP Architecture

all_drinks

queue

.*
drink
drink.cold cold_drinks

queue

hot_drinks

queue

21

AMQP Architecture

all_drinks

queue

.*
drink

queue

dri
nk.
ho hot_drinks
t
queue

21

AMQP Architecture

all_drinks

queue

.*
drink

queue

dri
nk.
ho hot_drinks
t
queue

Message Routing Keys:
1.drink.hot
2.drink.cold
3.drink.warm
21

AMQP Architecture

all_drinks

1 2 3
queue

.*
drink

2
queue

dri
nk.
ho hot_drinks
t
1
queue

Message Routing Keys:
1.drink.hot
2.drink.cold
3.drink.warm
21

Spring AMQP

 Encapsulates low-level details
Producer Consumer
 Simplifies sending and
receiving of messages

Amqp Listener
Template Container

Spring AMQP

AMQP


Spring’s AMQP support makes AMQP easy

 AMQP is protocol centric
• numerous clients for any number of language bindings
 AMQP surfaces more of the administration concerns over the
protocol
• easy to create queues, bindings, exchanges from client APIs


Spring’s AMQP support makes AMQP easy

 AmqpTemplate
 AMQP MessageListenerContainer SPIs make it easy to
asynchronously respond to messages
• POJO centric
 AMQP’s server side constructs (queues, bindings, etc.) can be
manipulated from the client APIs


Easy to Configure

@Bean
public MessageConverter jsonMessageConverter() {
MarshallingMessageConverter marshallingMessageConverter =
new MarshallingMessageConverter();
marshallingMessageConverter.setMarshaller(this.oxmMarshaller());
marshallingMessageConverter.setUnmarshaller(this.oxmMarshaller());
return marshallingMessageConverter;
}

@Bean
public RabbitTemplate rabbitTemplate() {
RabbitTemplate rabbitTemplate = new
RabbitTemplate(connectionFactory());
rabbitTemplate.setMessageConverter(jsonMessageConverter());
return rabbitTemplate;
}


Easy to Configure
@Bean
public AmqpAdmin amqpAdmin() {
return new RabbitAdmin(this.connectionFactory());
}

@Bean
public Queue customerQueue() {
Queue q = new Queue(this.customersQueueAndExchangeName);
amqpAdmin().declareQueue(q);
return q;
}

@Bean
public DirectExchange customerExchange() {
DirectExchange directExchange = new DirectExchange(“customers”);
this.amqpAdmin().declareExchange(directExchange);
return directExchange;
}

@Bean
public Binding marketDataBinding() {
return BindingBuilder.bind(customerQueue())
.to(customerExchange())
.with(this.customersQueueAndExchangeName);
}


Easy to Use in Code

Customer customer = new Customer("Mario", "Gray");

amqpTemplate.convertAndSend( “exchange”, “routingkey”, customer);

Customer ogCustomer =
(Customer) amqpTemplate.receiveAndConvert(“queue”);


DEMO
 Demos:
• Sending and receiving data with Spring’s AMQP support


Integration with Spring Integration


What is Spring Integration

 Generic framework for building messaging-based applications
 Hides nuances of external systems (be they AMQP, JMS, email, FTP,
TCP, etc.): everything’s a Message



Declare channels

<channel id = “stocksChannel” />


Send Messages over JMS

<channel id = “stockChannel” />

<jms:outbound-channel-adapter
channel = “stockChannel”
destination-name=“stocks”
connection-factory = “connectionFactory”
/>


Connect Components with Channels

public class StockClientImpl {

@Value(“#{stocksChannel}”) private MessageChannel channel ;

@Autowired private MessagingTemplate messagingTemplate ;

public void publishStockUpdate ( String stock , double price ) {
Message msg = MessageBuilder
.withPayload(price)
.setHeader(“stock”, stock).build();
this.messagingTemplate.send( this.channel, msg ) ;
}
}


Being Notified of Files When They Appear

<file:inbound-channel-adapter
auto-create-directory="true"
channel="filesReceived"
directory="#{systemProperties['user.home']}/Desktop/in">
<int:poller fixed-rate="1000"/>
</file:inbound-channel-adapter>

<int:service-activator input-channel="filesReceived" ref="myPojo" />

@ServiceActivator
public class MyPojo {
public void myCustomFileCallback ( @Payload File fileReceived) {
// do something with the file
}
}


DEMO
• Reading file Data with Spring Integration


Spring Data


http://www.springsource.org/spring-data

•Spring Data Key-value
•Spring Data Document
•Spring Data Graph
•Spring Data Column
•Spring Data Blob
•Spring Data JPA Repository / JDBC Extensions
•Spring Gemfire / Spring Hadoop ...
•Grails iNcOnSeQuentiaL
125

Spring Data Building Blocks

•Low level data access APIs
✓MongoTemplate, RedisTemplate ...
•Object Mapping (Java and GORM)
•Cross Store Persistence Programming model
•Generic Repository support
•Productivity support in Roo and Grails

126

NoSQL with Redis


NoSQL offers several data store categories

Key-Value Column Document Graph

Redis,
Riak

128

Spring Data Redis

 Works with Redis
• super fast
• “data structure server” (maps, lists, sets, queue, etc.)
 RedisTemplate reduces tedious boilerplate code to one liners
 CacheManager implementation
• works with Spring 3.1’s CacheManager implementation
 RedisMessageListenerContainer
• provides same queue / publish-subscribe features as with JMS and AMQP


Configuring Redis support

@Bean
public RedisConnectionFactory redisConnectionFactory() {
return new JedisConnectionFactory();
}

@Bean
public RedisTemplate<String, Object> redisTemplate()
throws Exception {
RedisTemplate<String, Object> ro = new RedisTemplate<String, Object>();
ro.setConnectionFactory(redisConnectionFactory());
return ro;
}

NOT CONFIDENTIAL -- TELL EVERYONE 130

Handling Persistence Duties with Redis...

@Inject RedisTemplate redisTemplate;

@Override
public Customer getCustomerById(long id) {
String ln = (String)redisTemplate.opsForValue().get(lastNameKey(id)) ;
String fn = (String)redisTemplate.opsForValue().get(ﬁrstNameKey(id));
return new Customer(id, fn, ln);
}

private void setCustomerValues(long lid, String fn, String ln) {
this.redisTemplate.opsForValue().set(lastNameKey(lid), ln);
this.redisTemplate.opsForValue().set(ﬁrstNameKey(lid), fn);
}

@Override
public Customer updateCustomer(long id, String fn, String ln) {
setCustomerValues(id, fn, ln);
return getCustomerById(id);
}


DEMO
• Reimplementing the CustomerService interface in terms of Redis
• introduce Spring 3.1 caching support
• Introduce RedisCacheManager implementation
•


NoSQL with MongoDB


NoSQL offers several data store categories

Key-Value Column Document Graph

MongoDB

134

Spring Data MongoDB

 works with MongoDB
 provides obvious API integrations:
• MongoTemplate
• Mongo-backed MessageStore (Spring Integration)
 Advanced API integrations, too:
• cross-store persistence
• MongoRepository (built on Spring Data JPA)


Simple Domain Class

136

Mongo Template

Direct Usage of the Mongo Template:

137

Mongo Template


Insert into “Person”
Collection

137

Mongo Template


findOne using query: { "name" : "Joe"}
in db.collection: database.Person

137

Mongo Template


Dropped collection [database.person]

137

Generic Repository

Interface for generic CRUD operations on a repository for a specific type

138

Paging and Sorting Repository

Paging and Sorting Repository: Extends “CrudRepository”

139

Paging and Sorting Repository

Paging and Sorting Repository: Extends “CrudRepository”

Usage:

139

Custom Repository

Custom Repository:

140

Custom Repository

Custom Repository:

Keywords :
Keyword Sample Logical result

GreaterThan findByAgeGreaterThan(int age) {"age" : {"$gt" : age}}

LessThan findByAgeLessThan(int age) {"age" : {"$lt" : age}}

Between findByAgeBetween(int from, int to) {"age" : {"$gt" : from, "$lt" : to}}

NotNull findByFirstnameNotNull() {”firstname" : {"$ne" : null}}

Null findByFirstnameNull() {”firstname" : null}

Like findByFirstnameLike(String name) "firstname" : firstname} (regex) 140

JPA and MongoDB can be used in cross-store persistence

JPA “Customer” with a “SurveyInfo” Document

141

Using a Cross-Store

Saving a Customer with a SurveryInfo

142

Using a Cross-Store

Create Customer

142

Using a Cross-Store


Create SurveyInfo

142

Using a Cross-Store


Assign Survey to Customer

142

Using a Cross-Store


Save

142

Using a Cross-Store


Save

Mongo Document:

142

DEMO
• Looking at Mongo Repository
• Look at a Cross-Store Persistence Example



The Client Side

144

Agenda

 Web Applications
• Spring MVC
• JSF
• Others
 REST
• the final frontier: TV, tablets, operating systems
 Mobile Clients
• Android
• iPhone
 RIA / SOFEA
• Flex
• GWT, Vaadin

145

Web Applications with Spring

146


 Spring Beans are Managed by An ApplicationContext
• whether you’re in an application server, a web server, in regular Java SE application, in
the cloud, Spring is initialized through an ApplicationContext
• In a Java SE application:

ApplicationContext ctx =
new GenericAnnotationApplicationContext( “com.foo.bar.my.package”);

• In a web application, you will configure an application context in your web.xml

<servlet>
<servlet-name>Spring Dispatcher Servlet</servlet-name>
<servlet-
class>org.springframework.web.servlet.DispatcherServlet</servlet-
class>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/spring/myAppContext*.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>

147


 Spring Beans are Managed by An ApplicationContext
• In Spring 3.1, you can also use Java configuration, negating the need for web.xml

public class SampleWebApplicationInitializer implements WebApplicationInitializer {

public void onStartup(ServletContext sc) throws ServletException {

AnnotationConﬁgWebApplicationContext ac =
new AnnotationConﬁgWebApplicationContext();
ac.setServletContext(sc);
ac.scan( “a.package.full.of.services”, “a.package.full.of.controllers” );

sc.addServlet("spring", new DispatcherServlet(webContext));

}
}

148

Thin, Thick, Web, Mobile and Rich Clients: Web Core

 Spring Dispatcher Servlet
• Objects don’t have to be web-specific.
• Spring web supports lower-level web machinery: ‘
• HttpRequestHandler (supports remoting: Caucho, Resin, JAX RPC)
• DelegatingFilterProxy.
• HandlerInterceptor wraps requests to HttpRequestHandlers
• ServletWrappingController lets you force requests to a servlet through the Spring Handler chain
• OncePerRequestFilter ensures that an action only occurs once, no matter how many filters are
applied. Provides a nice way to avoid duplicate filters
• Spring provides access to the Spring application context using
WebApplicationContextUtils, which has a static method to look up the context, even in
environments where Spring isn’t managing the web components

Thin, Thick, Web, Mobile and Rich Clients: Web Core

 Spring provides the easiest way to integrate with your web
framework of choice
• Spring Faces for JSF 1 and 2
• Struts support for Struts 1
• Tapestry, Struts 2, Stripes, GWT, Wicket, Vaadin, Play framework, etc.

Thin, Thick, Web, Mobile and Rich Clients: Spring MVC

151

The Client Side: Spring MVC
Spring MVC configuration - config

@Configuration @EnableWebMvc @Import(JdbcConfiguration.class)
public class WebConfig extends WebMvcConfigurerAdapter {

@Bean
public UrlBasedViewResolver resolver() {
UrlBasedViewResolver url = new UrlBasedViewResolver();
url.setPrefix("views/");
url.setViewClass(JstlView.class);
url.setSuffix(".jsp");
return url;
}

@Override
public void addViewControllers(ViewControllerRegistry registry) {
registry.addViewController("/").setViewName("welcome");
}

@Override
public void configureDefaultServletHandling(
DefaultServletHandlerConfigurer configurer) {
configurer.enable();
}
}

152

The Client Side: Spring MVC

A Controller - config

@Controller
public class CustomerController {
private Log log = LogFactory.getLog(getClass());

@Autowired private CustomerService customerService;

@ModelAttribute public Customer customer() { return new Customer(); }

@RequestMapping(value = "/display", method = RequestMethod.GET)
public Map<String, Object> customer(@RequestParam("id") Long id) {
Customer customerById = this.customerService.getCustomerById(id);
Map<String, Object> out = new HashMap<String, Object>();
out.put("customer", customerById);
return out;
}

@RequestMapping(value = "/add", method = RequestMethod.POST)
public String processAddition(@ModelAttribute Customer c, Model modelAndView) {
Customer customer = customerService.createCustomer(
c.getFirstName(), c.getLastName());
modelAndView.addAttribute("id", customer.getId());
return "redirect:/display";
}

}

153

DEMO
 Demos
• Spring MVC and associated configuration


Thin, Thick, Web, Mobile and Rich Clients: REST

 Spring MVC is basis for REST support
• Spring’s server side REST support is based on the standard controller model
 RestTemplate
• provides dead simple, idiomatic RESTful services consumption
• can use Spring OXM, too.
• Spring Integration and Spring Social both build on the RestTemplate where possible.
 JavaScript and HTML5 can consume JSON-data payloads
 REST is the ultimate connectivity mechanism: everything can speak
HTTP.

Thin, Thick, Web, Mobile and Rich Clients: REST

 Origin
• The term Representational State Transfer was introduced and defined in 2000 by Roy
Fielding in his doctoral dissertation.
 His paper suggests these four design principles:
• Use HTTP methods explicitly.
• POST, GET, PUT, DELETE
• CRUD operations can be mapped to these existing methods
• Be stateless.
• State dependencies limit or restrict scalability
• Expose directory structure-like URIs.
• URI’s should be easily understood
• Transfer XML, JavaScript Object Notation (JSON), or both.
• Use XML or JSON to represent data objects or attributes

CONFIDENTIAL
157

Thin, Thick, Web, Mobile and Rich Clients: RestTemplate

 Google search example
RestTemplate restTemplate = new RestTemplate();
String url = "https://ajax.googleapis.com/ajax/services/search/web?v=1.0&q={query}";
String result = restTemplate.getForObject(url, String.class, "SpringSource");

 Multiple parameters
RestTemplate restTemplate = new RestTemplate();
String url = "http://example.com/hotels/{hotel}/bookings/{booking}";
String result = restTemplate.getForObject(url, String.class, "42", “21”);

CONFIDENTIAL
158


 RestTemplate class is the heart the client-side story
• Entry points for the six main HTTP methods
• DELETE - delete(...)
• GET - getForObject(...)
• HEAD - headForHeaders(...)
• OPTIONS - optionsForAllow(...)
• POST - postForLocation(...)
• PUT - put(...)
• any HTTP operation - exchange(...) and execute(...)

CONFIDENTIAL
159


 Http Client
• The HttpComponents HttpClient is a native HTTP client
 Message Converters
• MappingJacksonHttpMessageConverter - object to JSON marshaling supported via
the Jackson JSON Processor
• MarshallingXmlMessageConverter - converts objects to XML using Spring OXM
• SyndFeedHttpMessageConverter - RSS and Atom feeds supported via the Android
ROME Feed Reader

CONFIDENTIAL
160

Thin, Thick, Web, Mobile and Rich Clients: REST with Spring MVC
RestCustomerController - server

@Controller @RequestMapping(headers = "Accept=application/json, application/xml")
public class RestCustomerController {

@Autowired private CustomerService cs;

@RequestMapping(value = "/customer/{cid}", method = RequestMethod.POST)
@ResponseBody public Customer updateCustomer(@RequestBody Customer c) {
return cs.updateCustomer( c.getId(), c.getFirstName(), c.getLastName());
}

WebConfig - server

@EnableWebMvc
@Import(Config.class)
@Configuration
public class WebConfig
extends WebMvcConfigurerAdapter {}

client

Customer customer1 = restTemplate.getForEntity(
url + "customer/{customerId}",
Customer.class, c.getId()).getBody();
log.info("fetched customer " + customer1.toString());

161

DEMO
 Demos:
• Spring REST service
• Spring REST client


Thin, Thick, Web, Mobile and Rich Clients: Mobile

 Best strategy? Develop Native
• Fallback to client-optimized web applications
 Spring MVC 3.1 mobile client-specific content negotiation and
rendering
• for other devices
• (there are other devices besides Android??)

164

WebConfig - server

! @Bean
public ViewResolver viewResolver() {
UrlBasedViewResolver viewResolver = new UrlBasedViewResolver();
viewResolver.setViewClass(TilesView.class);
return viewResolver;
}

@Bean
public TilesConfigurer tilesConfigurer() {
TilesConfigurer configurer = new TilesConfigurer();
configurer.setDefinitions(new String[]{
"/WEB-INF/layouts/tiles.xml",
"/WEB-INF/views/**/tiles.xml"
});
configurer.setCheckRefresh(true);
return configurer;
}

@Override
public void configureInterceptors(InterceptorConfigurer configurer) {
configurer.addInterceptor(new DeviceResolverHandlerInterceptor());
}

165

DEMO
 Demos:
• Mobile clients using client specific rendering



 Spring REST is ideal for mobile devices
 Spring MVC 3.1 mobile client-specific content
negotiation and rendering
• for other devices
 Spring Android
• RestTemplate

168


CustomerServiceClient - client

! private <T> T extractResponse( ResponseEntity<T> response) {
! ! if (response != null && response().value() == 200) {
! ! ! return response.getBody();
! ! }
! ! throw new RuntimeException("couldn't extract response.");
! }

! @Override
! public Customer updateCustomer(long id, String fn, String ln) {
! ! String urlForPath = urlForPath("customer/{customerId}");!!
! ! return extractResponse(this.restTemplate.postForEntity(
urlForPath, new Customer(id, fn, ln), Customer.class, id));
! }

170


 Demos:
• consuming the Spring REST service from Android

Rich Internet Applications

172

Thin, Thick, Web, Mobile and Rich Clients: Flex

 Spring Flex
• Dead-simple to expose Spring beans as Flex services
• Developed with support from Adobe
• But it still has strengths:
• form driven apps
• video, 2D and 3D graphics, sound
• Adobe AIR
• blazing fast communication
• server side push
• Spring ActionScript is a cool framework “sponsored” by SpringSource

Thin, Thick, Web, Mobile and Rich Clients: Flex
crm-flex-servlet.xml - server
<?xml version="1.0" encoding="UTF-8"?>
<beans ...>

<context:component-scan base-package="org.springsource.examples.sawt.web.flex"/>

<mvc:default-servlet-handler/>

<flex:message-broker mapping-order="1">
<flex:mapping pattern="/messagebroker/*"/>
<flex:message-service default-channels="my-streaming-amf,my-longpolling-amf,my-polling-amf"/>
</flex:message-broker>

<flex:remoting-destination ref="jdbcCustomerService" destination-id="customerService"/>

</beans>

CustomerForm.mxml - client

<fx:Declarations><s:RemoteObject id="cs" destination="customerService"
endpoint="{serviceUrl}">
<s:method name="createCustomer" result="create_resultHandler(event)"/>
<s:method name="updateCustomer" result="update_resultHandler(event)"/>
</s:RemoteObject> </fx:Declarations>
<fx:Script><![CDATA[ cs.updateCustomer( c.id, c.firstName, c.lastName); ]]>
</fx:Script>

174

Thin, Thick, Web, Mobile and Rich Clients: RIA with Flex

 Demos:
• exposing Spring services through BlazeDS
• consuming it from a Flex client

Thin, Thick, Web, Mobile and Rich Clients: GWT

 Google Web Toolkit
• Lots of popular options
• We’ll look at building a simple example by simple delegating as
appropriate
• Server-side: standard DispatcherServlet

Thin, Thick, Web, Mobile and Rich Clients: GWT
GwtCustomerService - client

import com.google.gwt.user.client.rpc.*;

@RemoteServiceRelativePath("crm")
public interface GwtCustomerService extends RemoteService {
void updateCustomer(long cid, String f, String l);
CustomerDto getCustomerById(long customerId);
CustomerDto createCustomer(String f, String ln);
}

GwtCustomerServiceImpl - server

private <T> T beanOfType(Class t) {
ApplicationContext ac = WebApplicationContextUtils.getWebApplicationContext(
getServletContext());
return (T) ac.getBean(t);
}

public void updateCustomer(long cid, String f, String l) {
try {
CustomerService customerService = beanOfType(CustomerService.class);
customerService.updateCustomer(cid, f, l);
} catch (Exception ex) {
throw new RuntimeException(ex);
}
}

177

DEMO
 Demos:
• building a simple GWT client that consumes services in Spring


Another Strategy....

 HTML5 all the way!
• HTML5 on the desktop browser interface
• HTML5 + PhoneGap on the client
• RESTful services on the server side to connect it all
I NEED AN HTM
here!!!!

DEMO
 HTML5Expense
• github.com/SpringSource/html5expenses


Social Communication


Spring Social

 Extension to Spring Framework to enable connectivity with
Software-as-a-Service providers
 Features...
• An extensible connection framework
• A connect controller
• Java API bindings
• A sign-in controller
 http://www.springsource.org/spring-social

182

Spring Social Projects

 Spring Social Core
 Spring Social Facebook
 Spring Social Twitter
 Spring Social LinkedIn
 Spring Social TripIt
 Spring Social GitHub
 Spring Social Gowalla
 Spring Social Samples
• Includes Showcase, Quickstart, Movies, Canvas, Twitter4J, Popup

183

Key Steps to Socializing an Application

 Configure Spring Social beans
• Connection Factory Locator and Connection Factories
• Connection Repository
• Connect Controller
• API Bindings
 Create connection status views
 Inject/use API bindings

184

Configuration: ConnectionFactoryLocator

@Bean
@Scope(value="singleton", proxyMode=ScopedProxyMode.INTERFACES)
public ConnectionFactoryLocator connectionFactoryLocator() {
ConnectionFactoryRegistry registry = new ConnectionFactoryRegistry();

registry.addConnectionFactory(
new TwitterConnectionFactory(
environment.getProperty("twitter.consumerKey"),
environment.getProperty("twitter.consumerSecret")));

registry.addConnectionFactory(
new FacebookConnectionFactory(
environment.getProperty("facebook.clientId"),
environment.getProperty("facebook.clientSecret")));

return registry;
}

185

Configuration: Connection Repository

@Bean
@Scope(value="request", proxyMode=ScopedProxyMode.INTERFACES)
public ConnectionRepository connectionRepository() {
Authentication authentication = SecurityContextHolder.getContext().
getAuthentication();
if (authentication == null) {
throw new IllegalStateException(
"Unable to get a ConnectionRepository: no user signed in");
}
return usersConnectionRepository().createConnectionRepository(
authentication.getName());
}

186

Configuration: Connection Repository

@Bean
public ConnectionRepository connectionRepository() {
Authentication authentication = SecurityContextHolder.getContext().
getAuthentication();
if (authentication == null) {
throw new IllegalStateException(
"Unable to get a ConnectionRepository: no user signed in");
}
return usersConnectionRepository().createConnectionRepository(
authentication.getName());
}

@Bean
@Scope(value="singleton", proxyMode=ScopedProxyMode.INTERFACES)
public UsersConnectionRepository usersConnectionRepository() {
return new JdbcUsersConnectionRepository(
dataSource,
connectionFactoryLocator(),
Encryptors.noOpText());
}

186

Configuration: ConnectController

@Bean
public ConnectController connectController() {
return new ConnectController(connectionFactoryLocator(),
connectionRepository());
}

187

Configuration: API Bindings

@Bean
public Facebook facebook() {
Connection<Facebook> facebook =
connectionRepository().ﬁndPrimaryConnection(Facebook.class);
return facebook != null ? facebook.getApi() : new FacebookTemplate();
}

@Bean
public Twitter twitter() {
Connection<Twitter> twitter =
connectionRepository().ﬁndPrimaryConnection(Twitter.class);
return twitter != null ? twitter.getApi() : new TwitterTemplate();
}

188

Injecting and Using the API Bindings

@Controller
public class TwitterTimelineController {

private ﬁnal Twitter twitter;

@Inject
public TwitterTimelineController(Twitter twitter) {
this.twitter = twitter;
}

@RequestMapping(value="/twitter/tweet",
method=RequestMethod.POST)
public String postTweet(String message) {
twitter.timelineOperations().updateStatus(message);
return "redirect:/twitter";
}
}
189

ConnectController Endpoints
 GET /connect
• Displays connection status for all providers
 GET /connect/{provider}
• Displays connection status for a given provider
 POST /connect/{provider}
• Initiates the authorization flow, redirecting to the provider
 GET /connect/{provider}?oauth_token={token}
• Handles an OAuth 1 callback
 GET /connect/{provider}?code={authorization code}
 DELETE /connect/{provider}
• Removes all connections for a user to the given provider
 DELETE /connect/{provider}/{provider user ID}
• Removes a specific connection for the user to the given provider

190

ConnectController Flow

Your Application

ConnectController

Service Provider
(Twitter, Facebook, etc)

191


Your Application

GET /connect/{provider ID}
ConnectController

Service Provider

Display connection status page
191


Your Application

POST /connect/{provider ID}
ConnectController

Service Provider

Initiate connection flow
191


Your Application

ConnectController

Service Provider

Fetch request token (OAuth 1.0/1.0a only)
191


Your Application

ConnectController

Service Provider

Redirect browser to provider’s authorization page
191


Your Application
GET /connect/{provider ID}?oauth_token={token}
GET /connect/{provider ID}?code={code}
ConnectController

Service Provider

Provider redirects to callback URL
191


Your Application

ConnectController

Service Provider

Exchange request token and/or code for access token
191


Your Application

ConnectController

Service Provider

ConnectController stores connection details in connection repository
191


Your Application

ConnectController

Service Provider

Application can make API calls via API binding
191

Connection Status Page View

<form action="<c:url value="/connect/twitter" />" method="POST">
<div class="formInfo">
<p>
You haven't created any connections with Twitter yet.
Click the button to connect with your Twitter account.
</p>
</div>
<p>
<button type="submit">
<img src="<c:url value="/resources/social/twitter/connect-with-twitter.png" />"/>
</button>
</p>
</form>

192

Provider Sign In

 A convenience for users
 Enables authentication to an app using their connection as
credentials
 Implemented with ProviderSignInController
 Works consistently with any provider

193

Configuration: ProviderSignInController

 Performs a similar flow as ConnectController
 Compares connections (by user ID)
 If there’s a match, the user is signed into the application
 Otherwise, the user is sent to signup page
• Connection is be established after signup

@Bean
public ProviderSignInController providerSignInController(
RequestCache requestCache) {
return new ProviderSignInController(connectionFactoryLocator(),
usersConnectionRepository(),
new SimpleSignInAdapter(requestCache));
}

194

ProviderSignInController Endpoints

 POST /signin/{provider}
• Initiates the authorization flow, redirecting to the provider
 GET /signin/{provider}?oauth_token={token}
 GET /signin/{provider}?code={authorization code}
 GET /signin
• Handles a callback when no oauth token or code is sent
• Likely indicates that the user declined authorization

195

Social Security OAuth


Spring Security OAuth

 Extension to Spring Security
• originally a community contribution (now officially part of the project)
 Features...
• endpoint management for OAuth service types
• (along with corresponding client management)
• token management (persistence, authentication)
• integrations for the web, as well as through standard Spring Security
 springsource.org/spring-security/oauth

197

Setup Spring Security with Spring MVC...

<http access-denied-page="/login.jsp"
xmlns="http://www.springframework.org/schema/security">

<form-login authentication-failure-url="/login.jsp"
default-target-url="/index.jsp"
login-page="/login.jsp"
login-processing-url="/login.do" />

<logout logout-success-url="/index.jsp" logout-url="/logout.do" />

<anonymous />

<intercept-url pattern="/sparklr/**" access="ROLE_USER" />

<custom-ﬁlter ref="oauth2ClientFilter" after="EXCEPTION_TRANSLATION_FILTER" />

</http>

198

Then Tell Spring Security About Our OAuth Endpoints

<authentication-manager
xmlns="http://www.springframework.org/schema/security">
<authentication-provider>
<user-service>
<user name="marissa" password="wombat"
authorities="ROLE_USER" />
<user name="sam" password="kangaroo"
authorities="ROLE_USER" />
</user-service>
</authentication-provider>
</authentication-manager>

<oauth:client id="oauth2ClientFilter"
redirect-on-error="${redirectOnError:false}" />

<oauth:resource id="sparklr"
type="authorization_code" client-id="tonr"
client-secret="secret" access-token-uri="${accessTokenUri}"
user-authorization-uri="${userAuthorizationUri}" scope="read" />

199

Then get an Instance of a RestTemplate for the client...

<bean class="org.springframework.security.oauth2.client.OAuth2RestTemplate">
<constructor-arg ref = “sparklr”/>
</bean>

200

springsource.org

Questions?
Say hi!
@starbuxman || josh.long@springsource.com

A Walking Tour of (almost) all of Springdom

More Related Content

What's hot (19)

Viewers also liked (10)

Similar to A Walking Tour of (almost) all of Springdom (20)

More from Joshua Long (14)

Recently uploaded (20)

A Walking Tour of (almost) all of Springdom

Editor's Notes