You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Joshua Beck <de...@jbeck.com.au> on 2017/03/30 03:04:12 UTC
DOM folder - where is it hiding?
Hi, I am new to Apache Isis and trying to get familiar with the setup and
workflow. I have been working through the official first tutorial, "Pet
Clinic".
In the archetype version used (1.13.1), the DOM folder appears as a top
level folder in the generated project. This corresponds to other
documentation and YouTube videos, and enables the Enhancer to be set up in
IntelliJ IDEA as per the instructions in the Developer's Guide, at:
https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
The setting up of the enhancer is pointed out to be a very important step,
and clearly, one needs to know what Working Directory to point the enhancer
to. But also, that DOM folder seems to be the key thing upon which the
entire Apache Isis concept is based.
So, after 1.13.1, where has it disappeared to? I have tried to puzzle
through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
expert and it's not making sense to me.
Thanks
Josh
Re: DOM folder - where is it hiding?
Posted by Joshua Beck <de...@jbeck.com.au>.
All good, thanks for the info. It would be helpful to update the
documentation about that.
It seems the enhancer in the IntelliJ launch config can now just be set to
point to the overall project, and it will sniff out the files that need to
be enhanced. That's a change from earlier, when it had to specifically
point to the DOM folder. Although, I guess it takes longer because it has
to evaluate every file in the other folders as well.
On Thu, Mar 30, 2017 at 4:55 PM, Stephen Cameron <steve.cameron.62@gmail.com
> wrote:
> I am quite behind the times, sorry Josh
>
> On Thu, Mar 30, 2017 at 6:09 PM, Dan Haywood <dan@haywood-associates.co.uk
> >
> wrote:
>
> > Actually, in the 1.14.0 version of the simpleapp archetype the 'dom',
> > 'fixture' and 'integtests' module have all been moved.
> >
> > Instead, you'll see a module/simple (or it might be called module-simple)
> > which contains each of these modules.
> >
> > The idea is to support modular development, so each module provides its
> own
> > fixtures and can have its own unit tests (which it already did) and also
> > integration tests.
> >
> > The 'app' module meanwhile has "smoke" integ tests which exercise the
> whole
> > app. I've left the BDD cucumber tests there also.
> >
> > We're slowly refactoring our Estatio app [1] to follow this structure. I
> > also discussed modular apps in a pair of articles on InfoQ [2], [3]
> >
> > Hope that makes sense.
> >
> > Dan
> >
> >
> > [1] http://github.com/estatio/estatio
> >
> > [2] https://www.infoq.com/articles/monolith-defense-part-1
> >
> > [3] https://www.infoq.com/articles/monolith-defense-part-2
> >
> > On Thu, 30 Mar 2017, 06:34 Stephen Cameron, <st...@gmail.com>
> > wrote:
> >
> > Hello Josh,
> >
> > The dom (domain object model) project has not disappeared after 1.13.1.
> >
> > The standard project setup is actually a group of 5 sub-projects (each
> > with their own maven project object model file 'pom.xml'): app, dom
> (domain
> > object model), fixtures, integtest, webapp.
> >
> > All are important and cross-link, but you are correct that the dom
> project
> > will normally contain the classes that need to be enhanced by
> DataNucleus,
> > which for efficient workflow you should enable in your IDE of choice.
> >
> >
> >
> >
> >
> > On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
> >
> > > Hi, I am new to Apache Isis and trying to get familiar with the setup
> and
> > > workflow. I have been working through the official first tutorial, "Pet
> > > Clinic".
> > >
> > > In the archetype version used (1.13.1), the DOM folder appears as a top
> > > level folder in the generated project. This corresponds to other
> > > documentation and YouTube videos, and enables the Enhancer to be set up
> > in
> > > IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> > > https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
> > >
> > > The setting up of the enhancer is pointed out to be a very important
> > step,
> > > and clearly, one needs to know what Working Directory to point the
> > enhancer
> > > to. But also, that DOM folder seems to be the key thing upon which the
> > > entire Apache Isis concept is based.
> > >
> > > So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> > > through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
> > > expert and it's not making sense to me.
> > >
> > > Thanks
> > > Josh
> > >
> >
>
Re: DOM folder - where is it hiding?
Posted by Stephen Cameron <st...@gmail.com>.
I am quite behind the times, sorry Josh
On Thu, Mar 30, 2017 at 6:09 PM, Dan Haywood <da...@haywood-associates.co.uk>
wrote:
> Actually, in the 1.14.0 version of the simpleapp archetype the 'dom',
> 'fixture' and 'integtests' module have all been moved.
>
> Instead, you'll see a module/simple (or it might be called module-simple)
> which contains each of these modules.
>
> The idea is to support modular development, so each module provides its own
> fixtures and can have its own unit tests (which it already did) and also
> integration tests.
>
> The 'app' module meanwhile has "smoke" integ tests which exercise the whole
> app. I've left the BDD cucumber tests there also.
>
> We're slowly refactoring our Estatio app [1] to follow this structure. I
> also discussed modular apps in a pair of articles on InfoQ [2], [3]
>
> Hope that makes sense.
>
> Dan
>
>
> [1] http://github.com/estatio/estatio
>
> [2] https://www.infoq.com/articles/monolith-defense-part-1
>
> [3] https://www.infoq.com/articles/monolith-defense-part-2
>
> On Thu, 30 Mar 2017, 06:34 Stephen Cameron, <st...@gmail.com>
> wrote:
>
> Hello Josh,
>
> The dom (domain object model) project has not disappeared after 1.13.1.
>
> The standard project setup is actually a group of 5 sub-projects (each
> with their own maven project object model file 'pom.xml'): app, dom (domain
> object model), fixtures, integtest, webapp.
>
> All are important and cross-link, but you are correct that the dom project
> will normally contain the classes that need to be enhanced by DataNucleus,
> which for efficient workflow you should enable in your IDE of choice.
>
>
>
>
>
> On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
>
> > Hi, I am new to Apache Isis and trying to get familiar with the setup and
> > workflow. I have been working through the official first tutorial, "Pet
> > Clinic".
> >
> > In the archetype version used (1.13.1), the DOM folder appears as a top
> > level folder in the generated project. This corresponds to other
> > documentation and YouTube videos, and enables the Enhancer to be set up
> in
> > IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> > https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
> >
> > The setting up of the enhancer is pointed out to be a very important
> step,
> > and clearly, one needs to know what Working Directory to point the
> enhancer
> > to. But also, that DOM folder seems to be the key thing upon which the
> > entire Apache Isis concept is based.
> >
> > So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> > through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
> > expert and it's not making sense to me.
> >
> > Thanks
> > Josh
> >
>
Re: Nature of JAXB Views Models
Posted by Patrick Pliessnig <p....@gmail.com>.
Perfect
Patrick
Am 20.10.2017 um 14:14 schrieb Dan Haywood:
> Hi Patrick,
>
> I agree, it should be possible to do what you want. I've raised a ticket
> [1] for it.
>
> In the meantime, go with nature=VIEW_MODEL and add a TODO in your code to
> update when we make the fix.
>
> Thx
> Dan
>
> [1] https://issues.apache.org/jira/browse/ISIS-1749
>
> On Fri, 20 Oct 2017 at 13:11 Patrick Pliessnig <p....@gmail.com>
> wrote:
>
>> It passes validation effectively with nature = Nature.VIEW_MODEL
>> indicating (as much as I can see) that the view model belongs to the
>> application layer.
>>
>> But using
>>
>> nature = Nature.INMEMORY_ENTITY or
>> nature = Nature.EXTERNAL_ENTITY
>>
>> to indicate that the view model is just a proxy for other domain objects
>> in the domain layer generates this validation error:
>>
>> ... has multiple incompatible annotations/interfaces indicating that
>> it is a recreatable object of some sort
>> (RecreatableObjectFacetForDomainObjectAnnotation and
>> RecreatableObjectFacetForXmlRootElementAnnotation)
>>
>> So, I don't know how to specify that a jaxb view model is - say - a
>> proxy for an external entity as I can do with legacy view models.
>>
>>
>>
>> Am 20.10.2017 um 13:22 schrieb Jeroen van der Wal:
>>> This is how I use it:
>>>
>>> @DomainObject(nature = Nature.VIEW_MODEL, objectType = "MyJaxbViewModel")
>>> @XmlRootElement(name = "myJaxbViewModel")
>>> @XmlType(
>>> propOrder = {
>>> "myIncludedProperty"
>>> }
>>> )
>>> @XmlAccessorType(XmlAccessType.FIELD)
>>> public class MyJaxbViewModel {
>>>
>>> @Getter @Setter @Nullable
>>> private String myIncludedProperty;
>>>
>>> @Getter @Setter @Nullable
>>> private String myIncludedProperty;
>>>
>>> @XmlTransient
>>> private String myExcludedProperty;
>>>
>>> }
>>>
>>> HTH
>>>
>>>
>>> On 20 October 2017 at 12:28, Patrick Pliessnig <p....@gmx.net>
>> wrote:
>>>> Hi
>>>>
>>>> Modeling a JAXB view model with @XmlRootElement and its nature with
>>>> @DomainObject( nature = ... ) does not pass metamodel validation.
>>>>
>>>> Is there way to indicate the nature of a JAXB view model?
>>>> Eg. whether it belongs to the domain model or the application layer.
>>>>
>>>> thx
>>>> Patrick
>>>>
>>
Re: Nature of JAXB Views Models
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi Patrick,
I agree, it should be possible to do what you want. I've raised a ticket
[1] for it.
In the meantime, go with nature=VIEW_MODEL and add a TODO in your code to
update when we make the fix.
Thx
Dan
[1] https://issues.apache.org/jira/browse/ISIS-1749
On Fri, 20 Oct 2017 at 13:11 Patrick Pliessnig <p....@gmail.com>
wrote:
> It passes validation effectively with nature = Nature.VIEW_MODEL
> indicating (as much as I can see) that the view model belongs to the
> application layer.
>
> But using
>
> nature = Nature.INMEMORY_ENTITY or
> nature = Nature.EXTERNAL_ENTITY
>
> to indicate that the view model is just a proxy for other domain objects
> in the domain layer generates this validation error:
>
> ... has multiple incompatible annotations/interfaces indicating that
> it is a recreatable object of some sort
> (RecreatableObjectFacetForDomainObjectAnnotation and
> RecreatableObjectFacetForXmlRootElementAnnotation)
>
> So, I don't know how to specify that a jaxb view model is - say - a
> proxy for an external entity as I can do with legacy view models.
>
>
>
> Am 20.10.2017 um 13:22 schrieb Jeroen van der Wal:
> > This is how I use it:
> >
> > @DomainObject(nature = Nature.VIEW_MODEL, objectType = "MyJaxbViewModel")
> > @XmlRootElement(name = "myJaxbViewModel")
> > @XmlType(
> > propOrder = {
> > "myIncludedProperty"
> > }
> > )
> > @XmlAccessorType(XmlAccessType.FIELD)
> > public class MyJaxbViewModel {
> >
> > @Getter @Setter @Nullable
> > private String myIncludedProperty;
> >
> > @Getter @Setter @Nullable
> > private String myIncludedProperty;
> >
> > @XmlTransient
> > private String myExcludedProperty;
> >
> > }
> >
> > HTH
> >
> >
> > On 20 October 2017 at 12:28, Patrick Pliessnig <p....@gmx.net>
> wrote:
> >
> >> Hi
> >>
> >> Modeling a JAXB view model with @XmlRootElement and its nature with
> >> @DomainObject( nature = ... ) does not pass metamodel validation.
> >>
> >> Is there way to indicate the nature of a JAXB view model?
> >> Eg. whether it belongs to the domain model or the application layer.
> >>
> >> thx
> >> Patrick
> >>
>
>
Re: Nature of JAXB Views Models
Posted by Patrick Pliessnig <p....@gmail.com>.
It passes validation effectively with nature = Nature.VIEW_MODEL
indicating (as much as I can see) that the view model belongs to the
application layer.
But using
nature = Nature.INMEMORY_ENTITY or
nature = Nature.EXTERNAL_ENTITY
to indicate that the view model is just a proxy for other domain objects
in the domain layer generates this validation error:
... has multiple incompatible annotations/interfaces indicating that
it is a recreatable object of some sort
(RecreatableObjectFacetForDomainObjectAnnotation and
RecreatableObjectFacetForXmlRootElementAnnotation)
So, I don't know how to specify that a jaxb view model is - say - a
proxy for an external entity as I can do with legacy view models.
Am 20.10.2017 um 13:22 schrieb Jeroen van der Wal:
> This is how I use it:
>
> @DomainObject(nature = Nature.VIEW_MODEL, objectType = "MyJaxbViewModel")
> @XmlRootElement(name = "myJaxbViewModel")
> @XmlType(
> propOrder = {
> "myIncludedProperty"
> }
> )
> @XmlAccessorType(XmlAccessType.FIELD)
> public class MyJaxbViewModel {
>
> @Getter @Setter @Nullable
> private String myIncludedProperty;
>
> @Getter @Setter @Nullable
> private String myIncludedProperty;
>
> @XmlTransient
> private String myExcludedProperty;
>
> }
>
> HTH
>
>
> On 20 October 2017 at 12:28, Patrick Pliessnig <p....@gmx.net> wrote:
>
>> Hi
>>
>> Modeling a JAXB view model with @XmlRootElement and its nature with
>> @DomainObject( nature = ... ) does not pass metamodel validation.
>>
>> Is there way to indicate the nature of a JAXB view model?
>> Eg. whether it belongs to the domain model or the application layer.
>>
>> thx
>> Patrick
>>
Re: Nature of JAXB Views Models
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
thanks Jeroen.
slight typo ... "myIncludedProperty" is listed twice.
D
On Fri, 20 Oct 2017 at 12:22 Jeroen van der Wal <je...@stromboli.it> wrote:
> This is how I use it:
>
> @DomainObject(nature = Nature.VIEW_MODEL, objectType = "MyJaxbViewModel")
> @XmlRootElement(name = "myJaxbViewModel")
> @XmlType(
> propOrder = {
> "myIncludedProperty"
> }
> )
> @XmlAccessorType(XmlAccessType.FIELD)
> public class MyJaxbViewModel {
>
> @Getter @Setter @Nullable
> private String myIncludedProperty;
>
> @Getter @Setter @Nullable
> private String myIncludedProperty;
>
> @XmlTransient
> private String myExcludedProperty;
>
> }
>
> HTH
>
>
> On 20 October 2017 at 12:28, Patrick Pliessnig <p....@gmx.net>
> wrote:
>
> > Hi
> >
> > Modeling a JAXB view model with @XmlRootElement and its nature with
> > @DomainObject( nature = ... ) does not pass metamodel validation.
> >
> > Is there way to indicate the nature of a JAXB view model?
> > Eg. whether it belongs to the domain model or the application layer.
> >
> > thx
> > Patrick
> >
>
Re: Nature of JAXB Views Models
Posted by Jeroen van der Wal <je...@stromboli.it>.
This is how I use it:
@DomainObject(nature = Nature.VIEW_MODEL, objectType = "MyJaxbViewModel")
@XmlRootElement(name = "myJaxbViewModel")
@XmlType(
propOrder = {
"myIncludedProperty"
}
)
@XmlAccessorType(XmlAccessType.FIELD)
public class MyJaxbViewModel {
@Getter @Setter @Nullable
private String myIncludedProperty;
@Getter @Setter @Nullable
private String myIncludedProperty;
@XmlTransient
private String myExcludedProperty;
}
HTH
On 20 October 2017 at 12:28, Patrick Pliessnig <p....@gmx.net> wrote:
> Hi
>
> Modeling a JAXB view model with @XmlRootElement and its nature with
> @DomainObject( nature = ... ) does not pass metamodel validation.
>
> Is there way to indicate the nature of a JAXB view model?
> Eg. whether it belongs to the domain model or the application layer.
>
> thx
> Patrick
>
Nature of JAXB Views Models
Posted by Patrick Pliessnig <p....@gmx.net>.
Hi
Modeling a JAXB view model with @XmlRootElement and its nature with
@DomainObject( nature = ... ) does not pass metamodel validation.
Is there way to indicate the nature of a JAXB view model?
Eg. whether it belongs to the domain model or the application layer.
thx
Patrick
Re: DOM folder - where is it hiding?
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
For 1.14.0 onwards, the preferred approach is to set properties. There are
used to configure the surefire plugin which is a "maven mixin", as per [1]
Specifically, you can use -DskipUTs , -DskipITs , -DskipBSs . You can also
use -DskipTests to skip all tests.
For earlier versions (1.13.x and previously), you can use -DskipTests to
skip all tests, or you can use -pl !integtests , described further here [2]
for example
HTH
Dan
[1] https://github.com/danhaywood/java-mavenmixin-surefire#how-to-use
[2] http://stackoverflow.com/a/27177197/56880
On Thu, 30 Mar 2017 at 09:09 Dan Haywood <da...@haywood-associates.co.uk>
wrote:
> Actually, in the 1.14.0 version of the simpleapp archetype the 'dom',
> 'fixture' and 'integtests' module have all been moved.
>
> Instead, you'll see a module/simple (or it might be called module-simple)
> which contains each of these modules.
>
> The idea is to support modular development, so each module provides its
> own fixtures and can have its own unit tests (which it already did) and
> also integration tests.
>
> The 'app' module meanwhile has "smoke" integ tests which exercise the
> whole app. I've left the BDD cucumber tests there also.
>
> We're slowly refactoring our Estatio app [1] to follow this structure. I
> also discussed modular apps in a pair of articles on InfoQ [2], [3]
>
> Hope that makes sense.
>
> Dan
>
>
> [1] http://github.com/estatio/estatio
>
> [2] https://www.infoq.com/articles/monolith-defense-part-1
>
> [3] https://www.infoq.com/articles/monolith-defense-part-2
>
> On Thu, 30 Mar 2017, 06:34 Stephen Cameron, <st...@gmail.com>
> wrote:
>
> Hello Josh,
>
> The dom (domain object model) project has not disappeared after 1.13.1.
>
> The standard project setup is actually a group of 5 sub-projects (each
> with their own maven project object model file 'pom.xml'): app, dom (domain
> object model), fixtures, integtest, webapp.
>
> All are important and cross-link, but you are correct that the dom project
> will normally contain the classes that need to be enhanced by DataNucleus,
> which for efficient workflow you should enable in your IDE of choice.
>
>
>
>
>
> On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
>
> > Hi, I am new to Apache Isis and trying to get familiar with the setup and
> > workflow. I have been working through the official first tutorial, "Pet
> > Clinic".
> >
> > In the archetype version used (1.13.1), the DOM folder appears as a top
> > level folder in the generated project. This corresponds to other
> > documentation and YouTube videos, and enables the Enhancer to be set up
> in
> > IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> > https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
> >
> > The setting up of the enhancer is pointed out to be a very important
> step,
> > and clearly, one needs to know what Working Directory to point the
> enhancer
> > to. But also, that DOM folder seems to be the key thing upon which the
> > entire Apache Isis concept is based.
> >
> > So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> > through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
> > expert and it's not making sense to me.
> >
> > Thanks
> > Josh
> >
>
>
Re: DOM folder - where is it hiding?
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Actually, in the 1.14.0 version of the simpleapp archetype the 'dom',
'fixture' and 'integtests' module have all been moved.
Instead, you'll see a module/simple (or it might be called module-simple)
which contains each of these modules.
The idea is to support modular development, so each module provides its own
fixtures and can have its own unit tests (which it already did) and also
integration tests.
The 'app' module meanwhile has "smoke" integ tests which exercise the whole
app. I've left the BDD cucumber tests there also.
We're slowly refactoring our Estatio app [1] to follow this structure. I
also discussed modular apps in a pair of articles on InfoQ [2], [3]
Hope that makes sense.
Dan
[1] http://github.com/estatio/estatio
[2] https://www.infoq.com/articles/monolith-defense-part-1
[3] https://www.infoq.com/articles/monolith-defense-part-2
On Thu, 30 Mar 2017, 06:34 Stephen Cameron, <st...@gmail.com>
wrote:
Hello Josh,
The dom (domain object model) project has not disappeared after 1.13.1.
The standard project setup is actually a group of 5 sub-projects (each
with their own maven project object model file 'pom.xml'): app, dom (domain
object model), fixtures, integtest, webapp.
All are important and cross-link, but you are correct that the dom project
will normally contain the classes that need to be enhanced by DataNucleus,
which for efficient workflow you should enable in your IDE of choice.
On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
> Hi, I am new to Apache Isis and trying to get familiar with the setup and
> workflow. I have been working through the official first tutorial, "Pet
> Clinic".
>
> In the archetype version used (1.13.1), the DOM folder appears as a top
> level folder in the generated project. This corresponds to other
> documentation and YouTube videos, and enables the Enhancer to be set up in
> IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
>
> The setting up of the enhancer is pointed out to be a very important step,
> and clearly, one needs to know what Working Directory to point the
enhancer
> to. But also, that DOM folder seems to be the key thing upon which the
> entire Apache Isis concept is based.
>
> So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
> expert and it's not making sense to me.
>
> Thanks
> Josh
>
AW: DOM folder - where is it hiding?
Posted by "Rade, Joerg / Kuehne + Nagel / Ham GI-DP" <Jo...@Kuehne-Nagel.com>.
Hi Stephen, Josh,
CMIIW the integtest folder gets important when there are more than one dom folder(s).
At least I have commented it out in the root pom.xml and it saves a couple of seconds when I build.
Writing this I think about putting test calls to the REST Api here ...
Best regards
Jörg
-----Ursprüngliche Nachricht-----
Von: Stephen Cameron [mailto:steve.cameron.62@gmail.com]
Gesendet: Donnerstag, 30. März 2017 06:34
An: users@isis.apache.org
Betreff: Re: DOM folder - where is it hiding?
Hello Josh,
The dom (domain object model) project has not disappeared after 1.13.1.
The standard project setup is actually a group of 5 sub-projects (each with their own maven project object model file 'pom.xml'): app, dom (domain object model), fixtures, integtest, webapp.
All are important and cross-link, but you are correct that the dom project will normally contain the classes that need to be enhanced by DataNucleus, which for efficient workflow you should enable in your IDE of choice.
On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
> Hi, I am new to Apache Isis and trying to get familiar with the setup
> and workflow. I have been working through the official first tutorial,
> "Pet Clinic".
>
> In the archetype version used (1.13.1), the DOM folder appears as a
> top level folder in the generated project. This corresponds to other
> documentation and YouTube videos, and enables the Enhancer to be set
> up in IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
>
> The setting up of the enhancer is pointed out to be a very important
> step, and clearly, one needs to know what Working Directory to point
> the enhancer to. But also, that DOM folder seems to be the key thing
> upon which the entire Apache Isis concept is based.
>
> So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no
> Maven expert and it's not making sense to me.
>
> Thanks
> Josh
>
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, Matthias Heimbach, 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.
Re: DOM folder - where is it hiding?
Posted by Stephen Cameron <st...@gmail.com>.
Hello Josh,
The dom (domain object model) project has not disappeared after 1.13.1.
The standard project setup is actually a group of 5 sub-projects (each
with their own maven project object model file 'pom.xml'): app, dom (domain
object model), fixtures, integtest, webapp.
All are important and cross-link, but you are correct that the dom project
will normally contain the classes that need to be enhanced by DataNucleus,
which for efficient workflow you should enable in your IDE of choice.
On Thu, Mar 30, 2017 at 2:04 PM, Joshua Beck <de...@jbeck.com.au> wrote:
> Hi, I am new to Apache Isis and trying to get familiar with the setup and
> workflow. I have been working through the official first tutorial, "Pet
> Clinic".
>
> In the archetype version used (1.13.1), the DOM folder appears as a top
> level folder in the generated project. This corresponds to other
> documentation and YouTube videos, and enables the Enhancer to be set up in
> IntelliJ IDEA as per the instructions in the Developer's Guide, at:
> https://isis.apache.org/guides/dg.html#__dg_ide_intellij_running .
>
> The setting up of the enhancer is pointed out to be a very important step,
> and clearly, one needs to know what Working Directory to point the enhancer
> to. But also, that DOM folder seems to be the key thing upon which the
> entire Apache Isis concept is based.
>
> So, after 1.13.1, where has it disappeared to? I have tried to puzzle
> through the pom.xml and pom-jdo-enhance-all.xml files, but I'm no Maven
> expert and it's not making sense to me.
>
> Thanks
> Josh
>