I took a quick look at the test-case - I think the problem is that using an XPath Transform is just not efficient with a very large input document, as the XPath Filter gets called on each input node. I'm not sure if there's a more efficient way of implementing the code - the XPath Transform is not used very often from my experience.
Colm. On Fri, Apr 6, 2018 at 10:30 AM, MRedford-Jones < martin.redford-jo...@capgemini.com> wrote: > Colm > > There is a code example available on the HMRC Developer site: IR Mark > Calculator > <http://www.hmrc.gov.uk/softwaredevelopers/hmrcmark/markcalculator.zip> > Although this version is slightly old in that it uses v1.4.1 of the xmlsec > library (we've seen the same performance issues on that library also). > I have attached two example XML submissions: Mark-Test-Files.zip > <http://apache-xml-project.6118.n7.nabble.com/file/t5735/ > Mark-Test-Files.zip> > . > > The fragment extracted is transformed against the XML Digital Signature > core schema > <https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/ > xmldsig-core-schema.xsd> > . An example of the transform and filter is within the IRMarkCalculator > class > > > Colm O hEigeartaigh-2 wrote > > Do you have a test-case to help reproduce the problem? What transforms > are > > you using? > > > > Colm. > > > > > > -- > Sent from: http://apache-xml-project.6118.n7.nabble.com/Apache-XML- > Security-Dev-f33675.html > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com