dendenners
Programmer
Hi there,
I'm developing ejb's locally, and dropping them onto a remote web server. At the moment I'm debugging a bean, so I'm adding new log messages to it. However, when I view the console output from weblogic, it seems as if weblogic is still reading the very first instance of the bean I deployed, even though it has been long overwritten. Do I have to do something more to weblogic to get it to re-deploy an ejb than just overwrite the older jar and restart WebLogic?
Thanks
I'm developing ejb's locally, and dropping them onto a remote web server. At the moment I'm debugging a bean, so I'm adding new log messages to it. However, when I view the console output from weblogic, it seems as if weblogic is still reading the very first instance of the bean I deployed, even though it has been long overwritten. Do I have to do something more to weblogic to get it to re-deploy an ejb than just overwrite the older jar and restart WebLogic?
Thanks