Oc4j generated finders in orion-ejb-jar.xml file causing errors

Question

Any information or assistance would be greatly appreciated.
I have encountered a problem with the generated orion-ejb-jar.xml file.
It looks like the additional finder methods that are generated when the application
is deployed are incorrect from the 9.0.3 version to the new 10.1.2.0.2 version.
The original content of orion-ejb-jar.xml before additional finder syntax is added:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
  SELECT H1.AUTOID                             
  FROM   NO_SYS_USER_OBJECT_HISTORY H1,                                
         (SELECT AUTOID                                     
          FROM   NO_SYS_USER_OBJECT_HISTORY                                    
          WHERE  USER_ID=UPPER($1)                                    
          ORDER BY DATE_TIME DESC) H2                            
  WHERE  ROWNUM &lt;= $2
    AND  H1.AUTOID = H2.AUTOID)">
<method>
  <ejb-name>NoUserHistoryEntry</ejb-name>
  <method-name>findOldest</method-name>
  <method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
  </method-params>
</method>
</finder-method>
After deploying in 9.0.3 the following information is added to the orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
  SELECT H1.AUTOID
  FROM   NO_SYS_USER_OBJECT_HISTORY H1,
         (SELECT AUTOID                                     
          FROM   NO_SYS_USER_OBJECT_HISTORY
          WHERE  USER_ID=$1   
          ORDER BY DATE_TIME DESC) H2
  WHERE  ROWNUM &lt;= $2
    AND  H1.AUTOID = H2.AUTOID)">
<!-- Generated SQL:
  "select NO_SYS_USER_OBJECT_HISTORY.autoid
   from   NO_SYS_USER_OBJECT_HISTORY
   where  NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
     and  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
          SELECT H1.AUTOID                             
          FROM   NO_SYS_USER_OBJECT_HISTORY H1,
                 (SELECT AUTOID
                  FROM   NO_SYS_USER_OBJECT_HISTORY
                  WHERE  USER_ID=?
                  ORDER BY DATE_TIME DESC) H2
          WHERE ROWNUM <= ?
            AND H1.AUTOID = H2.AUTOID) -->
<method>
  <ejb-name>NoUserHistoryEntry</ejb-name>
  <method-name>findOldest</method-name>
  <method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
  </method-params>
</method>
</finder-method>
After deploying in 10.1.2.0.2 the following information is added to the
orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
  SELECT H1.AUTOID
  FROM   NO_SYS_USER_OBJECT_HISTORY H1,
         (SELECT AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY
          WHERE  USER_ID=UPPER($1)
          ORDER BY DATE_TIME DESC) H2
  WHERE  ROWNUM &lt;= $2
    AND  H1.AUTOID = H2.AUTOID)">
<!-- Generated SQL (pk only):
  "select H1.autoid
   from   NO_SYS_USER_OBJECT_HISTORY
   where  NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
     and  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
          SELECT H1.AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY H1,
                 (SELECT AUTOID
                  FROM   NO_SYS_USER_OBJECT_HISTORY
                  WHERE  USER_ID=UPPER(?)
                  ORDER BY DATE_TIME DESC) H2
          WHERE  ROWNUM <= ?
            AND  H1.AUTOID = H2.AUTOID) -->
<!-- Generated SQL (all columns):
  "select H1.autoid, H1.USER_ID, H1.OBJECT_CLASS_ID,
             H1.DATE_TIME, H1.COMMENT_TEXT, H1.ACTION,
             H1.ACTION_DATA, H1.SITE_DESCRIPTION
   from   NO_SYS_USER_OBJECT_HISTORY
   where  NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
     and  NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
          SELECT H1.AUTOID
          FROM   NO_SYS_USER_OBJECT_HISTORY H1,
                 (SELECT AUTOID
                  FROM   NO_SYS_USER_OBJECT_HISTORY
                  WHERE  USER_ID=UPPER(?)
                  ORDER BY DATE_TIME DESC) H2
          WHERE  ROWNUM <= ?
            AND  H1.AUTOID = H2.AUTOID) -->
<method>
  <ejb-name>NoUserHistoryEntry</ejb-name>
  <method-name>findOldest</method-name>
  <method-params>
   <method-param>java.lang.String</method-param>
   <method-param>java.lang.Integer</method-param>
  </method-params>
</method>
</finder-method>
The problem with the 10.1.2.0.2 generated finders is that it is prepending H1 when
it should be NO_SYS_USER_OBJECT_HISTORY which results in the following error:
Exception in thread "main" com.cdtelecom.vygroe.configuration.ConfigurationException:
com.evermind.server.rmi.OrionRemoteException:
Transaction was rolled back: Database error: java.sql.SQLException:
ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
; nested exception is:
        java.sql.SQLException: ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
        at com.cdtelecom.vygroe.configuration.ConfigurationSession.internalRecordAction(ConfigurationSession.java:869)
        at com.cdtelecom.vygroe.configuration.ConfigurationSession.recordAction(ConfigurationSession.java:401)
        at com.cdtelecom.vygroe.configuration.Configuration.recordActionSaveOrder(Configuration.java:886)
        at com.cdtelecom.vygroe.configuration.Configuration.getOrder(Configuration.java:239)
        at test10g.main(test10g.java:47)
I tried to manually edit the file but when I shutdown and restart oc4j it regenerates the file again.

Answer 1

Jingzhi -- If you define the correct EJB-QL you should get the correct SQL generated for the finder. If that's not happening can you verify it against the OC4J v903 production release and see if it is still happening. I don't know if this helps with the JDeveloper problem specifically but if you don't need to create your own finders then that I hope should help.
Thanks -- Jeff