In a Java EE web or EJB container, when there is an active JTA transaction in progress: Using an acknowledgement mode of JMSContext.AUTO_ACKNOWLEDGEįor a definition of the meaning of this acknowledgement mode see the link below. The session will be non-transacted and received messages will be acknowledged automatically.In a Java SE environment or in the Java EE application client container: There is an active JTA transaction in progress. If this method is called in the Java EE web or EJB container then theīehaviour of the session also depends on whether or not In the Java EE application client container, or in the Java EE web or EJB container. Whether this method is called in a Java SE environment,
The behaviour of the session that is created depends on The connection is created in stopped mode but will be automatically started Since: JMS 1.0 Version: JMS 2.0 See Also: Connection,Ĭreates a JMSContext with the default user identityĪ connection and session are created for use by the new JMSContext. Looking them up should not have any hidden side effects or use surprisingĪmounts of local resources. Its lookup should not use remote resources other than those used by theĬlients should think of administered objects as local Java objects. Of administered objects that will run everywhere.Īn administered object should not hold on to any remote resources. Services, this means that JMS providers can deliver one implementation Since there will be JNDI providers for all popular naming.That are easily organized and administered from a common It abstracts administrative information into objects in the Java.It hides provider-specific details from JMS clients.In addition, it is recommended that these Java.io.Serializable so that they can be stored in all
JMS provider implementations of administered objects It is expected that JMS providers will provide the tools anĪdministrator needs to create and configure administered objects in a The JMS API does not define a naming policy. They make it practical to administer the JMS API in theĪlthough the interfaces for administered objects do not explicitlyĭepend on the Java Naming and Directory Interface (JNDI) API, the JMS APIĮstablishes the convention that JMS clients find administered objects byĪn administrator can place an administered object anywhere in a Information that are created by an administrator and later used by JMS administered objects are objects containing configuration It to create a connection with a JMS provider.Ī ConnectionFactory object is a JMS administered object and Parameters that has been defined by an administrator. A ConnectionFactory object encapsulates a set of connection
0 kommentar(er)
