HTML5 Application Development with WebLogic 12.1.2 Doug Clarke Oracle Ottawa, Canada The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. Keywords: Introduction WebLogic, TopLink, HTML5, WebSockets, REST Application development of Thin Server Architecture applications with HTML5 and JavaScript has become much easier with WebLogic 12.1.2. The enhanced support for TopLink's RESTful Data Services, JSON Binding, and the new Web Socket programming model enables active clients to leverage Live Data notifications. This session will introduce and demonstrate how these technologies can be used to construct WebLogic services that work well with HTML5/JS and native mobile client applications. This transcript provides much of the technical background and links to learn more but you are invited to attend the Oracle WebLogic Developer Day to learn more. HTML5 Application Development with WebLogic Server December 3rd, 2013-9am - 1pm GMT / 1pm to 5pm GST / 2:30pm - 6:30 PM IST
Web Sockets Starting with WebLogic 12.1.2 first class support for using WebSockets has been added. This support allows HTML5 clients (and others) to setup a bi-directional communication channel with their components hosted in the WebLogic Server. This support pre-dates JSR 356 offering it own programming model. The following is an example of how the HTTP protocol supports upgrading a connection to be a WebSocket. Server Programming Model Within the WebLogic server application developers can easily develop the server side components required to setup and handle Web Socket communication. In the following example a WebSocketAdapater is provided leveraging the base class and the @WebSocket annotation. This provides the root URL for the Web Socket connection as well as an implementation of the onmessage method which will be invoked when the client passes a message on the Web Socket. @WebSocket(pathPatterns = "/helloworld.ws") public class HelloWorldWebSocket extends WebSocketAdapter { final String MSG = "%s @ %tt"; @Override public void onmessage(websocketconnection connection, String payload) { try { connection.send(string.format(msg, payload, new Date())); } catch (Exception ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } } }
For more information on using Web Sockets in WebLogic 12.1.2 please refer to: http://docs.oracle.com/middleware/1212/wls/wlprg/websockets.htm TopLink Data Services The data access requirements of today s Java applications keep expanding and have grown to include features such as tenant data isolation for cloud deployment, extensible models to support per tenant customization, JSON binding for RESTful web services, the ability to store Java objects in NoSQL databases and more. EclipseLink, included in Oracle TopLink, is well known as an object-relational mapping framework and as the JPA 2.0 reference implementation in Java EE 6 and JPA 2.1 reference implementation in Java EE 7, but it continues to evolve and now provides a comprehensive set of data services for Java developers building enterprise and cloud applications in Java EE and SE. Java Persistence is most commonly associated with Relational Database usage Object- Relational mapping as first standardized with JPA. The scope of the problem space most developers actually deal with in today s application is much larger. It includes not only physical storage of the data but also in transformations dealing with XML and JSON and the service interfaces that require these. The ability to bind objects to XML with JAXB and soon to JSON must also be considered part of the persistence problem space. EclipseLink Project - Background The EclipseLink project (www.eclipse.org/eclipselink) is a key component of the Java Persistence community. EclipseLink delivers the reference implementation for JPA 2.0 and is leading the way with many of the innovations. Within this session we ll highlight some of these innovations as they have been delivered in recent EclipseLink releases.
The EclipseLink Project is composed of three main components: JPA: The Object-relational core of EclipseLink enables, optimizes, and scales applications leveraging relational databases. Its flexible mappings and powerful caching solutions combined with extended functionality for leading databases. MOXy: The JAXB and JSON binding solution simplify mapping object or JPA entities using standard JAXB annotations or extended XML mapping files. Its fidelity with JPA makes it truly unique and important for developers needing XML or JSON binding support for the JPA entity classes. Database Web Services: Starting from a JAX-WS based solution focussed on generation of WSDL and supporting infrastructure this component now includes JPA-RS or RESTful JPA simplifying exposing JPA persistence units over REST. This session builds on these three components explain how the new features evolved based on customer and technology demands and how they can be easily used with Java EE.
JSON Binding and JPA Fidelity The EclipseLink project early on recognized the need to mapping objects into XML based on its own configuration file requirements and the need to support multiple versions of these files to ensure backwards compatibility and minimize forcing customers to continually upgrade their configuration resources. This support eventually became the OXM infrastructure and with the creation of the EclipseLink project was named MOXy. This infrastructure soon became a compliant JAXB implementation and now serves as the default JAXB implementation with Java EE containers such as Oracle WebLogic. With the growing demand for JSON support with RESTful services the EclipseLink MOXy team evolved its XML binding solution to also work with JSON. Now developers could easily map their persistent classes using annotations or XML and decide what format to marshal into at runtime using a media type configuration. In addition to MOXy s expansion into supporting JSON binding it has also adapted to better work with JPA entities. JPA providers generally enhance or extend the JPA entity classes to
contain additional state. These enhanced classes and complex mappings do not always work well with JAXB so MOXy has additional support for dealing with these challenges including handling cyclic relationships. This support allows developers to simply map their JPA entity classes to XML/JSON without require a parallel object model and the conversion code that goes along with it. RESTful JPA (JPA-RS) Based on all of these MOXy and JPA extended features, EclipseLink was able to develop and release its first RESTful JPA solution. This feature is based on all the functionality highlighted in this session and delivers a new breed of persistence service. Developers can now expose their existing JPA persistence unit over REST with automated end point definition and XML/JSON binding. Alternatively a dynamic JPA persistence unit can be defined meaning that the entire service definition is declarative and easily be developed, tested, and deployed in a hosted service. For more information on TopLink please refer to: Project Avatar http://oracle.com/toplink Project Avatar provides a JavaScript services layer zeroed in on supporting REST, WebSockets and Server-Sent Events, and a rich client side framework that assumes very minor JavaScript knowledge. The services side is focused on building data services using JavaScript, while the optional client side is entirely focused on supporting HTML5 and TSA (Thin Server Architecture).
http://avatar.java.net Project Avatar.js - Server-side JavaScript for the JVM Avatar.js is a project to bring the node programming model, APIs and module ecosystem to the Java platform, enabling a new class of hybrid server applications that can leverage two of the most popular programming languages and ecosystems today. These Java+JavaScript applications can leverage capabilities of both environments - access the latest node frameworks while taking advantage of the Java platform's scalability, manageability, tools, and extensive collection of Java libraries and middleware. http://avatar-js.java.net Summary This session introduces so of the functionality available in Oracle WebLogic 12.1.2 and Oracle TopLink that enable the development of Thin Server Architecture (TSA) applications. Leveraging the new WebSocket support and TopLink Data Services developers can easily construct services in WebLogic that provide access to their databases as well as integrating Live Data delivery of changes across Web Sockets.
Contact address: Doug Clarke Oracle Canada ULC 45 O Connor Street K1P 1A4, Ottawa Canada Email douglas.clarke@oracle.com