EJB3 - JPA 2.0 issues and answers
Starting with EJB3 may be quite confusing in the beginning but once you get into it you enjoy and recalls the ejb 2.x issues and probelms. Some of the issues faced by me are as follows: 1. Since there is no ejb-jar xml it became a challege to use it with portal factory. 2. jndi lookup was initially giving the trouble both local as well as the remote calls. 3. Anotation is new and to use with problem statement. Few tips: 1. In case if something is based on ejb-jar .xml try to put some framework in between client and buisness logic. 2. for Local ejb call: the jndi strig starts with ejblocal:<full name of ejb method with packages> 3. For Remote calls: Use "corbaloc:<>" and see that client jar do not contains the source file else you will end with classcast exception and incompitable filesexception. 4. You may need to use dumpNames.bat file of WAS for botsrap address conflict and jni string name to check. JPA2.0 Its won