In a new Application, the ApplicationResources_en.properties file is not having the constraint messages created

Question

Hi Everyone:
          We are using JDev 11.1.2 and JHeadstart 11.1.2.  We have been having a multitude of problems when running applications through the migrator (and we have now been told by an Oracle consultant that the migrator is problematic), so we are trying to re-write things from scratch to bring them over from 11.1.1.4 to 11.1.2.
          I have been working on a simple application from scratch and discovered that the messages for constraints on the entities that I am using are not showing up in the ApplicationResources_en.properties.file.  We noticed a similar thing with converting an application using the migrator and that post is found here - java.lang.NullPointerException ADF_FACES-60097 message ***WITH SOLUTION*** -. 
          However, I didn't get a single reply to that thread. 
          I initially thought it was a migration issue, but this application is from scratch.  Whenever I tried to input an invalid value into a page column, the following exception would be received.
"java.lang.NullPointerException  ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #"
           This Null Pointer turned out to be the missing message from the ApplicationResources_en.properties file.  In the new application I just wrote, I had to manually edit to add the following lines to the ApplicationResources_en.properties file and the application no longer gives me the error if I input an invalid value.
VALIDATE_FEE_CATEGORY_3=Feecategory with this FeeCategory does not exist
VALIDATE_ACADEMIC_TERM36=Academicterm with this EffectiveTermStart does not exist
VALIDATE_ACADEMIC_TERM36_CASDEL=Cannot delete Academicterm while dependent Specialexchange exists
VALIDATE_ACADEMIC_TERM37=Academicterm with this EffectiveTermEnd does not exist
VALIDATE_ACADEMIC_TERM37_CASDEL=Cannot delete Academicterm while dependent Specialexchange exists
VALIDATE_CURRENCY23=Currency with this Currency does not exist
VALIDATE_CURRENCY23_CASDEL=Cannot delete Currency while dependent Specialexchange exists
VALIDATE_FEE_CATEGORY_3=Feecategory with this FeeCategory does not exist
VALIDATE_FEE_CATEGORY_3_CASDEL=Cannot delete Feecategory while dependent Specialexchange exists
These constraints are found in the Entities .xml files  as shown below.  We are using a re-usable business components .jar file to import them in.
  <Key
    Name="UniqueFeeCategory"
    PrimaryKey="true">
    <DesignTime>
      <Attr Name="_DBObjectName" Value="UNIQUE_FEE_CATEGORY"/>
    </DesignTime>
    <AttrArray Name="Attributes">
      <Item
        Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.FeeCategory"/>
      <Item Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.Currency"/>
      <Item
        Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.EffectiveTermEnd"/>
    </AttrArray>
  </Key>
  <Key
    Name="ValidateAcademicTerm36">
    <DesignTime>
      <Attr Name="_referencedKey" Value="UNIQUE_ACADTERM_CODE"/>
      <Attr Name="_isForeign" Value="true"/>
      <Attr Name="_DBObjectName" Value="VALIDATE_ACADEMIC_TERM36"/>
    </DesignTime>
    <AttrArray Name="Attributes">
      <Item
        Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.EffectiveTermStart"/>
    </AttrArray>
  </Key>
  <Key
    Name="ValidateAcademicTerm37">
    <DesignTime>
      <Attr Name="_referencedKey" Value="UNIQUE_ACADTERM_CODE"/>
      <Attr Name="_isForeign" Value="true"/>
      <Attr Name="_DBObjectName" Value="VALIDATE_ACADEMIC_TERM37"/>
    </DesignTime>
    <AttrArray Name="Attributes">
      <Item
        Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.EffectiveTermEnd"/>
    </AttrArray>
  </Key>
  <Key
    Name="ValidateCurrency23">
    <DesignTime>
      <Attr Name="_referencedKey" Value="UNIQUE_CURRENCY_CODE"/>
      <Attr Name="_isForeign" Value="true"/>
      <Attr Name="_DBObjectName" Value="VALIDATE_CURRENCY23"/>
    </DesignTime>
    <AttrArray Name="Attributes">
      <Item Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.Currency"/>
    </AttrArray>
  </Key>
  <Key
    Name="ValidateFeeCategory3">
    <DesignTime>
      <Attr Name="_referencedKey" Value="UNIQUE_FEECAT_CODE"/>
      <Attr Name="_isForeign" Value="true"/>
      <Attr Name="_DBObjectName" Value="VALIDATE_FEE_CATEGORY_3"/>
    </DesignTime>
    <AttrArray Name="Attributes">
      <Item
        Value="its.sis.uwbm.AREdit.entityobjects.Specialexchange.FeeCategory"/>
    </AttrArray>
    Is this a known bug (I have searched and havent found it) and is there anything that I can do about it without having to manually add the messages?
Mary
UofW

Answer 1

Hi Everyone:
           I have done some further testing.  We are using a re-usable Business Components .jar file to access our entities.  We import the .jar file into the project and create the ViewObjects and ViewLinks from that .jar file.
            It APPEARS that a test case using the HRSchema and using the Entities & Associates generates the constraint error messages, but when I use the .jar file of re-usable business components imported into the project, those constraint error messages are not created in the ApplicationResources_en.properties file.  I have created two testcases as well as the re-usable .jar file that I can send to you to show what I mean. 
            This behaviour seems to have shown up in 11.1.2 as there was no problem before this.
             Please let me know where you'd like me to upload the testcases.
             Thank you.
Mary
UofW