Your current filters are…
by Ales Justin
Google App Engine (GAE) is among the most popular cloud application platforms today, offering decent service at a low price point or even for free. Unfortunately, however, its Java environment is also fairly restrictive. This session presents several tips and tricks on how to use top Java EE specs—CDI, JPA, JSF2, and Bean Validation, for instance—within GAE's restrictive sandbox while still benefiting from the highly scalable environment it provides and maintaining portability to other Java EE containers. It demonstrates how CDI can be used to abstract from GAE's services and how state-of-the-art testing frameworks such as ShrinkWrap and Arquillian can be made to work with a GAE application.
There are now quite a few programming languages available on the Java platform (JVM), which has been the case for quite a while. This allows developers to pick the language best suited to their application's needs without sacrificing the power and stability of the JVM. We're not losing the advantages of the JVM by choosing a language other than Java, but what do we gain? For more expressive JVM languages, we can develop faster, and bring back some of the joy of programming. Ruby is a popular and powerful programming language. It owes its success (and power) to its clean and expressive syntax. Why not take advantage of its power and create a system where pretty applications can be run on a very stable and scalable environment? Meet TorqueBox. TorqueBox is the first real application server for Ruby. It allows you to run multiple applications based on Rack (Rails, Sinatra) on the JBoss Application Server. Big deal you say. In reality TorqueBox is much more. Many enterprise-class services offered by JBoss AS such as messaging (JMS) and scheduled jobs are fully available to applications written in Ruby. It is even possible to inject Java EE 6 components like CDI beans into Ruby. Engine written in EJB, front-end in Rails? And everything clustered? Why not! In this session you'll learn how to connect various Java components (CDI beans, message queues) with a simple Rails application.
Originally created for embedded and mobile appliances, OSGi has become a widespread foundation for building modular and dynamic applications on top of the Java platform. Despite its maturity and proven track record, OSGi is more than often referred to as a source of significant complexity for no actual benefits. In this presentation, we will show you how OSGi, CDI and Weld nicely fit together in Weld-OSGi to assemble regular and dynamic components with no added complexity on the developer side. The agenda of the presentation is the following : - CDI, a really nice tech. for Java EE environments - ... and more ? - OSGi, deep dive into a modular and dynamic world - Meet Weld-OSGi - Weld-OSGi design - Features and programming model - Pro and cons - Back to the future ! - Demo: real life app with Weld-OSGi - Conclusion First part of the presentation is about CDI technology, how you can use this amazing piece of tech. inside and outside Java EE containers with Weld and how Weld wasn't yet available for OSGi environment despite its amazing assets. Then the Weld-OSGi framework will be presented after a small summary about OSGi platform. We'll see how the framework is designed and how it enhances standard OSGi bundles with the power of CDI. Each major feature of the framework will be simply explained with short examples. We'll also see how you can benefit from this framework in your modular applications. We will present the future of the Weld-OSGi framework and how we plan to enhance it and integrate it with other techs. Then the presentation will end on a real life app. demo written with Weld-OSGi.
31st October to 1st November 2011