User: mnf999  
  Date: 01/11/13 17:19:40

  Modified:    src/main/org/jboss/ejb CacheKey.java
  Log:
  Warming up :)
  
  Revision  Changes    Path
  1.18      +7 -6      jboss/src/main/org/jboss/ejb/CacheKey.java
  
  Index: CacheKey.java
  ===================================================================
  RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/CacheKey.java,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- CacheKey.java     2001/11/13 23:41:20     1.17
  +++ CacheKey.java     2001/11/14 01:19:40     1.18
  @@ -29,7 +29,7 @@
    * 
    * @author <a href="mailto:[EMAIL PROTECTED]";>Marc Fleury</a>
    * @author <a href="[EMAIL PROTECTED]">Bill Burke</a>
  - * @version $Revision: 1.17 $
  + * @version $Revision: 1.18 $
    */
   public class CacheKey
      implements Externalizable
  @@ -78,20 +78,21 @@
         this.id = null;
           
         try {
  -         
  +            
  +         // Equals rely on the MarshalledObject itself
  +         mo =  new MarshalledObject(id);
   
  -         /*
  +        /*
            * FIXME MARCF: The reuse of the primary key is an "exception" and this fix 
makes 
             everyone pay an hefty price.  If we really want this behavior we can put 
it in 
             the cache.  Is there a test for this? 
  -         
  -         // Equals rely on the MarshalledObject itself
  -         mo =  new MarshalledObject(id);
  +
            // Make a copy of the id to enforce copy semantics and 
            // allow reuse of the original primary key
            this.id = mo.get();
            
            */
  +         this.id = id;
            
            // Precompute the hashCode (speed)
            hashCode = mo.hashCode();
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to