[
https://issues.apache.org/activemq/browse/SM-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44481#action_44481
]
Ron Gavlin commented on SM-1479:
--------------------------------
It appears to handle my straightforward use case, albeit in a not-so-intuitive
fashion IMHO. In my use case, people are not thinking "proxy". They simply
expect the xslt and xquery endpoints to support all MEPs. Since the
ExchangeTarget is now already defined, would it not make sense to expose it for
optional use on the xslt and xquery endpoints?
Should I also add a JIRA for an XQueryProxy?
> smx-saxon should support IN-ONLY MEP to eliminate pipeline requirement for
> in-only flow
> ---------------------------------------------------------------------------------------
>
> Key: SM-1479
> URL: https://issues.apache.org/activemq/browse/SM-1479
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-saxon
> Affects Versions: 3.2.1
> Environment: smx-saxon should support IN-ONLY MEP to eliminate
> pipeline requirement for in-only flow. Furthermore, since the Xslt
> lightweight component supported an IN-ONLY MEP, it makes sense for smx-saxon
> to do likewise to ease migration to smx4.
> Reporter: Ron Gavlin
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
