From: Anthony Green <green@redhat.com>
To: Tom Karagianes <t.karagianes@f5.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: Bundle LocalStrings not found
Date: Tue, 01 Oct 2002 14:44:00 -0000 [thread overview]
Message-ID: <1033508665.1686.6.camel@dhcppc2> (raw)
In-Reply-To: <004801c2698b$45df2de0$090ba8c0@win.net>
On Tue, 2002-10-01 at 13:44, Tom Karagianes wrote:
> I keep running into the error listed below whenever I attempt to view one of
> Tomcat's servlet examples. On investigation, LocalStrings is where it
> belongs (actually the various LocalStrings appear to be where they belong)
> so the error has me somewhat confused.
Just put the directory with LocalString.properties on your CLASSPATH
before running tomcat. For me, this looks like:
$ CLASSPATH=/menlo/green/rhug/i/etc/tomcat/webapps/examples/WEB-INF/classes tomcat
I'm pretty sure you shouldn't have to do this. :-)
Any help debugging this would be great. Even a pointer to where tomcat
sets the classpath based on the webapps that are installed...
> (p.s. I think what you have done so far is remarkable. Thanks a lot.)
Thanks!!
AG
next prev parent reply other threads:[~2002-10-01 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 13:34 Tom Karagianes
2002-10-01 14:44 ` Anthony Green [this message]
2002-10-09 12:50 ` Tom Karagianes
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=1033508665.1686.6.camel@dhcppc2 \
--to=green@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
--cc=t.karagianes@f5.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).