Hi, we encounter the same phenomenon with weblogic 8.1 sp1. With a hot deploy the OJB responds like normal but with null or empty result. This could be fixed by restarting weblogic. But this is very time expensive.
cheers, Ralf Armin Waibel <[EMAIL PROTECTED]> schrieb am 28.10.2003 10:11:05: > Hi, > > 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. > > > hmm, maybe it's a classpath problem. Are all libraries used > by OJB in the same "classpath path" as ojb.jar? > > regards, > Armin > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
