Java One 2005 Technical Conference Report Web

1
Java One 2005 Technical Conference ReportWeb

• Eben Hewitt

2
Goals

• Communicate an overview of Web-specific technical
  content at Java One.
• Articulate and generate ideas for our enterprise
  platform.

3
General Presentation Overview

• General Sessions/Keynote overview
• Java SE 6
• Java EE 5
• EJB 3.0
• Concurrency
• Maven
• APT
• Agile Methods

4
Web-Specific Presentation Overview

• Recap Java EE Roadmap
• Rich UIs with AJAX and JSF
• What's New in WebLogic 9
• Hacking a Web Application
• Hibernate 3
• JavaServer Faces and Shale
• Tapestry
• Scripting Framework
• Other talk overviews

5
Platform Roadmap for EE

• POJO based programming model.
• Fewer deploy descriptors
• Extensive annotations
• Dependency injection
• Annotations will map Java to XML, Java to DB, and
  simplify EJBs

6
Major Features for Java EE 5

• EJB 3, JSP 2.1 (mostly EL), JavaServer Faces
• New Persistence API
• One model usable in JSE/Entities
• Web Services support expanded
• Support SOAP 1.2, Schema, WS-I (Basic profile,
  attachment profile)
• Easier Web Services (no clients, annotations).
  Ex
• _at_WebService public class Hello

7
Status of Java EE 5

• All Specs available now
• Spec final draft Q305
• Beta in Q405
• Final Release Q106

8
Project Glassfish

• Implementation of Java EE
• Can be downloaded via CVS and built with Maven
• See http//glassfish.dev.java.net

9
AJAX

• Asynchronous JavaScript API for XML

10
Rich Web Applications with AJAX

• Conventional apps require complete refresh or
  ActiveX, applet, Flash, etc.
• XMLHttpRequest object
• does GET or POST
• All browsers support it
• Page continues to process events as XHR object
  works in background
• Source code on java.net in the BluePrints

11
AJAX Overview

• Create and object to respond to some DHTML event
  (keyup, etc)
• Set content type to text/xml
• Dont need fully schemad XML (ltvalidgttruelt/valid
  gt is OK).
• Clients can be set up to poll server at
  intervals.
• Doesnt change your EE programming model.

12
AJAX Demo http//labs.google.com/suggest
13
Use Cases for AJAX

• Refreshing data
• Realtime validation
• Auto-completion
• Server polling
• Navigate large data sets
• Show progress bar without refreshing surrounding
  HTML
• Other advanced GUI interaction

14
AJAX Example

• in HttpServlet
• response.setContentType(text/xml)
• Well suited to render CSS/JS from JSF components
• Develop using Firefox built in JS debugger

15
Demo Firefox Debugger
16
AJAX JSF Example

• Best practice Use PhaseListener to process AJAX
  requests, page only has tag reference. Example
• ltajaxcompletionField idemail
  completionMethodmyBean.completeEmail /gt
• Sych state in HTML DOM and JSF

17
Trade-offs for AJAX

• Have to train developers to use it
• Dependent on JS
• Some source in plain view
• Spending time ensuring browser support
• Requires latest generation of browsers
• Chatty

18
Future of AJAX

• AJAX-enabled JSF component libraries
• Standardization of XmlHttpRequest
• Greater support in browsers and frameworks

19
Getting AJAX

• Studio Creator 2
• Download source from java.net, allows you to drag
  completion field onto page
• Free 180,000 word dictionary you can download
• http//ajax.dev.java.net
• https//bpcatalog.dev.java.net/nonav/ajax/index.ht
  ml
• http//weblogs.java.net/blog/gmurray71

20
WebLogic 9.0
21
New in Web Logic 9.0

• Available NOW
• Platform 9 will follow (Portal and Workshop)
• Keys
• Enterprise-grade kernel
• Zero downtime
• Reliable messaging
• SOA
• Enhanced management security
• Multi-programming model interface

22
WL9 Supports

• JSP 2.0
• Servlet 2.4
• SSO
• from browsers via SAML
• from Windows via SPNego
• WSEE 1.1 (JSR 109/192)
• JCA bi-di 1.5
• JMS 1.1
• Foreign JNDI
• JMX 1.2
• JMX components can now communicate across JVMs
• So Weblogic.management.MBeanHome is deprecated
• Deployment plans through scripting tool
• EJB 2.1
• EJB 3 via JAR (coming soon)

23
JSP 2.0 Support Means

• SimpleTag handler
• Dynamic Attributes for any tag handler
• JSP Property Groups
• Configurable implicit include-prelude and
  include-code for JSP page groups

24
WL9 Disruption-free upgrades

• Managed across a cluster
• Round-robin servers when applying service packs
• Whole server migrations
• Singleton services
• Session failover across a WAN or MAN
• Side-by-side deployment
• same JNDI, simultaneous response

25
WL9 Enterprise Kernel

• J2EE
• BPEL
• Portal
• CFML
• Beehive
• JFC/Swing
• WebServices
• Native WS

26
WebLogic 9 Self-Tuning

• Workload Management
• admins can define scheduling policies and
  constraints at domain/app/module level
• Auto thread count tuning based on throughput and
  queue size history

27
WL9 Web Services

• Now supports JSR 181 Annotations
• _at_WebService(nameSimplePortType,
  serviceNameSimpleService, targetNamespacehttp
  /some.com)
• _at_SOAPBinding(styleSOAPBinding.Style.DOCUMENT,
• useSOAPBinding.Use.LITERAL,
• parameterStyleSOAPBinding.ParameterStyle.WRAPPED
  )
• _at_WLHttpTransport(contextPathsimple,
  serviceUriSimpleService, portNameSimpleServic
  ePort)
• public class SimpleImpl
• _at_WebMethod()
• public String sayHello() return Hello

28
WL9 Web Services Notes

• WL Ant tasks included
• Entire 8.1 WS API deprecated
• 8.1 WS will run unchanged

29
WL9 JMS Enhancements

• Supports JMS 1.1
• Migrates a JMS server automatically if it thinks
  it is not in good health
• JMS resources defined as module that can be
  included in an EAR or deployed (no more 2-step
  process)

30
WL9 More JMS

• MDB Batch transactions
• Store-forward like in Tuxedo preserves message
  ordering
• Asynchronous store and forward between servers
  and domains in case of fault
• Faster persistence messaging

31
WL9 SOA

• Use JSR 109 or JSR 181 annotations to author and
  deploy WS
• Performance improvements
• Integrates with Enterprise Service Bus
  (AquaLogic) to provide governable homogenous
  callable services
• Flexible databinding with XMLBeans support
• BEA project donated to Apache in 2003.
• Allows Java object view of XML data without
  losing original structure.
• Classes generated from schema provides all major
  functions of XML Schema

32
WL9 Management

• Configuration and change management
• Takes advantage of instrumentation API in Java 5
• Auditing configuration through channels
• Totally new WLS Console now Struts app based on
  Portal
• You can add admin features for your own apps into
  Console

33
Demo WL 9 Console

34
WL9 Diagnostics

• WL can introspect its own health
• Standard Logging
• Improved JMX controls
• Dynamic instrumentation
• Request dyeing and context tracing, even across
  containers, even while running
• Ability to understand any entry point into
  servers (ie, RMI)
• Set watches to trigger events
• Server Image Capture

35
Web Logic 9 Deployment

• Extends JSR 88 SPI with PlanGenerator
• New Directory Structure
• Separates config files from app files
• /Install-Root
• /App-Root
• Some.ear
• /Plan-Root
• Plan.xml
• Applications as Domain Libraries

36
Upgrading from 8.1 to 9

• Server domain upgrades Performed via Upgrade
  Wizard
• Also performs compatibility inspection of Java
  classes and identify WL APIs.

37
Portal Vendors Debate Architecture

• BEA, Sun, Plumtree, Vignette attended
• Portlet spec never took off.

38
Oracle Keynote

• Almost entirely about JSF and EJB 3
• Oracle is spending a lot of RnD on JSF components
  and donating to MyFaces
• Oracle is building a DnD tool for JSF, built on
  Eclipse

39
JSF VoiceXML Render Kit

• 3 classes and a config file
• Voice browser is much like an internet browser,
  but there is a gateway, and it reads VoiceXML
• Vendors
• Voicegeni
• TellMe Studios
• Vocalocity
• Cisco has them integrated with their 10S routers

40
9 Ways to Hack a Web App

• 1. Unvalidated input
• 2. Broken Access Control
• 3. Broken Account/Session Management
• 4. Cross Site Scripting
• 5. Buffer overflow
• 6. Injection Flows
• 7. Improper Error Handling
• 8. Insecure Storage
• 9. DoS

41
How to Address Hacks

• Load testing
• Code reviews
• Handle exceptions
• Use real Encryption with Key (not base64encode)
• Use only what you need instead of OOB
• Developers are not Web Masters
• Turn off all unused services

42
Hacking Tools

• BRUTUS password generator
• www.hoobie.net/brutus

43
Demo Brutus
44
JSF with Studio Creator

• Graphical CSS Editor
• DnD EJBs, Web Services, DB tables, code clips
• AJAX Component Library
• Google Suggest
• HTTP Monitor
• Integrated CVS (like NetBeans)
• Visual Portlet Creation
• Query Editor
• Project Manager

45
Hibernate 3.0

• Allow inheritance mappings
• Allows filters
• Bulk update/delete
• Support for handwritten SQL
• Embeddable in JBoss microcontainer, can use
  Hibernate via Mbean

46
Shale
47
Shale The Next Struts

• Given by David Geary and Craig McClanahan
• Shale assumes JSF
• This is McClanahans proposal for Struts 2.0.
• No direct connection to current versions of
  Struts
• Shale is entirely new code.

48
Shale Features

• WebFlow scope
• Built in remoting for AJAX
• Validator extensions with JSF components
• Spring and Tiles integration
• Parameterized subtrees
• Tapestry-like views (match IDs in tags to XML)
• Utils (back button abuse, JNDI simplification

49
What Shale Does

• Variable resolver means you can reference Spring
  beans in faces-config or in JSF expressions
• Tie plain HTML elements to components with jsfid
  attribute
• You can then run in two modes (HTML view .html
  and Runtime view .faces)
• Shale is a filter, not a controller servlet

50
ViewController Interface

• If you implement ViewController, you get services
  for free
• Dependency Injection
• Indicates postback
• Additional lifecycle events
• Init
• Preprocess
• Prerender
• Destroy

51
Shale and Spring

• WebFlow modeled after Springs WebFlow but more
  intuitive
• Uses Spring beans by just adding shale-spring.jar

52
Shale Dialogs

• Hold state, like UML State diagram
• Action States and View States
• Dialogs defined in dialog-config.xml
• Shale nav handler takes over until dialog is done

53
Future of Shale

• Struts is not quite dead.
• Likely to be Struts 2.0 (it assumes JSF)
• New Apache project
• May be folded into MyFaces
• May become JSF 2.0

54
Shale Info

• Wiki http//wiki.apache.org/struts/StrutsShale
• Page http//struts.apache.org/shale

55
Tapestry
56
Tapestry Overview

• Started in 2000
• Goals are Minimal Java coding, clean HTML
• Component-oriented, not operation-oriented
• Eliminates plumbing in URLs, query params

57
Tapestry Benefits

• RAD
• Easy team development
• Easy to create new components
• True component reuse
• Hides Servlet API
• Highly localized

58
Tapestry is not

• Merely a template engine
• Not Struts
• Not one-man project

59
Writing Tapestry Templates

• lthtml jwcid_at_Bordergt
• ltform jwcidform_at_form listenerdologingt
• Uses Object Graph Navigation Library available at
  httpwww.ognl.org

60
OGNL

• EL for getting and setting Java object
  properties.
• Uses
• as a binding language between GUI elements to
  model objects (Swing and Web)
• A data source language to map table columns to a
  table model.
• More expressive replacement for more rudimentary
  BeanUtils.

61
Tapestry Pages

• Extend BasicPage
• Contains methods and Properties
• Properties are abstract
• Page objects are pooled, Tapestry writes the
  subclass

62
Scripting Use Cases in JSE 6

• Stand-alone script interpreter
• Script uses Java objects
• Java technology extends script language
• Java application calls script engine
• Script engine used as macro interpreter
• Script generates web content
• Scripting Framework

63
Scripting Support

• JSR 223
• javax.script package
• javax.script.http package
• Depends on Servlet, so wait until Dolphin

64
Inside Scripting

• jrunscript
• Experimental command all-language tool.
• scripting language independent shell
• JavaScript technology engine implementation based
  on Mozilla Rhino
• JavaScript for Java
• var strArr java.lang.reflect.Array.newInstance(j
  ava.lang.String, 5)
• A JS compiler to transform JS source into Java
  classes
• A shell for executing JavaScripts
• Few optional components of Rhino engine have been
  removed
• See http//www.mozilla.org/rhino

65
Scripting Framework

• Manages multiple script engines in a registry
• Script engine discovery and instantiation
• Maintains state shared by script engines

66
ScriptEngine

• Executes scripts
• Map script variables to application objects
• Invoke script functions through Java technology
  interface
• Implement Java technology interfaces using script
  functions
• Rhino has no bytecode compilation requires Java
  Adapter to implement
• Compile script to intermediate form
• Execute multiple times without recompilation

67
Presentation Available at

• M\\JavaOne\2005

68
Discussion