Re: [Wrapper-user] are any of these features I have added desirable in the wrapper code base

[Glen <gle...@mo...>]

The VM to use (client/server/hotspot) is pertinent regardless of app or 
service.

You are right about the others they are specific to using JSW to run 
apps.  Which is why I have a wrapperw.exe which is separate and distinct 
from wrapper.exe.  Wrapperw.exe has allthe cool app features I mentioned 
(though I rename the wrapperw.exe to myapp.exe) and I still use 
wrapper.exe for running services.

The idea here is that from my research of the various java start 
products JSW is by far hte most mature so why not use the excelent code 
base to make a great app launcher too.




nic...@uk... wrote:

>    It seems most of these enhancements are centred around a generic
>      java-executable-wrapper rather than a "service wrapper".
>    The latter being for server, long running, tasks...
>
>    Is that where JSW wants to go?
>    Its quite a different goal...
>
>    -Nick
>
>
>
>
>
>
>Internet
>gle...@ap...@lists.sourceforge.net - 15/02/2005 03:39
>
>
>Please respond to wra...@li...
>
>Sent by:    wra...@li...
>
>
>
>To:    wrapper-user
>
>cc:
>
>
>Subject:    [Wrapper-user] are any of these features I have added desirable
>       in the wrapper code base
>
>
>Hi All,
>I have added a few options  to java service wrapper and I am wondeirng
>if they are desirable for the main branch.  Here they are
>
>    * An option to create the java command specified in the
>      "wrapper.java.command" property if it doesn't already exist.  This
>      is a simplification for me.  Before I did this I would just have a
>      scrpit run to create all the java command copies I needed, which
>      worked but was more maintenance.  With this I have more
>      flexibility (like if I think a java comand is not used anymore I
>      can just delete it knowing that the wrapper will recreate it if
>      needed)
>    * An altered wrapperw.exe that runs as a console application and
>      looks for a .conf file in the same directory with the same base
>      name as the wrapperw.exe.  So if the wrapperw.exe is renamed to
>      myprog.exe it will look for myprog.conf.  Also any command line
>      arguments are passed directly into the java app.  This allows one
>      to use myprog.exe as a windows explorer file handler with minimum
>      effort.  If  you use the wrapper.exe as is you would have to go
>      into the registry and add the appropriate command line parms (-c
>      myprog.conf).  I implemented this as a completely new executable
>      since all the options (-c -t -p -i -r -?) are still there just as
>      (--c --t --p --i --r --?)
>    * An option for running in console mode to run the java app in the
>      same process as wrapper.exe.  Now I know this sort of defeats the
>      robustness that the java service wrapper offers but for "quick
>      click" utilities it is simpler and slightly less resource intensive.
>    * An option to choose the JIT (client or server).  This currently
>      only works on win32 since I don't currently vae a linux machine to
>      play with but I am fairly certain I could make it portable with
>      minimum effort.  Also questions about hwo this should work with
>      non-sun jvm's
>
>
>If these ideas are desirable I am willing to code it (currently it is
>50% hack 50% clean by code it I mean make it 100% clean).  I am also
>open to alternative ways of implementing.
>
>Let me know what you all think.
>
>regards,
>Glen
>
>
>(See attached file: C.htm)
>
>This message and any attachments (the "message") is 
>intended solely for the addressees and is confidential. 
>If you receive this message in error, please delete it and 
>immediately notify the sender. Any use not in accord with
>its purpose, any dissemination or disclosure, either whole 
>or partial, is prohibited except formal approval. The internet 
>can not guarantee the integrity of this message. 
>BNP PARIBAS (and its subsidiaries) shall (will) not 
>therefore be liable for the message if modified. 
>
>**********************************************************************************************
>
>BNP Paribas Private Bank London Branch is authorised 
>by CECEI & AMF and is regulated by the Financial Services
>Authority for the conduct of its investment business in the
>United Kingdom.
>
>BNP Paribas Securities Services London Branch is authorised
>by CECEI & AMF and is regulated by the Financial Services
>Authority for the conduct of its investment business in the 
>United Kingdom.
>  
>BNP Paribas Fund Services UK Limited is authorised and 
>regulated by the Financial Services Authority.
>
>  
>
>
> ------------------------------------------------------------------------
>
> Hi All,
> I have added a few options  to java service wrapper and I am wondeirng 
> if they are desirable for the main branch.  Here they are
>
>     * An option to create the java command specified in the
>       "wrapper.java.command" property if it doesn't already exist. 
>       This is a simplification for me.  Before I did this I would just
>       have a scrpit run to create all the java command copies I
>       needed, which worked but was more maintenance.  With this I have
>       more flexibility (like if I think a java comand is not used
>       anymore I can just delete it knowing that the wrapper will
>       recreate it if needed)
>     * An altered wrapperw.exe that runs as a console application and
>       looks for a .conf file in the same directory with the same base
>       name as the wrapperw.exe.  So if the wrapperw.exe is renamed to
>       myprog.exe it will look for myprog.conf.  Also any command line
>       arguments are passed directly into the java app.  This allows
>       one to use myprog.exe as a windows explorer file handler with
>       minimum effort.  If  you use the wrapper.exe as is you would
>       have to go into the registry and add the appropriate command
>       line parms (-c myprog.conf).  I implemented this as a completely
>       new executable since all the options (-c -t -p -i -r -?) are
>       still there just as (--c --t --p --i --r --?)
>     * An option for running in console mode to run the java app in the
>       same process as wrapper.exe.  Now I know this sort of defeats
>       the robustness that the java service wrapper offers but for
>       "quick click" utilities it is simpler and slightly less resource
>       intensive.
>     * An option to choose the JIT (client or server).  This currently
>       only works on win32 since I don't currently vae a linux machine
>       to play with but I am fairly certain I could make it portable
>       with minimum effort.  Also questions about hwo this should work
>       with non-sun jvm's
>
>
> If these ideas are desirable I am willing to code it (currently it is 
> 50% hack 50% clean by code it I mean make it 100% clean).  I am also 
> open to alternative ways of implementing.
>
> Let me know what you all think.
>
> regards,
> Glen
>