Date: 2004-04-20T02:05:04 Editor: 82.109.31.35 <> Wiki: Apache Geronimo Wiki Page: WishList URL: http://wiki.apache.org/geronimo/WishList
no comment Change Log: ------------------------------------------------------------------------------ @@ -115,3 +115,11 @@ The inclusion of a JDO implementation would add tremendous value to the Geronimo Application Server. pippo + += Easy EAR deployment without special EAR config = + +I would just love to write an EAR and drop it into a J2EE server. Unfortunately with a certain app server I cannot. Configuration is required in both app specific config files in the EAR and outside the EAR in another app server directory. I would prefer a way to deploy an EAR and hold such implementation details in an accompanying package (gar - geronimo config archive anyone?). This means I don't have to rip apart my EAR using an install utility then re-build it before deploying to an app server. After all, whats the point in an EAR format if you have to unarchive it in order to set some small number of app server specific config options. Also, such a GAR format should be obvious, easy and as small as possible IMHO. I.e. it should use sensible defaults, not duplicate code found in standard J2EE descriptors, each component should have its own config section/file (like cmp.xml, jms.xml, etc. - this also separates config from provider - is this feasible?). Having the configuration self-documenting as much as possible would be great, as then I as an app developer would not have to learn different config files all over again. + +Adam Fowler. + +
