Message-
From: Jim Lynch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 8:00 PM
To: Tomcat Users List
Subject: getResourceAsStream woes was: getRealPath woes
As I mentioned, all of these systems are pretty much identical. What I
didn't include in the source was a test to s
ist
>Subject: getResourceAsStream woes was: getRealPath woes
>
>As I mentioned, all of these systems are pretty much identical. What I
>didn't include in the source was a test to see if getRealPath was
>working and if not, to issue a getResourceAsStream. It also return
Howdy,
>> On the dev. and prod. systems the getRealPath method returns the
>> expected string. On the testing environment it returns null.
>
>I guess this is because it is too complicated to patch into all the
file
>manipulation functions to allow access to the packed contents of the
war
>file.
As I mentioned, all of these systems are pretty much identical. What I
didn't include in the source was a test to see if getRealPath was
working and if not, to issue a getResourceAsStream. It also returns a
null value. See:
stream=getServletContext().getResourceAsStream(APP_FILE_PROP_KEY);
N
On Wed, 2003-11-05 at 12:30, Jim Lynch wrote:
> On the dev. and prod. systems the getRealPath method returns the
> expected string. On the testing environment it returns null.
I've found that getRealPath returns null when you are running your
application from a war file without unpacking it. If
I have 3 almost identical tomcat servers running on Linux. Production,
testing and development. They are all running 4.1.24. I have the
following code running on all three:
fullPath=getServletContext().getRealPath("/")+APP_FILE_PROP_KEY;
On the dev. and prod. systems the getRealPath method r
