Error Compiling EJB QL

Question

Hi,
We have just moved to 9.0.3, we loaded our 9.0.2 project, and added two CMP beans. However, we get the error below. It has problems getting the class for a field while compiling the EJB QL. I have pasted the XML for the two beans as well.
javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
     java.lang.Class com.sun.enterprise.deployment.PersistenceDescriptor.getClass(java.lang.String)
          PersistenceDescriptor.java:770
     java.lang.Class com.sun.enterprise.deployment.PersistenceDescriptor.getStateClass()
          PersistenceDescriptor.java:753
     java.lang.Class com.sun.enterprise.deployment.PersistenceDescriptor.getCMPFieldType(java.lang.String)
          PersistenceDescriptor.java:1302
     void com.sun.enterprise.deployment.PersistenceDescriptor.initializeFieldInfo()
          PersistenceDescriptor.java:1052
     com.sun.enterprise.deployment.PersistentFieldInfo[] com.sun.enterprise.deployment.PersistenceDescriptor.getPersistentFieldInfo()
          PersistenceDescriptor.java:805
     void com.sun.ejb.sqlgen.SQLGenerator.<init>(com.sun.enterprise.deployment.PersistenceDescriptor, java.lang.String, com.sun.ejb.sqlgen.SQLTypeMapper, com.sun.ejb.sqlgen.DBMetaData)
          SQLGenerator.java:151
     void com.sun.ejb.sqlgen.SQLGenerator.generateSQL(com.sun.enterprise.deployment.EjbCMPEntityDescriptor, boolean, com.sun.ejb.sqlgen.DBMetaData, com.sun.ejb.sqlgen.SQLTypeMapper)
          SQLGenerator.java:360
     void com.sun.ejb.sqlgen.SQLGenerator.generateSQL(com.sun.enterprise.deployment.EjbBundleDescriptor, com.sun.enterprise.deployment.ResourceReferenceDescriptor, boolean, com.sun.ejb.sqlgen.DBInfo)
          SQLGenerator.java:309
     void com.evermind.server.ejb.deployment.EJBPackage.translateEjbqlQeries()
          EJBPackage.java:2044
     void com.evermind.server.ejb.compilation.Compilation.translateEjbqlQeries()
          Compilation.java:140
     void com.evermind.server.ejb.compilation.Compilation.compile()
          Compilation.java:178
     void com.evermind.server.ejb.EJBContainer.postInit(com.evermind.server.ejb.EJBContainerConfig, com.evermind.server.administration.ApplicationInstallation)
          EJBContainer.java:551
     void com.evermind.server.Application.postInit(com.evermind.server.ApplicationConfig, com.evermind.server.administration.ApplicationInstallation)
          Application.java:431
     void com.evermind.server.Application.setConfig(com.evermind.server.ApplicationConfig, com.evermind.server.administration.ApplicationInstallation)
          Application.java:136
     void com.evermind.server.ApplicationServer.addApplication(com.evermind.server.ApplicationConfig, com.evermind.server.Application, com.evermind.server.administration.ApplicationInstallation)
          ApplicationServer.java:1635
     com.evermind.server.Application com.evermind.server.ApplicationServer.getApplication(java.lang.String, com.evermind.util.ErrorHandler)
          ApplicationServer.java:2130
     void com.evermind.server.XMLApplicationServerConfig.initHttp(com.evermind.server.ApplicationServer)
          XMLApplicationServerConfig.java:1550
     void com.evermind.server.ApplicationServerLauncher.run()
          ApplicationServerLauncher.java:97
Error compiling C:\dir\icis\classes: Error translating EJBQL: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized
     void java.lang.Thread.run()
          Thread.java:484
<entity>
<description>Entity Bean ( CMP )</description>
<display-name>WorkplacePersonHistoryBean</display-name>
<ejb-name>WorkplacePersonHistoryBean</ejb-name>
<home>gov.dir.cis.entity.WorkplacePersonHistoryHome</home>
<remote>gov.dir.cis.entity.WorkplacePersonHistory</remote>
<ejb-class>gov.dir.cis.entity.WorkplacePersonHistoryBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>gov.dir.cis.entity.WorkplacePersonHistoryPK</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>WORKPLACE_PERSON_HISTORY</abstract-schema-name>
<cmp-field>
<field-name>reg_no</field-name>
</cmp-field>
<cmp-field>
<field-name>persons</field-name>
</cmp-field>
<cmp-field>
<field-name>fee_start_date</field-name>
</cmp-field>
<cmp-field>
<field-name>fee_end_date</field-name>
</cmp-field>
<cmp-field>
<field-name>created_date</field-name>
</cmp-field>
<query>
<query-method>
<method-name>findLast</method-name>
<method-params>
<method-param>java.lang.Long</method-param>
</method-params>
</query-method>
<ejb-ql>SELECT OBJECT (o) FROM WORKPLACE_PERSON_HISTORY o WHERE o.reg_no = ?1 AND fee_end_date IS NULL</ejb-ql>
</query>
</entity>
<entity>
<description>Entity Bean ( CMP )</description>
<display-name>SecurityBean</display-name>
<ejb-name>SecurityBean</ejb-name>
<home>gov.dir.cis.entity.SecurityHome</home>
<remote>gov.dir.cis.entity.Security</remote>
<ejb-class>gov.dir.cis.entity.SecurityBean</ejb-class>
<persistence-type>Container</persistence-type>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>SECURITY_EXT</abstract-schema-name>
<cmp-field>
<field-name>user_name</field-name>
</cmp-field>
<cmp-field>
<field-name>password</field-name>
</cmp-field>
<cmp-field>
<field-name>status</field-name>
</cmp-field>
<cmp-field>
<field-name>type</field-name>
</cmp-field>
<cmp-field>
<field-name>owner_no</field-name>
</cmp-field>
<cmp-field>
<field-name>created_date</field-name>
</cmp-field>
<cmp-field>
<field-name>last_accessed_date</field-name>
</cmp-field>
<cmp-field>
<field-name>failed_password</field-name>
</cmp-field>
<primkey-field>user_name</primkey-field>
<prim-key-class>java.lang.String</prim-key-class>
<query>
<query-method>
<method-name>findByOwner</method-name>
<method-params>
<method-param>java.lang.Long</method-param>
</method-params>
</query-method>
<ejb-ql>SELECT OBJECT(o) FROM SECURITY_EXT o WHERE o.owner_no = ?1</ejb-ql>
</query>
</entity>
<entity-deployment name="SecurityBean" data-source="jdbc/DEVDS" table="SECURITY_EXT">
<primkey-mapping>
<cmp-field-mapping name="user_name" persistence-name="USER_NAME" persistence-type="VARCHAR2(20)"/>
</primkey-mapping>
<cmp-field-mapping name="user_name" persistence-name="USER_NAME" persistence-type="VARCHAR2(20)"/>
<cmp-field-mapping name="password" persistence-name="PASSWORD" persistence-type="VARCHAR2(20)"/>
<cmp-field-mapping name="status" persistence-name="STATUS" persistence-type="VARCHAR2(1)"/>
<cmp-field-mapping name="type" persistence-name="TYPE" persistence-type="NUMBER(1)"/>
<cmp-field-mapping name="owner_no" persistence-name="OWNER_NO" persistence-type="NUMBER(6)"/>
<cmp-field-mapping name="created_date" persistence-name="CREATED_DATE" persistence-type="DATE"/>
<cmp-field-mapping name="last_accessed_date" persistence-name="LAST_ACCESSED_DATE" persistence-type="DATE"/>
<cmp-field-mapping name="failed_password" persistence-name="FAILED_PASSWORD" persistence-type="NUMBER(22)"/>
</entity-deployment>
<entity-deployment name="WorkplacePersonHistoryBean" data-source="jdbc/DEVDS" table="WORKPLACE_PERSON_HISTORY">
<primkey-mapping>
<cmp-field-mapping>
<fields>
<cmp-field-mapping name="reg_no" persistence-name="REG_NO" persistence-type="NUMBER(6)"/>
<cmp-field-mapping name="fee_start_date" persistence-name="FEE_START_DATE" persistence-type="DATE"/>
</fields>
</cmp-field-mapping>
</primkey-mapping>
<cmp-field-mapping name="reg_no" persistence-name="REG_NO" persistence-type="NUMBER(6)"/>
<cmp-field-mapping name="persons" persistence-name="PERSONS" persistence-type="NUMBER(5)"/>
<cmp-field-mapping name="fee_start_date" persistence-name="FEE_START_DATE" persistence-type="DATE"/>
<cmp-field-mapping name="fee_end_date" persistence-name="FEE_END_DATE" persistence-type="DATE"/>
<cmp-field-mapping name="created_date" persistence-name="CREATED_DATE" persistence-type="DATE"/>
</entity-deployment>
</enterprise-beans>

Answer 1

Paul -- It looks like the problem may be that you are using a date attribute in your EJB-QL. This is a weakness in EJB-QL in that is is not allowed. Per the specification they recommend using a long representing time as milliseconds like that generated using java.util.Calendar. An option we allow in OC4J to work around this issue is to override your generated SQL in the orion-ejb-jar.xml. This is probably the easiest way to work through this.
To test my theory I would try to just remove the the date related clause and see if it works (although of course the data would be wrong.)
Thanks -- Jeff