Github user afs commented on the issue:
https://github.com/apache/jena/pull/369
Yes, this is models passing down transactions. It only became possible
with dataset-transaction promotion (new to 3.7.0).
This all has a lot of knock on consequences. The wrap/create distinction is
quite important and that touches a lot of files; it is not reformatting. "wrap"
a model and the dataset can not have named graphs added, "create" with a model
and it starts with that model and can have named graphs added. We only used to
have "create" which has overhead and complexity as well as occasionally leading
to unexpected behaviour with SPARQL Updates (updates work but the new NG are
in-memory and disappear on restart - better to have a closed dataset and catch
the issue at update time).
While testing, I found lack of test coverage and integration testing, which
is the root of the users@ email that triggered this, was the place to put this.
There as a lack of assemblers for certain other special cases so I included
them as well as they arose naturally from checking test coverage.
---
