[jboss-cvs] JBossCache/src/org/jboss/cache/config ...

[Manik Surtani]

  User: msurtani
  Date: 07/05/24 06:58:54

  Modified:    src/org/jboss/cache/config  RuntimeConfig.java
  Log:
  Made ctor public
  
  Revision  Changes    Path
  1.10      +19 -20    JBossCache/src/org/jboss/cache/config/RuntimeConfig.java
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: RuntimeConfig.java
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/src/org/jboss/cache/config/RuntimeConfig.java,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -b -r1.9 -r1.10
  --- RuntimeConfig.java	9 May 2007 18:24:09 -0000	1.9
  +++ RuntimeConfig.java	24 May 2007 10:58:54 -0000	1.10
  @@ -26,9 +26,9 @@
      private transient NodeFactory nodeFactory;
      private transient BuddyGroup buddyGroup;
   
  -   RuntimeConfig()
  +   public RuntimeConfig()
      {
  -      // package protected ctor
  +      // needs a public ctor for DI frameworks to instantiate.
      }
   
      /**
  @@ -69,18 +69,17 @@
      
      /**
       * Gets the channel the cache is using.
  -    * <p>
  +    * <p/>
       * External callers should use extreme care if they access the channel.
       * The cache expects it has exclusive access to the channel; external code
       * trying to send or receive messages via the channel will almost certainly
       * disrupt the operation of the cache.
       * </p>
       * 
  -    * @see #setChannel(Channel)
  -    * 
       * @return the channel. May return <code>null</code> if the channel was
       *         not externally set via {@link #setChannel(Channel)} and the
       *         cache has not yet been started.
  +    * @see #setChannel(Channel)
       */
      public Channel getChannel()
      {
  @@ -90,24 +89,24 @@
      /**
       * Sets the channel the cache will use.  The channel should not be 
       * connected or closed.
  -    * <p>
  +    * <p/>
       * External callers should use extreme care if they access the channel.
       * The cache expects it has exclusive access to the channel; external code
       * trying to send or receive messages via the channel will almost certainly
       * disrupt the operation of the cache.
       * </p>
  -    * <p>
  +    * <p/>
       * If an application wishes to send and receive messages using the same
       * underlying channel as the <ocde>Cache</code>, a multiplexed channel should
       * be used. Two separate mux channels should be created from the same
       * <code>ChannelFactory</code> using the same <i>stack name</i> but different
       * <code>id</code>s.  
  -    * See {@link ChannelFactory#createMultiplexerChannel(String, String, boolean, String)}.
  +    * See {@link ChannelFactory#createMultiplexerChannel(String,String,boolean,String)}.
       * These two mux channels will share the same underlying channel. One of the 
       * two mux channels can be injected into the cache; the other can be used by 
       * the application.  The cache will not see the application messages and vice versa.
       * </p>
  -    * <p>
  +    * <p/>
       * Configuring the cache to use a mux channel can also be done by configuring
       * {@link #setMuxChannelFactory(ChannelFactory) the channel factory} and the
       * {@link Configuration#setMultiplexerStack(String) stack name}, in which case