Hi,
I am currently evaluating whether the Xalan dependency can be dropped
from taglibs and replaced with javax.xml.*.
The reason for this is a conflict which occurs when I have Apache Fop as
a dependency:
java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
cannot be cast to
olean, XNumber, XString etc...
I will keep trying things. Can I come back to you with specific queries?
On 26/11/2017 17:33, Jeremy Boynes wrote:
On Nov 26, 2017, at 6:32 AM, Matthew Broadhead
wrote:
Hi,
I am currently evaluating whether the Xalan dependency can be dropped from
taglib
TomEE 7.0.4 I cannot even start without this error so I cannot
upgrade.
It seems like a classloader issue but taglibs is the only hardcoded
dependency on xalan
On 27/11/2017 01:12, Jeremy Boynes wrote:
On Nov 26, 2017, at 2:17 PM, Matthew Broadhead
wrote:
So to run the tests I could reverse
:
2017-11-27 16:31 GMT+01:00 Jeremy Boynes :
On Nov 27, 2017, at 12:07 AM, Matthew Broadhead
wrote:
In TomEE 7.0.3 everything is fine at startup. But if a webapp is reloaded I
get
java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
cannot be cast to
, 2017, at 3:14 AM, Matthew Broadhead
wrote:
has anything been decided? if i try to redeploy a context in production all my
xslt processors blow up. there should be a solution that fits all?
Taglibs (both Apache and Glassfish) has always had a dependency on Xalan. My
understanding is that TomEE
it in my system to see what effect it has?
On 06/12/2017 14:30, Romain Manni-Bucau wrote:
requires a classloader hack, no other trivial way, and that's why we
removed it from tomee
2017-12-06 14:27 GMT+01:00 Matthew Broadhead :
is there any way that i can get the correct xalan at runtime?
here is a patch which removes the xalan dependency. but it breaks the
ForEachTagTest.
i notice that every constructor generates a JSTLXPathCompiler. could it
not be a singleton?
On 07/12/2017 15:08, Matthew Broadhead wrote:
is there any other way to rewrite it so that it doesn'
ok i created an issue https://bz.apache.org/bugzilla/show_bug.cgi?id=61875
On 08/12/2017 16:29, Jeremy Boynes wrote:
On Dec 8, 2017, at 3:58 AM, Matthew Broadhead
wrote:
here is a patch which removes the xalan dependency. but it breaks the
ForEachTagTest.
i notice that every constructor
0 Jeremy Boynes :
On Nov 27, 2017, at 7:38 AM, Romain Manni-Bucau wrote:
2017-11-27 16:31 GMT+01:00 Jeremy Boynes :
On Nov 27, 2017, at 12:07 AM, Matthew Broadhead
wrote:
In TomEE 7.0.3 everything is fine at startup. But if a webapp is reloaded I
get
java.lang.ClassCastException: org.apache.x
/12/2017 17:08, Matthew Broadhead wrote:
ok i created an issue
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875
On 08/12/2017 16:29, Jeremy Boynes wrote:
On Dec 8, 2017, at 3:58 AM, Matthew Broadhead
wrote:
here is a patch which removes the xalan dependency. but it breaks
the
than it solves problem for others :(
Le 4 avr. 2018 17:24, "Matthew Broadhead"
a écrit :
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-perform
so it seems xalan could easily be fixed but nobody has done it. also the
project is abandoned. should we still be depending on an abandoned
project? what is the alternative? lots of projects still depend on
xalan surely?
Forwarded Message
Subject: [jira] [Commented] (XAL
12 matches
Mail list logo
