Scenario: A user specifies mappings directly into the cache and uses that. As it stands now, issuing a saveMappings() would write all of these to the specified mapping context. This might mean that a user who has not set the mapping context (e.g. just using the single argument constructor) will now have mappings end up in the data context.

That might be desirable as a feature. Another possibility is to prevent writing to any other than a designated mapping context to prevent mappings from landing unintentionally in the data context.

This is not an issue for anyone yet, but I'm making a note to myself to think about this more deeply in Tupelo 2.5. Perhaps have to explicitly set the mapping context or throw an exception on saveMappings??