Re: xalan usage in taglibs
Romain Manni-Bucau <[email protected]> Wed, 4 Apr 2018 23:57:41 +0200
| Newsgroups | gmane.comp.jakarta.taglibs.user |
|---|---|
| Message-ID | <CACLE=7OPOOxNT=-3Wcde+_UxbNvwXW2CcSM3ivE-vV4-8wX1KQ@mail.gmail.com> |
--000000000000866f2b05690ce9e2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Well issues i mentionned were to have xalan in the classpath. This particular issue can be solved but this will not help tomee sadly. Le 4 avr. 2018 19:48, "Matthew Broadhead" <[email protected]> a =C3=A9crit : > could xalan be fixed or has everyone given up on it > meaning https://issues.apache.org/jira/browse/XALANJ-2540 which has 31 up > votes > > On 04/04/2018 17:30, Romain Manni-Bucau wrote: > >> That is why we have that hardcoded dep ATM but in tomee it creates as mu= ch >> issues for apps not using that featire than it solves problem for others >> :( >> >> Le 4 avr. 2018 17:24, "Matthew Broadhead" <[email protected]= k >> > >> a =C3=A9crit : >> >> i posted these links to the issue. did anyone see them? they seem >>> important to the problem >>> https://stackoverflow.com/questions/6340802/java-xpath-apach >>> e-jaxp-implementation-performance >>> https://blogs.sap.com/2009/12/04/performance-improvements-in >>> -nw-java-applications-with-xml-processing/ >>> >>> On 08/12/2017 17:08, Matthew Broadhead wrote: >>> >>> ok i created an issue https://bz.apache.org/bugzilla >>>> /show_bug.cgi?id=3D61875 >>>> >>>> On 08/12/2017 16:29, Jeremy Boynes wrote: >>>> >>>> On Dec 8, 2017, at 3:58 AM, Matthew Broadhead < >>>>> >>>>>> [email protected]> wrote: >>>>>> >>>>>> here is a patch which removes the xalan dependency. but it breaks t= he >>>>>> ForEachTagTest. >>>>>> i notice that every constructor generates a JSTLXPathCompiler. could >>>>>> it >>>>>> not be a singleton? >>>>>> >>>>>> Thanks for the patch. I tried applying it but it looks like the >>>>> support >>>>> classes from o.a.t.standard.xpath e.g. JSTLXPathCompiler were not >>>>> included >>>>> - please could you update. It would also be easier to read the diff i= f >>>>> you >>>>> removed the old code rather than commenting it out. >>>>> >>>>> How about creating an new issue in Bugzilla and attaching patches to >>>>> that. >>>>> >>>>> Cheers >>>>> Jeremy >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> > --000000000000866f2b05690ce9e2--