FLUID-4039: Extend Fluid model accessors (fluid.get) to support access through any form of "direct model" in place of "EL"

Description

Plain EL paths are an awkward form to express the "coordinates" of a part of model indirected through a general query. Where the "coordinates" of the required state in the model require variable numbers of arguments or an irregular sequence, "escaping" all of the coordinate details to a flat string creates a fragile and unreadable representation. It would be preferable to express these forms of "coordinate models" (that is, "coordinates OF models, expressed as a model", also known in the context of DataSources, as "direct models") in JSON form. The fluid.get pathway needs to be upgraded to support suitably structured JSON supplied as the "EL" argument, as well as a system for configuring an expandable collection of "resolvers", which are "typed machines for resolving coordinate state". This functionality also relates to the upcoming functionality for expressing model transformations - the collection of "resolvers" should be possible to view as, or transform into, a configuration suitable for a model transformation as operated by the "options chewing framework".

Attachments

• failing.test.patch.txt

Comments

• y z commented 2011-01-21T13:22:01.214-0500

  failing.test.patch.txt has a test with an empty model.

• Antranig Basman commented 2011-02-04T03:40:19.828-0500

  Resolved with new implementation at what is now git revision 1971f9a.

• y z commented 2011-05-17T11:53:27.300-0400

  The test case is now passing and the issue can be resolved.