[
https://issues.apache.org/jira/browse/SYNAPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578019#action_12578019
]
Andreas Veithen commented on SYNAPSE-235:
-----------------------------------------
Some comments on the "$transport/Content-Type" proposal:
I think Jaxen doesn't support mixing of different object models in the same
XPath expression. Therefore to support this syntax we would have to construct
an AXIOM tree from the transport headers (and also from the context properties,
etc.). Also this kind of information is more naturally exposed via XPath
functions, e.g. "get-property('OperationName')".
There is however a third possibility which is easy to implement and that
provides a very elegant and compact syntax. It takes advantage of the fact that
XPath variables also live in namespaces (i.e. variable names are QNames). If we
define a mapping between header names and valid XPath variable names (e.g.
Content-Type <-> contentType), then we could expose transport headers as XPath
variables in a well defined namespace. Assuming that in the config file, this
namespace is bound to the prefix "http", one could then refer to the
Content-Type header by writing "$http:contentType".
> Allow XPath expressions to be specified relative to envelope or body via an
> attribute
> -------------------------------------------------------------------------------------
>
> Key: SYNAPSE-235
> URL: https://issues.apache.org/jira/browse/SYNAPSE-235
> Project: Synapse
> Issue Type: Improvement
> Reporter: Asankha C. Perera
> Assignee: Ruwan Linton
> Fix For: 1.2
>
>
> This would make XPath expressions simpler without consideration for SOAP 1.1
> or 1.2 or REST etc
> Default could be envelope (i.e. what we have now - for backward
> compatibility), and an optional attribute could specify if it should be
> relative to the body
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
