RE: Deployment xml files in ear file? If so, where?
Orion will copy the deployment files in your EAR the first time it deploys it. Thereafter it will use the files in the deployment directory. It will never copy a file if it exists in the deployment directory. Therefore you are free to modify those to customise your deployment. (The only exception here seems to be web.xml which always gets overwritten by web.xml from a WAR but this is in Bugzilla and I think has been fixed in the latest JAR) -mike > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Weissman > Sent: Thursday, March 29, 2001 4:58 AM > To: Orion-Interest > Subject: Re: Deployment xml files in ear file? If so, where? > > > Maybe I misunderstand, I thought orion will create orion-*.xml in the > deployment area, if not supplied in the ear. If placed in the ear, > Orion would only copy it to the application-deployment area. I did not > think a person edited in the application-deployment area. > mike > > Hani Suleiman wrote: > > > > No, orion is doing the right thing by not clearing > application-deployment. > > People keep forgetting that deployment!=assembly, the deployer should be > > free to override values from the assembly, Orion clobbering > > application-deployments would effectively make the deployer's job > > impossible! > > > > deployment = orion-*.xml (application, web, ejb-jar, principals) > > assembly = *.xml (application, web, ejb-jar > > > > Hani > > > > >From: Mike Weissman <[EMAIL PROTECTED]> > > >Reply-To: Orion-Interest <[EMAIL PROTECTED]> > > >To: Orion-Interest <[EMAIL PROTECTED]> > > >Subject: Re: Deployment xml files in ear file? If so, where? > > >Date: Wed, 28 Mar 2001 08:21:08 -0700 > > > > > >It seems that orion auto-deployment should clean both the applications > > >and application-deployment areas. In development especially when you > > >make many changes, I have been bit a few times by leftovers when the > > >areas were not cleaned. > > >mike > > > > > >Yves Bossel wrote: > > > > > > > > > Note though that if the application has already been > > > > > deployed, then these > > > > > files won't be copied over the existing ones. They're only > > > > > used in the case > > > > > of a 'fresh install'. > > > > > > > > When you make changes to your descriptors and/or any class > in your app, > > > > (having packed everything in the ear), you should delete > the directory > > > > /application-deployments/ > > > > Then shutdown and restart Orion. Shutdown is important (not > hot restart) > > > > because any class that changed, specifically the EJBs tend > to remain in > > > > memory. > > > > > > > > Yves > > > > > >-- > > >## > > >Michael Weissman e-mail: [EMAIL PROTECTED] > > >Clarent Corporation 303-734-5003 Fax 303-734-4244 > > >1221 W. Mineral Ave. Littleton, Co 80120 > > >In the land of the dark, the ship of the sun is > > >drawn by the grateful dead -- Egyptian Book of the Dead > > >## > > > > > > > _ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > -- > ## > Michael Weissman e-mail: [EMAIL PROTECTED] > Clarent Corporation 303-734-5003 Fax 303-734-4244 > 1221 W. Mineral Ave. Littleton, Co 80120 > In the land of the dark, the ship of the sun is > drawn by the grateful dead -- Egyptian Book of the Dead > ## > >
RE: Deployment xml files in ear file? If so, where?
> Maybe I misunderstand, I thought orion will create orion-*.xml in the > deployment area, if not supplied in the ear. If placed in the ear, > Orion would only copy it to the application-deployment area. > I did not > think a person edited in the application-deployment area. > mike >From observations: Be /.ear the path to my application's EAR. 1. Orion "opens" the ear in // directory (if you have orion-*.ejb files they get "opened" there too) 2. Orion creates /application-deployments// directory 3. Orion copies all *.xml files into /application-deployments// and creates there unexisting orion-*.xml if needed 4. Orion will compile JSP into the necessary persitence directories under /application-deployments// To answer the question, sometimes you need to include your own (e.j.) orion-ejb-jar.xml which specifies SQL queries for finder methods (for example) - in this case we do not let orion generate the orion-ejb-jar.xml. Another example is that that same file defines the data-source for each method of your ejb, etc. Yves
Re: Deployment xml files in ear file? If so, where?
Maybe I misunderstand, I thought orion will create orion-*.xml in the deployment area, if not supplied in the ear. If placed in the ear, Orion would only copy it to the application-deployment area. I did not think a person edited in the application-deployment area. mike Hani Suleiman wrote: > > No, orion is doing the right thing by not clearing application-deployment. > People keep forgetting that deployment!=assembly, the deployer should be > free to override values from the assembly, Orion clobbering > application-deployments would effectively make the deployer's job > impossible! > > deployment = orion-*.xml (application, web, ejb-jar, principals) > assembly = *.xml (application, web, ejb-jar > > Hani > > >From: Mike Weissman <[EMAIL PROTECTED]> > >Reply-To: Orion-Interest <[EMAIL PROTECTED]> > >To: Orion-Interest <[EMAIL PROTECTED]> > >Subject: Re: Deployment xml files in ear file? If so, where? > >Date: Wed, 28 Mar 2001 08:21:08 -0700 > > > >It seems that orion auto-deployment should clean both the applications > >and application-deployment areas. In development especially when you > >make many changes, I have been bit a few times by leftovers when the > >areas were not cleaned. > >mike > > > >Yves Bossel wrote: > > > > > > > Note though that if the application has already been > > > > deployed, then these > > > > files won't be copied over the existing ones. They're only > > > > used in the case > > > > of a 'fresh install'. > > > > > > When you make changes to your descriptors and/or any class in your app, > > > (having packed everything in the ear), you should delete the directory > > > /application-deployments/ > > > Then shutdown and restart Orion. Shutdown is important (not hot restart) > > > because any class that changed, specifically the EJBs tend to remain in > > > memory. > > > > > > Yves > > > >-- > >## > >Michael Weissman e-mail: [EMAIL PROTECTED] > >Clarent Corporation 303-734-5003 Fax 303-734-4244 > >1221 W. Mineral Ave. Littleton, Co 80120 > >In the land of the dark, the ship of the sun is > >drawn by the grateful dead -- Egyptian Book of the Dead > >## > > > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com -- ## Michael Weissman e-mail: [EMAIL PROTECTED] Clarent Corporation 303-734-5003 Fax 303-734-4244 1221 W. Mineral Ave. Littleton, Co 80120 In the land of the dark, the ship of the sun is drawn by the grateful dead -- Egyptian Book of the Dead ##
Re: Deployment xml files in ear file? If so, where?
No, orion is doing the right thing by not clearing application-deployment. People keep forgetting that deployment!=assembly, the deployer should be free to override values from the assembly, Orion clobbering application-deployments would effectively make the deployer's job impossible! deployment = orion-*.xml (application, web, ejb-jar, principals) assembly = *.xml (application, web, ejb-jar Hani >From: Mike Weissman <[EMAIL PROTECTED]> >Reply-To: Orion-Interest <[EMAIL PROTECTED]> >To: Orion-Interest <[EMAIL PROTECTED]> >Subject: Re: Deployment xml files in ear file? If so, where? >Date: Wed, 28 Mar 2001 08:21:08 -0700 > >It seems that orion auto-deployment should clean both the applications >and application-deployment areas. In development especially when you >make many changes, I have been bit a few times by leftovers when the >areas were not cleaned. >mike > >Yves Bossel wrote: > > > > > Note though that if the application has already been > > > deployed, then these > > > files won't be copied over the existing ones. They're only > > > used in the case > > > of a 'fresh install'. > > > > When you make changes to your descriptors and/or any class in your app, > > (having packed everything in the ear), you should delete the directory > > /application-deployments/ > > Then shutdown and restart Orion. Shutdown is important (not hot restart) > > because any class that changed, specifically the EJBs tend to remain in > > memory. > > > > Yves > >-- >## >Michael Weissman e-mail: [EMAIL PROTECTED] >Clarent Corporation 303-734-5003 Fax 303-734-4244 >1221 W. Mineral Ave. Littleton, Co 80120 >In the land of the dark, the ship of the sun is >drawn by the grateful dead -- Egyptian Book of the Dead >## > _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Deployment xml files in ear file? If so, where?
It seems that orion auto-deployment should clean both the applications and application-deployment areas. In development especially when you make many changes, I have been bit a few times by leftovers when the areas were not cleaned. mike Yves Bossel wrote: > > > Note though that if the application has already been > > deployed, then these > > files won't be copied over the existing ones. They're only > > used in the case > > of a 'fresh install'. > > When you make changes to your descriptors and/or any class in your app, > (having packed everything in the ear), you should delete the directory > /application-deployments/ > Then shutdown and restart Orion. Shutdown is important (not hot restart) > because any class that changed, specifically the EJBs tend to remain in > memory. > > Yves -- ## Michael Weissman e-mail: [EMAIL PROTECTED] Clarent Corporation 303-734-5003 Fax 303-734-4244 1221 W. Mineral Ave. Littleton, Co 80120 In the land of the dark, the ship of the sun is drawn by the grateful dead -- Egyptian Book of the Dead ##
RE: Deployment xml files in ear file? If so, where?
> Note though that if the application has already been > deployed, then these > files won't be copied over the existing ones. They're only > used in the case > of a 'fresh install'. When you make changes to your descriptors and/or any class in your app, (having packed everything in the ear), you should delete the directory /application-deployments/ Then shutdown and restart Orion. Shutdown is important (not hot restart) because any class that changed, specifically the EJBs tend to remain in memory. Yves
RE: Deployment xml files in ear file? If so, where?
I believe this is fixed in the forthcoming 1.4.8 (that mythical beast...) so that orion-ejb-jar.xml will go in /META-INF along with all its friends. Cheers, Dan/tastapod At 10:39 27/03/2001 +1000, you wrote: >This is true EXCEPT for orion-ejb-jar.xml which goes in /orion not /META-INF >in your EJB.jar (no idea why this one is different ;)) > >-mike > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Hani Suleiman > > Sent: Tuesday, March 27, 2001 9:36 AM > > To: Orion-Interest > > Subject: Re: Deployment xml files in ear file? If so, where? > > > > > > You can place your orion-*.xml files alongside their *.xml counterparts. > > (eg, principals.xml and orion-application.xml alongside application.xml). > > Note though that if the application has already been deployed, then these > > files won't be copied over the existing ones. They're only used > > in the case > > of a 'fresh install'. > > > > > > >From: "Rian Schmidt" <[EMAIL PROTECTED]> > > >Reply-To: Orion-Interest <[EMAIL PROTECTED]> > > >To: Orion-Interest <[EMAIL PROTECTED]> > > >Subject: Deployment xml files in ear file? If so, where? > > >Date: Mon, 26 Mar 2001 14:47:50 -0800 > > > > > >Hi all, > > > > > >Firstly, we're having great luck with our adventures with Orion. Most > > >everything works as advertised, and the performance is great-- > > particularly > > >the CMP EJB stuff. Just thought I'd spew a little positivity. > > > > > >Is there some way to include the application-deployments XML > > files with an > > >application? By that I mean, fer instance, we've made all kinds of > > >modifications to orion-ejb-jar.xml to deal with our OR relationships, the > > >legacy database name mappings, etc. orion-application.xml has a bunch of > > >custom settings too. Were either of those to get wiped by an overzealous > > >Orion, we'd be... sad. So, we're gonna back them up, but... > > > > > >Do we need to manually make those changes after deploying the > > application > > >on > > >another machine? That seems a little goofy. I'd hate to have > > to say to a > > >customer "OK, start it up, and then stop it, open this file up and > > >everywhere it says requestId, well, change that to request_id, blah blah, > > >and then restart it." > > > > > >Thanks, > > >Rian > > > > > >-- > > >Rian Schmidt > > >[EMAIL PROTECTED] > > > > > > > > > > > > > _ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > > > -- Dan North VP Development - Cadrion Software Ltd - +44 (0)20 7440 9550 CONFIDENTIALITY This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium
RE: Deployment xml files in ear file? If so, where?
This is true EXCEPT for orion-ejb-jar.xml which goes in /orion not /META-INF in your EJB.jar (no idea why this one is different ;)) -mike > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Hani Suleiman > Sent: Tuesday, March 27, 2001 9:36 AM > To: Orion-Interest > Subject: Re: Deployment xml files in ear file? If so, where? > > > You can place your orion-*.xml files alongside their *.xml counterparts. > (eg, principals.xml and orion-application.xml alongside application.xml). > Note though that if the application has already been deployed, then these > files won't be copied over the existing ones. They're only used > in the case > of a 'fresh install'. > > > >From: "Rian Schmidt" <[EMAIL PROTECTED]> > >Reply-To: Orion-Interest <[EMAIL PROTECTED]> > >To: Orion-Interest <[EMAIL PROTECTED]> > >Subject: Deployment xml files in ear file? If so, where? > >Date: Mon, 26 Mar 2001 14:47:50 -0800 > > > >Hi all, > > > >Firstly, we're having great luck with our adventures with Orion. Most > >everything works as advertised, and the performance is great-- > particularly > >the CMP EJB stuff. Just thought I'd spew a little positivity. > > > >Is there some way to include the application-deployments XML > files with an > >application? By that I mean, fer instance, we've made all kinds of > >modifications to orion-ejb-jar.xml to deal with our OR relationships, the > >legacy database name mappings, etc. orion-application.xml has a bunch of > >custom settings too. Were either of those to get wiped by an overzealous > >Orion, we'd be... sad. So, we're gonna back them up, but... > > > >Do we need to manually make those changes after deploying the > application > >on > >another machine? That seems a little goofy. I'd hate to have > to say to a > >customer "OK, start it up, and then stop it, open this file up and > >everywhere it says requestId, well, change that to request_id, blah blah, > >and then restart it." > > > >Thanks, > >Rian > > > >-- > >Rian Schmidt > >[EMAIL PROTECTED] > > > > > > > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com > > >
Re: Deployment xml files in ear file? If so, where?
Except for orion-ejb-jar.xml, which alone has its own place in /orion/. tim > You can place your orion-*.xml files alongside their *.xml counterparts. > (eg, principals.xml and orion-application.xml alongside application.xml). > Note though that if the application has already been deployed, then these > files won't be copied over the existing ones. They're only used in the case > of a 'fresh install'. > > > >From: "Rian Schmidt" <[EMAIL PROTECTED]> > >Reply-To: Orion-Interest <[EMAIL PROTECTED]> > >To: Orion-Interest <[EMAIL PROTECTED]> > >Subject: Deployment xml files in ear file? If so, where? > >Date: Mon, 26 Mar 2001 14:47:50 -0800 > > > >Hi all, > > > >Firstly, we're having great luck with our adventures with Orion. Most > >everything works as advertised, and the performance is great-- particularly > >the CMP EJB stuff. Just thought I'd spew a little positivity. > > > >Is there some way to include the application-deployments XML files with an > >application? By that I mean, fer instance, we've made all kinds of > >modifications to orion-ejb-jar.xml to deal with our OR relationships, the > >legacy database name mappings, etc. orion-application.xml has a bunch of > >custom settings too. Were either of those to get wiped by an overzealous > >Orion, we'd be... sad. So, we're gonna back them up, but... > > > >Do we need to manually make those changes after deploying the application > >on > >another machine? That seems a little goofy. I'd hate to have to say to a > >customer "OK, start it up, and then stop it, open this file up and > >everywhere it says requestId, well, change that to request_id, blah blah, > >and then restart it." > > > >Thanks, > >Rian > > > >-- > >Rian Schmidt > >[EMAIL PROTECTED]
Re: Deployment xml files in ear file? If so, where?
You can place your orion-*.xml files alongside their *.xml counterparts. (eg, principals.xml and orion-application.xml alongside application.xml). Note though that if the application has already been deployed, then these files won't be copied over the existing ones. They're only used in the case of a 'fresh install'. >From: "Rian Schmidt" <[EMAIL PROTECTED]> >Reply-To: Orion-Interest <[EMAIL PROTECTED]> >To: Orion-Interest <[EMAIL PROTECTED]> >Subject: Deployment xml files in ear file? If so, where? >Date: Mon, 26 Mar 2001 14:47:50 -0800 > >Hi all, > >Firstly, we're having great luck with our adventures with Orion. Most >everything works as advertised, and the performance is great-- particularly >the CMP EJB stuff. Just thought I'd spew a little positivity. > >Is there some way to include the application-deployments XML files with an >application? By that I mean, fer instance, we've made all kinds of >modifications to orion-ejb-jar.xml to deal with our OR relationships, the >legacy database name mappings, etc. orion-application.xml has a bunch of >custom settings too. Were either of those to get wiped by an overzealous >Orion, we'd be... sad. So, we're gonna back them up, but... > >Do we need to manually make those changes after deploying the application >on >another machine? That seems a little goofy. I'd hate to have to say to a >customer "OK, start it up, and then stop it, open this file up and >everywhere it says requestId, well, change that to request_id, blah blah, >and then restart it." > >Thanks, >Rian > >-- >Rian Schmidt >[EMAIL PROTECTED] > > > _ Get your FREE download of MSN Explorer at http://explorer.msn.com
