On 4 February 2015 at 11:24, Edward Burns <edward.burns_at_oracle.com> wrote:
EB> <newText>
EB> If there is a "WEB-INF" entry inside the META-INF/resources entry of a
EB> JAR file in WEB-INF/lib, it and all child entries must be ignored.
EB> META-INF/resources is not intended for content that is consumed as
EB> executable code in the JVM, with the one notable exception of JSP
EB> files.
EB> </newText>
EB>
EB> ...
EB> How's that?
>>>>> On Wed, 4 Feb 2015 13:34:11 +1100, Greg Wilkins <gregw_at_intalio.com> said:
GW> Almost. But I think we need something better than "must be ignored".
GW> I assume that getResource would still be able to access files in
GW> META-INF/resources/WEB-INF ?
GW> The use case for this is that libraries might like to put resource files in
GW> WEB-INF so that they are not static content the default servlet can serve,
GW> but they are still available to libraries (eg a TLD descriptor).
If that is a requirement, then my text is indeed too broad.
GW> How about something like
GW> If there is a "WEB-INF" entry inside the META-INF/resources entry of
GW> a JAR file in WEB-INF/lib, then it and all child entries are
GW> available only as static resources. From such a "WEB-INF" entry, no
GW> classes or jars will be placed on the context classpath and no
GW> descriptors will be processed.
Yes, that looks good. I like how you call out no descriptors will be
processed. Because other frameworks may have their own descriptors, I
will say "no Servlet specific descriptors will be processed."
Ok?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 23 days til DevNexus 2015
| 33 days til JavaLand 2015
| 43 days til CONFESS 2015