Versions Compared

Old Version 16

changes.mady.by.user Bob Harner

Saved on

compared with

New Version 17

changes.mady.by.user Howard Ship

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: ordere configurations implicit constraint

...

Null values, once ordered, are edited out (the List passed to the service builder method does not include any nulls). Again, they are allowed as placeholders, for the actual contributed objects to organize themselves around.

Since
since5.3

When using add() without any specific contraints, a default contraint is added: after the previously added element. These default constraints are only within a single contribution method, but makes it much easier to set the order of several related contributions. Note that the contributions will be ordered relative to each other and its possible that contributions by some other module or method may be interspersed between them.

Mapped Configurations

As discussed in the earlier examples, mapped configurations are also supported. The keys passed in must be unique. When conflicts occur, Tapestry will log warnings (identifying the source, in terms of invoked methods, of the conflict), and ignore the conflicting value.

...