Slide 1: JavaOne – May 16 – 19, 2006 Chuck Caplan
Slide 2: Key Points 1. 2. 3. 4. Rapid Application Development Performance Separation of Concerns Other
Slide 3: Rapid Application Development   EJB 3.0 Scripting    Javascript in Mustang Groovy Config    Grails XML as part of the language (Dolphin) AJAX
Slide 4: EJB 3.0      Makes use of annotations and therefore requires JDK 5.0 Backwards compatible No more deployment descriptors Session beans and MDB’s are now much easier Entity beans are still fairly complex
Slide 5: Scripting     Dynamically typed scripting (Javascript) will be build into JDK 6.0 (Mustang) Groovy is available now Great for allowing customers to write their own configuration scripts. Java objects can be made available to the script. Too much scripting can hurt performance.
Slide 6: Grails      Based on the Ruby on Rails framework RAD MVC Framework written in Groovy Still in beta Easy to incorporate regular Java as well as Groovy scripting. Alternative to Struts
Slide 7: XML as part of the language    There is a movement to make XML a data type in Java like String, int, etc. XML is widely used but it is very time consuming to properly code in Java. Proposed syntax: #top{element{element2{}element3{}}}
Slide 8: AJAX    Dozens of AJAX frameworks currently exist. There is a proposal to build AJAX into Java Server Faces (JSF) There is almost no need to use the XMLHTTPREQUEST object directly because of great framework support.
Slide 9: Performance   Each JDK version gets better performance Myths about Java being slow because of the JVM are untrue   Playstation emulator Real-time Java Specification  Reduce shared data calls for better performance
Slide 10: JDK Versions
Slide 11: Java is not slow   A real-time Sony Playstation emulator can play 3 simultaneous games on a standard PC without a hiccup. The real-time Java specification (JSR 1) is being used in mission critical applications such as health care and geology.
Slide 12: Reduce Shared Data Calls     Each database call significantly slows down performance. Cache whenever possible Locking is possible so be careful Use the new atomic data structures in JDK 5.0 in multi-threaded applications instead of wait() and notify()
Slide 13: Separation of Concerns  Keep adding layers to further abstract sections of an application  Don’t add too many layers because of performance  SOA is becoming more and more welldefined  Loose coupling, config files, annotations
Slide 14: Other    NetBeans Mobile Applications (J2ME) Java Open Source
Slide 15: NetBeans       Alternative to Eclipse Created by Sun Microsystems Free Features Eclipse does not have like a great tool for creating J2ME applications. Try it and see if you like it. http://www.netbeans.org
Slide 16: Mobile Applications (J2ME)     J2ME is a subset of J2SE with a few added features for mobile phones Midlets are used instead of servlets Millions of J2ME phones on the market and more to come Think about how current apps can coexist with J2ME apps
Slide 17: Java Open Source     “It is not whether Sun will open-source Java, but how.” – Jonathan Schwartz, Sun Microsystems CEO What about fragmenting, I.e. Linux? Java source-code is already freely available, it is just not “Open Source” Try looking at the source to String.java
Slide 18: Summary     Performance is key Standards and Platform Compatibility is key Java is getting easier and more powerful every day The Open Source community is critical