I have found a solution to this problem.
You have to separate those database entity classes from application classes. Jar your entity classes and put inside system classpath. Remove those entity classes with application logic classes.
The reason could be everytime you redeploy the whole thing in BEA, it would use a different new class loader. After that, the OJB broker could not find the class definition from original class loader and return you a null.
Alen Tan wrote:
Hi,
I have this problem with OJB in weblogic. I have already set up the OJB to run in weblogic 7.1. There is a startup class to load the OJB up and bind to the JNDI tree.
I store my application in the domain/applications directory. Everytime I changed my source code, I will touch the REDEPLOY file to redeploy the whole EJB application.
There is a problem here. Whenever I redeploy my application in weblogic using the above method, the broker will return null record to me. Although the query is valid and the record is certainly inside the database. It just return me with a null record and without any error. But, if I restart the weblogic, everything would be ok.
So, I wonder what has gone wrong. Anyone got any idea? Appreciate the help very much, because I have been stuck with this problem for quite a while.
Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
