You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/07/23 13:49:00 UTC
[jira] Created: (SM-1479) smx-saxon should support IN-ONLY MEP to
eliminate pipeline requirement for in-only flow
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.
[jira] Resolved: (SM-1479) smx-saxon should support IN-ONLY MEP to
eliminate pipeline requirement for in-only flow
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SM-1479.
---------------------------------
Resolution: Fixed
I think this issue is already solved since a few days.
Last week, I've added a new endpoint in saxon, the <saxon:proxy/> endpoint acts as a proxy between two JBI endpoints and support all the MEPs.
See http://servicemix.apache.org/servicemix-saxon.html#servicemix-saxon-XSLTProxy
It can be used to transform the In and Out message in a single endpoint (and avoid using a static routing slip with 2 saxon endpoints), but it should also be able to handle your use case.
Please reopen the issue is it does no work for you.
> 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.
[jira] Commented: (SM-1479) smx-saxon should support IN-ONLY MEP to
eliminate pipeline requirement for in-only flow
Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
[ 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.