This is an automated email from the ASF dual-hosted git repository. danhaywood pushed a commit to branch 3.6.0 in repository https://gitbox.apache.org/repos/asf/causeway.git
commit 5a50eb13674c0a02f22eff32c11cd752fa6fd271 Author: Dan Haywood <[email protected]> AuthorDate: Sun Jul 12 14:57:47 2026 +0100 updates after regen site --- .../adoc/modules/config/pages/sections/Other.adoc | 4 +- .../config/pages/sections/causeway.applib.adoc | 68 +++++++++++----------- .../causeway.core.meta-model.introspector.adoc | 4 +- .../causeway.core.meta-model.validator.adoc | 2 +- .../sections/causeway.core.runtime-services.adoc | 2 +- .../pages/sections/causeway.core.runtime.adoc | 2 +- .../config/pages/sections/causeway.extensions.adoc | 20 +++---- .../sections/causeway.persistence.commons.adoc | 2 +- .../sections/causeway.persistence.schema.adoc | 2 +- .../pages/sections/causeway.prototyping.adoc | 2 +- .../pages/sections/causeway.security.keycloak.adoc | 4 +- .../config/pages/sections/causeway.testing.adoc | 6 +- .../pages/sections/causeway.value-types.adoc | 16 ++--- .../pages/sections/causeway.viewer.graphql.adoc | 18 +++--- .../pages/sections/causeway.viewer.wicket.adoc | 26 ++++----- .../modules/config/pages/sections/datanucleus.adoc | 8 +-- 16 files changed, 93 insertions(+), 93 deletions(-) diff --git a/core/config/src/main/adoc/modules/config/pages/sections/Other.adoc b/core/config/src/main/adoc/modules/config/pages/sections/Other.adoc index b0f472f2eab..e1dfd106930 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/Other.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/Other.adoc @@ -17,7 +17,7 @@ causeway.schema.command. + param-identifier-strategy | by-id -| Whether the `ParamDto#getName()` field - which uniquely identifies a parameter within the action's of parameters - is populated with the parameter's formal Id (eg "firstName") or instead using the parameter's friendly name (eg "First Name"). +| Whether the `ParamDto++#++getName()` field - which uniquely identifies a parameter within the action's of parameters - is populated with the parameter's formal Id (eg "firstName") or instead using the parameter's friendly name (eg "First Name"). The default is to use the Id, but the name is provided as an alternative for compatibility with v1. Note that the name is potentially translated, so this could also cause issues within integration scenarios. @@ -31,7 +31,7 @@ require-only-viewing-permission | | If set, allows _Actions_ with SAFE Semantics to be invoked with only VIEWING permissions. -default: false @see org.apache.causeway.applib.annotation.Action#semantics() @see SemanticsOf +default: false @see org.apache.causeway.applib.annotation.Action++#++semantics() @see SemanticsOf diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.applib.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.applib.adoc index 918d3dd599a..50638fdc08f 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.applib.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.applib.adoc @@ -103,7 +103,7 @@ disk, switch.*:fa-exchange, random. + Providing a default set of patterns encourages a common set of verbs to be used. -The font awesome class for individual actions can be overridden using `ActionLayout#cssClassFa()`. +The font awesome class for individual actions can be overridden using `ActionLayout++#++cssClassFa()`. | @@ -137,7 +137,7 @@ action-layout.css-class.patterns Providing a default set of patterns encourages a common set of verbs to be used. -The CSS class for individual actions can be overridden using `ActionLayout#cssClass()`. +The CSS class for individual actions can be overridden using `ActionLayout++#++cssClass()`. | @@ -158,7 +158,7 @@ command-publishing | none | The default for whether action invocations should be reified as a `Command`, to be sent to any registered `CommandSubscriber`s, typically for auditing purposes. -This setting can be overridden on a case-by-case basis using `Action#commandPublishing()`. +This setting can be overridden on a case-by-case basis using `Action++#++commandPublishing()`. | @@ -171,7 +171,7 @@ domain-event.post-for-default Up to five different events can be fired during an interaction, with the event's phase determining which (hide, disable, validate, executing and executed). Subscribers can influence the behaviour at each of these phases. -The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Action#domainEvent()` for the action in question +The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Action++#++domainEvent()` for the action in question * If set to some subtype of ActionDomainEvent.Noop, then _no_ event is sent. * If set to some subtype of ActionDomainEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -188,7 +188,7 @@ execution-publishing The service's onExecution method is called only once per transaction, with `Execution` collecting details of the identity of the target object, the action invoked, the action arguments and the returned object (if any). -This setting can be overridden on a case-by-case basis using `Action#executionPublishing() Action#executionPublishing()`. +This setting can be overridden on a case-by-case basis using `Action++#++executionPublishing() Action++#++executionPublishing()`. | @@ -199,7 +199,7 @@ collection-layout.default-view | table | Defines the initial view to display collections when rendered. -The value of this can be overridden on a case-by-case basis using `CollectionLayout#defaultView()`. Note that this default configuration property is an enum and so defines only a fixed number of values, whereas the annotation returns a string; this is to allow for flexibility that individual viewers might support their own additional types. For example, the Wicket viewer supports which can render objects that have a date on top of a calendar view. +The value of this can be overridden on a case-by-case basis using `CollectionLayout++#++defaultView()`. Note that this default configuration property is an enum and so defines only a fixed number of values, whereas the annotation returns a string; this is to allow for flexibility that individual viewers might support their own additional types. For example, the Wicket viewer supports which can render objects that have a date on top of a calendar view. | @@ -210,7 +210,7 @@ collection-layout.paged | 12 | Defines the default number of objects that are shown in a "parented" collection of a domain object, result of invoking an action. -This can be overridden on a case-by-case basis using `CollectionLayout#paged()`. +This can be overridden on a case-by-case basis using `CollectionLayout++#++paged()`. | @@ -220,7 +220,7 @@ collection-layout. + sequence-policy-if-unreferenced | -| How `CollectionLayout#sequence()` should be handled when calculating the slot-in order for unreferenced _Collections_. ++{++@code AS++_++PER++_++SEQUENCE} will use Dewey order based on available 'sequence' attributes, whereas ++{++@code ALPHABETICALLY} will use alphabetical order based on member names. +| How `CollectionLayout++#++sequence()` should be handled when calculating the slot-in order for unreferenced _Collections_. ++{++@code AS++_++PER++_++SEQUENCE} will use Dewey order based on available 'sequence' attributes, whereas ++{++@code ALPHABETICALLY} will use alphabetical order based on member names. default: ++{++@code AS++_++PER++_++SEQUENCE} @@ -245,7 +245,7 @@ post-for-default Up to two different events can be fired during an interaction, with the event's phase determining which (hide, disable)Subscribers can influence the behaviour at each of these phases. -The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Collection#domainEvent()` for the collection action in question: +The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Collection++#++domainEvent()` for the collection action in question: * If set to some subtype of CollectionDomainEvent.Noop, then _no_ event is sent. * If set to some subtype of CollectionDomainEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -260,9 +260,9 @@ css-class-ui-event. + post-for-default | -| Influences whether an `CssClassUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `CssClassUiEvent#setCssClass(String)` change) the CSS classes that are used. +| Influences whether an `CssClassUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `CssClassUiEvent++#++setCssClass(String)` change) the CSS classes that are used. -The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout#cssClassUiEvent()` @DomainObjectLayout(cssClassEvent=...)} for the domain object in question. +The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout++#++cssClassUiEvent()` @DomainObjectLayout(cssClassEvent=...)} for the domain object in question. * If set to some subtype of CssClassUiEvent.Noop, then _no_ event is sent. * If set to some subtype of CssClassUiEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -278,9 +278,9 @@ domain-object-layout.icon-ui-event. + post-for-default | -| Influences whether an `IconUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `IconUiEvent#setIconName(String)` change) the icon that is used. +| Influences whether an `IconUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `IconUiEvent++#++setIconName(String)` change) the icon that is used. -The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout#iconUiEvent()` @DomainObjectLayout(iconEvent=...)} for the domain object in question. +The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout++#++iconUiEvent()` @DomainObjectLayout(iconEvent=...)} for the domain object in question. * If set to some subtype of IconUiEvent.Noop, then _no_ event is sent. * If set to some subtype of IconUiEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -296,11 +296,11 @@ domain-object-layout. + layout-ui-event.post-for-default | -| Influences whether an `LayoutUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `LayoutUiEvent#setLayout(String)` change) the layout that is used. +| Influences whether an `LayoutUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `LayoutUiEvent++#++setLayout(String)` change) the layout that is used. If a different layout value has been set, then a layout in the form `xml` use used (where `zzz` is the name of the layout). -The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout#layoutUiEvent()` @DomainObjectLayout(layoutEvent=...)} for the domain object in question. +The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout++#++layoutUiEvent()` @DomainObjectLayout(layoutEvent=...)} for the domain object in question. * If set to some subtype of LayoutUiEvent.Noop, then _no_ event is sent. * If set to some subtype of LayoutUiEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -317,7 +317,7 @@ domain-object-layout.paged | 25 | Defines the default number of objects that are shown in a "standalone" collection obtained as the result of invoking an action. -This can be overridden on a case-by-case basis using `DomainObjectLayout#paged()`. +This can be overridden on a case-by-case basis using `DomainObjectLayout++#++paged()`. | @@ -337,9 +337,9 @@ domain-object-layout. + title-ui-event.post-for-default | -| Influences whether an `TitleUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `TitleUiEvent#setTitle(String)` change) the title that is used. +| Influences whether an `TitleUiEvent` should be published (on the internal `EventBusService`) whenever a domain object is about to be rendered in the UI - thereby allowing subscribers to optionally `TitleUiEvent++#++setTitle(String)` change) the title that is used. -The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout#titleUiEvent()` @DomainObjectLayout(titleEvent=...)} for the domain object in question. +The algorithm for determining whether (and what type of) an event is sent depends on the value of the `DomainObjectLayout++#++titleUiEvent()` @DomainObjectLayout(titleEvent=...)} for the domain object in question. * If set to some subtype of TitleUiEvent.Noop, then _no_ event is sent. * If set to some subtype of TitleUiEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -373,7 +373,7 @@ domain-object.editing | false | The default for whether the properties of domain objects can be edited, or whether instead they can be modified only using actions (or programmatically as a side-effect of actions on other objects). -This setting can be overridden on a case-by-case basis using `DomainObject#getEditing() DomainObject#getEditing()` +This setting can be overridden on a case-by-case basis using `DomainObject++#++getEditing() DomainObject++#++getEditing()` | @@ -385,7 +385,7 @@ entity-change-publishing | none | The default for whether _domain entities_ should be audited or not (meaning that any changes are sent through to `EntityChangesSubscriber`s and sent through to `EntityPropertyChangeSubscriber`. -This setting can be overridden on a case-by-case basis using `DomainObject#entityChangePublishing()` +This setting can be overridden on a case-by-case basis using `DomainObject++#++entityChangePublishing()` Note: this applies only to domain entities, not view models. @@ -514,9 +514,9 @@ parameter-layout.label-position | not-specified | Defines the default position for the label for an action parameter. -Can be overridden on a case-by-case basis using `ParameterLayout#labelPosition()`. +Can be overridden on a case-by-case basis using `ParameterLayout++#++labelPosition()`. -If left as `LabelPosition#NOT++_++SPECIFIED` and not overridden, then the position depends upon the viewer implementation. +If left as `LabelPosition++#++NOT++_++SPECIFIED` and not overridden, then the position depends upon the viewer implementation. | @@ -528,7 +528,7 @@ preceding-parameters-policy | reset | Whether parameters should be reset to their default if an earlier parameter changes its value, or whether instead a parameter value, once changed by the end-user, should never be overwritten even if the end-user changes an earlier parameter value. -This setting can be overridden on a case-by-case basis using `Parameter#precedingParamsPolicy() Parameter#precedingParametersPolicy()`. +This setting can be overridden on a case-by-case basis using `Parameter++#++precedingParamsPolicy() Parameter++#++precedingParametersPolicy()`. | @@ -539,9 +539,9 @@ property-layout.label-position | not-specified | Defines the default position for the label for a domain object property. -Can be overridden on a case-by-case basis using `ParameterLayout#labelPosition()`. +Can be overridden on a case-by-case basis using `ParameterLayout++#++labelPosition()`. -If left as `LabelPosition#NOT++_++SPECIFIED` and not overridden, then the position depends upon the viewer implementation. +If left as `LabelPosition++#++NOT++_++SPECIFIED` and not overridden, then the position depends upon the viewer implementation. | @@ -551,7 +551,7 @@ property-layout. + sequence-policy-if-unreferenced | -| How `PropertyLayout#sequence()` should be handled when calculating the slot-in order for unreferenced _Properties_. ++{++@code AS++_++PER++_++SEQUENCE} will use Dewey order based on available 'sequence' attributes, whereas ++{++@code ALPHABETICALLY} will use alphabetical order based on member names. +| How `PropertyLayout++#++sequence()` should be handled when calculating the slot-in order for unreferenced _Properties_. ++{++@code AS++_++PER++_++SEQUENCE} will use Dewey order based on available 'sequence' attributes, whereas ++{++@code ALPHABETICALLY} will use alphabetical order based on member names. default: ++{++@code AS++_++PER++_++SEQUENCE} @@ -564,7 +564,7 @@ property.command-publishing | none | The default for whether property edits should be reified as a `Command`, to be sent to any registered `CommandSubscriber`s, either for auditing or for replayed against a secondary system, eg for regression testing. -This setting can be overridden on a case-by-case basis using `Property#commandPublishing()`. +This setting can be overridden on a case-by-case basis using `Property++#++commandPublishing()`. | @@ -578,7 +578,7 @@ post-for-default Up to five different events can be fired during an interaction, with the event's phase determining which (hide, disable, validate, executing and executed). Subscribers can influence the behaviour at each of these phases. -The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Property#domainEvent()` for the property in question: +The algorithm for determining whether (and what type of) an event is actually sent depends on the value of the `Property++#++domainEvent()` for the property in question: * If set to some subtype of propertyDomainEvent.Noop, then _no_ event is sent. * If set to some subtype of propertyDomainEvent.Default, then an event is sent _if and only if_ this configuration setting is set. @@ -593,9 +593,9 @@ property.execution-publishing | none | The default for whether property edits should be sent through to the `ExecutionSubscriber` for publishing. -The service's `ExecutionSubscriber#onExecution(Execution)` publish} method is called only once per transaction, with `Execution` collecting details of the identity of the target object, the property edited, and the new value of the property. +The service's `ExecutionSubscriber++#++onExecution(Execution)` publish} method is called only once per transaction, with `Execution` collecting details of the identity of the target object, the property edited, and the new value of the property. -This setting can be overridden on a case-by-case basis using `Property#executionPublishing()`. +This setting can be overridden on a case-by-case basis using `Property++#++executionPublishing()`. | @@ -606,7 +606,7 @@ css-class-ui-event. + post-for-default | true -| Influences whether an `CssClassUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject#nature of `Nature#VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `CssClassUiEvent#setCssClass(String)` change) the CSS classes that are used. +| Influences whether an `CssClassUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject++#++nature of `Nature++#++VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `CssClassUiEvent++#++setCssClass(String)` change) the CSS classes that are used. The algorithm for determining whether (and what type of) an event is sent depends on the value of the `)` for the domain object in question: @@ -622,7 +622,7 @@ view-model-layout.icon-ui-event. + post-for-default | true -| Influences whether an `IconUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject#nature of `Nature#VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `IconUiEvent#setIconName(String)` change) the icon that is used. +| Influences whether an `IconUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject++#++nature of `Nature++#++VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `IconUiEvent++#++setIconName(String)` change) the icon that is used. The algorithm for determining whether (and what type of) an event is sent depends on the value of the `)` for the domain object in question: @@ -638,7 +638,7 @@ view-model-layout.layout-ui-event. + post-for-default | true -| Influences whether an `LayoutUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject#nature of `Nature#VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `LayoutUiEvent#setLayout(String)` change) the layout that is used. +| Influences whether an `LayoutUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject++#++nature of `Nature++#++VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `LayoutUiEvent++#++setLayout(String)` change) the layout that is used. If a different layout value has been set, then a layout in the form `xml` use used (where `zzz` is the name of the layout). @@ -656,7 +656,7 @@ view-model-layout.title-ui-event. + post-for-default | true -| Influences whether an `TitleUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject#nature of `Nature#VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `TitleUiEvent#setTitle(String)` change) the title that is used. +| Influences whether an `TitleUiEvent` should be published (on the internal `EventBusService`) whenever a view model (annotated with @DomainObject++#++nature of `Nature++#++VIEW++_++MODEL`) is about to be rendered in the UI - thereby allowing subscribers to optionally `TitleUiEvent++#++setTitle(String)` change) the title that is used. The algorithm for determining whether (and what type of) an event is sent depends on the value of the `)` for the domain object in question: diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.introspector.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.introspector.adoc index 2551241578a..a62249122f1 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.introspector.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.introspector.adoc @@ -20,7 +20,7 @@ lock-after-full-introspection | true | If true, then no new specifications will be allowed to be loaded once introspection has been complete. -Only applies if the introspector is configured to perform full introspection up-front (either because of `IntrospectionMode#FULL` or `IntrospectionMode#LAZY++_++UNLESS++_++PRODUCTION` when in production); otherwise is ignored. +Only applies if the introspector is configured to perform full introspection up-front (either because of `IntrospectionMode++#++FULL` or `IntrospectionMode++#++LAZY++_++UNLESS++_++PRODUCTION` when in production); otherwise is ignored. | @@ -31,7 +31,7 @@ introspector.mode | lazy-unless-production | Whether all known types should be fully introspected as part of the bootstrapping, or should only be partially introspected initially. -Leaving this as lazy means that there's a chance that metamodel validation errors will not be discovered during bootstrap. That said, metamodel validation is still run incrementally for any classes introspected lazily after initial bootstrapping (unless `#isValidateIncrementally()` is disabled. +Leaving this as lazy means that there's a chance that metamodel validation errors will not be discovered during bootstrap. That said, metamodel validation is still run incrementally for any classes introspected lazily after initial bootstrapping (unless `++#++isValidateIncrementally()` is disabled. | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.validator.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.validator.adoc index 7b7ecbcc487..e996b6aaf43 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.validator.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.meta-model.validator.adoc @@ -40,7 +40,7 @@ causeway.core.meta-model.validator. + allow-logical-type-name-as-alias | -| Allows logical type name in `Named` also be included in the list of `DomainObject#aliased()` or `DomainService#aliased()`. +| Allows logical type name in `Named` also be included in the list of `DomainObject++#++aliased()` or `DomainService++#++aliased()`. It is _highly advisable_ to leave this disabled. This option is meant as a practical way to enable to transition from old names to new logical type names. Especially when you have a large number of files that have to migrated and you want to do the migration in incremental steps. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime-services.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime-services.adoc index 827ea714952..84926f68358 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime-services.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime-services.adoc @@ -78,7 +78,7 @@ bulk.threshold | 1 | Determines the threshold as to whether to execute a set of entity changes in blk, in other words without a transaction flush in between. -If the threshold is passed (by default, anything more than 1 entity to persist), then the `RepositoryService#execInBulk(Callable)` API is used. +If the threshold is passed (by default, anything more than 1 entity to persist), then the `RepositoryService++#++execInBulk(Callable)` API is used. | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime.adoc index a0a5ec26ce5..385b2cc3e8b 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.core.runtime.adoc @@ -16,7 +16,7 @@ include::../section-hooks/causeway.core.runtime~pre.adoc[] causeway.core.runtime.locale | -| If set, then overrides the application's `Locale#getDefault()` +| If set, then overrides the application's `Locale++#++getDefault()` | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.extensions.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.extensions.adoc index 55f30b5b9f0..5a1788f3a7a 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.extensions.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.extensions.adoc @@ -369,7 +369,7 @@ additional These are in addition to the main namespaces granted. -@see NamespacePermissions#getSticky() +@see NamespacePermissions++#++getSticky() | @@ -384,9 +384,9 @@ These namespaces are intended to be sufficient to allow users with this admin ro These roles cannot be removed via user interface -WARNING: normally these should not be overridden. Instead, specify additional namespaces using `NamespacePermissions#getAdditional()`. +WARNING: normally these should not be overridden. Instead, specify additional namespaces using `NamespacePermissions++#++getAdditional()`. -@see NamespacePermissions#getAdditional() +@see NamespacePermissions++#++getAdditional() | @@ -395,7 +395,7 @@ causeway.extensions.secman.seed. + admin.password | -| The corresponding password for user. @see #getUserName() +| The corresponding password for user. @see ++#++getUserName() | @@ -406,9 +406,9 @@ admin.role-name | | The name of security admin role. -Users with this role (in particular, the default user are granted access to a set of namespaces (`NamespacePermissions#getSticky()` and `NamespacePermissions#getAdditional()`) which are intended to be sufficient to allow users with this admin role to be able to administer the security module itself, for example to manage users and roles. +Users with this role (in particular, the default user are granted access to a set of namespaces (`NamespacePermissions++#++getSticky()` and `NamespacePermissions++#++getAdditional()`) which are intended to be sufficient to allow users with this admin role to be able to administer the security module itself, for example to manage users and roles. -@see Admin#getUserName() @see NamespacePermissions#getSticky() @see NamespacePermissions#getAdditional() +@see Admin++#++getUserName() @see NamespacePermissions++#++getSticky() @see NamespacePermissions++#++getAdditional() | @@ -421,9 +421,9 @@ admin.user-name This user is automatically made a member of the role, from which it is granted permissions to administer other users. -The password for this user is set in `Admin#getPassword()`. +The password for this user is set in `Admin++#++getPassword()`. -@see #getPassword() @see #getRoleName() +@see ++#++getPassword() @see ++#++getRoleName() | @@ -454,9 +454,9 @@ causeway.extensions.secman. + user-menu-me-action-policy | hide -| Whether the presence of SecMan should result in the automatic suppression of the `UserMenu`'s `me#act() me()` action. +| Whether the presence of SecMan should result in the automatic suppression of the `UserMenu`'s `me++#++act() me()` action. -This is normally what is required as SecMan's `ApplicationUser` is a more comprehensive representation of the current user. If the default `me#act() me()` action is not suppressed, then the end-user will see two actions with the name "me" in the tertiary menu. +This is normally what is required as SecMan's `ApplicationUser` is a more comprehensive representation of the current user. If the default `me++#++act() me()` action is not suppressed, then the end-user will see two actions with the name "me" in the tertiary menu. | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.commons.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.commons.adoc index c5a98025fbd..0457820477b 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.commons.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.commons.adoc @@ -29,7 +29,7 @@ entity-change-tracker. + suppress-auto-flush | true -| Normally any query submitted to `RepositoryService#allMatches(Query)` will trigger a flush first, unless auto-flush has been disabled. +| Normally any query submitted to `RepositoryService++#++allMatches(Query)` will trigger a flush first, unless auto-flush has been disabled. However, this auto-flush behaviour can be troublesome if the query occurs as a side-effect of the evaluation of a derived property, whose value in turn is enlisted by an implementation of a subscriber (in particular `EntityPropertyChangeSubscriber`) which captures the value of all properties (both persisted and derived). However, this behaviour can (at least under JDO), result in a `ConcurrentModificationException`. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.schema.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.schema.adoc index 8bfb139ae26..5a8cba19c71 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.schema.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.persistence.schema.adoc @@ -28,7 +28,7 @@ auto-create-schemas | | List of additional schemas to be auto-created. -Explicitly creates given list of schemas by using the specified `#getCreateSchemaSqlTemplate()` to generate the actual SQL statement against the configured data-source. +Explicitly creates given list of schemas by using the specified `++#++getCreateSchemaSqlTemplate()` to generate the actual SQL statement against the configured data-source. This configuration mechanism does not consider any schema-auto-creation configuration (if any), that independently is provided the standard JPA way. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.prototyping.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.prototyping.adoc index 334aef2d6b9..a42846be62d 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.prototyping.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.prototyping.adoc @@ -21,7 +21,7 @@ generate-random-web-admin-password If a password is generated, it is logged to the logging subsystem (Log4j2). -Recommended (`true`) when `#isWebAllowRemoteAccess()` is also `true`. +Recommended (`true`) when `++#++isWebAllowRemoteAccess()` is also `true`. | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.security.keycloak.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.security.keycloak.adoc index c59fb066c6b..0634e79cc09 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.security.keycloak.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.security.keycloak.adoc @@ -34,7 +34,7 @@ causeway.security.keycloak. + client-role-prefix | -| If `#isExtractClientRoles()` client roles are to be extracted}, this allows the resultant role to be optionally prefixed. +| If `++#++isExtractClientRoles()` client roles are to be extracted}, this allows the resultant role to be optionally prefixed. | @@ -108,7 +108,7 @@ causeway.security.keycloak. + role-prefix | -| If `#isExtractRoles()` roles are to be extracted}, this allows the resultant role to be optionally prefixed. +| If `++#++isExtractRoles()` roles are to be extracted}, this allows the resultant role to be optionally prefixed. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.testing.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.testing.adoc index 701eefc843b..f2540dd12ef 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.testing.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.testing.adoc @@ -22,7 +22,7 @@ context-class Either this or packagePrefix must be specified. This property is used by preference. -@see #getPackagePrefix() +@see ++#++getPackagePrefix() | @@ -58,9 +58,9 @@ package-prefix | | Specifies the base package from which to search for fixture scripts. -Either this or `#getContextClass()` must be specified; `#getContextClass()` is used by preference. +Either this or `++#++getContextClass()` must be specified; `++#++getContextClass()` is used by preference. -@see #getContextClass() +@see ++#++getContextClass() | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.value-types.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.value-types.adoc index 876749eee17..83cfd3c92b8 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.value-types.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.value-types.adoc @@ -19,7 +19,7 @@ display.min-scale | | The minimum scale to use for all `BigDecimal`s. -Is only used if the minimum scale has not been specified explicitly by some other means, typically either `Digits#fraction()` or an ORM semantic such as the (JPA) `Column#scale()`. +Is only used if the minimum scale has not been specified explicitly by some other means, typically either `Digits++#++fraction()` or an ORM semantic such as the (JPA) `Column++#++scale()`. | @@ -28,7 +28,7 @@ causeway.value-types.big-decimal. + display.use-grouping-separator | true -| Whether to use a grouping (thousands) separator (eg the "," (comma) in the English locale) when rendering a big decimal. @see Editing#isUseGroupingSeparator() +| Whether to use a grouping (thousands) separator (eg the "," (comma) in the English locale) when rendering a big decimal. @see Editing++#++isUseGroupingSeparator() | @@ -56,7 +56,7 @@ For maximum safety, allowing the grouping separator is disallowed, but the alter The same configuration property is also used for rendering the value. -@see Display#isUseGroupingSeparator() +@see Display++#++isUseGroupingSeparator() | @@ -67,11 +67,11 @@ use-scale-for-min-fractional-facet | true | Indicates how to derive the min fractional facet (the minimum number of digits after the decimal point). -If this flag is set, then the `Digits#fraction()` annotation or ORM equivalent (the JDO `@Column#scale` or the JPA `Column#scale()`) should be used for the `MinFractionalFacet` as well as the `MaxFractionalFacet`. +If this flag is set, then the `Digits++#++fraction()` annotation or ORM equivalent (the JDO `@Column++#++scale` or the JPA `Column++#++scale()`) should be used for the `MinFractionalFacet` as well as the `MaxFractionalFacet`. What this means in practice is that a numeric values will be rendered to the same number of fractional digits, irrespective of whether they are whole numbers or fractional. For example, with a scale of 2, then "123.4532" will be rendered as "123.45", while "123" will be rendered as "123.00". -If this flag is NOT set, or if it is set but there is no annotation, then the `#minScale` config property is used as a fallback. +If this flag is NOT set, or if it is set but there is no annotation, then the `++#++minScale` config property is used as a fallback. If there is no fallback, then it means that a big decimal such as "123.00" will be presented as just "123" (that is, the shortest possible textual representation). @@ -93,7 +93,7 @@ causeway.value-types.kroki. + request-timeout | 5000ms -| Max time for requests to the `#getBackendUrl()`, when waiting for a response. (default: 5 seconds) +| Max time for requests to the `++#++getBackendUrl()`, when waiting for a response. (default: 5 seconds) | @@ -221,7 +221,7 @@ min-scale | | The minimum scale to use for all `BigDecimal`s. -Is only used if the minimum scale has not been specified explicitly by some other means, typically either `Digits#fraction()` or an ORM semantic such as the (JPA) `Column#scale()`. @deprecated - use `Display#getMinScale()` instead +Is only used if the minimum scale has not been specified explicitly by some other means, typically either `Digits++#++fraction()` or an ORM semantic such as the (JPA) `Column++#++scale()`. @deprecated - use `Display++#++getMinScale()` instead | @@ -240,7 +240,7 @@ For maximum safety, allowing the grouping separator is disallowed, but the alter The same configuration property is also used for rendering the value. -@deprecated - use `Editing#isUseGroupingSeparator()` instead. +@deprecated - use `Editing++#++isUseGroupingSeparator()` instead. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.graphql.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.graphql.adoc index f6322c03b4d..263b451ba08 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.graphql.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.graphql.adoc @@ -25,7 +25,7 @@ causeway.viewer.graphql. + api-variant | query-and-mutations -| Which variant of API to expose: `ApiVariant#QUERY++_++ONLY` (which suppresses any actions that mutate the state of the system), or as `ApiVariant#QUERY++_++AND++_++MUTATIONS` (which additionally exposes actions that mutate the system as mutations) or alternatively as `ApiVariant#QUERY++_++WITH++_++MUTATIONS++_++NON++_++SPEC++_++COMPLIANT`, a query-only schema that relaxes the read-only rule by exposing actions that mutate the system; it is therefore not compliant with the GraphQL spec), +| Which variant of API to expose: `ApiVariant++#++QUERY++_++ONLY` (which suppresses any actions that mutate the state of the system), or as `ApiVariant++#++QUERY++_++AND++_++MUTATIONS` (which additionally exposes actions that mutate the system as mutations) or alternatively as `ApiVariant++#++QUERY++_++WITH++_++MUTATIONS++_++NON++_++SPEC++_++COMPLIANT`, a query-only schema that relaxes the read-only rule by exposing actions that mutate the system; it is therefore not compliant with the G [...] | @@ -99,7 +99,7 @@ response-type | forbidden | How resources (`Blob` bytes, `Clob` chars, grids and icons) can be downloaded from the resource controller. -By default the download of these resources if `ResponseType#FORBIDDEN`, but alternatively they can be enabled to download either `ResponseType#DIRECT`ly or as an `ResponseType#ATTACHMENT`. +By default the download of these resources if `ResponseType++#++FORBIDDEN`, but alternatively they can be enabled to download either `ResponseType++#++DIRECT`ly or as an `ResponseType++#++ATTACHMENT`. | @@ -138,7 +138,7 @@ causeway.viewer.graphql. + schema-style | rich-and-simple -| Which `SchemaStyle` to expose, "simple" or "rich". By default both are exposed under top-level field names. @see Schema.Rich#getTopLevelFieldName() @see Schema.Simple#getTopLevelFieldName() +| Which `SchemaStyle` to expose, "simple" or "rich". By default both are exposed under top-level field names. @see Schema.Rich++#++getTopLevelFieldName() @see Schema.Simple++#++getTopLevelFieldName() | @@ -147,9 +147,9 @@ causeway.viewer.graphql.schema. + rich.enable-scenario-testing | -| If the `#getSchemaStyle()` is set to either `SchemaStyle#RICH++_++ONLY` or `SchemaStyle#SIMPLE++_++AND++_++RICH`, then determines whether the "Scenario" field is included in order to allow given/when/then tests to be expressed. +| If the `++#++getSchemaStyle()` is set to either `SchemaStyle++#++RICH++_++ONLY` or `SchemaStyle++#++SIMPLE++_++AND++_++RICH`, then determines whether the "Scenario" field is included in order to allow given/when/then tests to be expressed. -Ignored if the `#getSchemaStyle()` is `SchemaStyle#SIMPLE++_++ONLY`. +Ignored if the `++#++getSchemaStyle()` is `SchemaStyle++#++SIMPLE++_++ONLY`. | @@ -158,9 +158,9 @@ causeway.viewer.graphql.schema. + rich.top-level-field-name | rich -| If the `#getSchemaStyle()` is set to `SchemaStyle#SIMPLE++_++AND++_++RICH`, defines the name of the top-level field under which the "rich" schema resides. +| If the `++#++getSchemaStyle()` is set to `SchemaStyle++#++SIMPLE++_++AND++_++RICH`, defines the name of the top-level field under which the "rich" schema resides. -Ignored for any other `#getSchemaStyle()`. +Ignored for any other `++#++getSchemaStyle()`. | @@ -169,9 +169,9 @@ causeway.viewer.graphql.schema. + simple.top-level-field-name | simple -| If the `#getSchemaStyle()` is set to `SchemaStyle#SIMPLE++_++AND++_++RICH`, defines the name of the top-level field under which the "simple" schema resides. +| If the `++#++getSchemaStyle()` is set to `SchemaStyle++#++SIMPLE++_++AND++_++RICH`, defines the name of the top-level field under which the "simple" schema resides. -Ignored for any other `#getSchemaStyle()`. +Ignored for any other `++#++getSchemaStyle()`. diff --git a/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.wicket.adoc b/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.wicket.adoc index fba2ec593f0..116c440c531 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.wicket.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/causeway.viewer.wicket.adoc @@ -149,7 +149,7 @@ max-date | 2100-01-01T00:00:00.000Z | Defines the first date available in the date picker. -As per http://eonasdan.github.io/bootstrap-datetimepicker/Options/#maxdate, in ISO format (per https://github.com/moment/moment/issues/1407). +As per http://eonasdan.github.io/bootstrap-datetimepicker/Options/++#++maxdate, in ISO format (per https://github.com/moment/moment/issues/1407). Use time zone 'Z', as the date/time picker UI component is not wired up to support time-zones. @@ -162,7 +162,7 @@ min-date | 1900-01-01T00:00:00.000Z | Defines the first date available in the date picker. -As per http://eonasdan.github.io/bootstrap-datetimepicker/Options/#maxdate, in ISO format (per https://github.com/moment/moment/issues/1407). +As per http://eonasdan.github.io/bootstrap-datetimepicker/Options/++#++maxdate, in ISO format (per https://github.com/moment/moment/issues/1407). Use time zone 'Z', as the date/time picker UI component is not wired up to support time-zones. @@ -186,7 +186,7 @@ causeway.viewer.wicket. + development-utilities.enable | -| Determines whether debug bar and other stuff influenced by `DebugSettings#isDevelopmentUtilitiesEnabled()` is enabled or not. +| Determines whether debug bar and other stuff influenced by `DebugSettings++#++isDevelopmentUtilitiesEnabled()` is enabled or not. By default, depends on the mode (prototyping = enabled, server = disabled). This property acts as an override. @@ -198,7 +198,7 @@ causeway.viewer.wicket.dialog-mode | sidebar | Whether the dialog mode rendered when invoking actions on domain objects should be to use the sidebar (the default) or to use a modal dialog. -This can be overridden on a case-by-case basis using `ActionLayout#promptStyle()`. +This can be overridden on a case-by-case basis using `ActionLayout++#++promptStyle()`. | @@ -209,7 +209,7 @@ dialog-mode-for-menu | modal | Whether the dialog mode rendered when invoking actions on domain services (that is, menus) should be to use a modal dialog (the default) or to use the sidebar panel. -This can be overridden on a case-by-case basis using `ActionLayout#promptStyle()`. +This can be overridden on a case-by-case basis using `ActionLayout++#++promptStyle()`. | @@ -232,7 +232,7 @@ disabled-preview-mime-types | text/csv | Some mime types can trigger unwanted download behavior, dependent on browser and or OS settings. -We have seen CSV files causing issues, so we disallow those by default. @see https://plugins.krajee.com/file-input/plugin-options#disabledPreviewMimeTypes +We have seen CSV files causing issues, so we disallow those by default. @see https://plugins.krajee.com/file-input/plugin-options++#++disabledPreviewMimeTypes | @@ -241,7 +241,7 @@ causeway.viewer.wicket.file-upload. + disabled-preview-types | object -| If left empty, the default allows ++[++'image', 'html', 'text', 'video', 'audio', 'flash', 'object'++]++, where 'object' enables fallback behavior. We remove this here. @see https://plugins.krajee.com/file-input/plugin-options#disabledPreviewTypes +| If left empty, the default allows ++[++'image', 'html', 'text', 'video', 'audio', 'flash', 'object'++]++, where 'object' enables fallback behavior. We remove this here. @see https://plugins.krajee.com/file-input/plugin-options++#++disabledPreviewTypes | @@ -300,7 +300,7 @@ causeway.viewer.wicket. + max-title-length-in-tables | 12 -| The maximum number of characters to use to render the title of a domain object (alongside the icon) in any table, if not otherwise overridden by either `#getMaxTitleLengthInParentedTables()` or `#getMaxTitleLengthInStandaloneTables()`. +| The maximum number of characters to use to render the title of a domain object (alongside the icon) in any table, if not otherwise overridden by either `++#++getMaxTitleLengthInParentedTables()` or `++#++getMaxTitleLengthInStandaloneTables()`. If truncated, then the remainder of the title will be replaced with ellipses (...). @@ -412,7 +412,7 @@ prompt-style | inline | Whether to use a modal dialog for property edits and for actions associated with properties. -This can be overridden on a case-by-case basis using `@PropertyLayout#promptStyle` and `@ActionLayout#promptStyle`. +This can be overridden on a case-by-case basis using `@PropertyLayout++#++promptStyle` and `@ActionLayout++#++promptStyle`. This behaviour is disabled by default; the viewer will use an inline prompt in these cases, making for a smoother user experience. @@ -470,7 +470,7 @@ replace-disabled-tag-with-readonly- + tag | true -| In Firefox and more recent versions of Chrome 54{plus}, cannot copy out of disabled fields; instead we use the readonly attribute (https://www.w3.org/TR/2014/REC-html5-20141028/forms.html#the-readonly-attribute) +| In Firefox and more recent versions of Chrome 54{plus}, cannot copy out of disabled fields; instead we use the readonly attribute (https://www.w3.org/TR/2014/REC-html5-20141028/forms.html++#++the-readonly-attribute) This behaviour is enabled by default but can be disabled using this flag @@ -504,7 +504,7 @@ suppress-password-reset | | Whether to suppress the password reset link on the sign-in page. -Although this is disabled by default (in other words the 'reset password' link is not suppressed), note that in addition the application must provide an implementation of the `UserRegistrationService` as well as a configured `EmailNotificationService` (same conditions as for the `#isSuppressSignUp()` sign-up link). +Although this is disabled by default (in other words the 'reset password' link is not suppressed), note that in addition the application must provide an implementation of the `UserRegistrationService` as well as a configured `EmailNotificationService` (same conditions as for the `++#++isSuppressSignUp()` sign-up link). | @@ -515,7 +515,7 @@ suppress-sign-up | | Whether to suppress the sign-up link on the sign-in page. -Although this is disabled by default (in other words the sign-up link is not suppressed), note that in addition the application must provide an implementation of the `UserRegistrationService` as well as a configured `EmailNotificationService` (same conditions as for the `#isSuppressPasswordReset()` password reset link). +Although this is disabled by default (in other words the sign-up link is not suppressed), note that in addition the application must provide an implementation of the `UserRegistrationService` as well as a configured `EmailNotificationService` (same conditions as for the `++#++isSuppressPasswordReset()` password reset link). | @@ -535,7 +535,7 @@ initial | Flatly | The initial theme to use. -Expected to be in the list of `#getEnabled()` themes. +Expected to be in the list of `++#++getEnabled()` themes. | diff --git a/core/config/src/main/adoc/modules/config/pages/sections/datanucleus.adoc b/core/config/src/main/adoc/modules/config/pages/sections/datanucleus.adoc index 75e038e9e6e..9d611fddbb5 100644 --- a/core/config/src/main/adoc/modules/config/pages/sections/datanucleus.adoc +++ b/core/config/src/main/adoc/modules/config/pages/sections/datanucleus.adoc @@ -80,7 +80,7 @@ For integration testing, it's generally better to use datanucleus.schema.generat For more details, see https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#pmf_properties[DataNucleus Config Property docs] and the https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#schema[DataNucleus Schema Guide]. -@see #setAutoCreateColumns(boolean) @see #setAutoCreateConstraints(boolean) @see #setAutoCreateTables(boolean) @see GenerateDatabase#setMode(String) +@see ++#++setAutoCreateColumns(boolean) @see ++#++setAutoCreateConstraints(boolean) @see ++#++setAutoCreateTables(boolean) @see GenerateDatabase++#++setMode(String) | @@ -93,7 +93,7 @@ auto-create-columns For more details, see https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#pmf_properties[DataNucleus Config Property docs] and the https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#schema[DataNucleus Schema Guide]. -@see #setAutoCreateAll(boolean) @see #setAutoCreateConstraints(boolean) @see #setAutoCreateTables(boolean) @see GenerateDatabase#setMode(String) +@see ++#++setAutoCreateAll(boolean) @see ++#++setAutoCreateConstraints(boolean) @see ++#++setAutoCreateTables(boolean) @see GenerateDatabase++#++setMode(String) | @@ -106,7 +106,7 @@ auto-create-constraints For more details, see https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#pmf_properties[DataNucleus Config Property docs] and the https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#schema[DataNucleus Schema Guide]. -@see #setAutoCreateAll(boolean) @see #setAutoCreateColumns(boolean) @see #setAutoCreateTables(boolean) @see GenerateDatabase#setMode(String) +@see ++#++setAutoCreateAll(boolean) @see ++#++setAutoCreateColumns(boolean) @see ++#++setAutoCreateTables(boolean) @see GenerateDatabase++#++setMode(String) | @@ -130,7 +130,7 @@ auto-create-tables For more details, see https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#pmf_properties[DataNucleus Config Property docs] and the https://www.datanucleus.org/products/accessplatform_6_0/jdo/persistence.html#schema[DataNucleus Schema Guide]. -@see #setAutoCreateAll(boolean) @see #setAutoCreateColumns(boolean) @see #setAutoCreateConstraints(boolean) @see GenerateDatabase#setMode(String) +@see ++#++setAutoCreateAll(boolean) @see ++#++setAutoCreateColumns(boolean) @see ++#++setAutoCreateConstraints(boolean) @see GenerateDatabase++#++setMode(String) |
