I have raised a JIRA with the name: Setters on JaxenXPathExpression have no effect on the underlying DOMXPath object (SM-579)
Unfortunately, I do not have a path for this, but the fix should be obvious from the description of the problem. Best Regards Horst Studer gnodet wrote: > > Could you please raise a JIRA and attach your patch ? > > On 9/14/06, Horst Studer <[EMAIL PROTECTED]> wrote: >> >> Namespace prefixes in an XPath expression within a <jbi:condition> >> element in >> a drools rule are not recognized when the expression is evaluated. >> >> This should work, since the JaxenConditionFactory correctly sets the >> namespace >> context in the JaxenXPathExpression object. >> >> The problem appears to be in the JaxenXPathExpression class. >> >> The setter methods of JaxenXPathExpression (for fields other than the >> xpathObject) >> only set the private field of the JaxenXPathExpression. The new values >> are >> not >> propagated to the xpathObject and therefore have no effect. >> >> The method "afterPropertiesSet()" probably was initially designed for >> this >> purpose, >> but it is only called in the constructor. Besides that, this method would >> have no >> effect if called in the setter methods, because it does nothing if the >> xpathObject >> is not null (i.e. after the first call). >> >> Best regards >> Horst Studer >> >> -- >> View this message in context: >> http://www.nabble.com/Bug-in-JaxenXPathExpression-tf2271960.html#a6307063 >> Sent from the ServiceMix - User forum at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Bug-in-JaxenXPathExpression-tf2271960.html#a6309942 Sent from the ServiceMix - User forum at Nabble.com.
