Upgraded Entity BindingStyle="Oracle" New Entity BindingStyle="OracleName"

Question

Thanks to Sacha see thread
ADF BC: Exception when using an association accessor  in polymorphic EOs
You'll notice that the read-only parameter BindingStyle is set to "OracleName" when creating a new entity with JDev 10.1.3.
Upgraded Entity have following setup: BindingStyle="Oracle"
There seems to be problem when using associations between entities with different BindingStyle.
I got following exception on a call to get associated entity
java.lang.ClassCastException: oracle.jbo.domain.Number
     at oracle.jbo.server.RowFilterKey.<init>(RowFilterKey.java:47)
     at oracle.jbo.server.ViewObjectImpl.buildRowFilter(ViewObjectImpl.java:4527)
     at oracle.jbo.server.ViewRowSetImpl.getRowFilter(ViewRowSetImpl.java:419)
     at oracle.jbo.server.ViewRowSetImpl.getRowFilter(ViewRowSetImpl.java:370)
     at oracle.jbo.server.ViewRowSetImpl.ensureStorage(ViewRowSetImpl.java:4632)
     at oracle.jbo.server.EntityRowSetImpl.<init>(EntityRowSetImpl.java:80)
     at oracle.jbo.server.EntityImpl.createAssociationAccessorRS(EntityImpl.java:7610)
     at oracle.jbo.server.AssociationDefImpl.get(AssociationDefImpl.java:329)
     at oracle.jbo.server.AssociationDefImpl.get(AssociationDefImpl.java:274)
     at oracle.jbo.server.EntityImpl.getAttributeInternal(EntityImpl.java:2144)
     at com.trivadis.adf.inheritance.model.eo.EmployeeImpl.getDepartment(EmployeeImpl.java:186)
     at com.trivadis.adf.inheritance.model.eo.EmployeeImpl.getSal(EmployeeImpl.java:103)
     at com.trivadis.adf.inheritance.model.eo.EmployeeImpl.getAttrInvokeAccessor(EmployeeImpl.java:141)
     at com.trivadis.adf.inheritance.model.eo.ManagerImpl.getAttrInvokeAccessor(ManagerImpl.java:76)
     at oracle.jbo.server.EntityImpl.getAttribute(EntityImpl.java:784)Can I change that parameter outside JDev to check if that solves my problem?
Thanks
Fred

Answer 1

The development team has fixed the bug in the JDeveloper 11g code line. The bug was incorrectly marked as being related to a non-production version of JDeveloper so it was not visible before through Metalink -- where only bugs on production products are relevant to external customers. It should be visible within 24 hours on metalink.
You can request a 10.1.3.1 backport of the bug by opening a service request on metalink, citing that bug number.
As a 24-hour-early preview, the bug mentions the workaround is manually modifying the XML Files to insure that the two entities on either side of an association have the same binding style.