Ability to configure a custom function library #2812

Closed
ebruchez opened this Issue Jun 14, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@ebruchez
Collaborator

ebruchez commented Jun 14, 2016

Motivated by #1095.

So how to provide a function library without the XForms engine depending on it? Options:

  1. "Push": Some external code, when creating an XFCD, passes an instance of the function library.
  2. "Pull": Use a new property, like xxf:function-library="org.orbeon.oxf.fr.library.FormRunnerFunctionLibrary".

The "push" solution doesn't work great currently as the XFCD is created from the general-purpose XFormsToSomething. If/when called from an XForms API, as we might have in the future in the browser (#1221), this could work.

The "pull" solution will work better for now, but will require use of reflection to load the function library, so won't work on the client. But there we can switch to a "push" solution.

So voting for "pull" for now.

The interface could be:

  • XForms calls instance() method, so org.orbeon.oxf.fr.library.FormRunnerFunctionLibrary.instance()
  • must implement org.orbeon.saxon.functions.FunctionLibrary

@ebruchez ebruchez self-assigned this Jun 14, 2016

@ebruchez ebruchez referenced this issue Jun 14, 2016

Closed

Stable API for Form Runner #1095

16 of 16 tasks complete

@ebruchez ebruchez added this to the 2016.2 milestone Jun 14, 2016

@ebruchez

This comment has been minimized.

Show comment
Hide comment
@ebruchez

ebruchez Jun 14, 2016

Collaborator
  • implement
  • test
  • doc
Collaborator

ebruchez commented Jun 14, 2016

  • implement
  • test
  • doc
@ebruchez

This comment has been minimized.

Show comment
Hide comment
Collaborator

ebruchez commented Jun 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment