You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2017/04/03 23:29:51 UTC
[37/59] [abbrv] [partial] isis-site git commit: ISIS-1521: deletes
content-OLDSITE
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/isis-1.5.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/isis-1.5.0.md b/content-OLDSITE/core/release-notes/isis-1.5.0.md
deleted file mode 100644
index 2e0e202..0000000
--- a/content-OLDSITE/core/release-notes/isis-1.5.0.md
+++ /dev/null
@@ -1,64 +0,0 @@
-Title: isis-1.5.0
-
-<h2> New Feature
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-550'>ISIS-550</a>] - Complete the guava EventBus support with new annotations
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-776'>ISIS-776</a>] - FixtureScripts service as means of doing fixture management for end-to-end stories.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-786'>ISIS-786</a>] - Allow event bus subscribers to veto interactions by throwing a RecoverableException or NonRecoverableException
-</li>
-</ul>
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-569'>ISIS-569</a>] - Fix JMock to support JDK7 (JavassistImposteriser)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-745'>ISIS-745</a>] - Do not suppress the org.apache.isis classes from the "download metamodel" action (as provided by DeveloperUtilities service)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-749'>ISIS-749</a>] - Make logging less noisy for selected classes
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-762'>ISIS-762</a>] - For commands on contributed actions, the target and "user friendly" target details should be captured as the contributee, not the contributed service.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-765'>ISIS-765</a>] - Allow UserMemento#hasRole to match on wildcards
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-770'>ISIS-770</a>] - Remove dependency on wicket-ioc (because brings in cglib/asm dependency)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-772'>ISIS-772</a>] - Reimplement WrapperFactory to use javassist instead of cglib/asm (for Java7 support)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-782'>ISIS-782</a>] - Integration testing framework should automatically install the FixtureClock singleton rather than the regular Clock
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-783'>ISIS-783</a>] - Integration test support enhancements
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-795'>ISIS-795</a>] - disable persistence-by-reachability-at-commit in the archetypes.
-</li>
-</ul>
-
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-758'>ISIS-758</a>] - Auditing should be able to cope with a change to a property where the referenced object has been deleted.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-759'>ISIS-759</a>] - Transient errors being logged as result of incorrect call to sendRedirect; not sure why, need diagnostics.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-760'>ISIS-760</a>] - IllegalStateException when commands/audit enabled in Estatio and failing to persist the Oid of a view model.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-769'>ISIS-769</a>] - IsisTransaction should do a "precommit" for pending updates to applib services, prior to commiting the underlying (JDO) transaction.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-777'>ISIS-777</a>] - RO Viewer is not thread-safe for concurrent requests.
-</li>
-</ul>
-
-
-<h2> Task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-751'>ISIS-751</a>] - Update NOTICE copyright dates
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-792'>ISIS-792</a>] - Tidy-up tasks for Isis 1.5.0 release
-</li>
-</ul>
-
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/isis-1.6.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/isis-1.6.0.md b/content-OLDSITE/core/release-notes/isis-1.6.0.md
deleted file mode 100644
index e1f83e7..0000000
--- a/content-OLDSITE/core/release-notes/isis-1.6.0.md
+++ /dev/null
@@ -1,81 +0,0 @@
-Title: isis-1.6.0
-
-<i>Isis core 1.6.0 also incorporates the Restful Objects viewer, Shiro Security and JDO Objectstore.</i>
-
-<h2> New Feature
-</h2>
-
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-493'>ISIS-493</a>] - Annotation to identify domain services/repositories
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-800'>ISIS-800</a>] - Wizard-like form for Wicket viewer
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-813'>ISIS-813</a>] - Provide the ability to mock out domain services in integration tests.
-</li>
-</ul>
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-421'>ISIS-421</a>] - Write TCK tests for Restful Objects viewer
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-574'>ISIS-574</a>] - Upgrade isis-security-shiro to use shiro 1.2.3 (currently using 1.2.1)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-798'>ISIS-798</a>] - Minor improvements in support of integration testing.
-</li>
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-823'>ISIS-823</a>] - Restructure Todo's tests, nested static classes.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-827'>ISIS-827</a>] - Introduce WrappingObject, with more unique method names, as a replacement for WrappedObject.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-831'>ISIS-831</a>] - Extend (custom) EventBus vetoing logic so that can also encompass hide, disable, validate.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-832'>ISIS-832</a>] - Move jdo, shiro and restful into core
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-833'>ISIS-833</a>] - Break out applib and JDO services into modules
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-838'>ISIS-838</a>] - Provide an additional hook method for AbstractIsisSessionTemplate that automatically sets up the transaction.
-</li>
-</ul>
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-796'>ISIS-796</a>] - lifecycle callback "updating()" is not firing
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-797'>ISIS-797</a>] - 'Restful objects' decodes json request body while this is not
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-801'>ISIS-801</a>] - Action method taking domain object paramater gets triggered automatically whenever instances of that object type is accessed
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-812'>ISIS-812</a>] - Isis 1.5 blob mapping broken for PostgreSQL (when set to null)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-818'>ISIS-818</a>] - wrapSkipRules does not execute action due to being hidden
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-821'>ISIS-821</a>] - Precision gets lost when double values are use in BigDecimal attributes
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-824'>ISIS-824</a>] - Generic repository is broken
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-828'>ISIS-828</a>] - Wrapping an already wrapped object should honour the mode if different.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-836'>ISIS-836</a>] - Not certain that FixtureScripts' ClassDiscoveryService works when referencing deployed 1.5.0 JAR
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-840'>ISIS-840</a>] - "Permission groups" for IsisPermission (custom security string for Shiro) not working as advertised.
-</li>
-</ul>
-
-<h2> Dependency upgrade
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-716'>ISIS-716</a>] - Update to DN 3.3.8 (deferred)
-</li>
-</ul>
-
-<h2> Task (Core)
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-751'>ISIS-751</a>] - Update NOTICE copyright dates
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-839'>ISIS-839</a>] - 1.6.0 release tasks
-</li>
-</ul>
-
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/isis-1.7.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/isis-1.7.0.md b/content-OLDSITE/core/release-notes/isis-1.7.0.md
deleted file mode 100644
index cc568a1..0000000
--- a/content-OLDSITE/core/release-notes/isis-1.7.0.md
+++ /dev/null
@@ -1,111 +0,0 @@
-Title: isis-1.7.0
-
-
-<h2> New Feature
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-809'>ISIS-809</a>] - Provide implementation of ViewModelFacet that doesn't require explicit implementation of the IViewModel interface.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-873'>ISIS-873</a>] - CommandContext.getCommand() should also expose the ActionInteractionEvent.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-917'>ISIS-917</a>] - Support pluggable representations for the RO viewer (object and list representations)
-</li>
-</ul>
-
-
-<h2> Security fixes
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-846'>ISIS-846</a>] - Enhance ExceptionRecognizer so that the stack trace can be suppressed in certain circumstances (for security)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-895'>ISIS-895</a>] - HomePage should honour authorization rules.
-</li>
-</ul>
-
-
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-864'>ISIS-864</a>] - Command should be persisted if any dirty objects enlisted into transaction, in order to ensure no accidental orphans.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-866'>ISIS-866</a>] - Request-scoped service should be told when the request is starting and stopping.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-882'>ISIS-882</a>] - Appropriate facets should be copied over to contributed collections and properties.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-907'>ISIS-907</a>] - Enums drop-downs are truncated... the (derived) typical length for enums uses the name() rather than the toString()
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-908'>ISIS-908</a>] - Enhance FixtureScript service, support "non-strict" mode
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-916'>ISIS-916</a>] - Provide a mechanism so that framework-provided services, such as MementoService or BookmarkService, can be overridden by the developer.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-918'>ISIS-918</a>] - Remove special-case handling of DomainObjectContainer; is just another service.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-927'>ISIS-927</a>] - BookmarkService should be WrapperFactory aware...
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-805'>ISIS-805</a>] - (Mac and Linux) Class discovery service throws errors on startup
-</li>
-</ul>
-
-
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-404'>ISIS-404</a>] - Testing if a "wrapped" Domain Object has been persisted fails
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-643'>ISIS-643</a>] - FrameworkSynchronizer throws NPE on delete of child entity in 1-N relationship
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-852'>ISIS-852</a>] - Derived property cannot be written properly
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-871'>ISIS-871</a>] - NPE - ActionInvocationFacetForInteractionAbstract passes Null to "ObjectSpecification.isViewModelCloneable"
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-879'>ISIS-879</a>] - ObjectMemberAbstract#isAlwaysHidden() does not honour where=Where.EVERYWHERE.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-899'>ISIS-899</a>] - Can't return a view model in Isis 1.6.0 over RO viewer.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-905'>ISIS-905</a>] - Transaction handling fix, if throw exception on flush for no-arg action.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-912'>ISIS-912</a>] - Not possible to specify the fixtures to be loaded from the command line (ie --fixture flag is broken).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-919'>ISIS-919</a>] - Don't "touch" a (request-scoped) service when logging in DEBUG mode.
-</li>
-</ul>
-
-
-<h2> Removed features - available in <a href="http://www.isisaddons.org">isiaddons.org</a>
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-851'>ISIS-851</a>] - Remove modules from Isis core (available instead through isisaddons).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-887'>ISIS-887</a>] - Mothball the o.a.isis.core:isis-module-xxx modules, as now in isisaddons.
-</li>
-</ul>
-
-
-<h2> Removed features (obsolete)
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-802'>ISIS-802</a>] - Remove the ProfileStore component (in future, can raise a ProfileService as and when we identify a concrete reqt).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-913'>ISIS-913</a>] - Remove the "ViewerInstaller" and "EmbeddedWebServerInstaller" APIs, since in effect defunct.
-</li>
-</ul>
-
-
-<h2> Unreleased features (Implemented but then backed out)
-</h2>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-865'>ISIS-865</a>] - Either warn or fail-fast if an action is annotated with safe semantics but nevertheless results in dirty objects in the xactn.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-921'>ISIS-921</a>] - Disable "ensure safe semantics" feature (ISIS-865), since does not cater for edits with contributed properties.
-</li>
-
-
-<h2> Task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-872'>ISIS-872</a>] - 1.7.0 release activities
-</li>
-</ul>
-
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/isis-1.8.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/isis-1.8.0.md b/content-OLDSITE/core/release-notes/isis-1.8.0.md
deleted file mode 100644
index 2e06f6f..0000000
--- a/content-OLDSITE/core/release-notes/isis-1.8.0.md
+++ /dev/null
@@ -1,216 +0,0 @@
-Title: isis-1.8.0
-
-Note that Isis 1.8.0 now incorporates the Wicket viewer, which was previously a separately released component. Other components that are included in core (that were previously released separately are: the Restful Objects viewer, Shiro Security and the JDO/DataNucleus ObjectStore.
-
-<h2> New Feature
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-284'>ISIS-284</a>] - Maven plugin to validate domain object model w.r.t. Isis programming conventions
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-537'>ISIS-537</a>] - Convert Wicket viewer to use Bootstrap, so that it can be themed.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-690'>ISIS-690</a>] - 'Show all' button for tables.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-702'>ISIS-702</a>] - Provide new annotation/facet as a hint for the layout of the label for a property.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-703'>ISIS-703</a>] - Provide a switch in the Wicket viewer to make the positioning of a fields label either to the left or above the field.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-819'>ISIS-819</a>] - Wicket viewer should show the environment details so can distinguish if running in productnio vs UAT/systest/dev etc
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-854'>ISIS-854</a>] - Separator between for menu items
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-874'>ISIS-874</a>] - Allow individual items to stand out in a collection, eg new reserved method
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-901'>ISIS-901</a>] - Use @DomainService(repositoryFor=...) as the basis for an implementation of the IconFacet.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-930'>ISIS-930</a>] - Support use of "font awesome" icons as decoration of actions and also instead of entity icons.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-933'>ISIS-933</a>] - Allow the RO viewer to be configured so that it can honour or ignore UI hints (in particular, the @Render(EAGERLY) facet).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-951'>ISIS-951</a>] - Add menu separators (bootstrap dividers) when multiple services define actions on the same menu
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-956'>ISIS-956</a>] - Allow fa-icons to be specified using pattern matching on member names.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-963'>ISIS-963</a>] - Allow service actions to be rendered either on a primary, secondary or tertiary (the "me" icon) menu
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-964'>ISIS-964</a>] - Unify UI hints into @XxxLayout annotations with corresponding support in .layout.json for properties, collections and actions.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-967'>ISIS-967</a>] - Let the LayoutMetadataReader implementation(s) be configured using isis.properties.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-983'>ISIS-983</a>] - Embedded Neo4J support
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-985'>ISIS-985</a>] - Filter collections so that objects that are not visible to the current user are not shown.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-987'>ISIS-987</a>] - Provide some sort of mechanism to allow users to self-register for an Isis application.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-990'>ISIS-990</a>] - Optional UserProfileService to allow the user profile information to be customized.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-995'>ISIS-995</a>] - Allow the label of a property to be rendered as HTML. Also, allow the label of boolean panels to be rendered on the right hand side.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-999'>ISIS-999</a>] - Provide a log to administrator of which users logged in and logged out
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1000'>ISIS-1000</a>] - Allow objects to return CSS class (analogous to iconName() method) so that their presentation can be dynamically reflected in tables or on an object form.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1016'>ISIS-1016</a>] - Make it possible to use brand logo instead of plain text in the header
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1024'>ISIS-1024</a>] - Support imperative validation of a single action parameter argument (as well as of entire parameter args).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1027'>ISIS-1027</a>] - Raise metamodel validation exceptions if deprecated annotations or method prefixes are used.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1033'>ISIS-1033</a>] - Extend DomainObjectContainer, add isViewModel(...).
-</li>
-</ul>
-
-<h2> Improvement
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-568'>ISIS-568</a>] - Drop support for JDK 1.6, standardize on JDK 1.7.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-650'>ISIS-650</a>] - Nested Menu Support in Apache ISIS
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-705'>ISIS-705</a>] - Support actions accepting parameters that return Blobs/Clobs
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-755'>ISIS-755</a>] - Allow external system data to be integrated and managed with an Apache Isis domain object
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-779'>ISIS-779</a>] - Refactor EventBusService as a @RequestScoped service, and have it own the guava EventBus as a field.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-903'>ISIS-903</a>] - Improve i18n support (in NamedFacetDecorator etc) to honour client-side locale.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-931'>ISIS-931</a>] - Make Isis faster to start.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-934'>ISIS-934</a>] - RO JSON representations should only be pretty-printed if running in prototype mode.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-935'>ISIS-935</a>] - RO viewer should return a 404 exception if object not found.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-936'>ISIS-936</a>] - Incorporate the objectstore modules (JDO and in-memory) into core (metamodel and runtime)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-937'>ISIS-937</a>] - Move TCK out of core
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-938'>ISIS-938</a>] - Mothball the core-bytecode modules (as no longer used by either objectstore)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-939'>ISIS-939</a>] - Simplify Persistor and ObjectStore components.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-944'>ISIS-944</a>] - Minor improvements to TitleBuffer.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-948'>ISIS-948</a>] - Fix concurrent exception in EventBus, improve support for request-scoped services
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-950'>ISIS-950</a>] - Suppress stack trace from Error page if exception is recognised.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-953'>ISIS-953</a>] - Minor enhancements to Fixture script execution context
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-955'>ISIS-955</a>] - Merge JDO Java Type Mapping for Money.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-960'>ISIS-960</a>] - The event bus swallows errors thrown in the subscribers
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-968'>ISIS-968</a>] - Rationalize handling of menu actions and contributed actions
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-969'>ISIS-969</a>] - Create new @DomainServiceLayout annotation, and move UI hints out of @DomainService
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-970'>ISIS-970</a>] - Introduce new annotations to collect together all non-UI (layout) hints, and deprecate old annotations
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-972'>ISIS-972</a>] - Make it possible to set FontAwesome icons after the label for action links
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-973'>ISIS-973</a>] - Simplify the FixtureScript API so that child fixtures are executed using the ExecutionContext object
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-980'>ISIS-980</a>] - Do not render empty sub-menu sections in the tertiary actions menu panel
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-981'>ISIS-981</a>] - Should be able to use the wrapper factory when installing fixtures.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1002'>ISIS-1002</a>] - Recognize (JDO) exceptions for foreign key constraint violations
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1003'>ISIS-1003</a>] - Add "veto" as a simpler API for EventBusSubscribers
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1008'>ISIS-1008</a>] - Make it possible to stream Lobs after using the action prompt
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1012'>ISIS-1012</a>] - Use the same date and time format across tables and fields
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1014'>ISIS-1014</a>] - Modal window improvements
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1018'>ISIS-1018</a>] - Do not allow http session replacement in Wicket because Shiro knowledge becomes outdated
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1019'>ISIS-1019</a>] - Upgrade dependencies to javassist, org.reflections
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1026'>ISIS-1026</a>] - Upgrade jetty-console-maven-plugin to 1.56
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1032'>ISIS-1032</a>] - Contract test for bidirectional relationship can't handle overridden methods
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1036'>ISIS-1036</a>] - Inject services into Comparators specified in a @CollectionLayout(sortedBy=...) clause
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1038'>ISIS-1038</a>] - Extend ActionDomainEvent so that it provides the return value during the Executed phase.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1039'>ISIS-1039</a>] - XmlSnapshot.Builder interface missing the build() method...
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1040'>ISIS-1040</a>] - Extend FixtureScript / ExecutionContext with defaultParam / checkParam...
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1043'>ISIS-1043</a>] - Enhance fixture script framework with better support for parameters being passed between scripts.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1049'>ISIS-1049</a>] - Move Wicket viewer under core.
-</li>
-</ul>
-
-
-<h2> Bug
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-853'>ISIS-853</a>] - joda DateTime properties loose time when persisted
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-878'>ISIS-878</a>] - Wicket viewer escape does not dismiss some (though not all) action dialog boxes
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-881'>ISIS-881</a>] - Menu service ordering appears to be non-deterministic?
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-897'>ISIS-897</a>] - Wrong format for org.joda.time.LocalDateTime
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-911'>ISIS-911</a>] - The blob panel's "additionalLinks" (for upload and clear buttons) should be hidden in Edit mode.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-941'>ISIS-941</a>] - Wicket viewer shouldn't try to flush properties that are disabled.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-942'>ISIS-942</a>] - Auditing broken for deleted objects.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-943'>ISIS-943</a>] - ObjectContracts#equals should be more resilient.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-946'>ISIS-946</a>] - Isis application won't run from Eclipse
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-954'>ISIS-954</a>] - Duplicate menu items in the application menu
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-961'>ISIS-961</a>] - Throwing exception in application code does NOT abort the transaction (it should, of course).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-966'>ISIS-966</a>] - Restful viewer doesn't return a JSON representation when hits a 500 internally (instead getting an HTML page)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-971'>ISIS-971</a>] - Ignore anonymous classes which inherit from @DomainService (eg in integ tests).
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1010'>ISIS-1010</a>] - "Session already open" error if attempting to login in a second browser tab
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1011'>ISIS-1011</a>] - Select2 component doesn't filter the suggestions
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1017'>ISIS-1017</a>] - @PreDestroy annotated method is not called
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1029'>ISIS-1029</a>] - Hidden{where} in layout is not honored by table representations
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1030'>ISIS-1030</a>] - Not possible for a declarative view model (@ViewModel) to reference another view model/
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1041'>ISIS-1041</a>] - Under certain circumstances, appears that auditing can cause the same tuple to be audited within a single transaction.
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-1042'>ISIS-1042</a>] - Dropdown of Enums does not honour title() method
-</li>
-</ul>
-
-<h2> Task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-928'>ISIS-928</a>] - Isis 1.8.0 release tasks
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-959'>ISIS-959</a>] - Update Jackson dependency from 1.9.11 to 2.4.3
-</li>
-</ul>
-
-<h2> Sub-task
-</h2>
-<ul>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-512'>ISIS-512</a>] - Wicket: render icons for actions (if available)
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-556'>ISIS-556</a>] - Re-enable maven-enforcer-plugin before merging ISIS-537 branch to master
-</li>
-<li>[<a href='https://issues.apache.org/jira/browse/ISIS-876'>ISIS-876</a>] - Action prompt dialog box rendering when title too long...
-</li>
-</ul>
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/migrating-to-1.6.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/migrating-to-1.6.0.md b/content-OLDSITE/core/release-notes/migrating-to-1.6.0.md
deleted file mode 100644
index 635c2a6..0000000
--- a/content-OLDSITE/core/release-notes/migrating-to-1.6.0.md
+++ /dev/null
@@ -1,113 +0,0 @@
-Title: Migrating from v1.5.0 to v1.6.0
-
-In v1.6.0 we've started work on simplifying and also modularizing the framework. Specifically:
-
-* [ISIS-832](https://issues.apache.org/jira/browse/ISIS-832) - to simplify the framework by bringing Restful Objects viewer, the JDO/DataNucleus objectstore and Shiro Security into Isis Core, and
-* [ISIS-833](https://issues.apache.org/jira/browse/ISIS-833) - to factor out re-usable modules from existing services (primarily the JDO auditing, publishing and command services).
-
-This has resulted in a number of Maven modules being renamed, added or removed. This will necessarily impact existing applications, requiring changes to existing `pom.xml` files. To minimize the migration effort, and to reduce risk, no classes/packages have been renamed.
-
-This approach does mean that there are now mismatches between package names and modules, but better to go with baby steps. In any case, Isis tries to follow semantic versioning, which means that the time to rationalize such matters is in Isis 2.0, not in the 1.6.x baseline.
-
-Another related change in 1.6.0 is [ISIS-493](https://issues.apache.org/jira/browse/ISIS-493), which introduces a new annotation called `@DomainService`. This allows services to be automatically registered (rather than have to register in `WEB-INF/isis.properties`).
-
-
-### Summary of changes
-
-components moved to core:
-
-* `o.a.i.security:isis-security-shiro` -> `o.a.i.core:isis-core-security-shiro`
-
-* `o.a.i.objectstore:isis-objectstore-jdo` -> DELETED (modules now parented by core directly)
-* `o.a.i.objectstore:isis-objectstore-jdo-applib` -> DELETED; see the new `isis-module-xxx` modules below
-* `o.a.i.objectstore:isis-objectstore-jdo-metamodel` -> `o.a.i.core:isis-core-objectstore-jdo-metamodel`
-* `o.a.i.objectstore:isis-objectstore-jdo-datanucleus` -> `o.a.i.core:isis-core-objectstore-jdo-datanucleus`
-
-* `o.a.i.viewer:isis-viewer-restfulobjects` -> DELETED (modules now parented by core directly)
-* `o.a.i.viewer:isis-viewer-restfulobjects-rendering` -> `o.a.i.core:isis-core-viewer-restfulobjects-rendering`
-* `o.a.i.viewer:isis-viewer-restfulobjects-server` -> `o.a.i.core:isis-core-viewer-restfulobjects-server`
-
-new modules:
-
-* `o.a.i.module:isis-module-settings`
- * this has `applib` and `impl` as submodules
- * application and user settings
-* `o.a.i.module:isis-module-devutils`
- * this has `applib` and `impl` as submodules
- * developer utilities service (download metamodel etc)
-* `o.a.i.module:isis-module-audit-jdo`
- * persisting `AuditEntry` entity
-* `o.a.i.module:isis-module-background`
- * scheduling background commands
-* `o.a.i.module:isis-module-command-jdo`
- * persisting `Command` entity and enabling background commands via scheduler
-* `o.a.i.module:isis-module-publishing-jdo`
- * persisting `PublishedEvent` entity
-* `o.a.i.module:isis-module-publishingeventserializer-ro`
- * used by publishing service to serialize object graph into JSON
-
-The reason that the first two modules have their own applib but the last four do not is because the latter four will be used by the framework if configured, eg to publish audit events. Their APIs are therefore defined in Isis' own applib. In contrast, the settings and devutils modules are not used or referenced in any capacity by the framework.
-
-
-### Impact to existing applications
-
-in `root/pom.xml`
-
-* remove dependency to `o.a.i.security:isis-security-shiro` (now parented by core parent pom).
-* remove dependency to `o.a.i.objectstore:isis-objectstore-jdo` (this is a deleted parent pom, child modules referenced instead by core parent pom).
-* remove dependency to `o.a.i.viewer:isis-viewer-restfulobjects` (this is a deleted parent pom, child modules referenced instead by core parent pom).
-
-in `dom/pom.xml`
-
-* delete dependency to `o.a.i-objectstore:isis-objectstore-jdo-applib`
-
-* add in dependencies (if used) to
- * `o.a.i.module:isis-module-settings-applib`
- * `o.a.i.module:isis-module-devutils-applib`
-
-in `webapp/pom.xml`
-
-* add in dependencies (if used) to:
- * `o.a.i.module:isis-module-audit-jdo`
- * `o.a.i.module:isis-module-background`
- * `o.a.i.module:isis-module-command-jdo`
- * `o.a.i.module:isis-module-publishing-jdo`
- * `o.a.i.module:isis-module-publishingeventserializer-ro`
- * `o.a.i.module:isis-module-devutils-impl`
- * `o.a.i.module:isis-module-settings-impl-jdo`
-
-in `webapp/src/main/webapp/WEB-INF/isis.properties`
-
-* enable `@DomainService` support using:
-
-<pre>
- isis.services-installer=configuration-and-annotation
- isis.services.ServicesInstallerFromAnnotation.packagePrefix=\
- com.mycompany.foo,com.mycompany.bar
-</pre>
-
-* for the `isis.services` key:
-
- * add (if required):
- * `org.apache.isis.applib.services.bookmark.BookmarkHolderActionContributions`
- * `org.apache.isis.objectstore.jdo.applib.service.background.BackgroundCommandServiceJdoContributions`
-
- * remove (since now automatically registered via `@DomainService`):
- * `org.apache.isis.objectstore.jdo.datanucleus.service.support.IsisJdoSupportImpl`
- * `org.apache.isis.objectstore.jdo.datanucleus.service.eventbus.EventBusServiceJdo`
- * `org.apache.isis.objectstore.jdo.applib.service.background.BackgroundCommandServiceJdo`
- * `org.apache.isis.objectstore.jdo.applib.service.command.CommandServiceJdo`
- * `org.apache.isis.objectstore.jdo.applib.service.command.CommandServiceJdoRepository`
- * `org.apache.isis.objectstore.jdo.applib.service.background.BackgroundCommandServiceJdoRepository`
- * `org.apache.isis.objectstore.jdo.applib.service.audit.AuditingServiceJdo`
- * `org.apache.isis.objectstore.jdo.applib.service.audit.AuditingServiceJdoRepository`
- * `org.apache.isis.objectstore.jdo.applib.service.publish.PublishingService`
- * `org.apache.isis.objectstore.jdo.applib.service.publish.PublishingServiceJdoRepository`
- * `org.apache.isis.viewer.restfulobjects.rendering.eventserializer.RestfulObjectsSpecEventSerializer`
-
-
-It is still necessary to:
-
-* explicitly register any service (`*Contributions`) that affects the UI
-* explicitly register `ExceptionRecognizerCompositeForJdoObjectStore` (as is desgned to be optionally subclassed)
-* explicitly register `ApplicationSettings`, `UserSettings` and `DeveloperUtilities` services (each is designed to be optionally subclassed)
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/migrating-to-1.7.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/migrating-to-1.7.0.md b/content-OLDSITE/core/release-notes/migrating-to-1.7.0.md
deleted file mode 100644
index ce82f3e..0000000
--- a/content-OLDSITE/core/release-notes/migrating-to-1.7.0.md
+++ /dev/null
@@ -1,187 +0,0 @@
- Title: Migrating from v1.6.0 to 1.7.0
-
-In v1.7.0 we've continued the work started in [1.6.0](migrating-to-1.6.0.html) in modularizing the framework. The most important change to note is that all Isis core modules (with the Maven `groupId` of `org.apache.isis.module` have now MOVED to [http://www.isisaddons.org](Isis Addons).
-
-In addition, we've retired some obsolete (and unused) functionality, specifically the `ProfileStore` component.
-
-To move up amounts to changing POM files and, where required, updating package names for any referenced modules.
-
-## Reorganized 'modules' ##
-
-The following modules are no longer released as part of Isis core and have moved to Isis Addons (or in one case, back into Isis core).
-
-Minor changes are required to `pom.xml` files and (in some cases) to `isis.properties` config file.
-
-In one or two exceptional cases it may be necessary to fix up import statements if there are reference to changed package/class names in code (most likely any dependency on the `devutils` module or `settings` module).
-
-### Audit module ###
-
-In `pom.xml`, replace:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-audit-jdo</artifactId>
- </dependency>
-
-with:
-
- <dependency>
- <groupId>org.isisaddons.module.audit</groupId>
- <artifactId>isis-module-audit-dom</artifactId>
- </dependency>
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-### Command module ###
-
-In `pom.xml`, replace:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-command-jdo</artifactId>
- </dependency>
-
-with:
-
- <dependency>
- <groupId>org.isisaddons.module.command</groupId>
- <artifactId>isis-module-command-dom</artifactId>
- </dependency>
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-### DevUtils module ###
-
-In `pom.xml`, replace:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-devutils-applib</artifactId>
- </dependency>
-
-with:
-
- <dependency>
- <groupId>org.isisaddons.module.devutils</groupId>
- <artifactId>isis-module-devutils-dom</artifactId>
- </dependency>
-
-Remove any references to:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-devutils</artifactId>
- </dependency>
-
-or to:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-devutils-impl</artifactId>
- </dependency>
-
-These modules are no longer required (the `org.apache.isis.module:isis-module-devutils-applib`
-and `org.apache.isis.module:isis-module-devutils-impl` submodules have been combined
-into the new `org.isisaddons.module.devutils:isis-module-devutils-dom` module).
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-### Publishing module ###
-
-In `pom.xml`, replace:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-publishing-jdo</artifactId>
- </dependency>
-
-with:
-
- <dependency>
- <groupId>org.isisaddons.module.publishing</groupId>
- <artifactId>isis-module-publishing-dom</artifactId>
- </dependency>
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-### Publishing Event Serializer RO module ###
-
-Remove any references to:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-publishingeventserializer-ro</artifactId>
- </dependency>
-
-This module has been merged with `org.isisaddons.module.publishing:isis-module-publishing-dom`, above.
-
-### Settings module ###
-
-In `pom.xml`, replace:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-settings-applib</artifactId>
- </dependency>
-
-with:
-
- <dependency>
- <groupId>org.isisaddons.module.settings</groupId>
- <artifactId>isis-module-settings-dom</artifactId>
- </dependency>
-
-Remove any references to:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-settings</artifactId>
- </dependency>
-
-or to:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-settings-impl</artifactId>
- </dependency>
-
-These modules are no longer required (the `org.apache.isis.module:isis-module-settings-applib`
-and `org.apache.isis.module:isis-module-settings-impl` submodules have been combined
-into the new `org.isisaddons.module.settings:isis-module-settings-dom` module).
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-### Background module ###
-
-In `pom.xml`, remove:
-
- <dependency>
- <groupId>org.apache.isis.module</groupId>
- <artifactId>isis-module-background</artifactId>
- </dependency>
-
-The service classes have been moved into existing `org.apache.isis.core:isis-core-runtime` Maven module (that is, already be referenced in the `pom.xml`).
-
-If necessary, also update any services registered in `isis.properties` (package/class names may have changed slightly).
-
-
-## Retired `ProfileStore` component ##
-
-As per <a href='https://issues.apache.org/jira/browse/ISIS-802'>ISIS-802</a>, the ProfileStore component has been removed. This functionality was not surfaced or available in the Wicket or Restful Objects viewers, so there is no meaningful loss of functionality. However, Maven `pom.xml` files will require updating:
-
-Specifically, remove any dependencies on `org.apache.isis:isis-core-profilestore`:
-
- <dependency>
- <groupId>org.apache.isis.core</groupId>
- <artifactId>isis-core-profilestore</artifactId>
- </dependency>
-
-A number of corresponding classes/interfaces have also been removed from the Isis applib:
-
-* `org.apache.isis.applib.fixtures.userprofile.UserProfileService`
-* `org.apache.isis.applib.fixtures.userprofile.UserProfileServiceAware`
-* `org.apache.isis.applib.fixtures.UserProfileFixture`
-* `org.apache.isis.applib.profiles.Profile`
-* `org.apache.isis.applib.profiles.Perspective`
-
-It is highly unlikely that any existing production code references these classes.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/release-notes/migrating-to-1.8.0.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/release-notes/migrating-to-1.8.0.md b/content-OLDSITE/core/release-notes/migrating-to-1.8.0.md
deleted file mode 100644
index 118b6ee..0000000
--- a/content-OLDSITE/core/release-notes/migrating-to-1.8.0.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Title: Migrating from v1.7.0 to 1.8.0
-
-Existing projects written against v1.7.0 should run against v1.8.0 without any changes. In particular (unlike 1.6.0 and
- 1.7.0) there should be no need to update `pom.xml` files of existing projects. If you *do* encounter any difficulties
-then let us know via the [users mailing list](../../support.html), so we can support you and document issues here.
-
-That said, many of the existing annotations have been deprecated in 1.8.0, replaced with a simplified and rationalized
- set of annotations; see [here](../../reference/recognized-annotations/about.html). To help you migrate your application
- over to the new annotations, there is a new configuration property that can be set in `isis.properties`:
-
- isis.reflector.validator.allowDeprecated=false
-
-If this flag is present and set to false, then metamodel validation errors will be thrown on startup if any deprecated
-annotations are encountered. These can be viewed either in the console or by browsing to the app (an error page will
-be displayed).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/runtime.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/runtime.md b/content-OLDSITE/core/runtime.md
deleted file mode 100644
index 4044741..0000000
--- a/content-OLDSITE/core/runtime.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Title: Core Runtime
-
-{stub
-This page is a stub.
-}
-
-This module implements the object lifecycle management. It defines the `ObjectStore` API (and other related APIs) and delegates persistence of objects to the object store components.
-
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/specsupport-and-integtestsupport.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/specsupport-and-integtestsupport.md b/content-OLDSITE/core/specsupport-and-integtestsupport.md
deleted file mode 100644
index 49e7bf3..0000000
--- a/content-OLDSITE/core/specsupport-and-integtestsupport.md
+++ /dev/null
@@ -1,318 +0,0 @@
-Title: BDD Specs and Integration testing Support
-
-[//]: # (content copied to _user-guide_testing_bdd-spec-support)
-
-> This new feature replaces the integration test support provided in 1.2.0. Please note that some small changes to your tests will be required.
-
-## Concepts ##
-
-The `isis-core-specsupport` and `isis-core-integtestsupport` modules provide the ability to bootstrap Isis and run either BDD specifications
-or regular integration tests.
-
-* In the case of BDD specs, these are run using [Cucumber-JVM](https://github.com/cucumber/cucumber-jvm), the Java port of the original Ruby [Cucumber](http://cukes.info) tool.
-
- Specifications are written in the [Gherkin](https://github.com/cucumber/cucumber/wiki/Gherkin) DSL, following the ["given/when/then"](https://github.com/cucumber/cucumber/wiki/Given-When-Then) format. Cucumber-JVM itself is a JUnit runner, and searches for [feature files](https://github.com/cucumber/cucumber/wiki/Feature-Introduction) on the classpath. These in turn are matched to [step definition](http://cukes.info/step-definitions.html)s through regular expressions. It is the step definitions (the "glue") that exercise the system.
-
-* In the case of integration tests, these are run using JUnit.
-
-To untangle the above a little: in terms of lines of code to be written, the code that goes in step definitions is broadly the same as the code that goes in an integration test method. The benefit of the former is that the given/then/when scenarios feature file describe the context of the interaction, and the step definitions are reusable across scenarios.
-
-There are some key framework classes that make up the spec/integtest support; these are discussed below.
-
-### IsisSystemForTest ###
-
-To support both BDD specs and integration tests, Isis provides the `IsisSystemForTest` class. This allows a complete running instance of Isis to be bootstrapped (usually with the JDO objectstore), and then held on a `ThreadLocal` from one test to another.
-
-Typically bootstrapping code is used to lazily instantiate the `IsisSystemForTest` once and once only. The mechanism for doing this is line-for-line identical in both BDD step defs and integration tests.
-
-
-### ScenarioExecution ###
-
-Isis also provides a `ScenarioExecution` class. The purpose of this class is to provide a context under which the specification or an integration test is executing.
-
-For both BDD specs and integration tests, the `ScenarioExecution` also provides access to the configured domain services (accessible through the `service(...)` method) and the `DomainObjectContainer` (through the `container()` method).
-
-In addition, UI behaviour can be integration tested by "wrapping" each domain object in a proxy. This proxy ensures that the "see it/use it/do it" rules (ie to hide, disable, or validate) are enforced. The wrapping is performed using the `WrapperFactory`, part of the [isis-core-wrapper](../reference/services/wrapper-factory.html) module. The `ScenarioExecution`'s `wrap()` and `unwrap()` helper methods provide access to this capability.
-
-The `ScenarioExecution` also provides the `install()` method, allowing fixtures to be installed in the normal way. If using the JDO Object store, then these fixtures the `IsisJdoSupport` service can be used to run arbitrary SQL against the underlying database (eg to truncate/delete existing tables as need be).
-
-Of relevance only to BDD specs, the `ScenarioExecution`'s `getVar()` and `putVar()` methods also allow variables to be passed from one step definition to the next. (Broadly speaking, this is the same as the "World" object in Ruby-flavoured Cucumber).
-
-Like the `IsisSystemForTest` class, the `ScenarioExecution` class also binds an instance of itself onto a `ThreadLocal`. It can then be accessed in both BDD step defs and in integration tests using `ScenarioExecution.current()` static method.
-
-### CukeGlueAbstract and IntegrationTestAbstract ###
-
-The `CukeGlueAbstract` acts as a convenience superclass for writing BDD step definitions. Similarly, the `IntegrationTestAbstract` acts as a convenience subclass for writing integration tests. These two classes are very similar in that they both delegate to an underlying `ScenarioExecution`.
-
-### Separate Glue from Specs ###
-
-The "glue" (step definitions) are intended to be reused across features. We therefore recommend that they reside in a separate package, and are organized by the entity type upon which they act.
-
-For example, given a feature that involves `Customer` and `Order`, have the step definitions pertaining to `Customer` reside in `CustomerGlue`, and the step definitions pertaining to `Order` reside in `OrderGlue`.
-
-The Cucumber-JVM spec runner allows you to indicate which package(s) should be recursively searched to find any glue.
-
-### Integration- vs Unit- Scope
-
-Although BDD specs are most commonly used for end-to-end tests (ie at the same scope as an integration test), the two concerns (expressability of a test to a business person vs granularity of the test) should not be conflated. There are a couple of [good](http://silkandspinach.net/2013/01/18/a-testing-strategy/) blog [posts](http://claysnow.co.uk/the-testing-iceberg/) discussing [this](http://claysnow.co.uk/living-documentation-can-be-readable-and-fast/). The basic idea is to avoid the overhead of a heavy-duty integration test if possible.
-
-Isis takes inspiration from these to optionally allow BDD specs to be run at a unit scope. The scope is indicated by annotating the scenario with the `@unit` or `@integration` tags.
-
-When running under unit-level scope, the Isis system is *not* instantiated. Instead, `ScenarioExecution` class returns JMock mocks (except for the `WrapperFactory`, if configured).
-
-Writing a BDD spec that supports both modes of operation therefore takes more effort, but the benefit is a (much) faster executing test suite. Writing to support both modes means that the developer/tester can easily check the scenario at both scopes just by altering the tag.
-
-To support unit-testing, Isis provides the `InMemoryDB` class; a glorified hashmap of "persisted" objects. Use of this utility class is optional.
-
-## Usage
-
-The following examples are taken from the [todoapp](https://github.com/apache/isis/tree/master/example/application/todoapp); in particular from that project's [integration test](https://github.com/apache/isis/tree/master/example/application/todoapp/integtests/src/test/java) module.
-
-
-### Root pom ###
-
-In the root [`pom.xml`](https://github.com/apache/isis/blob/master/example/application/todoapp/pom.xml), we recommend that you update the `maven-surefire-plugin` patterns, so that BDD specs are recognised alongside unit and integration tests:
-
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-plugin</artifactId>
- <version>2.10</version>
- <configuration>
- <includes>
- <include>**/*Test.java</include>
- <include>**/*Test_*.java</include>
- <include>**/*Spec*.java</include>
- </includes>
- <excludes>
- <exclude>**/Test*.java</exclude>
- <exclude>**/*ForTesting.java</exclude>
- <exclude>**/*Abstract*.java</exclude>
- </excludes>
- <useFile>true</useFile>
- <printSummary>true</printSummary>
- <outputDirectory>${project.build.directory}/surefire-reports</outputDirectory>
- </configuration>
- </plugin>
-
-### Integration testing module ###
-
-Assuming you have a module for your integration tests, add in the dependencies:
-
- <dependency>
- <groupId>org.apache.isis.core</groupId>
- <artifactId>isis-core-specsupport</artifactId>
- </dependency>
- <dependency>
- <groupId>org.apache.isis.core</groupId>
- <artifactId>isis-core-integtestsupport</artifactId>
- </dependency>
-
-There is no need to explicitly add in a dependency on `isis-core-wrapper`; this is done automatically.
-
-### Writing an Integration test ###
-
-Integration tests should subclass from `IntegrationTestAbstract`. For example, here's a the [`ToDoItemTest_completed`](https://github.com/apache/isis/blob/master/example/application/todoapp/integtests/src/test/java/integration/tests/actions/ToDoItemTest_completed.java) test which exercises of the `ToDoItem`'s `completed()` action:
-
-
- public class ToDoItemTest_completed {
-
- @BeforeClass
- public static void initClass() {
- PropertyConfigurator.configure("logging.properties");
- ToDoSystemInitializer.initIsft();
-
- // instantiating will install onto ThreadLocal
- new ScenarioExecutionForIntegration();
- }
-
- private ToDoItem toDoItem;
-
- @Before
- public void setUp() throws Exception {
- scenarioExecution().install(new ToDoItemsFixture());
-
- final List<ToDoItem> all = wrap(service(ToDoItems.class)).notYetComplete();
- toDoItem = wrap(all.get(0));
- }
-
- @Test
- public void happyCase() throws Exception {
- assertThat(toDoItem.isComplete(), is(false));
- toDoItem.completed();
- assertThat(toDoItem.isComplete(), is(true));
- }
-
- @Test
- public void cannotCompleteIfAlreadyCompleted() throws Exception {
- unwrap(toDoItem).setComplete(true);
- expectedExceptions.expectMessage("Already completed");
- toDoItem.completed();
- }
-
- @Test
- public void cannotSetPropertyDirectly() throws Exception {
- expectedExceptions.expectMessage("Always disabled");
- toDoItem.setComplete(true);
- }
- }
-
-The [ToDoItemsFixture](https://github.com/apache/isis/blob/master/example/application/todoapp/fixture/src/main/java/fixture/todo/ToDoItemsFixture.java) referenced above tears down data as well as installs new data. In this example it runs at the class level (`@BeforeClass`), but it can also run at the instance level (`@Before`).
-
-Note also that when the `ToDoItem` is wrapped, it is not possible to call `setComplete()` directly on the object; but when it is unwrapped then this call can be made as per normal.
-
-The [ToDoSystemInitializer](https://github.com/apache/isis/blob/master/example/application/todoapp/integtests/src/test/java/integration/ToDoSystemInitializer.java) class referenced above is responsible for setting up the `IsisSystemForTest`. You can think of it as being broadly equivalent to the information that is in the regular `isis.properties` file:
-
- public class ToDoSystemInitializer {
-
- public static IsisSystemForTest initIsft() {
- IsisSystemForTest isft = IsisSystemForTest.getElseNull();
- if(isft == null) {
- isft = new ToDoSystemBuilder().build().setUpSystem();
- IsisSystemForTest.set(isft);
- }
- return isft;
- }
-
- private static class ToDoSystemBuilder extends IsisSystemForTest.Builder {
- public ToDoSystemBuilder() {
- withLoggingAt(Level.INFO);
- with(testConfiguration());
- with(new DataNucleusPersistenceMechanismInstaller());
- withServices(
- new ToDoItemsJdo(),
- new WrapperFactoryDefault(),
- new RegisterEntities(),
- new IsisJdoSupportImpl()
- );
- }
-
- private IsisConfiguration testConfiguration() {
- // ... elided ...
- }
- }
- }
-
-### Writing a BDD specification ###
-
-BDD specifications contain a few more parts:
-
-* a `XxxSpec.feature` file, describing the feature and the scenarios (given/when/then)s that constitute its acceptance criteria
-
-* a `RunSpecs.java` class file to run the specification (all boilerplate). This will run all `.feature` files in the same package or subpackages.
-
-* one or several `XxxGlue` constituting the step definitions to be matched against. These are normally placed in a separate package(s) to the specifications; the `glue` attribute of the Cucumber-JVM JUnit runner indicates which package(s) to search in.
-
-* a system initializer class. This can be reused with any integration tests (eg the `ToDoSystemInitializer` class, shown above).
-
-You may find it more convenient to place the `.feature` files in `src/test/java`, rather than `src/test/resources`. If you wish to do this, then your integration test module's `pom.xml` must contain:
-
- <build>
- <testResources>
- <testResource>
- <filtering>false</filtering>
- <directory>src/test/resources</directory>
- </testResource>
- <testResource>
- <filtering>false</filtering>
- <directory>src/test/java</directory>
- <includes>
- <include>**</include>
- </includes>
- <excludes>
- <exclude>**/*.java</exclude>
- </excludes>
- </testResource>
- </testResources>
- </build>
-
-Let's now look at the a specification for the `ToDoItem'`s "completed" feature. Firstly, the [`ToDoItemSpec_findAndComplete.feature`](https://github.com/apache/isis/blob/master/example/application/todoapp/integtests/src/test/java/integration/specs/todoitem/ToDoItemSpec_findAndComplete.feature):
-
- @ToDoItemsFixture
- Feature: Find And Complete ToDo Items
-
- @integration
- Scenario: Todo items once completed are no longer listed
- Given there are a number of incomplete ToDo items
- When I choose the first of the incomplete items
- And mark the item as complete
- Then the item is no longer listed as incomplete
-
-The `@ToDoItemsFixture` is a custom tag we've specified to indicate the prerequisite fixtures to be loaded; more on this in a moment. The `@integration` tag, meanwhile, says that this feature should be run with integration-level scope. (If we wanted to run at unit-level scope, the tag would be `@unit`).
-
-The [`RunSpecs`](https://github.com/apache/isis/blob/master/example/application/todoapp/integtests/src/test/java/integration/specs/todoitem/RunSpecs.java) class to run this feature (and any other features in this package or subpackages) is just boilerplate:
-
- @RunWith(Cucumber.class)
- @Cucumber.Options(
- format = {
- "html:target/cucumber-html-report",
- "json:target/cucumber.json"
- },
- glue={"classpath:com.mycompany.integration.glue"},
- strict = true,
- tags = { "~@backlog", "~@ignore" })
- public class RunSpecs {
- // intentionally empty
- }
-
-The JSON formatter allows integration with enhanced reports, for example as provided by [Masterthought.net](http://www.masterthought.net/section/cucumber-reporting) (screenshots at end of page). (Commented out) configuration for this is provided in the [simpleapp](../intro/getting-started/simpleapp-archetype.html) `integtests` module's [pom.xml](https://github.com/apache/isis/blob/07fe61ef3fb029ae36427f60da2afeeb931e4f88/example/application/simpleapp/integtests/pom.xml#L52).
-
-The bootstrapping of Isis can be moved into a [`BootstrappingGlue`](https://github.com/apache/isis/blob/07fe61ef3fb029ae36427f60da2afeeb931e4f88/example/application/simpleapp/integtests/src/test/java/domainapp/integtests/specglue/BootstrappingGlue.java#L26) step definition:
-
- public class BootstrappingGlue extends CukeGlueAbstract {
-
- @Before(value={"@integration"}, order=100)
- public void beforeScenarioIntegrationScope() {
- PropertyConfigurator.configure("logging.properties");
- SimpleAppSystemInitializer.initIsft();
-
- before(ScenarioExecutionScope.INTEGRATION);
- }
-
- @After
- public void afterScenario(cucumber.api.Scenario sc) {
- assertMocksSatisfied();
- after(sc);
- }
-
- // bootstrapping of @unit scope omitted
- }
-
-The fixture to run also lives in its own step definition, [`CatalogOfFixturesGlue`](https://github.com/apache/isis/blob/07fe61ef3fb029ae36427f60da2afeeb931e4f88/example/application/simpleapp/integtests/src/test/java/domainapp/integtests/specglue/CatalogOfFixturesGlue.java#L24):
-
- public class CatalogOfFixturesGlue extends CukeGlueAbstract {
-
- @Before(value={"@integration", "@SimpleObjectsFixture"}, order=20000)
- public void integrationFixtures() throws Throwable {
- scenarioExecution().install(new RecreateSimpleObjects());
- }
-
- }
-
-Note that this is annotated with a tag (`@SimpleObjectsFixture`) so that the correct fixture runs. (We might have a whole variety of these).
-
-The step definitions pertaining to `SimpleObject` domain entity then reside in the [`SimpleObjectGlue`](https://github.com/apache/isis/blob/07fe61ef3fb029ae36427f60da2afeeb931e4f88/example/application/simpleapp/integtests/src/test/java/domainapp/integtests/specglue/modules/simple/SimpleObjectGlue.java#L31) class. This is where the heavy lifting gets done:
-
- public class SimpleObjectGlue extends CukeGlueAbstract {
-
- @Given("^there are.* (\\d+) simple objects$")
- public void there_are_N_simple_objects(int n) throws Throwable {
- try {
- final List<SimpleObject> findAll = service(SimpleObjects.class).listAll();
- assertThat(findAll.size(), is(n));
- putVar("list", "all", findAll);
-
- } finally {
- assertMocksSatisfied();
- }
- }
-
- @When("^I create a new simple object$")
- public void I_create_a_new_simple_object() throws Throwable {
- service(SimpleObjects.class).create(UUID.randomUUID().toString());
- }
-
- }
-
-## BDD Tooling ##
-
-To help write feature files and generate step definitions, we recommend [Roberto Lo Giacco's Eclipse plugin](https://github.com/rlogiacco/Natural). For more information, see Dan's short [blog post](http://danhaywood.com/2013/07/05/cucumber-editors-in-eclipse/). It works very well. Of interest: this is implemented using [XText](http://www.eclipse.org/Xtext/).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/unittestsupport.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/unittestsupport.md b/content-OLDSITE/core/unittestsupport.md
deleted file mode 100644
index 35627ef..0000000
--- a/content-OLDSITE/core/unittestsupport.md
+++ /dev/null
@@ -1,165 +0,0 @@
-Title: Unit Test Support
-
-[//]: # (content copied to user-guide_testing_unit-test-support)
-
-This module provides unit test helpers for use by all other modules. There are also utilities that you may find useful in testing your domain objects:
-
-To use, update the `pom.xml`:
-
- <dependency>
- <groupId>org.apache.isis.core</groupId>
- <artifactId>isis-core-unittestsupport</artifactId>
- </dependency>
-
-
-##SortedSets Contract Test
-
-This contract test automatically checks that all fields of type `java.util.Collection` are declared as `java.util.SortedSet`. In other words, it precludes either `java.util.List` or `java.util.Set` from being used as a collection.
-
-
-For example, the following passes the contract test:
-
- public class Department {
-
- private SortedSet<Employee> employees = new TreeSet<Employee>();
-
- ...
- }
-
-whereas this would not:
-
- public class SomeDomainObject {
-
- private List<Employee> employees = new ArrayList<Employee>();
-
- ...
- }
-
-If using the JDO Objectstore then we strongly recommend that you implement this test, for several reasons:
-
-* First, `Set`s align more closely to the relational model than do `List`s. A `List` must have an additional index to specify order.
-
-* Second, `SortedSet` is preferable to `Set` because then the order is well-defined and predictable (to an end user, to the programmer).
-
- The [ObjectContracts](../reference/Utility.html) utility class substantially simplifies the task of implementing `Comparable` in your domain classes.
-
-* Third, if the relationship is bidirectional then JDO/Objectstore will automatically maintain the relationship. See [here](../components/objectstores/jdo/managed-1-to-m-relationships.html) for further discussion.
-
-To use the contract test, subclass `SortedSetsContractTestAbstract`, specifying the root package to search for domain classes.
-
-For example:
-
- public class SortedSetsContractTestAll extends SortedSetsContractTestAbstract {
-
- public SortedSetsContractTestAll() {
- super("org.estatio.dom");
- withLoggingTo(System.out);
- }
- }
-
-##Injected Services Method Contract Test
-
-It is quite common for some basic services to be injected in a project-specific domain object superclass; for example a `ClockService` might generally be injected everywhere:
-
- public abstract class EstatioDomainObject {
- protected ClockService clockService;
- public void injectClockService(ClockService clockService) {
- this.clockService = clockService;
- }
- }
-
-If a subclass inadvertantly overrides this method and provides its own `ClockService` field, then the field in the superclass will never initialized. As you might imagine, `NullPointerException`s could then arise.
-
-This contract test automatically checks that the `injectXxx(...)` method, to allow for injected services, is not overridable, ie `final`.
-
-To use the contract test, , subclass `SortedSetsContractTestAbstract`, specifying the root package to search for domain classes.
-
-For example:
-
- public class InjectServiceMethodMustBeFinalContractTestAll extends InjectServiceMethodMustBeFinalContractTestAbstract {
-
- public InjectServiceMethodMustBeFinalContractTestAll() {
- super("org.estatio.dom");
- withLoggingTo(System.out);
- }
- }
-
-
-##Bidirectional Contract Test
-
-This contract test automatically checks that bidirectional 1:m or 1:1 associations are being maintained correctly (assuming that they follow the [mutual registration pattern](../more-advanced-topics/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html)
-
-> *Note* If using the [JDO Object Store](../components/objectstores/jdo/about.html), then there is generally no need to programmatically maintain 1:m relationships (indeed it may introduce subtle errors). For more details, see [here](../components/objectstores/jdo/managed-1-to-m-relationships.html). Check out the [Eclipse templates](../intro/resources/editor-templates.html) for further guidance.
-
-For example, suppose that `ParentDomainObject` and `ChildDomainObject` have a 1:m relationship (`ParentDomainObject#children` / `ChildDomainObject#parent`), and also `PeerDomainObject` has a 1:1 relationship with itself (`PeerDomainObject#next` / `PeerDomainObject#previous`).
-
-The following will exercise these relationships:
-
- public class BidirectionalRelationshipContractTestAll
- extends BidirectionalRelationshipContractTestAbstract {
-
- public BidirectionalRelationshipContractTestAll() {
- super("org.apache.isis.core.unittestsupport.bidir",
- ImmutableMap.<Class<?>,Instantiator>of(
- ChildDomainObject.class, new InstantiatorForChildDomainObject(),
- PeerDomainObject.class, new InstantiatorSimple(PeerDomainObjectForTesting.class)
- ));
- withLoggingTo(System.out);
- }
- }
-
-The first argument to the constructor scopes the search for domain objects; usually this would be something like `"com.mycompany.dom"`.
-
-The second argument provides a map of `Instantiator` for certain of the domain object types. This has two main purposes. First, for abstract classes, it nominates an alternative concrete class to be instantiated. Second, for classes (such as `ChildDomainObject`) that are `Comparable` and are held in a `SortedSet`), it provides the ability to ensure that different instances are unique when compared against each other. If no `Instantiator` is provided, then the contract test simply attempts to instantiates the class.
-
-If any of the supporting methods (`addToXxx()`, `removeFromXxx()`, `modifyXxx()` or `clearXxx()`) are missing, the relationship is skipped.
-
-To see what's going on (and to identify any skipped relationships), use the `withLoggingTo()` method call. If any assertion fails then the error should be descriptive enough to figure out the problem (without enabling logging).
-
-The example tests can be found [here](https://github.com/apache/isis/tree/master/core/unittestsupport/src/test/java/org/apache/isis/core/unittestsupport/bidir).
-
-##JUnitRuleMockery2
-
-An extension to the JMock's `JunitRuleMockery`, providing a simpler API and also providing support for autowiring.
-
-For example, here we see that the class under test, an instance of `CollaboratingUsingSetterInjection`, is automatically wired up with its `Collaborator`:
-
- public class JUnitRuleMockery2Test_autoWiring_setterInjection_happyCase {
-
- @Rule
- public JUnitRuleMockery2 context = JUnitRuleMockery2.createFor(Mode.INTERFACES_AND_CLASSES);
-
- @Mock
- private Collaborator collaborator;
-
- @ClassUnderTest
- private CollaboratingUsingSetterInjection collaborating;
-
- @Test
- public void wiring() {
- assertThat(collaborating.collaborator, is(not(nullValue())));
- }
- }
-
-The example tests can be found [here](https://github.com/apache/isis/tree/master/core/unittestsupport/src/test/java/org/apache/isis/core/unittestsupport/jmocking)
-
-##ValueTypeContractTestAbstract
-
-Automatically tests that a custom value type implements `equals()` and `hashCode()` correctly.
-
-For example, testing JDK's own `java.math.BigInteger` can be done as follows:
-
- public class ValueTypeContractTestAbstract_BigIntegerTest extends ValueTypeContractTestAbstract<BigInteger> {
-
- @Override
- protected List<BigInteger> getObjectsWithSameValue() {
- return Arrays.asList(new BigInteger("1"), new BigInteger("1"));
- }
-
- @Override
- protected List<BigInteger> getObjectsWithDifferentValue() {
- return Arrays.asList(new BigInteger("2"));
- }
- }
-
-The example unit tests can be found [here](https://github.com/apache/isis/tree/master/core/unittestsupport/src/test/java/org/apache/isis/core/unittestsupport/value).
http://git-wip-us.apache.org/repos/asf/isis-site/blob/365806f1/content-OLDSITE/core/webserver.md
----------------------------------------------------------------------
diff --git a/content-OLDSITE/core/webserver.md b/content-OLDSITE/core/webserver.md
deleted file mode 100644
index afec972..0000000
--- a/content-OLDSITE/core/webserver.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Title: Webapp and Webserver Support
-
-[//]: # (content copied to _user-guide_xxx)
-
-{stub
-This page is a stub.
-}
-
-This module provides support for bootstrapping and running Isis as a web application.