[oXygen-user] Extension functions in validation scenario

[George Cristian Bina]

Dear Peter,

The integrated extensions can be registered to Saxon through an 
Initializer class or though a configuration file. We have support for 
setting a Saxon configuration file and an Initializer for XSLT and 
XQuery but not for XML Schema - this is on our todo list.
It may be the case that Saxon looks automatically at some place for a 
configuration file - in that case that can be a workaround to setup your 
extensions, you will still need to have the library in the lib folder to 
have the extensions Java classes are accessible.

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 4/26/13 9:51 PM, Rushforth, Peter wrote:
> Hi,
>
> I added the classes and dependencies to the  [oXygen]/lib folder, but it
> does not make a difference to Oxygen recognizing the extensions.
>
> I don't quite see how it could, since the functions I write have to be explicitly
> registered with the saxon processor with code like :
>
> proc.registerExtensionFunction(MyExtensionFunctions.validEpsg4326Locations);
>
> for example.
>
> Maybe this will have to wait for the validation scenarios enhancement.
>
> Thanks
> Peter
>
>> -----Original Message-----
>> From: George Cristian Bina [mailto:george at oxygenxml.com]
>> Sent: April 25, 2013 14:52
>> To: Rushforth, Peter
>> Cc: oxygen-user at oxygenxml.com
>> Subject: Re: [oXygen-user] Extension functions in validation scenario
>>
>> I just want to add that we have an enhancement request to add
>> support for specifying additional libraries also in
>> validation scenarios, similar with what we provide for
>> transformation scenarios.
>>
>> Best Regards,
>> George
>> --
>> George Cristian Bina
>> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
>> http://www.oxygenxml.com
>>
>> On 4/25/13 9:50 PM, George Cristian Bina wrote:
>>> Hi Peter,
>>>
>>> I am not sure how you want to use those extensions, I guess
>> you want
>>> to use them in an XML Schema 1.1 in the xs:assert/@test attribute?
>>> In that case the suggestion below will not work but you can
>> add your
>>> extensions library to the [oXygen]/lib folder and oXygen will load
>>> that automatically (for the Eclipse plugin you need to also
>> edit the
>>> plugin.xml file to add a pointer to that library in the
>> <runtime> section).
>>> On the other hand I have not checked if the XML Schema 1.1
>> spec allows
>>> using extension functions inside the xs:assert/@test attribute...
>>>
>>> Best Regards,
>>> George
>>> --
>>> George Cristian Bina
>>> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
>>> http://www.oxygenxml.com
>>>
>>> On 4/25/13 9:26 PM, oXygen XML Editor Support wrote:
>>>> Hello,
>>>>
>>>> I've already replied to your question on the support email.
>>>>
>>>> Please see the response forwarded below:
>>>>
>>>>> -------- Original Message --------
>>>>> Subject: Re: Extension functions in validation scenario
>>>>> Date: Thu, 25 Apr 2013 20:45:46 +0300
>>>>> From: oXygen XML Editor Support <support at oxygenxml.com>
>>>>> To: Rushforth, Peter <Peter.Rushforth at NRCan-RNCan.gc.ca>
>>>>>
>>>>> Hello,
>>>>>
>>>>> Thank you for contacting us.
>>>>>
>>>>> The fastest way to add the jars containing your extension
>> functions
>>>>> would be to add them as extensions in the transformation scenario.
>>>>> For that, you should go to the "Configure Transformation
>>>>> Scenario(s)", even by oXygen menu Document > Transformation, or
>>>>> using its corresponding icon in the Transformation
>> toolbar then choose to "Edit"
>>>>> the scenario.
>>>>>
>>>>> Once in the scenario editing dialog, in the "XSLT"
>> (first) tab, you
>>>>> have "Extensions". Here is where your jars should go.
>>>>>
>>>>> You could also add the extension using a Saxon
>> configuration file,
>>>>> but this operation is more complex than the first.
>>>>> You can add the Saxon configuration file in the same edit
>> scenario
>>>>> dialog, same tab (XSLT).
>>>>> For that you should access the "Advanced options" for the Saxon
>>>>> engine (yellow cogwheel icon neat the Transformer chooser).
>>>>>
>>>>> Let us know if you need additional information or any
>> further help.
>>>>>
>>>>> Regards,
>>>>> Costin
>>>>
>>>> Costin Sandoi
>>>> oXygen XML Editor and Author Support
>>>>
>>>> Tel: +1-650-352-1250 ext.302
>>>> Fax: +40-251-461482
>>>> support at oxygenxml.com
>>>> http://www.oxygenxml.com
>>>>
>>>>
>> ---------------------------------------------------------------------
>>>> ------ This message (including any attachments) contains
>> confidential
>>>> information and is intended only for the individual(s)
>> named. If you
>>>> are not the named addressee you should not disseminate,
>> distribute or
>>>> copy this e-mail. Please notify the sender immediately by
>> e-mail if
>>>> you have received this e-mail by mistake and delete this
>> e-mail from your system.
>>>> Any quotation contained herein has a validity of 30 days, unless
>>>> otherwise specified.
>>>>
>>>> On 4/25/2013 6:03 PM, Rushforth, Peter wrote:
>>>>> Hi,
>>>>>
>>>>> I have written some saxon extension functions which
>> support XML Schema assertions.
>>>>>
>>>>> Is there any way to add the jar containing those
>> functions such that I can test them in Oxygen?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Peter Rushforth
>>>>>
>>>>> _______________________________________________
>>>>> oXygen-user mailing list
>>>>> oXygen-user at oxygenxml.com
>>>>> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>>>>>
>>>> _______________________________________________
>>>> oXygen-user mailing list
>>>> oXygen-user at oxygenxml.com
>>>> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>>>>
>>> _______________________________________________
>>> oXygen-user mailing list
>>> oXygen-user at oxygenxml.com
>>> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>>>
>>