01: /*
02: * JBoss, Home of Professional Open Source.
03: * Copyright 2006, Red Hat Middleware LLC, and individual contributors
04: * as indicated by the @author tags. See the copyright.txt file in the
05: * distribution for a full listing of individual contributors.
06: *
07: * This is free software; you can redistribute it and/or modify it
08: * under the terms of the GNU Lesser General Public License as
09: * published by the Free Software Foundation; either version 2.1 of
10: * the License, or (at your option) any later version.
11: *
12: * This software is distributed in the hope that it will be useful,
13: * but WITHOUT ANY WARRANTY; without even the implied warranty of
14: * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
15: * Lesser General Public License for more details.
16: *
17: * You should have received a copy of the GNU Lesser General Public
18: * License along with this software; if not, write to the Free
19: * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
20: * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
21: */
22: package javax.jms;
23:
24: /** A <CODE>Destination</CODE> object encapsulates a provider-specific
25: * address.
26: * The JMS API does not define a standard address syntax. Although a standard
27: * address syntax was considered, it was decided that the differences in
28: * address semantics between existing message-oriented middleware (MOM)
29: * products were too wide to bridge with a single syntax.
30: *
31: * <P>Since <CODE>Destination</CODE> is an administered object, it may
32: * contain
33: * provider-specific configuration information in addition to its address.
34: *
35: * <P>The JMS API also supports a client's use of provider-specific address
36: * names.
37: *
38: * <P><CODE>Destination</CODE> objects support concurrent use.
39: *
40: * <P>A <CODE>Destination</CODE> object is a JMS administered object.
41: *
42: * <P>JMS administered objects are objects containing configuration
43: * information that are created by an administrator and later used by
44: * JMS clients. They make it practical to administer the JMS API in the
45: * enterprise.
46: *
47: * <P>Although the interfaces for administered objects do not explicitly
48: * depend on the Java Naming and Directory Interface (JNDI) API, the JMS API
49: * establishes the convention that JMS clients find administered objects by
50: * looking them up in a JNDI namespace.
51: *
52: * <P>An administrator can place an administered object anywhere in a
53: * namespace. The JMS API does not define a naming policy.
54: *
55: * <P>It is expected that JMS providers will provide the tools an
56: * administrator needs to create and configure administered objects in a
57: * JNDI namespace. JMS provider implementations of administered objects
58: * should implement the <CODE>javax.naming.Referenceable</CODE> and
59: * <CODE>java.io.Serializable</CODE> interfaces so that they can be stored in
60: * all JNDI naming contexts. In addition, it is recommended that these
61: * implementations follow the JavaBeans<SUP><FONT SIZE="-2">TM</FONT></SUP>
62: * design patterns.
63: *
64: * <P>This strategy provides several benefits:
65: *
66: * <UL>
67: * <LI>It hides provider-specific details from JMS clients.
68: * <LI>It abstracts JMS administrative information into objects in the Java
69: * programming language ("Java objects")
70: * that are easily organized and administered from a common
71: * management console.
72: * <LI>Since there will be JNDI providers for all popular naming
73: * services, JMS providers can deliver one implementation
74: * of administered objects that will run everywhere.
75: * </UL>
76: *
77: * <P>An administered object should not hold on to any remote resources.
78: * Its lookup should not use remote resources other than those used by the
79: * JNDI API itself.
80: *
81: * <P>Clients should think of administered objects as local Java objects.
82: * Looking them up should not have any hidden side effects or use surprising
83: * amounts of local resources.
84: *
85: * @see javax.jms.Queue
86: * @see javax.jms.Topic
87: */
88:
89: public interface Destination {
90: }
|