public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: Christophe Roux <ch_roux@club-internet.fr>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: rhug servlet in linux native compile
Date: Tue, 01 Oct 2002 14:54:00 -0000	[thread overview]
Message-ID: <1033509291.1668.11.camel@dhcppc2> (raw)
In-Reply-To: <E17vMNm-0007oe-00@smarthost2.mail.easynet.fr>

On Sat, 2002-09-28 at 11:36, Christophe Roux wrote:
> I found that the byte code for my servlet is slower than with jdk.
> So I ask, is it possible to use a natively linux compiled servlet instead of 
> byte code with tomcat-rhug?

Yes.  Just compile your servlet .class files into .so files.

For instance, HelloWorldExample.class..

$ gcj -shared -o HelloWorldExample.so HelloWorldExample.class

Just leave that in your WEB-INF/classes dir and tomcat should pick it up
(remove the .class file just to be sure!).

Let us know how it works...

AG


      reply	other threads:[~2002-10-01 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 11:32 Christophe Roux
2002-10-01 14:54 ` Anthony Green [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1033509291.1668.11.camel@dhcppc2 \
    --to=green@redhat.com \
    --cc=ch_roux@club-internet.fr \
    --cc=rhug-rhats@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).