[
https://issues.apache.org/jira/browse/JXPATH-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025045#comment-15025045
]
Michael Osipov commented on JXPATH-183:
---------------------------------------
Thanks for this. {{XMLGregorianCalendar}} is nowhere directly used in JXPath.
This is a hard one. I have an idea how we could narrow this down but it will
take some work from your side.
Assuming that you are generating your Java model with JAXB's XJC, you could
create a mapper with converts {{xs:dateTime}} to a Joda class or Java 8 Date
and Time API and you'll see whether it is truly {{XMLGregorianCalendar}} or
rather JXPath.
What do you think?
> XMLGregorianCalendar existence adding a lot of performance penalty
> ------------------------------------------------------------------
>
> Key: JXPATH-183
> URL: https://issues.apache.org/jira/browse/JXPATH-183
> Project: Commons JXPath
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: Windows 7, Amazon Unix, Weblogic
> Reporter: Ganna Shmatova
> Labels: performance
>
> We're using JXPath to parse some input from a client. When they give us a
> valid date it gets transformed from a SOAP message into Java objects. When
> this happens JXPath queries suddenly take 1-8 seconds more (depending on
> system -- the optimized system it's 1 second, dev & test machines it's 8).
> Kicker is, we don't even look for this field. Just its existence does it.
> (we've quickfixed to omit the xml tags before the string is parsed into Java
> for now)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
