From derby-dev-return-32065-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Thu Oct 19 05:05:59 2006 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 71138 invoked from network); 19 Oct 2006 05:05:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Oct 2006 05:05:58 -0000 Received: (qmail 66241 invoked by uid 500); 19 Oct 2006 05:05:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 66200 invoked by uid 500); 19 Oct 2006 05:05:58 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 66187 invoked by uid 99); 19 Oct 2006 05:05:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2006 22:05:58 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates 64.233.162.201 as permitted sender) Received: from [64.233.162.201] (HELO nz-out-0102.google.com) (64.233.162.201) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2006 22:05:57 -0700 Received: by nz-out-0102.google.com with SMTP id o37so197093nzf for ; Wed, 18 Oct 2006 22:05:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OpAC9PCkYWTlq4hiljyaEJddoJ5hb8A8xUaQXmo33W4ERxt6P3KA9hKYV9FvU+H059AXqhbRe7LalUboqyT6RqbKnOtBzT7IXQM0ZnTl+Y5e2QIWDjorFSoBXOdZlpZ22059Iws6VGrqRmeYoGPTWrjzX5TG5aaj4Xp9E3IYYkc= Received: by 10.65.20.3 with SMTP id x3mr391959qbi; Wed, 18 Oct 2006 21:38:21 -0700 (PDT) Received: by 10.64.180.10 with HTTP; Wed, 18 Oct 2006 21:38:21 -0700 (PDT) Message-ID: <54ac72d70610182138u39525fccsb99d0f2a84172a5@mail.gmail.com> Date: Wed, 18 Oct 2006 21:38:21 -0700 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: Re: [Vote] Include tomcat5.exe as derby.exe (Re: [jira] Commented: (DERBY-187) Starting derby network server as a service in Win OS) In-Reply-To: <4536A7D2.40803@amberpoint.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <17992086.1161178719830.JavaMail.jira@brutus> <45364AC3.3040600@basil.ocn.ne.jp> <4536A7D2.40803@amberpoint.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 10/18/06, Bryan Pendleton wrote: > > Now I'm thinking to include tomcat5.exe into derby as derby.exe as > > resolution for DERBY-187. > > Are the following two statements true? > > 1) This derby.exe program would be useful to Windows users, not to other users Correct, since tomcat5.exe is just a renamed procrun/prunsrv from the Jakarta Commons Daemon project. > 2) This derby.exe program can be used with any release of Derby (that is, we > don't have to modify the NetworkServerControl class to enable it to be run as > a service by Derby.exe). Procrun/prunsrv can be used to interface any program, not just java, with Windows' services. Consider it an Apache licensed srvany.exe. The question that I think needs to be asked is: 3) Why can't users get a native Windows binary for procrun from the Jakarta Commons Daemon project that they can use with Derby? There's even a JIRA that's over a year old (migrated from Bugzilla) with no comments that asks for exactly that: http://issues.apache.org/jira/browse/DAEMON-51 > If both the above statements are true, then it occurs to me that it might be > nice to be able to distribute this new program separately, rather than as > part of the basic Derby release. While I don't see any problem with Derby redistributing procrun, I don't think we necessarily need to be redistributing it either. It would be sufficient to provide a pointer to the commons daemon project and instructions in our documentation for those that want this functionality. But, since you can't actually get procrun as a Windows executable anywhere that I could find from the links at http://jakarta.apache.org/commons/daemon/index.html, I suppose redistributing it is probably the best way of providing this functionality for users. Maybe there's some reason why they don't redistribute their own code in binary form? I find it sort of odd, but I haven't gone to look for the reasons yet. > That way users could decide whether or not to download this program, and we > also could release this program independently of releasing the basic Derby > software. If it were possible to download procrun as a binary from the Commons Daemon project, I would prefer that users pick it up from there, and we could provide Derby-specific instructions on using it with the network server. Since that doesn't seem to be possible, I think it's reasonable to consider redistributing it ourselves and having a vote on that. DERBY-187 is the 8th most popular issue in our JIRA, tied with full text search, so that indicates demand for the feature. I will vote on this later. I want to do some more research into procrun and think about how it might fit into the Derby -bin distribution. andrew