> As of 3.0.1 (I can't speak to 3.1 because its not
> baked enough for me to
> spend time with) that name element is what you will
> see when you open up the
> Window's Services Control Panel and look at the
> "Name" column. It is used as
> the "Display Name" property of the service.
OK; that jives with Kohsuke's project.
> The XML
> tag probably should have
> been displayName instead of name.
Cool; I know that Kohsuke usually fixes things within seconds of their being reported; perhaps a note to
http://kenai.com/bugzilla/buglist.cgi?product=winsw&order=Importance&limit=25 is in order.
> The service
> property called "Service Name"
> is what gets set by the --name switch to
> create-service. Interestingly,
> there does not appear to be a serviceName element in
> the XML you included.
So it's probably not applicable on Windows, but only on Solaris or something. Who knows. :-) There is a somewhat cryptic remark earlier in this thread where it is suggested that repeated invocations of this command could leave artifacts lying around, though the author didn't go into any detail; perhaps the --name element affects those artifacts?
> If <id> is supposed to be the "Service name" then
> call it <serviceName> not
> some cryptic ID. At least have the markup clearly
> convey what it is supposed
> to describe!
In fairness to the Glassfish guys, this is something defined by the winsw project (
http://kenai.com/projects/winsw/pages/ConfigurationSyntax).
> The whole bit of proper Windows service support in GF
> either v2.x or v3.0.x
> has *never* worked out of the box.
That has always been my perception as well; Google my user id and "Glassfish Windows service" or some other likely combination and you'll see what I mean. :-)
> You have always
> had to end up hacking
> this file or that file with things like JVM settings
> and such. It really
> amazes me that something intended for Enterprise
> usage can't deliver proper
> Windows service functionality.
I gather it's tough to get right.
I would be interested to know from the command's author(s) if -Xrs is included or should be included or was omitted on purpose--my service seems to be running fine at this point, but a while back you had to make sure that the -Xrs JVM option was hacked into your Glassfish service startup script machinery or the damn thing would hang up on you when you logged out.
Best,
Laird
[Message sent by forum member 'ljnelson']
http://forums.java.net/jive/thread.jspa?messageID=482562