More explaination needed about EJB issues published

Question

when I read the part of "EJB issues" of the page
http://otn.oracle.com/products/jdev/htdocs/readme_903Preview.html#viadcm
I have several questions:
first one:
Invalid column name when the primary key in one table is different from the foreign key name. (2514361)
does that mean that the foreign key in table 2 should have the same name as the primary key in the table 1?
second one:
Null pointer exception when an EJBSelect() method is called. (2428884)
does that mean you can not call EJBSelect in your code?
third:
Pure MDB cannot run in an embedded OC4J server but can be deployed to a standalone OC4J server.
"can be deployed" means MDB can run on standalone OC4J, right?
last one:
If a CMR exists between two CMP entity beans with the same Primary Key names than the association table generated is incorrect - Workaround is to make sure that primary key names don't match
All my entity beans use uniqueId as the primary key. In the association table we are using other name as the foreign key. can I use orion-ejb-jar.xml to explicit mapping to overcome this problem?

Answer 1

Hi Han -
I had a further look through the bug database for the numbers you specified:
Invalid column name when the primary key in one table is different from the foreign key name. (2514361) :
- the base OC4J bug for this has been fixed in the 904 code line and will be in 904. If this is causing you problems with 903, then I recommend you call Oracle support and log a TAR. They may be able to have the base bug for this backported to 903 as a patch.
You may also want to try deploying this using the non-association table operation mode. You can start OC4J with a system property of "-DassociateUsingThirdTable=false" which will force the container to use pk/fk columns in the direct tables for 1-M relationships rather than the association table. I don't know if this will resolve the specific problem you have, but it is worth trying.
Null pointer exception when an EJBSelect() method is called. (2428884) : the base OC4J bug for this was fixed in the production release.
If a CMR exists between two CMP entity beans with the same Primary Key names than the association table generated is incorrect - try using the non association table operation mode.
Pure MDB cannot run in an embedded OC4J server but can be deployed to a standalone OC4J server. - I pointed out the area of the JDeveloper documentation where this problem and solution is discussed in an earlier post in this thread.
Hope that helps you somewhat. You mentioned that you were still having a problem - can you post a new thread which has more details of the nature of the problem, stack traces, etc. so we can look at that separately.
cheers
-steve-