Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <181830207.1105318033856.JavaMail.jira@ajax.apache.org>
Date: Mon, 10 Jan 2005 01:47:13 +0100 (CET)
From: "Felipe Leme (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-117) [PATCH] Improvements on the NetServlet
In-Reply-To: <1005460324.1105318033158.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-117?page=history ]

Felipe Leme updated DERBY-117:
------------------------------

    Attachment: DERBY-117.patch

Here is the patch I mentioned. Notice that I didn't add the new key (SRV_PortNumber) in all bundles, 
only at the en and pt_BR.

-- Felipe


> [PATCH] Improvements on the NetServlet
> --------------------------------------
>
>          Key: DERBY-117
>          URL: http://issues.apache.org/jira/browse/DERBY-117
>      Project: Derby
>         Type: Improvement
>   Components: Network Server
>     Versions: 10.0.2.1
>  Environment: Subversion Trunk
>     Reporter: Felipe Leme
>     Priority: Minor
>  Attachments: DERBY-117.patch
>
> Hi all,
> I did some minor enhancements on the Net Servlet:
> - changed Cloudscape to Derby in the i18n bundles
> - added pt_BT to know languages (the bundle was already there, but the language
>   was not set at the .java)                                    
> - improved use of tracingDirectory:
>   * init-parameter is now used (it was documented but not used before)
>   * current value is shown when the user try to change it
> - improved function that handles the request locale (for instance, mozilla uses a - instead of _ to separate the country from language)
> - shows on the screen which port the server is running on
>   * added a new SRV_POrtNumber message key for such info
> So, I'm sending a trunk patch with such changes.
> -- Felipe

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira