You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by mg...@apache.org on 2015/11/12 21:02:11 UTC
[29/50] [abbrv] isis git commit: ISIS-1195: updating adocs,
removing references to 1.10.0-SNAPSHOT
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action.adoc
index 1470487..9c68b4e 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action.adoc
@@ -79,7 +79,7 @@ Currently this is only supported for no-arg actions.
(`NON_IDEMPOTENT`)
|the action's semantics (ie whether objects are modified as the result of invoking this action, and if so whether reinvoking the action would result in no further change; if not whether the results can be cached for the remainder of the request).
-The `...ARE_YOU_SURE` variants (1.10.0-SNAPSHOT) cause a confirmation dialog to be displayed in the xref:ug.adoc#_ug_wicket-viewer[Wicket viewer].
+The `...ARE_YOU_SURE` variants cause a confirmation dialog to be displayed in the xref:ug.adoc#_ug_wicket-viewer[Wicket viewer].
|xref:rg.adoc#_rg_annotations_manpage-Action_typeOf[`typeOf()`]
|(none)
@@ -93,33 +93,27 @@ For example:
[source,java]
----
public class ToDoItem {
- public static class CompletedEvent extends ActionDomainEvent<ToDoItem> { } // <1>
+ public static class CompletedEvent extends ActionDomainEvent<ToDoItem> { }
@Action(
command=CommandReification.ENABLED,
- commandExecuteIn=CommandExecuteIn.FOREGROUND, // <2>
- commandPersistence=CommandPersistence.NOT_PERSISTED, // <3>
+ commandExecuteIn=CommandExecuteIn.FOREGROUND, // <1>
+ commandPersistence=CommandPersistence.NOT_PERSISTED, // <2>
domainEvent=CompletedEvent.class,
- hidden = Where.NOWHERE, // <4>
- invokeOn = InvokeOn.OBJECT_ONLY, // <5>
+ hidden = Where.NOWHERE, // <3>
+ invokeOn = InvokeOn.OBJECT_ONLY, // <4>
publishing = Publishing.ENABLED,
semantics = SemanticsOf.IDEMPOTENT
)
public ToDoItem completed() { ... }
}
----
-<1> `1.10.0-SNAPSHOT`, can use no-arg constructor.
+<1> default value, so could be omitted
<2> default value, so could be omitted
<3> default value, so could be omitted
<4> default value, so could be omitted
-<5> default value, so could be omitted
-[NOTE]
-====
-Currently are you sure semantics (1.10.0-SNAPSHOT) only work for actions that take one or more parameters (that is, generate a dialog).
-====
-
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_domainEvent.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_domainEvent.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_domainEvent.adoc
index 6bbf130..8bce8b1 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_domainEvent.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_domainEvent.adoc
@@ -33,40 +33,25 @@ For example:
[source,java]
----
public class ToDoItem {
- public static class CompletedEvent extends ActionDomainEvent<ToDoItem> { // <1>
- private static final long serialVersionUID = 1L;
- public CompletedEvent( // <2>
- final ToDoItem source, // <3>
- final Identifier identifier, // <4>
- final Object... arguments) { // <5>
- super("completed", source, identifier, arguments);
- }
- }
+ public static class CompletedEvent extends ActionDomainEvent<ToDoItem> { } // <1>
@Action(domainEvent=CompletedEvent.class)
public ToDoItem completed() { ... }
}
----
-<1> inherit from `ActionDomainEvent<T>` where `T` is the type of the domain object being interacted with.
-<2> constructor called reflectively by the framework
-<3> populated with the object being interacted with (the source of the event)
-<4> identifier of the collection
-<5> action argument(s)
-The benefit is that subscribers can be more targetted as to the events that they subscribe to.
+The benefit is that subscribers can be more targeted as to the events that they subscribe to.
+
+
+[NOTE]
+====
+As of `1.10.0` the framework provides no-arg constructor and will initialize the domain event using (non-API) setters
+rather than through the constructor. This substantially reduces the boilerplate.
+====
+
-As of `1.10.0-SNAPSHOT` this can be simplified to just:
-[source,java]
-----
-public class ToDoItem {
- public static class CompletedEvent extends ActionDomainEvent<ToDoItem> { }
- @Action(domainEvent=CompletedEvent.class)
- public ToDoItem completed() { ... }
-}
-----
-where the framework will initialize the domain event using setters rather than through the constructor. This substantially reduces the boilerplate.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_semantics.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_semantics.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_semantics.adoc
index e926f57..72fac39 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_semantics.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Action_semantics.adoc
@@ -34,14 +34,14 @@ The table below summarizes the semantics:
`IDEMPOTENT_ARE_YOU_SURE`
| Yes
| Will make no further changes if called multiple times (eg sets a property or adds to a `Set`). +
-The "are you sure" variant (`1.10.0-SNAPSHOT`) requires that the user must explicitly confirm the action.
+The "are you sure" variant requires that the user must explicitly confirm the action.
| `PUT`
| `NON_IDEMPOTENT` +
`NON_IDEMPOTENT_ARE_YOU_SURE`
| Yes
| Might change the state of the system each time called (eg increments a counter or adds to a `List`). +
-The "are you sure" variant (`1.10.0-SNAPSHOT`) requires that the user must explicitly confirm the action.
+The "are you sure" variant requires that the user must explicitly confirm the action.
| `POST`
|===
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection.adoc
index f755c00..b28ba8f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection.adoc
@@ -78,7 +78,7 @@ public class ToDoItem {
...
}
----
-<1> `1.10.0-SNAPSHOT`, can use no-arg constructor.
+<1> as of `1.10.0`, can use no-arg constructor.
<2> default value, so could be omitted
<3> default value, so could be omitted
<4> default value, so could be omitted
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout.adoc
index 80a64e2..2e9699f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout.adoc
@@ -24,8 +24,7 @@ The table below summarizes the annotation's attributes.
|the css class that a collection should have, to allow more targetted styling in xref:rg.adoc#_rg_runtime_application-specific_application-css[`application.css`]
-|xref:rg.adoc#_rg_annotations_manpage-CollectionLayout_defaultView[`defaultView()`] +
-(`1.10.0-SNAPSHOT`)
+|xref:rg.adoc#_rg_annotations_manpage-CollectionLayout_defaultView[`defaultView()`]
|`table`, `excel`, `calendar`, `map`, ...
|Which view is selected by default, if multiple views are available.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout_defaultView.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout_defaultView.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout_defaultView.adoc
index 40e91c5..359a33e 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout_defaultView.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-CollectionLayout_defaultView.adoc
@@ -7,7 +7,7 @@
The xref:ug.adoc#_ug_wicket-viewer[Wicket viewer] allows additional views to be configured to render collections of objects; at the time of writing thesee include the (non-ASF) (non-ASF) link:http://isisaddons.org[Isis Addons]' (non-ASF) http://github.com/isisaddons/isis-wicket-excel[excel] view, the http://github.com/isisaddons/isis-wicket-fullcalendar2[fullcalendar2] view, and the http://github.com/isisaddons/isis-wicket-gmap3[gmap3] view. If the objects to be rendered have the correct "shape", then the appropriate view will be made available. For example, objects with a date can be rendered using `calendar`; objects with locations can be rendered using `map`.
-The `defaultView()` attribute (`1.10.0-SNAPSHOT`) is used to select which of these views should be used by default for a given collection.
+The `defaultView()` attribute is used to select which of these views should be used by default for a given collection.
For example:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection_domainEvent.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection_domainEvent.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection_domainEvent.adoc
index 96beabb..3950861 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection_domainEvent.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Collection_domainEvent.adoc
@@ -43,16 +43,7 @@ For example:
----
public class ToDoItem {
public static class DependenciesChangedEvent
- extends CollectionDomainEvent<ToDoItem, ToDoItem> { // <1>
- private static final long serialVersionUID = 1L;
- public DependenciesChangedEvent( // <2>
- ToDoItem source, // <3>
- Identifier identifier, // <4>
- Of of, // <5>
- ToDoItem value) { // <6>
- super(source, identifier, of, value);
- }
- }
+ extends CollectionDomainEvent<ToDoItem, ToDoItem> { } // <1>
@Collection(
domainEvent=DependenciesChangedEvent.class
)
@@ -61,32 +52,17 @@ public class ToDoItem {
}
----
<1> inherit from `CollectionDomainEvent<T,E>` where `T` is the type of the domain object being interacted with, and `E` is the type of the element in the collection (both `ToDoItem` in this example)
-<2> constructor called reflectively by the framework
-<3> populated with the object being interacted with (the source of the event)
-<4> identifier of the collection
-<5> indicates if the collection is being accessed, added to or removed from.
-<6> the element being added or removed from the collection
The benefit is that subscribers can be more targetted as to the events that they subscribe to.
-As of `1.10.0-SNAPSHOT` this can be simplified to just:
-
-[source,java]
-----
-public class ToDoItem {
- public static class DependenciesChangedEvent
- extends CollectionDomainEvent<ToDoItem, ToDoItem> { }
- @Collection(
- domainEvent=DependenciesChangedEvent.class
- )
- public SortedSet<ToDoItem> getDependencies() { ... }
- ...
-}
-----
+[NOTE]
+====
+As of `1.10.0` the framework provides no-arg constructor and will initialize the domain event using (non-API) setters
+rather than through the constructor. This substantially reduces the boilerplate.
+====
-where the framework will initialize the domain event using setters rather than through the constructor. This substantially reduces the boilerplate.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-DomainObject_nature.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-DomainObject_nature.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-DomainObject_nature.adoc
index 250a92c..206dea0 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-DomainObject_nature.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-DomainObject_nature.adoc
@@ -42,7 +42,7 @@ The identity of an inmemory entity is determined solely by the state of entity's
* `MIXIN` +
+
-(`1.10.0-SNAPSHOT`) indicates that the domain object is part of the domain layer, and is contributing behaviour to objects of some other type as a mixin (also known as a trait).
+indicates that the domain object is part of the domain layer, and is contributing behaviour to objects of some other type as a mixin (also known as a trait).
Equivalent to annotating with xref:rg.adoc#_rg_annotations_manpage-Mixin[`@Mixin`]. For further discussion on using mixins, see xref:ug.adoc#_ug_more-advanced_decoupling_mixins[mixins] in the user guide.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Inject.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Inject.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Inject.adoc
index 99c8676..00ddc71 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Inject.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Inject.adoc
@@ -58,7 +58,7 @@ Generally we recommend using `@javax.inject.Inject`; it involves less code, and
-== Injecting collection of services (1.10.0-SNAPSHOT)
+== Injecting collection of services
It can sometimes be useful to have declared multiple implementations of a particular domain service. For example,
you may have a module that defines an SPI service, where multiple other modules might provide implementations of that SPI
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Mixin.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Mixin.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Mixin.adoc
index d10a7b1..0d9b27e 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Mixin.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Mixin.adoc
@@ -6,7 +6,7 @@
-The `@Mixin` annotation (`1.10.0-SNAPSHOT`) indicates that the class acts as a mixin, contributing behaviour -
+The `@Mixin` annotation indicates that the class acts as a mixin, contributing behaviour -
actions, (derived) properties and (derived) collections - to another domain object.
For example:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-PostConstruct.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-PostConstruct.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-PostConstruct.adoc
index 3047d66..1f03136 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-PostConstruct.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-PostConstruct.adoc
@@ -7,7 +7,7 @@
The `@javax.annotation.PostConstruct` annotation, as defined in link:https://jcp.org/en/jsr/detail?id=250[JSR-250], is recognized by Apache Isis as a callback method on domain services to be called just after they have been constructed, in order that they initialize themselves.
-It is also recognized (`1.10.0-SNAPSHOT`) for xref:ug.adoc#http://localhost:4000/guides/ug.html#_ug_more-advanced_view-models[view models] (eg annotated with xref:rg.adoc#_rg_annotations_manpage-ViewModel[`@ViewModel`]).
+It is also recognized for xref:ug.adoc#http://localhost:4000/guides/ug.html#_ug_more-advanced_view-models[view models] (eg annotated with xref:rg.adoc#_rg_annotations_manpage-ViewModel[`@ViewModel`]).
For the default application-scoped (singleton) domain services, this means that the method, if present, is called during the bootstrapping of the application. For xref:rg.adoc#_rg_annotations_manpage-RequestScoped[`@RequestScoped`] domain services, the method is called at the beginning of the request.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Property_domainEvent.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Property_domainEvent.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Property_domainEvent.adoc
index b5c1bf7..080b235 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Property_domainEvent.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_annotations_manpage-Property_domainEvent.adoc
@@ -34,45 +34,21 @@ For example:
[source,java]
----
public class ToDoItem {
- public static class DueByChangedEvent extends PropertyDomainEvent<ToDoItem, LocalDate> { // <1>
- private static final long serialVersionUID = 1L;
- public DueByChangedEvent( // <2>
- ToDoItem source, // <3>
- Identifier identifier, // <4>
- LocalDate oldValue, // <5>
- LocalDate newValue) { // <6>
- super(source, identifier, oldValue, newValue);
- }
- }
+ public static class DueByChangedEvent extends PropertyDomainEvent<ToDoItem, LocalDate> { } // <1>
@Property(domainEvent=ToDoItem.DueByChangedEvent)
public LocalDate getDueBy() { ... }
...
}
----
<1> inherit from `PropertyDomainEvent<T,P>` where `T` is the type of the domain object being interacted with, and `P` is the type of the property (`LocalDate` in this example)
-<2> constructor called reflectively by the framework
-<3> populated with the object being interacted with (the source of the event)
-<4> identifier of the property
-<5> current value of the property
-<6> proposed new value for the property; if being cleared then will be `null`.
The benefit is that subscribers can be more targetted as to the events that they subscribe to.
-
-As of `1.10.0-SNAPSHOT` this can be simplified to just:
-
-[source,java]
-----
-public class ToDoItem {
- public static class DueByChangedEvent extends PropertyDomainEvent<ToDoItem, LocalDate> { }
- @Property(domainEvent=ToDoItem.DueByChangedEvent)
- public LocalDate getDueBy() { ... }
- ...
-}
-----
-
-where the framework will initialize the domain event using setters rather than through the constructor. This substantially reduces the boilerplate.
-
+[NOTE]
+====
+As of `1.10.0` the framework provides no-arg constructor and will initialize the domain event using (non-API) setters
+rather than through the constructor. This substantially reduces the boilerplate.
+====
== Subscribers
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_classes_lifecycleevent.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_classes_lifecycleevent.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_classes_lifecycleevent.adoc
index f51ea02..2c21026 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_classes_lifecycleevent.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_classes_lifecycleevent.adoc
@@ -1,11 +1,11 @@
[[_rg_classes_lifecycleevent]]
-= Lifecycle Events (1.10.0-SNAPSHOT)
+= Lifecycle Events
:Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at. http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
:_basedir: ../
:_imagesdir: images/
-This section catalogues the various lifecycle event classes defined by Apache Isis (1.10.0-SNAPSHOT). These events
+This section catalogues the various lifecycle event classes defined by Apache Isis. These events
are fired automatically when a domain object is loaded, created, updated and so forth.
The lifecycle event classes are listed in the table below:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_methods_lifecycle.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_methods_lifecycle.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_methods_lifecycle.adoc
index ca38de0..27cbf58 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_methods_lifecycle.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_methods_lifecycle.adoc
@@ -16,7 +16,7 @@ Note that these callbacks are fired by Apache Isis rather than JDO. In the futu
* in Isis 1.9.0 and earlier, you may therefore want to consider using the JDO API directly to set up a lifecycle
listener; see xref:rg.adoc#_rg_methods_lifecycle_jdo-api[here] for further discussion.
-* alternatively (1.10.0-SNAPSHOT), you can use a subscriber for the xref:rg.adoc#_rg_classes_lifecycleevent[lifecycle event]s fired in Isis.
+* alternatively, you can use a subscriber for the xref:rg.adoc#_rg_classes_lifecycleevent[lifecycle event]s fired in Isis.
====
The lifecycle callback methods supported by Isis are:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_methods_prefixes_manpage-autoComplete.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_methods_prefixes_manpage-autoComplete.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_methods_prefixes_manpage-autoComplete.adoc
index f91cd09..8d6d627 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_methods_prefixes_manpage-autoComplete.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_methods_prefixes_manpage-autoComplete.adoc
@@ -25,7 +25,7 @@ For an action parameter in (0-based) position _N_, and of type `T`, the signatur
public List<T> autoCompleteNXxx(String search) { ... }
----
-It is also valid to return `T[]` or (from `1.10.0-SNAPSHOT onwards`) either `Set<T>` or `Collection<T>`.
+It is also valid to return `T[]`, a `Set<T>` or a `Collection<T>`.
For example:
@@ -73,7 +73,7 @@ For a property of type `T`, the signature is:
public List<T> autoCompleteXxx(String search) { ... }
----
-(As for action parameters) it is also valid to return `T[]` or (from `1.10.0-SNAPSHOT onwards`) either `Set<T>` or `Collection<T>`.
+(As for action parameters) it is also valid to return `T[]`, a `Set<T>` or a `Collection<T>`.
For example:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_runtime_configuring-core.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_runtime_configuring-core.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_runtime_configuring-core.adoc
index 7134c76..6faf78e 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_runtime_configuring-core.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_runtime_configuring-core.adoc
@@ -49,8 +49,7 @@ See xref:ug.adoc#_ug_how-tos_ui-hints_action-icons-and-css[UI hints] for more de
See xref:ug.adoc#_ug_how-tos_ui-hints_action-icons-and-css[UI hints] for more details.
|`isis.reflector.facet.` +
-`filterVisibility` +
-(1.10.0-SNAPSHOT)
+`filterVisibility`
| `true`,`false` (`true`)
|Whether objects should be filtered for visibility. +
@@ -257,7 +256,7 @@ See xref:ug.adoc#_ug_more-advanced_i18n[i18n support] to learn more about the tr
[[_rg_runtime_configuring-core_filterVisibility]]
-== Filtering visibility (1.10.0-SNAPSHOT)
+== Filtering visibility
The framework provides the `isis.reflector.facet.filterVisibility` configuration property that influences whether a returned object is visible to the end-user:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-DomainObjectContainer_object-creation-api.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-DomainObjectContainer_object-creation-api.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-DomainObjectContainer_object-creation-api.adoc
index 4301d70..50dca58 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-DomainObjectContainer_object-creation-api.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-DomainObjectContainer_object-creation-api.adoc
@@ -22,7 +22,7 @@ public interface DomainObjectContainer {
----
<1> create a new non-persisted domain entity. Any services will be automatically injected into the service
<2> create a new view model, with the specified memento (as per xref:rg.adoc#_rg_classes_super_manpage-AbstractViewModel[ViewModel#viewModelMemento()]. In general it is easier to just annotate with xref:rg.adoc#_rg_annotations_manpage-ViewModel[`@ViewModel`] and let Apache Isis manage the memento automatically.
-<3> (`1.10.0-SNAPSHOT`) programmatically instantiate a mixin, as annotated with
+<3> programmatically instantiate a mixin, as annotated with
xref:rg.adoc#_rg_annotations_manpage-Mixin[`@Mixin`] or xref:rg.adoc#_rg_annotations_manpage-DomainObject_nature[`@DomainObject#nature()`].
For example:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-EventBusService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-EventBusService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-EventBusService.adoc
index 9ea536f..fb01cba 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-EventBusService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_services-api_manpage-EventBusService.adoc
@@ -178,12 +178,15 @@ package com.mycompany.modules.libmem;
public static class LibMemModule {
private LibMemModule() {}
public abstract static class ActionDomainEvent<S>
- extends org.apache.isis.applib.event.ActionDomainEvent<S> {} // <1>
-... // <2>
+ extends org.apache.isis.applib.event.ActionDomainEvent<S> {}
+ ... // <1>
+ public abstract static class PropertyDomainEvent<S,T>
+ extends org.apache.isis.applib.event.PropertyDomainEvent<S,T> {}
+ public abstract static class CollectionDomainEvent<S,E>
+ extends org.apache.isis.applib.event.CollectionDomainEvent<S,E> {}
}
----
-<1> as of 1.10.0-SNAPSHOT, can use the no-arg constructor
-<2> similar events for properties and collections should also be defined
+<1> similar events for properties and collections should also be defined
For the class-level we can define:
@@ -191,27 +194,23 @@ For the class-level we can define:
----
public static class LibraryMember {
public abstract static class ActionDomainEvent
- extends LibMemModule.ActionDomainEvent<LibraryMember> { } // <1>
- ... // <2>
+ extends LibMemModule.ActionDomainEvent<LibraryMember> { }
+ ... // <1>
}
----
-<1> as of 1.10.0-SNAPSHOT, can use the no-arg constructor
-<2> similar events for properties and collections should also be defined
+<1> similar events for properties and collections should also be defined
and finally at the action level we can define:
[source,java]
----
public class LibraryMember {
- public static class LeaveEvent
- extends LibraryMember.ActionDomainEvent { } // <1>
- }
+ public static class LeaveEvent extends LibraryMember.ActionDomainEvent { }
@Action(domainEvent=LeaveEvent.class)
public void leave() { ... }
...
}
----
-<1> as of 1.10.0-SNAPSHOT, can use the no-arg constructor
The subscriber can subscribe either to the general superclass (as before), or to any of the classes in the hierarchy.
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi.adoc
index 73971b1..b0575ec 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi.adoc
@@ -98,7 +98,7 @@ a configured `EmailService`
`ErrorReportingService`]
|Record details of an error occurring in the system (eg in an external incident recording system such as JIRA), and return a more friendly (jargon-free) message to display to the end user, with optional reference (eg `XXX-1234`).
|(none)
-|`1.10.0-SNAPSHOT`
+|
|xref:rg.adoc#_rg_services-spi_manpage-EventSerializer[`o.a.i.applib.` +
`services.publish` +
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi_manpage-ErrorReportingService.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi_manpage-ErrorReportingService.adoc b/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi_manpage-ErrorReportingService.adoc
index d02daa0..a4c81d5 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi_manpage-ErrorReportingService.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_rg_services-spi_manpage-ErrorReportingService.adoc
@@ -5,7 +5,7 @@
:_imagesdir: images/
-The `ErrorReportingService` service (`1.10.0-SNAPSHOT`) is an optional SPI that providies the ability to record any errors/exceptions that
+The `ErrorReportingService` service is an optional SPI that providies the ability to record any errors/exceptions that
might occur in the application into an external incident recording system (such as JIRA). The service also allows
a user-friendly (jargon-free) error message to be returned and rendered to the end-user, along with an optional
incident reference (eg a JIRA issue `XXX-1234`).
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_tg_pet-clinic.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_tg_pet-clinic.adoc b/adocs/documentation/src/main/asciidoc/guides/_tg_pet-clinic.adoc
index 7173bf8..cd8a726 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_tg_pet-clinic.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_tg_pet-clinic.adoc
@@ -62,7 +62,7 @@ Run the simpleapp archetype to build an empty Isis application:
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.9.0 \
+ -D archetypeVersion=1.10.0 \
-D groupId=com.mycompany \
-D artifactId=petclinic \
-D version=1.0-SNAPSHOT \
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc b/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
index 0abebb3..b8b9d86 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_tg_stop-scaffolding-start-coding.adoc
@@ -30,7 +30,7 @@ Run the simpleapp archetype to build an empty Isis application:
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.9.0 \
+ -D archetypeVersion=1.10.0 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_ug_getting-started_simpleapp-archetype.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_getting-started_simpleapp-archetype.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_getting-started_simpleapp-archetype.adoc
index 1cfb0d5..c5e3024 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_getting-started_simpleapp-archetype.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_getting-started_simpleapp-archetype.adoc
@@ -22,7 +22,7 @@ To build the app from the latest stable release, then run the following command:
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.9.0 \
+ -D archetypeVersion=1.10.0 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
@@ -47,7 +47,7 @@ The process is almost identical to that for stable releases, however the `archet
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.10.0-SNAPSHOT \
+ -D archetypeVersion=1.11.0-SNAPSHOT \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_contributions.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_contributions.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_contributions.adoc
index ef7a341..f3d6c1a 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_contributions.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_contributions.adoc
@@ -6,7 +6,7 @@
Contributed services provide many of the same benefits as xref:ug.adoc#_ug_more-advanced_decoupling_mixins[mixins];
-indeed mixins (`1.10.0-SNAPSHOT`) are an evolution and refinement of the contributions concept.
+indeed mixins are an evolution and refinement of the contributions concept.
The main difference between contributed services and mixins is that the actions of a contributed service will
contribute to _all_ the parameters of its actions, whereas a mixin only contributes to the type accepted in its
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_mixins.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_mixins.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_mixins.adoc
index c5fb367..dc20da0 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_mixins.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_decoupling_mixins.adoc
@@ -5,7 +5,7 @@
:_imagesdir: images/
-A mixin object (`1.10.0-SNAPSHOT`) allows one class to contribute behaviour - actions, (derived) properties and
+A mixin object allows one class to contribute behaviour - actions, (derived) properties and
(derived) collections - to another domain object, either a domain entity or view model.
Some programming languages use the term "trait" instead of mixin, and some languages (such as AspectJ) define their own
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_tips-n-tricks_are-you-sure.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_tips-n-tricks_are-you-sure.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_tips-n-tricks_are-you-sure.adoc
index 74a019b..958464f 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_tips-n-tricks_are-you-sure.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_more-advanced_tips-n-tricks_are-you-sure.adoc
@@ -8,7 +8,7 @@
Sometimes an action might perform irreversible changes. In such a case it's probably a good idea for the UI to require that the
end-user explicitly confirms that they intended to invoke the action.
-== Using action semantics (`1.10.0-SNAPSHOT`)
+== Using action semantics
One way to meet this requirement is using the framework's built-in xref:rg.adoc#_rg_annotations_manpage-Action_semantics[`@Action#semantics()`] attribute:
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
index e5893bd..af475dd 100644
--- a/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/_ug_testing_fixture-scripts_api-and-usage.adoc
@@ -325,7 +325,7 @@ The composite style tends to combine these, which one could argue does not separ
=== Further approaches
-As of `1.10.0-SNAPSHOT` there are two other approaches.
+As of there are two other approaches.
The first is to take advantage of a new `MultipleExecutionStrategy`, namely `EXECUTE_ONCE_BY_VALUE`. Under this strategy the determination as to whether to run a given fixture script is by comparing the fixture script against all others that have run. If all fixture scripts implement value semantics, then they can effectively determine
whether they need to run or not.
@@ -339,7 +339,7 @@ value semantics of the `ExcelFixture`, which is based on the contents of the spr
[NOTE]
====
-Note that in `1.10.0-SNAPSHOT` the `IGNORE` enum has been deprecated, replaced by `EXECUTE_ONCE_BY_CLASS`
+Note that as of `1.10.0` the `IGNORE` enum has been deprecated, replaced by `EXECUTE_ONCE_BY_CLASS`
====
The second approach is in recognition that there is, in fact, something of a design flaw with the concept of
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/guides/simpleapp-archetype.adoc
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/guides/simpleapp-archetype.adoc b/adocs/documentation/src/main/asciidoc/guides/simpleapp-archetype.adoc
index ed4ac26..ed0394d 100644
--- a/adocs/documentation/src/main/asciidoc/guides/simpleapp-archetype.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/simpleapp-archetype.adoc
@@ -25,7 +25,7 @@ Then run the following command:
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.9.0 \
+ -D archetypeVersion=1.10.0 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
@@ -54,7 +54,7 @@ The process is almost identical to that for stable releases, however the `archet
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.10.0-SNAPSHOT \
+ -D archetypeVersion=1.11.0-SNAPSHOT \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
http://git-wip-us.apache.org/repos/asf/isis/blob/7d0c84d6/adocs/documentation/src/main/asciidoc/index.html
----------------------------------------------------------------------
diff --git a/adocs/documentation/src/main/asciidoc/index.html b/adocs/documentation/src/main/asciidoc/index.html
index 7698385..5c622a8 100644
--- a/adocs/documentation/src/main/asciidoc/index.html
+++ b/adocs/documentation/src/main/asciidoc/index.html
@@ -654,7 +654,7 @@
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
- -D archetypeVersion=1.9.0 \
+ -D archetypeVersion=1.10.0 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \