Stephen,
Thanks for your advice. I figured it out and it was amazingly silly.
My MERLIN_HOME environmental variable was set as a user variable, not a system variable. Thus it ran just fine in console mode, but wouldn't run as a service.
Which brings me to my next questions:
Is there any way to set MERLIN_HOME via a command line option?
No - but you can override ${merlin.system) which is probably what you really want to do. The ${merlin.system} property equivalent to the ${merlin.home}/system (i.e. the merlin install directory system repository).
And what exactly is the difference between merlin.dir and merlin.home?
There is an inconsistency between property names and cli options which I think is a source of confusion. The property names have been much more strict in terms of being consistent with the java conventions whereas the cli options have tended to reflect product evolution.
Here is a summary:
Property CLI Note
${merlin.home} none Defaults to MERLIN_HOME if defined
otherwise ${user.home}/.merlin${merlin.dir} -home Sets the working directory. This is
root directory from which things like
context File values are established
relative to. If not defined the value
defaults to ${user.dir}.These two are obviously different, but they're naming is so close, it gets
very confusing:
I figure the confusion is arising from the -home cli parameter. This was the command line argument back in 2.X for setting the working directory and its kind of stuck. A more consistent approach would suggest that we replace -home with -dir.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
