Re: A few changes proposed for the Synapse Configuration Language

[Asankha C. Perera]

Sanjiva Yes, this is possible.. and default is to enable on all available transports (as Axis2) , else you could specify multiple transports separated by commas or spaces Please don't do both - the proper XML way is to use spaces so that the schema can be defined properly. Sure, I will drop the comma I thought Ruchith was going to change Rampart to use the sec policy stuff instead of using a parameter. In fact the same can be done for the JMS stuff .. basically with policy being burnt into Axis2, there's we could even completely get rid of the parameter concept. Anyway that's an Axis2 discussion. Ok.. will check about the change in Rampart from Ruchith. I didn't quite understand what you mean by 'the same can be done for the JMS stuff'.. +1. I suggest we don't put <xquery ..> right now - let someone put that in when we decide which xquery impl to do it with. No need to pretend we have function that we don't have! Ok.. this will be changed ASAP OK let me make sure I understand correctly: - filter has a "source" property saying what item to filter (xpath or regex) on No - filter either has an (@source *and* @regex) OR (@xpath) The @source applies *only* when a @regex is being used. As the regex performs a text match, the @source specifies an XPath _expression_ which will extract the given _expression_ from the current message as "Text". Then the regex match is performed on this "Text". - default value of that is the /s:Envelope (separately I'd like to propose a model where that supports SOAP 1.1 and 1.2 both simultaneously) Default value is //*:Envelope/*:Body/child::* and we create an AXIOMXPath object on this at the creation time of a validate mediator instance and use it multiple times to process SOAP 1.1 and 1.2 messages without creating a new XPath object at runtime. - in addition, there is EITHER: - regex: meaning match the regex aganst the text value of whatever "source"gives .. so clearly if you use regex you must use @source to point to something interesting .. s:Envelope has no text value - xpath: a boolean valued xpath which is executed with an xpath context set to whatever node the source property points to If a @xpath attribute is specified, it should be a boolean valued XPath _expression_. The @source will not be used here. thanks asankha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]