Error In CMP Generated Code

Question

I have a CMP 2.0 local entity bean, and when I try to create one from a session bean, I get this:
java.lang.IllegalStateException: Can not call getPrimaryKey() inside ejbCreate(...) methods, the entity does not have an identity yet, see the EJB 2.0 specification chapter 10.5.4
     at com.evermind.server.ejb.EJBUtils.throwGetPrimaryKeyInEJBCreateException(EJBUtils.java:963)
     at WebLine_EntityBeanWrapper2.getPrimaryKey(WebLine_EntityBeanWrapper2.java:2595)
     at WebLineHome_EntityHomeWrapper16.create(WebLineHome_EntityHomeWrapper16.java:497)In other words, the generated code for the home's create method is calling getPrimaryKey on the generated code for the entity, and this is failing because even the container can't call getPrimaryKey at that time. It doesn't seem to matter what's in my ejbCreate method, unless it throws an exception (which prevents this problem, of course). Looks like a problem with the generated code to me.

Answer 1

Thanks for that tip. Looking at the generated code, I see:
          boolean imIt = false;
          try
            while(!imIt)
              if(com.evermind.server.ApplicationServer.DEBUG) debug("In while(!imIt)\n");
              WebLine_EntityBeanWrapper2 other;
              other = (WebLine_EntityBeanWrapper2)getWrapperInstance(response.getPrimaryKey(), 90000l, false);That last line is where the error happens (line 520 in the stack trace above). It seems like getPrimaryKey is being called intentionally, to see if the entity is already in the cache or something? Anyway, the generated code for the instance call is:
  public Object getPrimaryKey()
    if(this.primaryKey == null) com.evermind.server.ejb.EJBUtils.throwGetPrimaryKeyInEJBCreateException();
    return this.primaryKey;
  }So that seems reasonable, I suppose. The question is, what is causing the instance to have no PK when the home thinks the PK should be there? I've tried a lot of variants of my code, with no improvement, but I could still be doing something wrong. Also, it only seems to be happening with one bean...