ValueGenerators parsing and json schema changes

[paterczm]

Metadata changes for lightblue-platform/lightblue#22. Without sequences implementation in lightblue-mongo, this does nothing. It should be merged together with lightblue-mongo changes.

[paterczm]

Uid fields are generated by UIDInterceptor. I think we can use interceptor for generating other values too, relaying on a db specific extension (similar to how LockingSupport extension).

[bserdar]

So: a constraint that associates a sequence name with a field, and an
interceptor that generates values on insert/update, right?

On Tue, Aug 4, 2015 at 4:32 AM, Marek notifications@github.com wrote:

Uid fields are generated by UIDInterceptor. I think we can use interceptor
for generating other values too, relaying on a db specific extension
(similar to how LockingSupport extension).

—
Reply to this email directly or view it on GitHub
#431 (comment)
.

[paterczm]

So: a constraint that associates a sequence name with a field, and an interceptor that generates values on insert/update, right?

Yes, except it's not a constraint, it's a generator (new keyword).

[bserdar]

Ok, saw that.

In that case, you have to change SimpleField as well, add generators to it.

On Tue, Aug 4, 2015 at 8:02 AM, Marek notifications@github.com wrote:

So: a constraint that associates a sequence name with a field, and an
interceptor that generates values on insert/update, right?

Yes, except it's not a constraint, it's a generator (new keyword).

—
Reply to this email directly or view it on GitHub
#431 (comment)
.

[paterczm]

In that case, you have to change SimpleField as well, add generators to it.

Why SimpleField and not Field? Field has constraints, so I would think it should have value generators as well.

[bserdar]

If you add to Field, then arrays and objects will have generators as well,
but not array elements.

On Mon, Aug 17, 2015 at 6:07 AM, Marek notifications@github.com wrote:

In that case, you have to change SimpleField as well, add generators to it.

Why SimpleField and not Field? Field has constraints, so I would think it
should have value generators as well.

—
Reply to this email directly or view it on GitHub
#431 (comment)
.

[paterczm]

Since we decided to use backend functionality to handle the sequence, I don't think the interceptor is needed. Value will be generated by the database and sequence defined by lightblue-mongo (or other backend with sequence support). For the same reason did not make any changes in LightblueFactory.

Had to add some dependencies between lightblue-core modules, pls verify.

[bserdar]

Sequence, not Sequance

[paterczm]

Agreed :)

[paterczm]

Squashed commits to hide all the back and forth. Defined Sequence and SequenceSupport as generics (expecting one implementation per kind of sequence).