Re: [Wrapper-user] Service configuraiton GUI

[Leif M. <le...@ta...>]

David,
    Sounds great.  It sounds like you want to manage it yourself and 
maintain ownership
so the GPL is fine.  This would be a standalone tool, so I don't think 
that would place
any restrictions on anyone.

    Things to keep in mind:
1) Include files (Nested).
2) Environment Variables.
3) Maybe warn users about environment variable references so they know 
those variables
must be system wide to work when running as a service under the system user.

Cheers,
Leif

David Days wrote:
> Leif,
>
>     I've finished that basic edit (turns out it was quicker and easier 
> than I thought.)  I'm posting it on my company's website (I own it, so 
> it's not a problem) unless you would have another option that you prefer.
>
>     The source code is included in the .jar file.  I haven't finished 
> polishing it up, but it seems to function well.
>
>     The enhancements I'd really like to make are a follows:
>
>     * "Standard" config files for the usual deployments
>     * Drop-down lists of available options (either based on current
>       category or checking against current setting
>     * Breaking the settings up into categories (something along "JVM",
>       "Application Parameters", "Service Options" etc...basically,
>       following the layout in the documentation.)
>     * Choosing absolute, relative, or environment file paths
>     * Auto-detect of  relevant files (jars, wrapper.exe, wrapper.conf,
>       etc.)
>
>     I'll write back when I get it set up.  Any suggestions, ideas, or 
> options would be appreciated.
>
> David
>
> PS.  Unless it's going to cause any major heartache, I'd like to put 
> it out under the GPL.  If this is going to be a problem, let me know.
>
> Leif Mortenson wrote:
>> David,
>>     Yes, please post what you have created.   That sounds like it could 
>> be a useful addition.
>>
>> Cheers,
>> Leif
>>
>> David Days wrote:
>>   
>>> Hello.
>>>
>>>     I've started using Java ServiceWrapper for deployment on my 
>>> development projects for Windows servers, and I am very impressed.  The 
>>> setup is straightforward, and I believe that if you understand *NIX-type 
>>> services, it comes very easy.
>>>
>>>     However, I have to send my work to a network administrator who is 
>>> more comfortable in an MS-only environment.  While not trying to step on 
>>> his toes, I have to explain very carefully where to place the 
>>> pre-configured files and wrapper.conf file without sounding pushy.
>>>
>>>     I was wondering if anyone has worked on a configuration GUI to 
>>> handle the wrapper.conf file?  I have created an application for 
>>> configuring for the smb.conf file while keeping all comments intact, and 
>>> I thought that there might be an interest in doing the same thing for 
>>> the wrapper.conf file.
>>>     (As an aside, I understand that there are plenty of other SAMBA 
>>> configuration apps out there (Webmin and SWAT are pretty obvious) but 
>>> they require the installation of another service with all the associated 
>>> overhead and security concerns.  I wanted to have a simple, 
>>> straight-forward app that would not require any outside support and run 
>>> on any client. While rough looking, it pretty much achieved my goals.)
>>>
>>>     I have started on the basics, and should have a running example in 
>>> about a week.  If there is enough interest, I'd be glad to submit it 
>>> either as an included part of the service wrapper or a separate jar 
>>> executable. (That way, the user could simply enter "java -jar 
>>> JSWConfig.jar" and go to work.)
>>>
>>>     I'm open to any comments, suggestions, heckling, or 
>>> name-calling--I've got tough skin, and I'd like to get a good idea if 
>>> this is worth pursuing for the good of everyone or just something I'll 
>>> keep in my own toolbox.
>>>
>>> David Days
>>> 3-D Computer Solutions, Inc
>>> 13973 Lyck Run Lyra
>>> South Webster, OH  45682
>>>   
>>>