chris monster wrote:
> > >
> > > in testing several containers including Tomcat 3.1.1, i was unable to
> > > get a null ( where a test for null would have been, um, desirable ), nor
> > > did it appear that the presence or absence of a leading "/" made any
> > > difference.
> > >
> >
> > Sound
> >
> > in testing several containers including Tomcat 3.1.1, i was unable to
> > get a null ( where a test for null would have been, um, desirable ), nor
> > did it appear that the presence or absence of a leading "/" made any
> > difference.
> >
>
> Sounds like a bug in 3.1.1. But it's unlikel
thanx guys! sorry, in the future i will try to exhaust later versions
before i post... ;)
> It also looks a totally different place -- inside /WEB-INF/classes or
> inside JAR files under /WEB-INF/lib.
true! however, my purpose was to create a singleton wrapper for access
to resources by non-se
On Mon, 13 Aug 2001, chris monster wrote:
> in the api-docs for ServletContext.getResource( String path ), it is
> further specified that:
>
>
> "This method returns null if no resource is mapped to the pathname."
>
> and
>
> "The path must begin with a "/"..."
>
>
> are these stipulation
chris monster wrote:
> in the api-docs for ServletContext.getResource( String path ), it is
> further specified that:
>
> "This method returns null if no resource is mapped to the pathname."
>
> and
>
> "The path must begin with a "/"..."
>
> are these stipulations in the servlet api-docs valid
in the api-docs for ServletContext.getResource( String path ), it is
further specified that:
"This method returns null if no resource is mapped to the pathname."
and
"The path must begin with a "/"..."
are these stipulations in the servlet api-docs valid?
in testing several containers incl
