Re: A few changes proposed for the Synapse Configuration Language

[Asankha C. Perera]

Hi Dims Davanum Srinivas wrote: #1: The example on the page says: <filter xpath="//*[wsx:symbol='MSFT']" xmlns:wsx="http://www.webserviceX.NET/"> So you are saying that it is implicitly <filter source="/soap:Envelope" xpath="//*[wsx:symbol='MSFT']" xmlns:wsx="http://www.webserviceX.NET/"> Because you need to run the xpath on something and that something is the soap envelope. Right? Yes #2: If #1 is true, then the syntax on the wiki has an implicit source, but one cannot specify a source explicitly when xpath is specified. Right? Yes "The <filter> mediator either test the given xpath _expression_ as a boolean _expression_, or match the evaluation result of a source xpath _expression_ against the given regular _expression_. If the test succeeds, the filter mediator will execute the enclosed mediators in sequence." The intention of @xpath was to specify a boolean test XPath _expression_, and the @source to specify an XPath _expression_ which will select a source element, on which the @regex would be matched against as 'text'. If the @source was omitted and a @regex is available, the first child of the soap body would be the default for the match. thanks asankha Thanks, dims On 7/14/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: On Wed, 2006-07-12 at 13:00 -0400, Davanum Srinivas wrote: > Let me try another variation to see if folks like it: > > Syntax: >   <filter source="xpath" [regex="string"]> >     mediator+ >   </filter> > > Explanation: > If the regular _expression_ is present then the <filter> mediator > matches the evaluation result of a source xpath _expression_ against the > given regular _expression_. If the regex is absent, then the mediator > tests the given source xpath _expression_ as a boolean _expression_. In > either case, If the test succeeds, the filter mediator will execute > the enclosed mediators in sequence. This is not what @source means .. it identifies the data to filter; the "source" for filtration. If @source is missing, the data is the /soap:Envelope element. If its there it can point to any place in the message and then the regex or xpath matches against that node. So your proposal has lost function. Again, I'm -1 to the *principle*: If the language syntax is bust let's fix it. But let's *not* convolute the syntax to make a nice(r) schema. Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]