Java EE Connector Architecture 1.6 (JSR 322) Technology - One Slide Overview

1,925 views

Published on

A shorter slide-deck highlighting the new features in JSR 322: Java EE Connector Architecture 1.6 Technology.

See http://blogs.sun.com/sivakumart/entry/java_ee_connector_architecture_1 for the announcement of the JSR release and http://jcp.org/en/jsr/detail?id=322 for the JSR.

This presentation has speaker notes

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,925
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
24
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • The Java EE Connector Architecture defines a standard architecture for connecting to heterogeneous enterprise information systems (EIS), such as enterprise resource planning (ERP), mainframe transaction processing and database systems from the Java EE platform. Ease of Development. Developing resource adapters has never been easier through the introduction of metadata annotations, obviating the need for ra.xml(deployment descriptor), better defaults, reducing the number of interfaces to implement etc. Generic work context contract . A generic contract that enables a resource adapter to control the execution context of a Work instance that it has submitted to the application server for execution. The Generic work contract provides the mechanism for a resource adapter to augment the runtime context of a Work instance with additional contextual information flown-in from the EIS. Security work context. A standard contract that enables a resource adapter to establish security information while submiting a Work instance for execution to a WorkManager and while delivering messages to message endpoints residing in the application server. This contract provides a mechanism to support the execution of a Work instance in the context of an established identity. It also supports the propagation of user information/Principal information from an EIS to a MessageEndpoint during Message Inflow. In short: This contract now enables an end-to-end security model for Java EE application-EIS integration Standalone Connector Container: Like “EJB Lite” in Java EE 6 , minimum set of requirements for a connector container is defined so that it can be used in a non-classic(Full) profile. Miscellaneous improvements in various contracts defined in the spec such as Work Management, Message Inflow, Transaction Management
  • - The Connectors 1.6 spec was developed as part of JSR 322 - Reference Implementation is at GlassFish v3 - Siva and Binod are spec leads and often blog about the spec. Jagadish is the RI lead and writes about GlassFish's Connectors implementation.
  • Java EE Connector Architecture 1.6 (JSR 322) Technology - One Slide Overview

    1. 1. Connector 1.6 <ul><li>Enhanced Enterprise Application Integration (EAI)
    2. 2. Easier to develop resource adapters </li><ul><li>New Annotations: @Connector, @ConnectionDefinition, @Activation and more </li></ul><li>Richer Context propagation during Work submission and Message Inflow </li><ul><li>Generic Work Context
    3. 3. Security Context Inflow </li></ul><li>Standalone Connector Container </li></ul>
    4. 4. Resources – learn more & get started <ul><li>JSR 322 page http://jcp.org/en/jsr/detail?id=322
    5. 5. Reference implementation at http://GlassFish.org </li><ul><li>Download GlassFish v3 – Java EE 6 release
    6. 6. Try Connector 1.6 samples and build 1.6 RAs </li></ul><li>Blogs </li><ul><li>Siva: http://blogs.sun.com/sivakumart
    7. 7. Binod: http://weblogs.java.net/blog/binod/
    8. 8. Jagadish: http://blogs.sun.com/JagadishPrasath/ </li></ul></ul>

    ×