Hi Jorg,

Thanks for tackling this, will be a nice resource.  Particularly like the
fact you've chosen to use Asciidoc !

Answers within...


On Fri, 3 Nov 2017 at 15:15 Rade, Joerg / Kuehne + Nagel / Ham GI-DP <
joerg.r...@kuehne-nagel.com> wrote:

> Hi,
>
> I am compiling an overview diagram for annotations and supported methods
> [1] and have some questions:
>
> * @Property has CommandReification, CommandExecuteIn, CommandPersistence.
> What is it's use?
>


Same as @Action [2] ... allows a Command object to be persisted which
represents the property edit, optionally to be invoked in the background
rather than immediately (requires an implementation of the Command SPI, eg
the Incode Platform stuff).

In answering this question, I noticed that attributes these aren't
documented in @Property [3], which is an oversight.  Would you be so good
as to raise a ticket, or even better a PR, to fix?





> * Will there be a kind of @Meta for 2.0.0 to wrap/combine JDO annotations?
>

Yes, though there is no new annotation ... just create a meta-annotation
and use.

I have this working in this branch [4], see [5], [6] for usage, also unit
tests at [7]




> * boolean flags in annotations will be removed and replaced by ...
>

... by enums.

For example @DomainObject(bounded=true|false) becomes
@DomainObject(bounding=Bounding.ENABLED|DISABLED|NOT_SPECIFIED)


Also, all the existing enums have a new NOT_SPECIFIED value so that the
logic to search for meta-annotations will know how to ignore.


> * Are references to @Pattern outdated and can completely be replaced by
> @Property.regexPattern* ?
>
>
Actually, the other way around... I did remove our @RegEx with
@Property(regex...), but where there are javax.  standard annotations, I'd
like to bring in support for them.  This is one such.

HTH
Dan


[2] http://isis.apache.org/guides/rgant/rgant.html#_rgant-Action
[3] http://isis.apache.org/guides/rgant/rgant.html#_rgant-Property
[4] https://github.com/apache/isis/tree/dev/2.0.0/ISIS-1632-meta-annotations
[5]
https://github.com/apache/isis/blob/dev/2.0.0/ISIS-1632-meta-annotations/example/application/simpleapp/module-simple/src/main/java/domainapp/modules/simple/dom/impl/SimpleObject.java#L77
[6]
https://github.com/apache/isis/blob/dev/2.0.0/ISIS-1632-meta-annotations/example/application/simpleapp/module-simple/src/main/java/domainapp/modules/simple/dom/types/Name.java
[7]
https://github.com/apache/isis/blob/dev/2.0.0/ISIS-1632-meta-annotations/core/metamodel/src/test/java/org/apache/isis/core/metamodel/facets/Annotations_getAnnotations_on_Method_Test.java




> -j
>
> [1]
> https://github.com/joerg-rade/dddsample-isis/blob/master/frameworkMetaModel.pdf
>
>
> Kühne + Nagel (AG & Co.) KG
> Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE
> 812773878.
> Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Dr. Hansjörg Rodi (Vors. ),
> Martin Brinkmann, Holger Ketz, Jan-Hendrik Köstergarten, Nicholas Minde,
> Michael Nebel, Lars Wedel, Matthias Weiner.
> Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform:
> Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745,
> Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt.
> Geschäftsleitung Region Zentral- und Osteuropa: Dr. Hansjörg Rodi (Vors.),
> Thierry Held, Uwe Hött, Richard Huhn, Holger Ketz, Jan-Hendrik
> Köstergarten, Jan Kunze, Michael Nebel, Guillaume Sauzedde, Mustafa Sener.
>
> Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen
> Spediteurbedingungen 2017 (ADSp 2017). Hinweis: Die ADSp 2017 weichen in
> Ziffer 23 hinsichtlich des Haftungshöchstbetrages für Güterschäden (§ 431
> HGB) vom Gesetz ab, indem sie die Haftung bei multimodalen Transporten
> unter Einschluss einer Seebeförderung und bei unbekanntem Schadenort auf 2
> SZR/kg und im Übrigen die Regelhaftung von 8,33 SZR/kg zusätzlich auf 1,25
> Millionen Euro je Schadenfall sowie 2,5 Millionen Euro je Schadenereignis,
> mindestens aber 2 SZR/kg, beschränken. Die ADSp sind auf unserer Webseite
> als Download erhältlich. Auf Anfrage senden wir Ihnen diese auch gerne zu.
>

Reply via email to