ALL, Thnx very much for all your replies. Its very nice to get so many replies. Thnx once again guys. I tried to just set the start up parameter to start in development mode. Then I used ANT and automatically the new class files seem to have taken effect. I understood the fact that since polling directory service is disabled in production mode, it is not possible for a server running in production mode to keep looking into the ejb directories at regular intervals for changes and it makes perfect sense as the robustness of the production server would be lost due to continous polling.
Once again, thnx very much to all of you. Very enthusiastic replies. Srinivas. -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Ashwani Kalra Sent: Thursday, August 08, 2002 5:38 PM To: [EMAIL PROTECTED] Subject: Re: Hot Deploy Both options are ok. Console can be used by anyone who does not like to work with ANT. One can write batch file(if on windows) or shell script(on unix) also which will do the equivalent of ANT(will work on both unix and windows). There is not hard and fast rule. But you have to rerun your client(look up ejb again ) for any changes to reflect. Am I right ? or the next fn call on the remote or home will take care of that (I have not tried this). Comments ?? -Ashwani ----- Original Message ----- From: "Marco Mistroni" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 08, 2002 5:19 PM Subject: Re: Hot Deploy >> But from your reply, i understood that u want to do everything automatically, >> like any other ANT tasks. so, you should choose the option 2, but i am >> not sure if WLS will allows you to replace one jar file meanwhile is >> running. >I am a bit confused by reading these posts - the term "hot deploy" >essentially means this right? - the ability to replace a jar with a newer >copy and the app server recognising this, undeploying the app and >redeploying it again? Well, according to the WLS docs that i've read (pls correct if i am wrong) hot deploy means simply that u can deploy apps/ejbs while WLS is running. So, it means also that you can REdeploy newer versions of applications, because the process 'deploying apps while WLS is running' is done anyway. that is what i mean. Pls anyone correct me if i got it wrong. As far as i read, best way to REdeploy newer versions of applications is to go thru the console, undeploy the old and redeploy the new ones, because you leave all the process to WLS (it will take care of putting in teh location etc...). Some guys said that u can also avoid to go thru the Console, and just place applications in the application directory. As of myself, i have never tried, so i can't say anything about that. that was the issue br marco ========================= To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
