Your existing directory structure should remain intact, as that is where Geronimo will be loading all your classes from. During redeployment, the deployer tool will delete the serialized config directory in the repository for your application, and then re-create it using the information form your in-place directory.
The deployer does create all those "ser" and "info" files from your deployment descriptors during the deployment process. Therefore, if you change one of your deployment descriptors, you need to redeploy your app. However, if you just swap in new code into your in-place directory, Geronimo will pick it up without having to redeploy. Thanks, Aman "Spotts, Joel \(ISS Atlanta\)" <[EMAIL PROTECTED]> wrote on 03-19-2007 02:03:26 PM: > My understanding is that even if I have an application deployed > in-place, if I redeploy it, the deployer will delete the current > directory structure, so I would need to copy the current directory > structure in any event. > > What does the deployer do? Does it simply create the config.ser, > config.info, etc files? > > Thanks, > > Yoel Spotts > > -----Original Message----- > From: Aman Nanner/MxI Technologies [mailto:[EMAIL PROTECTED] > Sent: Friday, March 16, 2007 4:41 PM > To: user@geronimo.apache.org > Subject: Re: redeploy > > If you are deploying in-place, there is no need to copy the EAR. You > should be able to just modify the application.xml, add the new web app > to > the EAR structure, and run the deployer tool to redeploy the EAR file. > > If you are not deploying in-place, then I'm not sure you can avoid > copying > out the EAR. Someone else might have more knowledge in this area. > > "Spotts, Joel \(ISS Atlanta\)" <[EMAIL PROTECTED]> wrote on 03-16-2007 > 04:26:37 PM: > > > I am looking for the easiest way to redeploy an EAR after adding a > > web application. The EAR has other webapps which added or modified > > some files, so I need the current EAR directory structure to remain > > as is. The only way I can see now is as follows: > > A) copy the entire ear directory to a temp staging area. > > B) modify application.xml > > C) add the new webapp > > D) run the deployer tool to redeploy the ear > > I would like to find a solution which does not require copying the > > current ear structure to another location, That seems wasteful. Is > > there an easier way? > > Thanks, > > Yoel Spotts > > ________________________________________________________________________ > __________ > * This message is intended only for the use of the individual or entity > to which it is addressed, and may contain information that is > privileged, confidential and exempt from disclosure under applicable > law. Unless you are the addressee (or authorized to receive for the > addressee), you may not use, copy or disclose the message or any > information contained in the message. If you have received this message > in error, please advise the sender by reply e-mail , and delete the > message, or call (collect) 001 613 747 4698. * > > > __________________________________________________________________________________ * This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *
