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 > > > > > > > >
