You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Andrea Zoppello (JIRA)" <ji...@apache.org> on 2007/03/13 09:40:34 UTC

[jira] Created: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation

EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
---------------------------------------------------------------------------------

                 Key: SM-879
                 URL: https://issues.apache.org/activemq/browse/SM-879
             Project: ServiceMix
          Issue Type: Bug
    Affects Versions: 3.1
            Reporter: Andrea Zoppello


When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the
drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document.

The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved SM-879.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2
                   3.1.1
         Assignee: Guillaume Nodet

$ svn commit -m "SM-879: EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation"
Sending        servicemix-eip/src/main/java/org/apache/servicemix/eip/patterns/XPathSplitter.java
Transmitting file data .Committed revision 517611.


$ svn commit -m "SM-879: EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation"
Sending        patterns/XPathSplitter.java
Transmitting file data .
Committed revision 517612.

> EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
> ---------------------------------------------------------------------------------
>
>                 Key: SM-879
>                 URL: https://issues.apache.org/activemq/browse/SM-879
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Andrea Zoppello
>         Assigned To: Guillaume Nodet
>             Fix For: 3.1.1, 3.2
>
>         Attachments: XPathSplitter.java.patch
>
>
> When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the
> drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document.
> The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation

Posted by "Andrea Zoppello (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Zoppello updated SM-879:
-------------------------------

    Attachment: XPathSplitter.java.patch

The patch attached resolve the problem reported

> EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
> ---------------------------------------------------------------------------------
>
>                 Key: SM-879
>                 URL: https://issues.apache.org/activemq/browse/SM-879
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Andrea Zoppello
>         Attachments: XPathSplitter.java.patch
>
>
> When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the
> drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document.
> The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-879) EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SM-879:
-------------------------------

    Patch Info: [Patch Available]

> EIP XPath Splitter and Drools3.1 used together cause problems in xpath evaluation
> ---------------------------------------------------------------------------------
>
>                 Key: SM-879
>                 URL: https://issues.apache.org/activemq/browse/SM-879
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Andrea Zoppello
>         Assigned To: Guillaume Nodet
>             Fix For: 3.1.1, 3.2
>
>         Attachments: XPathSplitter.java.patch
>
>
> When a service assembly use an XPath spltter and then a drools router, there are problems in xpath evaluations on the
> drools router, this because probably the two components are evaluating xpath expressions in the same DOM Document.
> The right behaviour must ensure that when the splitter component has done his job the resulting sub-elements will be processes as separated documents not related to the original DOM processed by the splitter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.