T2 Web Framework

T2 framework T2 project http://t-2.googlecode.com/ Shinpei Ohtani(shot6)

Agenda Introduce myself and the team An overview of T2 framework Current web development situation T2 architecture and mechanism Demos Conclusion

Introduce myself Shinpei Ohtani Open source programmer Java/ActionScript/JavaScript/C#... Works at ISI Dentsu, Ltd Blog http://d.hatena.ne.jp/shot6/ (Japanese) Twitter http://twitter.com/shot6/

Introduce the T2 team The team are: 5 committers All professional programmer, especially Java Each of us create both applications and frameworks The experiences are the core of creating T2

Web development situation The time for web application re-invented RIA is no more new thing, it is just choice! Ajax, Flex, Silverlight, there are just choices. Cloud environment is the matter Web application needs to deploy to multiple clouds HTTP based protocol and format rises up AMF, XMPP, reversehttp, pubsubhubbub Or, legacy SOAP:P

RIP –Rich Internet Platform- RIA to RIP(Rich Internet Platform) RIP is the platform to support multiple RIA environment(HTML5, Ajax, Flex, Silverlight…). HTML5 is the flagship of RIP Unlike HTML4, HTML5 is the platform for RIA. Runtime is the key such as WebSockets WebStorage WebWorker CacheManifest Geolocation API

Cloudability Cloudability Ability to work well at cloud environment Work well means: Deploy easily Scale easily so be stateless Interoperable to multiple cloud environment Not only for GAE, Amazon, or other, do work with all these.

HTTP matters HTTP/HTTPS it the protocol The unified protocol for next generation apps The format also matters AMF for Flex, XMPP for jabber, pubsubhubbub for WebHook, so many format rises up! These formats and mechanism is the key for new interactive web apps

To the next level web apps Choose good/simple framework that has some features for: RIP Cloudability HTTP based multiple format is one of the choice for you.

What is T2 framework Simple and modernized java web framework for real developer Easy to use and maintain by annotation Current version is T2 0.6.1-ga. ASL2 License. http://code.google.com/p/t-2/ The framework for RIP apps Ofcourse support classic web application! Extensible and embeddable framework

The big picture Browser HTTP POST JavaScript Client XmlHttp Request Flex/AIR AMF REST-like Client PUT /hoge/foo POJO POJO POJO Serverside java applications …… …… …… Request format doesn’t effect server side POJO-based model.

The motivation The motivation All of Java webframework is too difficult to use and maintain Also mention none of these follow modernized web clients with one unified model Does your framework handle Ajax, AMF, REST request using one unified programming model? No clean url, no life. No choice of template engine, no life. Less configuration without difficult CoC!

The motivation(cont’d) Web framework: should be much more simple . should give developer loosely-coupled unified model . Request type and format doesn’t effect server side. should handle modernized web request well Ajax, AMF from Flex, REST, POX from Silverlight… should give you clean beatiful url should give you free to choose template engine

The concept Concept Do one thing well T2 just connects between multiple HTTP clients to POJO using url pattern gracefully.Doesn’t do things at all. Accepts WEB diversity 100 ways to make web application with technology (browser/RIA/CUI…), and we can’t push developer to one way.Do it freely using T2. Only things for sure is using HTTP and URL .

The target user Who should use T2? Developers who’d like to: Develop and control web application easily. Separate clients and server side application gracefully Develop his/her framework based on simple and extensible framework and control perfectly Develop RIA application quickly using REST like request, Ajax request, or Flex AMF request Develop cloud based application

Programming model Page model All of T2 application uses page model Basically POJO but annotations enhanced for class, method, parameter Very unobtrusive model, no one harms for this  Page is a class to map an url for a pojo. Page has action methods for executing user request. Action parameter is injected by T2

Programming model(cont’d) Example: @Page("employee") public class EmployeePage { @Default public Navigation index(WebContext context) { … ... } @GET @ActionPath("list/detail") public Navigation detail(WebContext context) { …… } }

Action method design Funnel-like design Page class is created as you put url and its parameter from whole to detail Set url for a page Set url for an action method Set parameter whichever you would like to receive

Action method design(cont’d) Example: HTTP GET /hoge/foo?bar=2 Page class takes /hoge as url Action method tales /foo as url Method args takes bar as String So it is like: @Page("/hoge”) public YourPage { @GET @ActionPath(“hoge”) public Navigation hoge( @RequestParam("bar") String bar ) {

Action parameter design Action parameter is injected by T2 T2 prepared contexts WebContext/Request/Response… Servlet spec contexts HttpServletRequest/HttpServletResponse… Converted POJO from form data From HTTP POST, or from Flex AMF Useful parameters REST-like some url, or foreach index, upload file…

Take a look code! @Page(”sample") public class SamplePage { @Default public Navigation index(WebContext context) {… @Amf public Navigation execute(HogeDto hoge) {… @ActionParam public Navigation submit(@Form FooDto foo) {… @ActionPath(“fuga/{moge}”) public Navigation submit( @Var(“moge”) String s) {…

Core components @Page HTTP handling using @GET/@POST URL pattern matching by @ActionPath Request data matching by @ActionParam Request type matching by @Ajax/@Amf Return type, Navigation ContainerAdapter for integrate with DI container

@Page The root annotation for T2 Page Page must have @Page. T2 does not have any configuration except web.xml and @Page Traverse by class path and finds page classes

HTTP matching HTTP matching is the first thing T2 does for action methods GET, POST, PUT, DELETE, even HEAD. These are distinguished by annotation like @GET or @POST

URL matching for action method URL matching for action method @ActionPath is the main role to do @Page(“hoge”) + @ActionPath(“foo”) -> /hoge/foo is the url to access to the method

Data matching for action method Data matching for action method @ActionParam is the main role to do Match submitted request parameter name. If it’s @ActionParam(“execute”), execute the action method if request paramete name “execute” exist Usually it is used to separate user submit action. Data update button, cancel button, things like that.

Request type matching T2 can separate methods for request type. @Ajax Accept only XmlHttpRequest, not others Done by “X-Requested-With” header @Amf Accept only Flex/AIR AMF request, not others Done by content-type header Request type is important The logic must be different with sync/async.

Default method for a page Default method is always good to have. At least some odd error does not happen Default behavior takes over and user doesn’t feel uncomfortable @Default is for default method Usually returns default page transition. Sometimes clear states if application contains.

Navigation Navigation is the user interface for: Telling T2 where the transition goes Telling T2 how view will be rendered Navigation is: Very simple to use. Extensible.Developer can implement easily.

Default prepared navigations Default navigations Forward/Redirect/Proceed(Psuedo redirect) Json(or SecureJson using json-prefixing) Direct(Stream response) AmfResponse(Flex AMF) CacheManifest(Generate HTML5 manifest) In the future: CVS, PDF, GoogleMaps, or Charts.

ContainerAdapter Dependency Injection is the defacto technology for easy and maintainable development T2 provides adapters for these containers: Spring/Guice/Seasar2 or our Lucy It can use by settings using web.xml <init-param> <param-name>t2.container.adapter</param-name> <param-value>org.t2framework.t2.adapter.SpringAdapter</param-value> </init-param>

Demos RIA type demo PureMVC + T2 + Spring + iBatis Complete sample for CRUD Cloud type demo Flex + GAEJ + T2 Using T2 AMF3 implementation Where is my lovely iPhone? Mushup Demo Geolocation(ajax) + T2 + Yahoo local search + iPhone serversman web server

Conclusion Web development will be re-invented by: RIP, mostly HTML5 Cloud environment Multiple HTTP based formats T2 framework is the simple framework for working well with these environments.

Resources Site http://code.google.com/p/t-2/ Download http://code.google.com/p/t-2/downloads/list Maven site http://maven.t2framework.org/maven2/

Resources(cont’d) Documents http://code.google.com/p/t-2/wiki/Index Mailing list http://groups.google.com/group/t2-users-en Source http://code.google.com/p/t-2/source/checkout

T2 Web Framework

Recommended

More Related Content

What's hot (20)

Similar to T2 Web Framework (20)

More from Shinpei Ohtani (17)

Recently uploaded (20)

T2 Web Framework