[jira] Issue Comment Edited: (CAMEL-2340) Split XSLT and XQuery

["Fernando Ribeiro (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56850#action_56850 ] 

Fernando Ribeiro edited comment on CAMEL-2340 at 1/10/10 12:08 AM:
-------------------------------------------------------------------

I think XSLT and XQuery, being different technologies, should be separate components, even if both *currently* depend on Saxon.

It came to me when a consultant tried to install "camel-xquery" instead of "camel-saxon" when I asked him to install "the XQuery component".

I don't care submitting the patch, will get to it ASAP.

Can I move forward here?

      was (Author: fribeiro):
    I don't call it an improvement instead, I think XSLT and XQuery, being different technologies, are to be separate components, even if both *currently* depend on Saxon.

It occured to me when one of my consultants tried to install "camel-xquery" instead of "camel-saxon" when I asked him to install "the XQuery component".

I don't care submitting the patch, will get to it ASAP.

Can I move forward here?
  
> Split XSLT and XQuery
> ---------------------
>
>                 Key: CAMEL-2340
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2340
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-saxon
>    Affects Versions: 2.1.0
>            Reporter: Fernando Ribeiro
>
> Although both are based on Saxon, the XSLT and XQuery components should have different lifecycles, like their specs.
> No change to the XSLT component should impact the users of the XQuery component.

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