org

- debug logging for the programming model and its refiners

- also adds stubs for metamodel validation smoketesting with good and

bad domain-objects

- that is bootstrapping without any persistence layer

- its now the responsibility of any persistence plugin (like JDO) to

publish (newly introduced) PreStore and PostStore events on the

framework's eventbus

- TimestampingService is now re-implemented to simply listen for

PreStore events and then act on the persistable objects that are passed

over by these events

- TimestampingService was also de-coupled from any JDO specific code,

which allowed us to move it to the 'runtime' module

in case there are multiple configurations to pick from when

bootstrapping with Spring, picking one configuration class works just

fine if the other are not auto-discovered by Spring's package scanning;

so the solution is to move any Spring configuration beans out of the

scanned package hierarchy

this commit does this for 'smoketests' and 'simpleapp' by moving the

config beans into xxx.conf packages that are out of scanning scope

- BuilderScriptWithResult

- BuilderScriptWithoutResult

to further simplify persona declarations

see for example usage

https://github.com/apache/isis/blob/v2/examples/smoketests/src/main/java/org/apache/isis/testdomain/jdo/JdoTestDomainPersona.java

- for now we are simply utilizing the 'common' ForkJoinPool, but users

might need more control here!

- simple smoketest added to test async execution with the 'wrapper'

- also bumps h2/hsqldb to their latest versions

consecutive smoketest runs might run into an issue with jdo/schema

creation failing due to schema not found, but running test classes

individually does work

- several principal and related objects have been improved to procude

less stress on the heap

- smoketests added that also test for the absence of a HttpSession when

using basic-auth strategy against a rest endpoint

- also moves the new restclient introduced with v2 from applib to a new

extension module 'restclient'

- improvements to the restclient to also handle scalar value types

- we now have the infrastructure to reproduce the memory leak issue

- also adds an optimization to the IsisModuleSecurityRealm, to not

authenticate a user twice per request

findings so far, PrincipalForApplicationUser indeed does not get garbage

collected