[oXygen-user] [ann] oXygen version 16 is available

[Oxygen XML Editor Support (Radu Coravu)]

Hi Andreas,

The XPath value inside the xpath_eval method should not be surrounded by 
single quotes, it should be like:

> http://www.google.com/search?tbm=bks&q=${xpath_eval(ancestor-or-self::*:TEI/*:teiHeader/*:fileDesc/*:titleStmt/*:title[type="main"])}

The XPath processor obtains the value exactly as it is (Oxygen does not 
remove starting and ending quotes) and in your case it received the 
value as a single quoted literal string which was evaluated and returned 
as such.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 5/22/2014 4:47 PM, Andreas Wagner wrote:
> Hi all,
>
> On 2014-05-22, http://www.oxygenxml.com/whatisnew16.0.html said:
>> Editor Variable for Evaluating XPath 3.0 Expressions
>>
>> The xpath_eval(expression) editor variable allows you to evaluate
>> XPath 3.0 expressions either statically, in non-XML contexts, or
>> dynamically, relative to the current element, in XML contexts. As an
>> example, this gives you access to all standard XPath functions like
>> replace(), substring() or upper-case() when you compute the output
>> file name of a transformation.
>
> Is this supposed to work in author actions as well? I have tried to
> define an action using
> ro.sync.ecss.extensions.commons.operations.ShowElementDocumentationOperation
>
> with the URL pattern parameter:
>
> http://www.google.com/search?tbm=bks&q=${xpath_eval('ancestor-or-self::*:TEI/*:teiHeader/*:fileDesc/*:titleStmt/*:title[type="main"]')}
>
>
> but the ${xpath_eval()} is just passed as-is to google.
>
> Thanks for any insight,
>
> Andreas
>
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>