JBO-25001 Business Components Error

Question

Hi to all,
I am experiencing some VERY STRANGE behaviour in JDeveloper ADFBC.
I am using Jdeveloper 10.1.3.1.0.3984 to build an application using ADF and Business Components.
I have four tables, JAAS_USERS, JAAS_ROLES, JAAS_REALMS and JAAS_MAPPINGS. The only associations are that JAAS_MAPPINGS have JAAS_USERS_ID, JAAS_ROLES_ID and JAAS_REALMS_ID.
I created my entities (package: datamodel.entities) and i have specified that JAAS_USERS entity use a DBSequence for USER_ID. Please note that i included control hints for every entity.
Then i created my first view (package: datamodel.views), called JaasUsers
that simply selects all attributes of the entity.
I then created an application module (package: datamodel) and i included the view. When i test the application module everything is fine!
I created a jsf and i dragged the view as a table -> read only table and everything was fine.
I then run the page and again everything is fine.
I then realized that i needed to change the control hint for some columns. Instead of changing the control hint of the entity (JAAS_USERS) i changed the object view (JAAS_USERS).
From this point and on NOTHING WORKS!!!!!!!!!!!!!!!!!!!
Here is the error message:
(oracle.jbo.common.ampool.ApplicationPoolException) JBO-30003: The application pool (.110255D7D2E) failed to checkout an application module due to the following exception:
----- LEVEL 1: DETAIL 0 -----
(oracle.jbo.JboException) JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught: oracle.jbo.NameClashException, msg=JBO-25001: Name JaasMappings of object type Attribute already exists
----- LEVEL 2: DETAIL 0 -----
(oracle.jbo.JboException) JBO-29000: Unexpected exception caught: oracle.jbo.NameClashException, msg=JBO-25001: Name JaasMappings of object type Attribute already exists
----- LEVEL 3: DETAIL 0 -----
(oracle.jbo.NameClashException) JBO-25001: Name JaasMappings of object type Attribute already exists
Please help me becuase i don;t know hot to fix this BUG!

Answer 1

Hey ppl , I got an exact similar error when trying to migrate from a 10g R2 to R3 version in Jdeveloper. Quite irritating this error,
Well i guess most would have figured this out , but for benefit of all , theres a slightly easier way to tackle this ( JDEV Release 3)
in the Application Navigator view Double click your Association , within association properties un-check your expose accessor checkboxes for both the source and destination .Apply changes and do a compile. If it is required , jdev will throw an error. Simply follow the process again and check the Expose accessor boxes again. This solves the problem most of the time.
Main advantage being , you can avoid the tedious task of manually changing the xml information on Notepad or the kind.
Hope this helps....