> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 3:46 PM
> To: [EMAIL PROTECTED]
> Subject: RE: TC3.3 Proposal: Refactoring org.apache.jasper.servlet
>
>
> On Wed, 28 Mar 2001, Steve Downey wrote:
>
> > The second most common cause of bugs in Jasper is confusion
> over when to use
> > File.separator and when to use '/'. It's hard to keep track
> of, since Jasper
> > does deal with both files and URIs. And the File methods are used to
> > regularize some URIs.
> >
> > Another reason to refactor.
>
> I would say this is also part of interfacing the jasper with the
> container, and not core to the jsp parser and jsp->java
> convertor ( which
> in my opinion represents the "core" of jasper ).
>
> There is the problem of importing jsps ( and few other cases
> where files
> are needed), but again that's related with the API that is
> needed to plug
> jasper into a ( cooperating ) container.
>
<SNIP>
... importing jsp text, determining the file to write java to, finding tag
library descriptors, finding the directory to direct the java compiler to
write class files to...
Files are inherent, at least as long as javac insists on having files. I
would love to be able to compile a stream, or array of streams, but that's
not happening near term.
Almost everything else uses URI's to refer to things. So, for the most part,
jasper should not be looking at, or using, files. Streams, yes, as in
getResourceAsStream, but mostly not Files. Most current uses of File are
wrong, and other parts of Jasper try to compensate.
Actually, I don't think that importing needs Files. It should be able to use
getResourceAsStream. That may need to work with Files, but that's something
that the container deals with, not Jasper.
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named. Any use, copying or disclosure by any other person is strictly
prohibited. If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>
