Multi client Development with Spring

Spring and the Many Faces of the Web
(or, Thin, Thick, Web, Mobile and Rich Clients with Spring)

Josh Long
@starbuxman
Spring Developer Advocate
SpringSource, a division of VMware

© 2009 VMware Inc. All rights reserved

About Josh Long
SpringSource Developer Advocate
twitter: @starbuxman
josh.long@springsource.com

NOT CONFIDENTIAL -- TELL EVERYONE 2

Agenda

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


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


Introduction to Spring


At its core, the Spring Framework...

 Provide comprehensive infrastructural support for developing
enterprise Java™ applications
• Spring deals with the plumbing
• So you can focus on solving the domain problem


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

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


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


Web Applications with Spring


The Spring ApplicationContext

 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>


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

NOT CONFIDENTIAL -- TELL EVERYONE

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


Spring MVC configuration - config

@Configuration @EnableWebMvc @Import(Config.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;
}
public void configureViewControllers(ViewControllerConfigurer configurer) {
configurer.mapViewName("/", "welcome") ;
}
}
A Controller - config

@Controller
public class CustomerController {
@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) {
Map<String, Object> out = new HashMap<String, Object>();
out.put("customer", customerService.getCustomerById(id) );
return out;
} NOT CONFIDENTIAL -- TELL EVERYONE 14


 Demos
• Spring MVC and associated configuration


REST


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.


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());



 Demos:
• Spring REST service
• Spring REST client


Mobile (pt 1.)


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??)


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());
}



 Demos:
• Mobile clients using client specific rendering


Mobile (pt 2.)



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



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));
! }



 Demos:
• consuming the Spring REST service from Android


Rich Internet Applications


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>


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


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);
}
}


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


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

36

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

37

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

38

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;
}

39

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());
}

40

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());
}

40

Configuration: ConnectController

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

41

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();
}

42

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";
}
}

43

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
44

ConnectController Flow

Your Application

ConnectController

Service Provider
(Twitter, Facebook, etc)

45


Your Application

GET /connect/{provider ID}
ConnectController

Service Provider

Display connection status page
45


Your Application

POST /connect/{provider ID}
ConnectController

Service Provider

Initiate connection flow
45


Your Application

ConnectController

Service Provider

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


Your Application

ConnectController

Service Provider

Redirect browser to provider’s authorization page
45


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

Service Provider

Provider redirects to callback URL
45


Your Application

ConnectController

Service Provider

Exchange request token and/or code for access token
45


Your Application

ConnectController

Service Provider

ConnectController stores connection details in connection repository
45


Your Application

ConnectController

Service Provider

Application can make API calls via API binding
45

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>

46

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

47

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));
}

48

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

49

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

51

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>

52

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" />

53

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

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

54

Questions?

Josh Long | josh.long@springsource.com | @starbuxman

Multi client Development with Spring

More Related Content

What's hot (20)

Similar to Multi client Development with Spring (20)

More from Joshua Long (20)

Recently uploaded (20)

Multi client Development with Spring

Editor's Notes