tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thom Park <tp...@borland.com>
Subject how to reload a getResourceAsStream() object
Date Wed, 08 Aug 2001 21:52:12 GMT
hello,

I have a requirement where i need to make multiple passes over a resource
stream
obtained via ServletContext.getResourceAsStream().

My problem is that as follows:

	InputStream is = sc.getResourceAsStream("/my_resource_name");

	.... do 1st processing pass

	is.close();

	is = sc.getResourceAsStream("/my_resource_name");

	... do second processing pass...

The problem is that, as far as the StandardClassLoader is concerned, the
cached copy of the input stream is still good (and it isn't I just closed
it)
and I get the original (now bad) input stream returned.


Is there anyway to force tomcat to reload the resource object (without
unloading the context).
as, right now I'm reading the whole resource into a byte array and using
[my] cached copy
for processing.

-Thom


-----Original Message-----
From: cmanolache@yahoo.com [mailto:cmanolache@yahoo.com]
Sent: Wednesday, August 08, 2001 2:13 PM
To: tomcat dev jakarta.apache.org
Cc: pmc@jakarta.apache.org
Subject: Re: [PROPOSAL] Deprecation of committers...



Can you send a list with the commiters that will become deprecated ?

Does this include 3.x commiters as well ? ( from the proposal it seems you
are talking about 4.0 commiters ).


Costin


On Wed, 8 Aug 2001, Pier P. Fumagalli wrote:

> I recently checked the list of committers for Tomcat 4.0 and MANY of them
> are inactive... Our PMC charter mentions:
>
>   At times, Committers may go inactive for a variety of reasons. A
Committer
>   that has been inactive for 6 months or more may lose their status as a
>   Committer. Getting access back is as simple as re-requesting it on the
>   projects developer mailing list.
>
> Can we start the process for "deprecating" them?
>
>     Pier
>



Mime
View raw message