https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
--- Comment #1 from Jarek Gawor 2010-02-05 12:38:53 UTC ---
Created an attachment (id=24933)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=24933)
Proposed patch for this issue.
Proposed patch for this issue is now attached. Th
https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
Mark Thomas changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #2 from Mark
https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
--- Comment #3 from Jarek Gawor 2010-02-06 10:01:14 UTC ---
First, can you quickly describe or point me to the features that were added to
support TLD scanning in OSGi env. in case I missed them?
We have a custom implementation of TldLocat
https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
--- Comment #4 from Mark Thomas 2010-02-06 12:13:37 UTC ---
It was bug47834 and mainly r814617 and r817685.
Bundles (as long as they are on the class path) are handled if
org.apache.jasper.compiler.TldLocationsCache.SCAN_ALL_FILES is set a
https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
--- Comment #5 from Jarek Gawor 2010-02-08 08:01:38 UTC ---
Thanks for the pointers. I am aware of that code but it doesn't really help or
address the problem described in this bug. Jasper shouldn't require (as it
doesn't really need) a jar
https://issues.apache.org/bugzilla/show_bug.cgi?id=48689
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
