Presentation is loading. Please wait.

Presentation is loading. Please wait.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 1.

Published byEsmond Marvin Cannon Modified over 9 years ago

Similar presentations

Presentation on theme: "Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 1."— Presentation transcript:

1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 1

2 2 What’s new in Java Message Service 2.0? Nigel Deakin JSR 343 Specification Lead Oracle

3 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 3 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.

4 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 4 BOF Meet the experts: JMS 2.0 expert group Tuesday 2 Oct 2012 1630 - 1715 Parc 55: Cyril Magnin II/III

5 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 5 JMS  A Java API for sending and receiving messages  Many competing implementations  Two distinct API variants – Java SE applications – Java EE applications (web, EJB, application client)  adds support for JTA transactions, MDBs  removes features considered inappropriate in a managed application server environment

6 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 6 What JMS is and isn't  A standard API – Not a messaging system in itself – Not a wire protocol  Defines Java API only – Doesn't define API for non-Java clients (e.g. C++, HTTP) - but many implementations do)  An application API – Not (currently) an admin, management or monitoring API

7 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 7 JMS 2.0  JMS 1.1 last updated in 2002  JMS 2.0 launched in 2011 as JSR 343 – Expert group contains 20 members, including FuseSource, IBM, Oracle, Pramati, Red Hat, TIBCO – Early Draft published Feb 2012 – NOT FINISHED! – Final release planned Q2 2013 (aligned with Java EE 7) – More information at http://jms-spec.java.nethttp://jms-spec.java.net – Join the user email alias and get involved

8 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 8 Goals of JMS 2.0  Simplicity and ease of use  New messaging features  Better Java EE integration – define the slightly different JMS API more clearly – simpler resource configuration – standardized configuration of JMS MDBs – better application server pluggability  Minor corrections and clarifications  Cloud / PaaS features deferred to Java EE 8

9 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 9 JMS 2.0: Simplifying the JMS API

10 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 10 What's wrong with the JMS 1.1 API?

11 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 11 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } 13 lines of code just to send a message

12 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 12 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } must create several intermediate objects

13 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 13 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } redundant and misleading arguments

14 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 14 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } boilerplate code

15 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 15 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } must close resources after use!

16 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 16 JMS 1.1: Sending a message @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessage(String payload) { try { Connection connection = connectionFactory.createConnection(); try { Session session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE); MessageProducer messageProducer = session.createProducer(demoQueue); TextMessage textMessage = session.createTextMessage(payload); messageProducer.send(textMessage); } finally { connection.close(); } } catch (JMSException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } all methods throw checked exceptions

17 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 17 Simplifying the JMS API  Simplify existing JMS 1.1 API where it won't break compatibility  Define new simplified API requiring fewer objects – JMSContext, JMSProducer, JMSConsumer  In Java EE, allow JMSContext to be injected and managed by the container Strategy

18 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 18 Simplifying the existing JMS 1.1 API  Need to maintain backwards compatibility limits scope for change  New methods on javax.jms.Connection to create a Session: – Existing method (will remain) – New method mainly for Java SE – New method mainly for Java EE Simpler API to create a Session connection.createSession(transacted,deliveryMode) connection.createSession(sessionMode) connection.createSession()

19 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 19 Simplifying the existing JMS 1.1 API  Make JMS objects implement java.jang.AutoCloseable – Connection – Session – MessageProducer – MessageConsumer – QueueBrowser  Requires Java SE 7 Simpler API to close JMS objects

20 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 20 Simplifying the existing JMS 1.1 API  Make JMS objects implement java.jang.AutoCloseable – Connection, Session, MessageProducer, MessageConsumer, QueueBrowser Simpler API to close JMS objects @Resource(lookup = "jms/connFactory") ConnectionFactory cf; @Resource(lookup="jms/inboundQueue") Destination dest; public void sendMessage (String payload) throws JMSException { try ( Connection conn = connectionFactory.createConnection(); Session session = conn.createSession(); MessageProducer producer = session.createProducer(dest); ){ Message mess = sess.createTextMessage(payload); producer.send(mess); } catch(JMSException e){ // exception handling } } close() is called automatically at end of block Create closeable resources in a try-with- resources block

21 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 21 New simplified API for JMS 2.0 Introducing JMSContext and JMSProducer @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessageNew(String payload) { try (JMSContext context = connectionFactory.createContext();){ context.createProducer().send(demoQueue, payload); } catch (JMSRuntimeException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } 13 lines reduced to 5

22 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 22 @Resource(lookup = "java:global/jms/demoConnectionFactory") ConnectionFactory connectionFactory; @Resource(lookup = "java:global/jms/demoQueue") Queue demoQueue; public void sendMessageNew(String payload) { try (JMSContext context = connectionFactory.createContext();){ context.createProducer().send(demoQueue, payload); } catch (JMSRuntimeException ex) { Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex); } New simplified API for JMS 2.0 Introducing JMSContext and JMSProducer JMSContext combines Connection and Session Payload can be sent directly No checked exceptions thrown close() is called automatically at end of block

23 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 23 JMSContext (1/2)  A new object which encapsulates a Connection, a Session and an anonymous MessageProducer  Created from a ConnectionFactory  Call close() after use, or create in a try-with-resources block  Can also be injected (into a Java EE web or EJB application) JMSContext context = connectionFactory.createContext(sessionMode);

24 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 24 JMSContext (2/2)  Can also create from an existing JMSContext (to reuse its connection – Java SE only)  Used to create JMSProducer objects for sending messages  Used to create JMSConsumer objects for receiving messages  Methods on JMSContext, JMSProducer and JMSConsumer throw only unchecked exceptions JMSContext context2 = context1.createContext(sessionMode);

25 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 25 JMSProducer  Messages are sent by creating a JMSProducer object – does not encapsulate a MessageProducer so is lightweight – supports method chaining for a fluid style  JMS 1.1  JMS 2.0 MessageProducer producer = session.createProducer(); producer.send(destination,message); JMSProducer producer = context.createProducer(); producer.send(destination,message);

26 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 26 JMSProducer  JMS 1.1  JMS 2.0 Setting message delivery options using method chaining context.createProducer().setDeliveryMode(DeliveryMode.NON_PERSISTENT). setPriority(1).setTimeToLive(1000).send(destination,message); MessageProducer producer = session.createProducer(); producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT); producer.setPriority(1); producer.setTimeToLive(1000); producer.send(destination,message);

27 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 27 JMSProducer  JMS 1.1 (need to set on the message)  JMS 2.0 (can also set on the JMSProducer) Setting message properties and headers context.createProducer().setProperty("foo","bar").send(destination,"Hello"); MessageProducer producer = session.createProducer(); TextMessage textMessage = session.createTextMessage("Hello); textMessage.setStringProperty("foo","bar"); producer.send(destination,message);

28 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 28 JMSProducer  Methods on JMSProducer to send a Message – send(Destination dest, Message message)  No need to create a Message – send(Destination dest, Map payload) – send(Destination dest, Serializable payload) – send(Destination dest, String payload) – send(Destination dest, byte[] payload)  Use methods on JMSProducer to set delivery options, message headers and message properties Sending message payloads directly

29 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 29 JMSConsumer  Messages are consumed by creating a JMSConsumer object – encapsulates a MessageConsumer – similar functionality and API to MessageConsumer  Synchronous  Asynchronous  Connection is automatically started (configurable) JMSConsumer consumer = context.createConsumer(destination); Message message = consumer.receive(1000); JMSConsumer consumer = context.createConsumer(destination); consumer.setMessageListener(messageListener);

30 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 30 JMSConsumer Receiving message payloads directly  Methods on JMSConsumer that return a Message – Message receive(); – Message receive(long timeout); – Message receiveNoWait();  Methods on JMSConsumer that return message payload directly – T receivePayload(Class c); – T receivePayload(Class c, long timeout); – T receivePayloadNoWait(Class c);

31 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 31 JMSConsumer Receiving message payloads directly public String receiveMessage() throws NamingException { InitialContext initialContext = getInitialContext(); ConnectionFactory connectionFactory = (ConnectionFactory) initialContext.lookup("jms/connectionFactory"); Queue inboundQueue = (Queue)initialContext.lookup("jms/inboundQueue"); try (JMSContext context = connectionFactory.createContext();) { JMSConsumer consumer = context.createConsumer(inboundQueue); return consumer.receivePayload(String.class); }

32 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 32 Injection of JMSContext objects into a Java EE web or EJB container @Inject @JMSConnectionFactory("jms/connectionFactory") private JMSContext context; @Resource(mappedName = "jms/inboundQueue") private Queue inboundQueue; public void sendMessage (String payload) { context.createProducer().send(inboundQueue, payload); }

33 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 33 Injection of JMSContext objects into a Java EE web or EJB container @Inject @JMSConnectionFactory("jms/connectionFactory") private JMSContext context; @Resource(mappedName = "jms/inboundQueue") private Queue inboundQueue; public void sendMessage (String payload) { context.createProducer().send(inboundQueue, payload); } Use @Inject to inject the JMSContext, specifying connection factory to use Container will close JMSContext automatically at end of transaction

34 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 34 Injection of JMSContext objects  Connection factory will default to platform default JMS  Specifying session mode  Specifying user and password (may be aliased) into a Java EE web or EJB container @Inject private JMSContext context; @Inject @JMSConnectionFactory("jms/connectionFactory") @JMSSessionMode(JMSContext.AUTO_ACKNOWLEDGE) private JMSContext context; @Inject @JMSConnectionFactory("jms/connectionFactory") @JMSPasswordCredential(userName="admin",password="mypassword") private JMSContext context;

35 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 35 Injection of JMSContext objects  Injected JMSContext objects have a scope – In a JTA transaction, scope is the transaction – If no JTA transaction, scope is the request  JMSContext is automatically closed when scope ends  Inject two JMSContext objects within the same scope and you get the same object – if @JMSConnectionFactory, @JMSPasswordCredential and @JMSSessionMode annotations match – Makes it easier to use same session within a transaction into a Java EE web or EJB container

36 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 36 JMS 2.0: New API features

37 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 37 Making durable subscriptions easier to use  Durable subscriptions are identified by {clientId, subscriptionName}  ClientId will no longer be mandatory when using durable subscriptions  For a MDB, container will generate default subscription name (EJB 3.2)

38 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 38 Delivery delay  Allows a JMS client to schedule the future delivery of a message  New method on MessageProducer  New method on JMSProducer  Sets minimum time in ms from that a message should be retained by the messaging system before delivery to a consumer  Why? If the business requires deferred processing, e.g. end of day public JMSProducer setDeliveryDelay(long deliveryDelay) public void setDeliveryDelay(long deliveryDelay)

39 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 39 Async send  Send a message and return immediately without blocking until an acknowledgement has been received from the server.  Instead, when the acknowledgement is received, an asynchronous callback will be invoked  New methods on MessageProducer  Feature also available on JMSProducer  Why? Allows thread to do other work whilst waiting for the acknowledgement messageProducer.send(message,completionListener)

40 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 40 Async send  Application specifies a CompletionListener instance public interface CompletionListener { void onCompletion(Message message); void onException(Message message, Exception exception); }

41 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 41 Better handling of "poison" messages  JMS 1.1 defines an optional JMS defined message property JMSXDeliveryCount. – When used, this is set by the JMS provider when a message is received, and is set to the number of times this message has been delivered (including the first time). The first time is 1, the second time 2, etc  JMS 2.0 will make this mandatory  Why? Allows app servers and applications to handle "poisonous" messages better Make JMSMXDeliveryCount mandatory

42 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 42 Multiple consumers on a topic subscription  Allows scalable consumption of messages from a topic subscription – multiple threads, multiple JVMs  New methods needed for non-durable subscriptions  Existing methods used for durable subscriptions  Also available on JMSContext MessageConsumer messageConsumer= session.createSharedConsumer(topic,sharedSubscriptionName); MessageConsumer messageConsumer= session.createDurableConsumer(topic,durableSubscriptionName);

43 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 43 Easier definition of JMS resources in Java EE Joint effort with JSR 342 (Java EE 7 platform)

44 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 44 Easier definition of JMS resources in Java EE  Java EE and JMS recommend applications should obtain JMS ConnectionFactory and Destination resources by lookup from JNDI  Keeps application code portable  Creating these resources is a burden on the deployer, and is non- standard The problem @Resource(lookupName = "jms/inboundQueue") private Queue inboundQueue;

45 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 45 Platform default connection factory  if you simply want to use the application server's built in JMS Making the simple case simple @Resource(lookup="java:comp/defaultJMSConnectionFactory") ConnectionFactory myJMScf;

46 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 46 Easier definition of JMS resources in Java EE  Application may specify the JMS connection factories and JMS destinations that it needs using annotations  Deployer can further define requirements using deployment descriptor elements  Application server can use this information to create resources automatically when application is deployed  The JMS equivalent to @DataSourceDefinition annotations  Supporting these automatically is optional New optional feature in Java EE 7

47 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 47 Easier definition of JMS resources in Java EE  Can also specify deployment-specific properties via annotations, but these are best added at deployment time Application defines required resources using annotations @JMSDestinationDefinition( name = "java:global/jms/demoQueue", description = "Queue to use in demonstration", className = "javax.jms.Queue", destinationName="demoQueue") @JMSConnectionFactoryDefinition( name="java:global/jms/demoConnectionFactory", className= "javax.jms.ConnectionFactory", description="ConnectionFactory to use in demonstration")

48 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 48 Easier definition of JMS resources in Java EE Deployer adds further requirements using deployment descriptor java:global/jms/demoConnectionFactory addressList mq://localhost:7676 30 20 5 "java:global/jms/demoQueue javax.jms.Queue jmsra demoQueue non-standard properties may be specified if needed

49 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 49 More standardized configuration of JMS MDBs Joint effort with JSR 345 (EJB 3.2)

50 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 50 More standardized configuration of JMS MDBs  Configuration of JMS MDBs is surprisingly non-standard  EJB 3.1 does not define how to specify – JNDI name of queue or topic (using annotation) – JNDI name of connection factory – clientID – durableSubscriptionName  EJB 3.1 does not define how topic messages delivered to clustered MDBs

51 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 51 More standardized configuration of JMS MDBs  Can also be configured in ejb-jar.xml New activation property to specify the queue or topic @MessageDriven(activationConfig = { @ActivationConfigProperty( propertyName = "destinationLookup", propertyValue = "jms/myTopic"),... })

52 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 52 More standardized configuration of JMS MDBs  Can also be configured in ejb-jar.xml New activation property to specify the connection factory @MessageDriven(activationConfig = { @ActivationConfigProperty( propertyName = "connectionFactoryLookup", propertyValue = "jms/myCF"),... })

53 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 53 More standardized configuration of JMS MDBs  Surprisingly, these have never been standardized before New activation properties to specify durable subscriptions @MessageDriven(activationConfig = { @ActivationConfigProperty( propertyName = "subscriptionDurability", propertyValue = "Durable"), @ActivationConfigProperty( propertyName = "clientId", propertyValue = "myClientID"), @ActivationConfigProperty( propertyName = "subscriptionName", propertyValue = "MySub"),... })

54 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 54 Easier configuration of durable subscriptions No need to specify clientId and subscription name @MessageDriven(activationConfig = { @ActivationConfigProperty( propertyName = "subscriptionDurability", propertyValue = "Durable"), @ActivationConfigProperty( propertyName = "clientId", propertyValue = "myClientID"), @ActivationConfigProperty( propertyName = "subscriptionName", propertyValue = "MySub"),... }) clientId no longer required for durable subscriptions if subscription name is omitted, the container generates a suitable name

55 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 55 Topic delivery to clustered application servers One message per instance or one message per cluster? Application server cluster Application server instance MDB Application server instance MDB Application server instance MDB Topic ?

56 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 56 Topic delivery to clustered application servers  Defined behavior if subscriptionName and clientId not set – each message will be delivered once per cluster – clustered app server instances will share the same subscription  To disable, set sharedSubscriptions activation property to false – each message will be delivered once per instance – each app server instance will have a separate subscription  Applies to both durable and non-durable subscriptions

57 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 57 Improved Java EE pluggability

58 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 58 Improved Java EE pluggability  The goal – To make it easier to use a particular JMS provider in different Java EE application servers – e.g. GlassFish application sending messages to WebLogic JMS  The solution – To require JMS providers to supply a JCA resource adapter

59 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 59 Improved Java EE pluggability  Java Connector Architecture is designed for this: – for integrating pooled, transactional resources in an application server – for async processing of messages by MDBs  JCA support already mandatory in Java EE  Many JMS vendors already provide JCA adapters  JMS 2.0 will make provision of a JCA adaptor mandatory  Should be invisible to applications! using the Java Connector Architecture (JCA)

60 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 60 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. What's new in JMS 2.0  Simplicity and ease of use  New messaging features – multi-threaded topic subscribers – delivery delay – async send  Better Java EE integration – simpler resource configuration – standardized configuration of JMS MDBs – better application server pluggability  Minor corrections and clarifications

61 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 61 Where to find out more  See the demo at the Java EE booth in the DemoGrounds  Come to the BOF tomorrow  Read the draft spec and API docs at jms-spec.java.net  Join users@jms-spec.java.net and send questions and commentsusers@jms-spec.java.net  Try the latest GlassFish and Open Message Queue builds

62 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 62 Try the new features as they are added  GlassFish 4.0 – http://glassfish.java.net/ http://glassfish.java.net/ – http://dlc.sun.com.edgesuite.net/glassfish/4.0/promoted/  Open Message Queue 5.0 – http://mq.java.net/ http://mq.java.net/ – http://mq.java.net/5.0.html http://mq.java.net/5.0.html  These are not finished! JMS 2.0, EJB 3.2 and Java EE

63 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 63 Any questions? More time for questions and comments at our BOF tomorrow Meet the JMS 2.0 expert group Tuesday 2 Oct 2012 1630 - 1715 Parc 55: Cyril Magnin II/III

64 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 64 Graphic Section Divider

65 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 65

Download ppt "Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 1."

Similar presentations

21 Copyright © 2005, Oracle. All rights reserved. Oracle Application Server 10g Transaction Support.

21 Copyright © 2005, Oracle. All rights reserved. Oracle Application Server 10g Transaction Support.
5 Copyright © 2005, Oracle. All rights reserved. Accessing the Database with Servlets.

5 Copyright © 2005, Oracle. All rights reserved. Accessing the Database with Servlets.
16 Copyright © 2005, Oracle. All rights reserved. Developing Message-Driven Beans.

16 Copyright © 2005, Oracle. All rights reserved. Developing Message-Driven Beans.
11 Copyright © 2005, Oracle. All rights reserved. Creating the Business Tier: Enterprise JavaBeans.

11 Copyright © 2005, Oracle. All rights reserved. Creating the Business Tier: Enterprise JavaBeans.
Java Message Service (JMS) CS 595 Web Services Aysu Betin-Can.

Java Message Service (JMS) CS 595 Web Services Aysu Betin-Can.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1.

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1.
MVC in JavaEE 8 Manfred Riem Principal Member of Technical Staff September, 2014 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

MVC in JavaEE 8 Manfred Riem Principal Member of Technical Staff September, 2014 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
J2EE Design patterns Sharath Sahadevan August 8, 2002 St Louis Java SIG.

J2EE Design patterns Sharath Sahadevan August 8, 2002 St Louis Java SIG.
A Java Architecture for the Internet of Things Noel Poore, Architect Pete St. Pierre, Product Manager Java Platform Group, Internet of Things September.

A Java Architecture for the Internet of Things Noel Poore, Architect Pete St. Pierre, Product Manager Java Platform Group, Internet of Things September.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13 1.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13 1.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1 Graphic Section Divider.

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1 Graphic Section Divider.
Approaches to EJB Replication. Overview J2EE architecture –EJB, components, services Replication –Clustering, container, application Conclusions –Advantages.

Approaches to EJB Replication. Overview J2EE architecture –EJB, components, services Replication –Clustering, container, application Conclusions –Advantages.
An architecture for webb applications, J2EE

An architecture for webb applications, J2EE
A Study in JMS (Java Messaging Service) Chad Beaudin CS 522 Fall Semester 2002.

A Study in JMS (Java Messaging Service) Chad Beaudin CS 522 Fall Semester 2002.
Java Messaging Services CS-328. Messaging Systems A messaging System allows and promotes the loose coupling of components –allows components to post messages.

Java Messaging Services CS-328. Messaging Systems A messaging System allows and promotes the loose coupling of components –allows components to post messages.
Enterprise Applications & Java/J2EE Technologies Dr. Douglas C. Schmidt Professor of EECS.

Enterprise Applications & Java/J2EE Technologies Dr. Douglas C. Schmidt Professor of EECS.
A Study in JMS (Java Messaging Service) Chad Beaudin CS 522 Fall Semester 2002.

A Study in JMS (Java Messaging Service) Chad Beaudin CS 522 Fall Semester 2002.
Java Message Service API CSE 487/587 Feb 17, 2005 References: JRun Programmer’s Guide.

Java Message Service API CSE 487/587 Feb 17, 2005 References: JRun Programmer’s Guide.
ECSE 6780- Software Engineering 1I - 1 - HO 7 © HY 2012 Lecture 7 Publish/Subscribe.

ECSE Software Engineering 1I HO 7 © HY 2012 Lecture 7 Publish/Subscribe.
The Safe Harbor The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated.

The Safe Harbor The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated.

Similar presentations

Ads by Google