[jboss-cvs] JBossAS SVN: r98806 - projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms.

[jboss-cvs-commits at lists.jboss.org]

Author: jaikiran
Date: 2009-12-22 13:06:36 -0500 (Tue, 22 Dec 2009)
New Revision: 98806

Removed:
   projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms/Destination.java
Log:
Autoversioning commit:  a non-deltaV client made a change to
/projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms/Destination.java

Deleted: projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms/Destination.java
===================================================================
--- projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms/Destination.java	2009-12-22 18:06:28 UTC (rev 98805)
+++ projects/javaee/tags/jboss-javaee-parent-6.0.0-alpha-1/jboss-jms-api/src/main/javax/jms/Destination.java	2009-12-22 18:06:36 UTC (rev 98806)
@@ -1,91 +0,0 @@
-/*
- * JBoss, Home of Professional Open Source
- * Copyright 2005, JBoss Inc., and individual contributors as indicated
- * by the @authors tag. See the copyright.txt in the distribution for a
- * full listing of individual contributors.
- *
- * This is free software; you can redistribute it and/or modify it
- * under the terms of the GNU Lesser General Public License as
- * published by the Free Software Foundation; either version 2.1 of
- * the License, or (at your option) any later version.
- *
- * This software is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- * Lesser General Public License for more details.
- *
- * You should have received a copy of the GNU Lesser General Public
- * License along with this software; if not, write to the Free
- * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
- * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
- */
-package javax.jms;
-
-/** A <CODE>Destination</CODE> object encapsulates a provider-specific 
- * address.
- * The JMS API does not define a standard address syntax. Although a standard
- * address syntax was considered, it was decided that the differences in 
- * address semantics between existing message-oriented middleware (MOM) 
- * products were too wide to bridge with a single syntax. 
- *
- * <P>Since <CODE>Destination</CODE> is an administered object, it may 
- * contain 
- * provider-specific configuration information in addition to its address.
- *
- * <P>The JMS API also supports a client's use of provider-specific address 
- * names.
- *
- * <P><CODE>Destination</CODE> objects support concurrent use.
- *
- * <P>A <CODE>Destination</CODE> object is a JMS administered object.
- *
- * <P>JMS administered objects are objects containing configuration 
- * information that are created by an administrator and later used by 
- * JMS clients. They make it practical to administer the JMS API in the 
- * enterprise.
- *
- * <P>Although the interfaces for administered objects do not explicitly 
- * depend on the Java Naming and Directory Interface (JNDI) API, the JMS API 
- * establishes the convention that JMS clients find administered objects by
- * looking them up in a JNDI namespace.
- *
- * <P>An administrator can place an administered object anywhere in a 
- * namespace. The JMS API does not define a naming policy.
- *
- * <P>It is expected that JMS providers will provide the tools an
- * administrator needs to create and configure administered objects in a
- * JNDI namespace. JMS provider implementations of administered objects
- * should implement the <CODE>javax.naming.Referenceable</CODE> and
- * <CODE>java.io.Serializable</CODE> interfaces so that they can be stored in 
- * all JNDI naming contexts. In addition, it is recommended that these
- * implementations follow the JavaBeans<SUP><FONT SIZE="-2">TM</FONT></SUP> 
- * design patterns.
- *
- * <P>This strategy provides several benefits:
- *
- * <UL>
- *   <LI>It hides provider-specific details from JMS clients.
- *   <LI>It abstracts JMS administrative information into objects in the Java 
- *       programming language ("Java objects") 
- *       that are easily organized and administered from a common 
- *       management console.
- *   <LI>Since there will be JNDI providers for all popular naming 
- *       services, JMS providers can deliver one implementation
- *       of administered objects that will run everywhere.
- * </UL>
- *
- * <P>An administered object should not hold on to any remote resources. 
- * Its lookup should not use remote resources other than those used by the
- * JNDI API itself.
- *
- * <P>Clients should think of administered objects as local Java objects. 
- * Looking them up should not have any hidden side effects or use surprising 
- * amounts of local resources.
- *
- * @see         javax.jms.Queue
- * @see         javax.jms.Topic
- */
-
-public interface Destination
-{
-}