Is there a particular reason you want the .x* files separated, or just personal preference?
The way I use these files, they are part of the source of the component. The .xinfo file doesn't actually exist except as an artifact of the build, generated via the meta plugin and javadoc tags. I use the .xconfig as reasonable configuration defaults for the component, but not for any configuration that is related to deployment in a particular environment. I view the .xconfig as the next step past setting static final default configuration values inside the class, but I wouldn't set default values for configuration such as database urls, host names, etc. -Cameron On Tue, 2004-04-20 at 14:56, Nader Aeinehchi wrote: > Hello > In the Merlin documentation and OpenIM, I observer that configuration > files (*.xinfo, *.xconfig,...) are bundled in the same directory as > the Java source code. > > IMHO it should be "motivated" to separate Java source code and > configuration files in different directories in the development > phase. For example, > > DEVELOPMENT > ============================================== > conf/ > acme/ > myclass.xinfo > src/ > java/ > acme/ > myclass.java > EXECUTION > ================================================ > bin/ > acme/ > myclass.xinfo > myclass.java > Best Regards > > -- > Nader Aeinehchi > Aasenhagen 66 E > 2020 Skedsmokorset > NORWAY > Direct and Mobile +47 41 44 29 57 > Tel (private): +47 64 83 09 08 > Fax +47 64 83 08 07 > www.aeinehchi.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
