Re: [Wrapper-user] Greed takes down the community version of Win x64

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

Boris,
The 64-bit Windows version had never existed prior to version 3.3.0
when we first released it in the Standard and Professional Edition.
At the time, supporting the 64-bit Windows platform required the
purchase of a new high end server specifically for that purpose along
with a 64-bit copy of Windows XP, which at the time did not come
cheap.  For this reason, and the ongoing need to support the
development of the Wrapper, we have made the business decision to not
make it available in the Community Edition for now.  This is also true
for the z/Linux and z/OS platforms as they both have significant
monthly server leasing charges we are covering.

On Windows, you only need to use the 64-bit Windows version if you are
running a 64-bit JVM.  It is possible to run the 32-bit Wrapper on a
64-bit Windows if you are also using a 32-bit JVM.  The 64-bit JVMs
are mainly needed by very large applications which tend to be of a
professional nature.  In these cases, yes, users would need to
purchase a Standard Edition license.

To be honest, comments like yours can be a bit frustrating.  Most
companies never make anything available for free.  We have always made
a great effort to generously support open source communities, both
with the Wrapper and in other projects.  Yet when we decide to make
small portion of our NEW features closed source to support the whole
development, you call us greedy and complain.  I am glad that you were
able to so easily find a solution which meets your needs and doesn't
make you "angry".

All well.  Regardless of whether or not you decide to make use of the
Wrapper in your projects, we will continue to do our best to support
the community which has always been great to us.

I wish you the best in life.
Cheers,
Leif

On Wed, Aug 25, 2010 at 5:02 PM, Boris Hamanov <bs...@gm...> wrote:
> Is that so? "the community edition has never had
>> a single feature, let alone platform, removed"
>
> So where is it then? The community version for Windows x86x64? Post the link
> maybe?
> And what it this note here? -
> http://wrapper.tanukisoftware.com/doc/english/download.jsp#downloadNote1
> I quote "*1: 64-bit Windows versions of the Java Service Wrapper are not
> currently being made available in the Community Edition."
> Are you aware that on 64 bit windows, only 64 bit services can be run?
> I think so. So why do it? To make me buy the wrapper? Well, you are
> unsuccessful.
>
> I don't mind buying a good software, I am a developer myself and know the
> value of this work.
> But those kind of dirty tricks just makes me angry. GL.
>
> --------------------------------------------------
> From: "Leif Mortenson" <lei...@ta...>
> Sent: Wednesday, August 25, 2010 4:34 AM
> To: <wra...@li...>
> Subject: Re: [Wrapper-user] Greed takes down the community version of Win
> x64
>
>> Boris,
>> Thank you for your constructive feedback, and for your first
>> contribution to the community.
>>
>> I do need to correct you however, the community edition has never had
>> a single feature, let alone platform, removed.  To this date we are
>> actively continuing to support and add to the platforms supported by
>> the community edition.
>>
>> The reality is that developing software consumes a lot of resources.
>> In the case of the Wrapper, after 8 years, thousands of hours of time,
>> and well over a million direct and indirect downloads, the development
>> community was still a team of one.   This was making it impossible to
>> keep the project alive and to keep up with requests for new features.
>> We decided to make the compromise of adding additional Standard and
>> Professional editions to help fund development.  This has been very
>> successful for the past 3 years.  The Wrapper, including the Community
>> Edition, is now very active with a team of several paid developers.
>>
>> We have been a long time contributor to open source, both with the
>> Wrapper and other projects, as is easily visible with Google.
>>
>> Unfortunately, not every solution will make everyone happy.
>>
>> There are actually a few ways to launch a JVM as a service.  The
>> Wrapper goes way beyond that however to actually protect, monitor, and
>> restart the JVM when needed.  It also contains a large number of
>> features useful to both developers and system administrators.
>>
>> We are always looking for ways to make the Wrapper more useful and
>> look forward to your feedback.
>>
>> Have a great day.
>>
>> Cheers,
>> Leif
>>
>> 2010/8/25 Boris Hamanov <bs...@gm...>:
>>> This wrapper software was recommended to me by Codehouse Jetty
>>> documentation. I read all the help and decided to download it. What was
>>> my
>>> surprise (very unpleasant one) when I discovered that my server
>>> configuration is missing from the community version!  Windows x86 64 bit!
>>> The authors were taken by greed and decided that they will charge almost
>>> 90
>>> euro for that wrapper (at minimum).  So people with Windows x64 have more
>>> money to waste is that it? I was so pissed off! I will never pay  a
>>> single
>>> cent for this software! I easily solved my simple need (to start my
>>> server
>>> on system startup) with Windows task scheduler. For less time that took
>>> me
>>> to read the Java Service Wrapper docs, I might add. Here is my scheduler
>>> task exported as an XML. You can import it and use it in any version of
>>> Windows Vista or Windows 7.  FREE OF CHARGE! I will also post this on my
>>> blog and notify Codehouse to stop recommending that software.
>>>
>>> <?xml version="1.0" encoding="UTF-16"?>
>>> <Task version="1.2"
>>> xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
>>>   <RegistrationInfo>
>>>     <Date>2010-08-24T18:11:18.0716</Date>
>>>     <Author>GreenHouseV\bsh666</Author>
>>>   </RegistrationInfo>
>>>   <Triggers>
>>>     <BootTrigger>
>>>       <Enabled>true</Enabled>
>>>     </BootTrigger>
>>>   </Triggers>
>>>   <Principals>
>>>     <Principal id="Author">
>>>       <UserId>SYSTEM</UserId>
>>>       <RunLevel>LeastPrivilege</RunLevel>
>>>     </Principal>
>>>   </Principals>
>>>   <Settings>
>>>     <IdleSettings>
>>>       <Duration>PT10M</Duration>
>>>       <WaitTimeout>PT1H</WaitTimeout>
>>>       <StopOnIdleEnd>true</StopOnIdleEnd>
>>>       <RestartOnIdle>false</RestartOnIdle>
>>>     </IdleSettings>
>>>     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
>>>     <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
>>>     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
>>>     <AllowHardTerminate>true</AllowHardTerminate>
>>>     <StartWhenAvailable>false</StartWhenAvailable>
>>>     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
>>>     <AllowStartOnDemand>true</AllowStartOnDemand>
>>>     <Enabled>true</Enabled>
>>>     <Hidden>false</Hidden>
>>>     <RunOnlyIfIdle>false</RunOnlyIfIdle>
>>>     <WakeToRun>false</WakeToRun>
>>>     <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
>>>     <Priority>7</Priority>
>>>   </Settings>
>>>   <Actions Context="Author">
>>>     <Exec>
>>>       <Command>C:\jetty-7.1.6.v20100715\start.cmd</Command>
>>>       <WorkingDirectory>C:\jetty-7.1.6.v20100715</WorkingDirectory>
>>>     </Exec>
>>>   </Actions>
>>> </Task>