[
https://issues.apache.org/jira/browse/JXPATH-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028982#comment-15028982
]
Michele Vivoda commented on JXPATH-183:
---------------------------------------
Not sure why this feature exists, to support [indexed
poperties|http://da2i.univ-lille1.fr/doc/tutorial-java/javabeans/properties/indexed.html]
I think, there is one test about it {{BeanModelTest}}, not sure if there are
use cases for it, for me is a not so common pattern.
I think that guessing in this way is risky as came out from this issue, the
method could have also more side effects than just waiting. If it were for me
I would remove this feature in a next release for the risks it creates, or at
least disable it by default.
> 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)
