Salta la navigazione

Java EE 7 (JSR 342) news

  • Annotated POJOs, which have proven to be the cornerstone of ease-of-development paradigm since Java EE 5, continue to rule the roost and further penetrate Java EE
  • Contexts and Dependency Injection (CDI) reputation of being the ‘magic glue’ has been taken to the next level – it’s now ‘default’ in Java EE 7 and its goal is to drive cohesiveness throughout the entire EE platform
  • JMS 2.0 (JSR 343) has been completely ‘revamped‘. A ‘new version’ of the API known as the ‘Simplified API‘ is more succinct, easy-to-use and will ensure that developers have to deal with ‘significantly lesser‘ amounts of ‘boilerplate‘ code
  • JAX-RS 2.0 (JSR 339) – The RESFTful API in Java EE 7 has been further enriched, including addition of a brand new ‘client’ side API, asynchronous capabilities, Servlet Filters and Interceptors
  • Java API for WebSocket (JSR 356) provides a ‘easy-to-use’ and powerful ‘high level’ abstraction for developers to write low latency, real-time and feature rich WebSocket driven applications
  • JSON Support – The Java API for JSON Processing (JSR 353) has finally ‘standardized’ JSON processing. No more ‘third party’ libraries required for dealing with JSON.
  • Concurrency Utilities (JSR 236) API now makes it possible to fire your own threads in Java EE 7 (forbidden prior to this) in a controlled/managed fashion
  • Batch Applications for Java Platform(JSR 352) – Brand new specification in Java EE 7, providing standard way to write efficient ‘batch processing‘ applications


JSR 356, Java API for WebSocket, specifies Java API that developers can use to integrate WebSockets into their applications — both on the server side as well as on the Java client side. Tyrus is the reference implementation for JSR 356.


Java API for JSON Processing


An Overview of Batch Processing in Java EE 7.0



IBM Best practices for developing and working with OSGi applications

This article describes the principal best practices relevant to writing OSGi applications for the OSGi Applications feature of WebSphere Application Server and the integration with Service Component Architecture (SCA).

Objects and method to access data stored in a tree-based Repository inspired from JCR, and extended for asynchronous model

Jackrabbit Oak – the next generation content repository

Sling component filters in CQ5

Sling servlet Filter Support

Java XSS Filter


This talk will discuss approaches to using Object Oriented techniques to remove many of those conditionals.

Apache Blueprint

Blueprint provides a dependency injection framework for OSGi

Startup Genome released the first half of its massive 160-page report on the world’s top startup ecosystems

Open Doors di iStarter, inaugurazione ufficiale nonchè prima uscita pubblica della iniziativa che abbiamo creato insieme ad altri 40 amici e colleghi lo scorso Luglio

CSS and XHTML 1.0 Transitional

Html5 CSS Javascript

Start from here

Blog resource

Apache Felix is a community effort to implement the OSGi R4 Service Platform and other interesting OSGi-related technologies under the Apache license.
Bundle tutorial

Apache Sling web application framework (provides REST-based request resolution) that use Jackrabbit for JCR

The OSGi Alliance is a non-profit corporation founded in March 1999.
The alliance provides specifications, reference implementations, test suites and certification to foster a valuable cross-industry ecosystem.

Modularity reduces software complexity; OSGi is the best model to modularize Java. The OSGi technology facilitates the componentization of software modules and applications and assures remote management and interoperability of applications and services over a broad variety of devices


Web CSS frontend