Re: [Wrapper-user] System.in unavailable

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

Haig,
    This has not been possible in any released versions of the Wrapper 
simply because I had
not been able to figure out how to get it working correctly in a 
reliable way.

    I gave it a try again today and was finally able to figure out how 
to resolve my previous
problems.    So good news.  This will be implemented in the next release.

    Bad news, for now at least.  Is that the Wrapper is undergoing 
several other feature
improvements at the moment.  Unless there are any bad bugs found, I was 
not planning
on doing another release until after new years some time.   You are 
welcome to build
your own version from source if you like, but I do not want to do a 
release until I have
gotten some of the new APIs worked out.

Cheers,
Leif

Haig Ehramdjian wrote:

>Hello,
>
>I am new to the mailing list.
>I am currently trying to wrap my command line driven application. Wehn I try
>to run it, I get the following warning:
>
>WARNING - System.in can not be used when the JVM is being controlled by the
>Java Service Wrapper.  Calls will block indefinitely.
>
>>From a thread on this list from the month of March, it seems this is a
>functionality, not a limitation.
>http://sourceforge.net/mailarchive/forum.php?thread_id=4088388&forum_id=1194
>8
>
>Unfortunately, my application is really requires System.in to get input from
>users.
>One of the reasons for using the wrapper is to avoid ugly classpath
>limitations on Win32 systems.
>
>Is there any known workaround to allow my application input without using
>System.in?
>  
>