That is something that I have not yet done, so I don't know how well that works...
"Spotts, Joel \(ISS Atlanta\)" <[EMAIL PROTECTED]> wrote on 03-20-2007 02:42:56 PM: > Sorry -- I should have specified, I am trying to deploy the jms > connector as a server wide connector -- not within an ear. Have you been > able to deploy a server wide connector in place? > > -----Original Message----- > From: Aman Nanner/MxI Technologies [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 20, 2007 2:39 PM > To: user@geronimo.apache.org > Subject: RE: redeploy > > Yes, I don't believe in-place deployment has anything to do with your > issue > as I've successfully deployed a JMS connector in my EAR with in-place > deployment. > > "Spotts, Joel \(ISS Atlanta\)" <[EMAIL PROTECTED]> wrote on 03-20-2007 > 02:36:20 PM: > > > Another question -- should in be possible to deploy jms connectors > > inplace as well? I am having trouble now -- a ClassNotFoundException > on > > a activemq class. > > > > Thanks, > > > > Yoel > > -----Original Message----- > > From: Aman Nanner/MxI Technologies [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 20, 2007 10:16 AM > > To: user@geronimo.apache.org > > Subject: RE: redeploy > > > > This is probably related to this JIRA issue: > > > > https://issues.apache.org/jira/browse/GERONIMO-2818 > > > > > > "Spotts, Joel \(ISS Atlanta\)" <[EMAIL PROTECTED]> wrote on > 03-20-2007 > > 09:58:41 AM: > > > > > Thanks so much for your response. > > > > > > I am trying to go that route, but am encoutering a different issue > > now. > > > > > > I have an EJB defined in the EAR. The actual EJB remote interface is > > > located in a jar which is specified in the manifest of the EJB > module > > > inside the EAR. Without the --inPlace option, it all works fine, the > > > classloader finds the EJB remote interface. However, when I try the > > > --inPlace, the deployer can't seem to find the EJB remote interface > > and > > > the deployer throws an exception trying to deploy the EJB in the > EAR. > > It > > > seems like there is some confusion in the classloaders when using > > > --inPlace. Any thoughts? > > > > > > Thanks! > > > > > > Yoel Spotts > > > > > > -----Original Message----- > > > From: Aman Nanner/MxI Technologies [mailto:[EMAIL PROTECTED] > > > Sent: Monday, March 19, 2007 2:20 PM > > > To: user@geronimo.apache.org > > > Subject: RE: redeploy > > > > > > 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. * > > > > > > > > > > > > > > ________________________________________________________________________ > > __________ > > * 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. * > > > __________________________________________________________________________________ * 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. *
