[Bug 61875] Investigate whether Xalan can be removed

2018-02-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #11 from Matthew Broadhead --- i have just tried TomEE 8.0.0-SNAPSHOT and it is working better than 7.0.4. i can transform xml on loadup. i haven't tried reloading a webapp though, as that is where it used to

[Bug 61875] Investigate whether Xalan can be removed

2017-12-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #10 from Matthew Broadhead --- https://blogs.sap.com/2009/12/04/performance-improvements-in-nw-java-applications-with-xml-processing/ -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61875] Investigate whether Xalan can be removed

2017-12-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #9 from Matthew Broadhead --- https://stackoverflow.com/questions/6340802/java-xpath-apache-jaxp-implementation-performance -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61875] Investigate whether Xalan can be removed

2017-12-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #8 from Jeremy Boynes --- (In reply to Matthew Broadhead from comment #7) > i stepped through ForEachTagTest.java > > line 140 if (tag.doStartTag() == IterationTag.EVAL_BODY_INCLUDE) { > seems to take a long

[Bug 61875] Investigate whether Xalan can be removed

2017-12-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #7 from Matthew Broadhead --- i stepped through ForEachTagTest.java line 140 if (tag.doStartTag() == IterationTag.EVAL_BODY_INCLUDE) { seems to take a long time line 142 result = dot.evaluate(tag.getCurrent());

[Bug 61875] Investigate whether Xalan can be removed

2017-12-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #6 from romain.manni-bucau --- A compromise can surely be to make xalan optional with a static check if it is here to select the impl. Also copying the needed classes should be doable if it doesnt import the

[Bug 61875] Investigate whether Xalan can be removed

2017-12-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #5 from Jeremy Boynes --- Created attachment 35598 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35598=edit JAXP with perf test $ mvn -Dtest=ForEachTagTest#testIterationPerformance

[Bug 61875] Investigate whether Xalan can be removed

2017-12-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #4 from Matthew Broadhead --- JSTLXPathContext needs to be set in ForEachTagTest.setup() somehow? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61875] Investigate whether Xalan can be removed

2017-12-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #3 from Matthew Broadhead --- i tried running that test and i got javax.servlet.jsp.JspTagException: javax.xml.xpath.XPathExpressionException: javax.xml.transform.TransformerException: Unable to evaluate

[Bug 61875] Investigate whether Xalan can be removed

2017-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 --- Comment #2 from Jeremy Boynes --- I applied the patch and made the ForEachTag tests work and am seeing the same performance problem we had before. With the current implementation the testIterationPerformance test

[Bug 61875] Investigate whether Xalan can be removed

2017-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61875 Jeremy Boynes changed: What|Removed |Added Depends on||27717 --- Comment