Re: orion xml's
oh cool, thats excactly what i was looking for... my bad and also thanks to mr ottinger for pointing out the same thing :) morten wilken -Original Message- From: Scott Farquhar <[EMAIL PROTECTED]> To: Orion-Interest <[EMAIL PROTECTED]> Date: 20. oktober 2001 18:07 Subject: Re: orion xml's >Morten, > >What you ask for already exists. You can create your own >orion-ejb-jar.xml files, and place them next to your ejb-jar.xml files, >and they will be automatically deployed. > >The reason that most people edit the deployed ones is that they don't >care to remember the syntax. If you let orion generate them, then you >can just edit the file. > >Also, if you create an orion-ejb-jar.xml file, you do not need to >specify all the parameters, orion will fill them in if you have missed some. > >One other point to watch out for, is that once an orion-ejb-jar.xml file >is deployed, it will not be overwritten. So you will need to delete the >existing one for it to be redeployed. > >Cheers, >Scott > >-- >Scott Farquhar :: [EMAIL PROTECTED] > >Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > >Morten Wilken wrote: > >> Am i the only one who thinks that the idea that you have to edit the >> autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? >> >> sure it can be done and it works, but i would be much happier if i could >> have 2 sets of xml files, the ones you edit (and you could put in your >> versioning system), and another set that orion generates, and that you never >> have to fiddle with. >> >> it seems an odd mix the way it is right now, as if it was meant to be >> seperated, but somehow it wasn't followed through >> >> i could be wrong, and missing the point of the structure entirely >> >> comments appreciated >> sincerely >> morten wilken >> >> >> >> > > > >
Re: orion xml's
Morten, What you ask for already exists. You can create your own orion-ejb-jar.xml files, and place them next to your ejb-jar.xml files, and they will be automatically deployed. The reason that most people edit the deployed ones is that they don't care to remember the syntax. If you let orion generate them, then you can just edit the file. Also, if you create an orion-ejb-jar.xml file, you do not need to specify all the parameters, orion will fill them in if you have missed some. One other point to watch out for, is that once an orion-ejb-jar.xml file is deployed, it will not be overwritten. So you will need to delete the existing one for it to be redeployed. Cheers, Scott -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World Morten Wilken wrote: > Am i the only one who thinks that the idea that you have to edit the > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > sure it can be done and it works, but i would be much happier if i could > have 2 sets of xml files, the ones you edit (and you could put in your > versioning system), and another set that orion generates, and that you never > have to fiddle with. > > it seems an odd mix the way it is right now, as if it was meant to be > seperated, but somehow it wasn't followed through > > i could be wrong, and missing the point of the structure entirely > > comments appreciated > sincerely > morten wilken > > > >
Re: orion xml's
On Thu, 18 Oct 2001, Morten Wilken wrote: > Am i the only one who thinks that the idea that you have to edit the > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? Probably. > sure it can be done and it works, but i would be much happier if i could > have 2 sets of xml files, the ones you edit (and you could put in your > versioning system), and another set that orion generates, and that you never > have to fiddle with. It's much more convenient than the alternative: having ot generate both sets of XML before you can deploy at all. As it is, you can manually generate the stuff you want, and Orion will... oh wait, looks like you're not aware of that fully, read on! > it seems an odd mix the way it is right now, as if it was meant to be > seperated, but somehow it wasn't followed through > > i could be wrong, and missing the point of the structure entirely Here's what I do: deploy with just the J2EE files, then copy the orion-generated files to my base directory (i.e., orion-web.xml into WEB-INF, etc.) and edit that file. Then I wipe out the deployment that orion made, and redeploy; Orion copies the orion-*.xml files in place and uses them. > comments appreciated > sincerely > morten wilken > > --- Joseph B. Ottinger [EMAIL PROTECTED] http://adjacency.org/ IT Consultant
RE: orion xml's
Or alternatively we use XDoclet to generate almost all of our deployment descriptors and EJBs. http://sf.net/projects/xdoclet It has @orion tags now in 1.1 and will generate the orion-ejb-jar file for ou. Cheers, Mike Mike Cannon-Brookes :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Magnus Rydin > Sent: Thursday, October 18, 2001 8:04 PM > To: Orion-Interest > Subject: SV: orion xml's > > > The EARDeployer tool will help out with this when its final. > WR > > > -Ursprungligt meddelande- > > Från: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]För The elephantwalker > > Skickat: den 18 oktober 2001 10:33 > > Till: Orion-Interest > > Ämne: RE: orion xml's > > > > > > Morten, > > > > At least the dd's are in xml, when Orion started they were the only ones > > that used xml descriptors. The way to do this is with gui's that are > > integrated with orion. Orion does have some gui's for generating this > > configuration files...but my experience with them has been miserable. > > > > Most of us use auto-generated files as a start...its true that > these have > > some things which aren't necessary for configuration (I mean > who needs to > > know the wrapper class name?). > > > > My experience is that you can strip out the auto-generated bits > which have > > nothing to do with configuration (version= , date= ,wrapper class > > =, etc.), > > and this has no impact on the deployment...and in fact may hinder the > > deployment. For example, if you put in the version stuff, I have > > found that > > the ejb will double-deploy > > > > What we need is a good gui for doing this...anybody good with jdom and > > swing? > > > > regards, > > > > the elephantwalker > > www.elephantwalker.com > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken > > Sent: Thursday, October 18, 2001 1:00 AM > > To: Orion-Interest > > Subject: orion xml's > > > > > > Am i the only one who thinks that the idea that you have to edit the > > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > > > sure it can be done and it works, but i would be much happier if i could > > have 2 sets of xml files, the ones you edit (and you could put in your > > versioning system), and another set that orion generates, and > > that you never > > have to fiddle with. > > > > it seems an odd mix the way it is right now, as if it was meant to be > > seperated, but somehow it wasn't followed through > > > > i could be wrong, and missing the point of the structure entirely > > > > comments appreciated > > sincerely > > morten wilken > > > > > > > >
RE: orion xml's
You can use Xdoclet's orion support. Instead of editing the autogenerated file you put some @tags in your source and orion-ejb-jar.xml is generated by xdoclet for you. And because you put it in your Ant build fie you always have uptodate file. http://sourceforge.net/projects/xdoclet Note that a new version will be available very soon with some fixes to some bugs in orion support/etc. So for the moment use the latest code from cvs. Stay tuned for the release. Ara. > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-orion- > [EMAIL PROTECTED]] On Behalf Of Morten Wilken > Sent: Thursday, October 18, 2001 11:30 AM > To: Orion-Interest > Subject: orion xml's > > Am i the only one who thinks that the idea that you have to edit the > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > sure it can be done and it works, but i would be much happier if i could > have 2 sets of xml files, the ones you edit (and you could put in your > versioning system), and another set that orion generates, and that you > never > have to fiddle with. > > it seems an odd mix the way it is right now, as if it was meant to be > seperated, but somehow it wasn't followed through > > i could be wrong, and missing the point of the structure entirely > > comments appreciated > sincerely > morten wilken _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
RE: orion xml's
Morten, Thanks for forwarding this to the list...90% of my posts don't get through for some reason. This is one reason I created www.elephantwalker.com. Regards, the elephantwalker www.elephantwalker.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken Sent: Thursday, October 18, 2001 1:59 AM To: Orion-Interest Subject: Fw: orion xml's - Original Message - From: "Morten Wilken" <[EMAIL PROTECTED]> To: "The elephantwalker" <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 10:58 AM Subject: Re: orion xml's > hi elephantwalker > > i see your point about gui's, but i really like the fact that you can go > down and mess with the xml files, i would just like to be sure i was the > only one messing with them :-) > > what i would envision is something like > ejb-jar.xml (as per specs) + custom-ejb-jar.xml = orion-ejb-jar.xml > > so that ejb-jar.xml and custom-ejb-jar.xml could be saely tucked away in > cvs, and orion managed orion-ejb-jar.xml all by itself (autorefreshing when > i changed anything in my xml files) > > but as you say, it's nice that orion even has xml files for configuration > :-) > > sincerely > morten wilken > - Original Message - > From: "The elephantwalker" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Thursday, October 18, 2001 10:32 AM > Subject: RE: orion xml's > > > > Morten, > > > > At least the dd's are in xml, when Orion started they were the only ones > > that used xml descriptors. The way to do this is with gui's that are > > integrated with orion. Orion does have some gui's for generating this > > configuration files...but my experience with them has been miserable. > > > > Most of us use auto-generated files as a start...its true that these have > > some things which aren't necessary for configuration (I mean who needs to > > know the wrapper class name?). > > > > My experience is that you can strip out the auto-generated bits which have > > nothing to do with configuration (version= , date= ,wrapper class =, > etc.), > > and this has no impact on the deployment...and in fact may hinder the > > deployment. For example, if you put in the version stuff, I have found > that > > the ejb will double-deploy > > > > What we need is a good gui for doing this...anybody good with jdom and > > swing? > > > > regards, > > > > the elephantwalker > > www.elephantwalker.com > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken > > Sent: Thursday, October 18, 2001 1:00 AM > > To: Orion-Interest > > Subject: orion xml's > > > > > > Am i the only one who thinks that the idea that you have to edit the > > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > > > sure it can be done and it works, but i would be much happier if i could > > have 2 sets of xml files, the ones you edit (and you could put in your > > versioning system), and another set that orion generates, and that you > never > > have to fiddle with. > > > > it seems an odd mix the way it is right now, as if it was meant to be > > seperated, but somehow it wasn't followed through > > > > i could be wrong, and missing the point of the structure entirely > > > > comments appreciated > > sincerely > > morten wilken > > > > > > >
SV: orion xml's
The EARDeployer tool will help out with this when its final. WR > -Ursprungligt meddelande- > Från: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]För The elephantwalker > Skickat: den 18 oktober 2001 10:33 > Till: Orion-Interest > Ämne: RE: orion xml's > > > Morten, > > At least the dd's are in xml, when Orion started they were the only ones > that used xml descriptors. The way to do this is with gui's that are > integrated with orion. Orion does have some gui's for generating this > configuration files...but my experience with them has been miserable. > > Most of us use auto-generated files as a start...its true that these have > some things which aren't necessary for configuration (I mean who needs to > know the wrapper class name?). > > My experience is that you can strip out the auto-generated bits which have > nothing to do with configuration (version= , date= ,wrapper class > =, etc.), > and this has no impact on the deployment...and in fact may hinder the > deployment. For example, if you put in the version stuff, I have > found that > the ejb will double-deploy > > What we need is a good gui for doing this...anybody good with jdom and > swing? > > regards, > > the elephantwalker > www.elephantwalker.com > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken > Sent: Thursday, October 18, 2001 1:00 AM > To: Orion-Interest > Subject: orion xml's > > > Am i the only one who thinks that the idea that you have to edit the > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > sure it can be done and it works, but i would be much happier if i could > have 2 sets of xml files, the ones you edit (and you could put in your > versioning system), and another set that orion generates, and > that you never > have to fiddle with. > > it seems an odd mix the way it is right now, as if it was meant to be > seperated, but somehow it wasn't followed through > > i could be wrong, and missing the point of the structure entirely > > comments appreciated > sincerely > morten wilken > > >
Fw: orion xml's
- Original Message - From: "Morten Wilken" <[EMAIL PROTECTED]> To: "The elephantwalker" <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 10:58 AM Subject: Re: orion xml's > hi elephantwalker > > i see your point about gui's, but i really like the fact that you can go > down and mess with the xml files, i would just like to be sure i was the > only one messing with them :-) > > what i would envision is something like > ejb-jar.xml (as per specs) + custom-ejb-jar.xml = orion-ejb-jar.xml > > so that ejb-jar.xml and custom-ejb-jar.xml could be saely tucked away in > cvs, and orion managed orion-ejb-jar.xml all by itself (autorefreshing when > i changed anything in my xml files) > > but as you say, it's nice that orion even has xml files for configuration > :-) > > sincerely > morten wilken > - Original Message - > From: "The elephantwalker" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Thursday, October 18, 2001 10:32 AM > Subject: RE: orion xml's > > > > Morten, > > > > At least the dd's are in xml, when Orion started they were the only ones > > that used xml descriptors. The way to do this is with gui's that are > > integrated with orion. Orion does have some gui's for generating this > > configuration files...but my experience with them has been miserable. > > > > Most of us use auto-generated files as a start...its true that these have > > some things which aren't necessary for configuration (I mean who needs to > > know the wrapper class name?). > > > > My experience is that you can strip out the auto-generated bits which have > > nothing to do with configuration (version= , date= ,wrapper class =, > etc.), > > and this has no impact on the deployment...and in fact may hinder the > > deployment. For example, if you put in the version stuff, I have found > that > > the ejb will double-deploy > > > > What we need is a good gui for doing this...anybody good with jdom and > > swing? > > > > regards, > > > > the elephantwalker > > www.elephantwalker.com > > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken > > Sent: Thursday, October 18, 2001 1:00 AM > > To: Orion-Interest > > Subject: orion xml's > > > > > > Am i the only one who thinks that the idea that you have to edit the > > autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? > > > > sure it can be done and it works, but i would be much happier if i could > > have 2 sets of xml files, the ones you edit (and you could put in your > > versioning system), and another set that orion generates, and that you > never > > have to fiddle with. > > > > it seems an odd mix the way it is right now, as if it was meant to be > > seperated, but somehow it wasn't followed through > > > > i could be wrong, and missing the point of the structure entirely > > > > comments appreciated > > sincerely > > morten wilken > > > > > > >
RE: orion xml's
Morten, At least the dd's are in xml, when Orion started they were the only ones that used xml descriptors. The way to do this is with gui's that are integrated with orion. Orion does have some gui's for generating this configuration files...but my experience with them has been miserable. Most of us use auto-generated files as a start...its true that these have some things which aren't necessary for configuration (I mean who needs to know the wrapper class name?). My experience is that you can strip out the auto-generated bits which have nothing to do with configuration (version= , date= ,wrapper class =, etc.), and this has no impact on the deployment...and in fact may hinder the deployment. For example, if you put in the version stuff, I have found that the ejb will double-deploy What we need is a good gui for doing this...anybody good with jdom and swing? regards, the elephantwalker www.elephantwalker.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Morten Wilken Sent: Thursday, October 18, 2001 1:00 AM To: Orion-Interest Subject: orion xml's Am i the only one who thinks that the idea that you have to edit the autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? sure it can be done and it works, but i would be much happier if i could have 2 sets of xml files, the ones you edit (and you could put in your versioning system), and another set that orion generates, and that you never have to fiddle with. it seems an odd mix the way it is right now, as if it was meant to be seperated, but somehow it wasn't followed through i could be wrong, and missing the point of the structure entirely comments appreciated sincerely morten wilken
orion xml's
Am i the only one who thinks that the idea that you have to edit the autogenerated files like orion-ejb-jar.xml etc. is a bit problematic? sure it can be done and it works, but i would be much happier if i could have 2 sets of xml files, the ones you edit (and you could put in your versioning system), and another set that orion generates, and that you never have to fiddle with. it seems an odd mix the way it is right now, as if it was meant to be seperated, but somehow it wasn't followed through i could be wrong, and missing the point of the structure entirely comments appreciated sincerely morten wilken
