You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com> on 2013/05/02 18:36:10 UTC
Hi to all. Project introduction and some doubts
Hi to all!
My name is Oscar and I'm the Team Leader of a software solution that is implemented with a vision really similar to Isis and we are also using some DDD patterns.
We are using JPA with an Hibernate implementation and custom annotations for defining field groups, localized names on the fields, field help texts extracted from the source Java help, etc.
All entity forms are generated automatically by a custom generator over Wavemaker technology stack (Spring + Hibernate + Java + JavaScript + DOJO).
Here are some examples of Domain classes:
A PARTY CLASS
@XMSEntityNames({
@XMSEntityName(locale = "es", name = "Organización / Persona"),
@XMSEntityName(locale = "en", name = "Party") })
@Entity
@Inheritance(strategy = InheritanceType.JOINED)
@DiscriminatorColumn(discriminatorType = DiscriminatorType.STRING, name = "DTYPE", length = 64)
public abstract class Party extends AbstractMultiTenantEntity {
@XMSField(locales = { @XMSLocale(locale = "es", caption = "Es Externa"),
@XMSLocale(locale = "en", caption = "Is External") })
private Boolean isExternal;
private String userName;
@OneToMany(mappedBy = "party", cascade = CascadeType.REMOVE)
@XMSField(locales = { @XMSLocale(locale = "es", caption = "Direcciones"),
@XMSLocale(locale = "en", caption = "Addresses") })
private Set<AddressParty> addresses;
@OneToMany(mappedBy = "party", cascade = CascadeType.REMOVE)
@XMSField(locales = {
@XMSLocale(locale = "es", caption = "Responsabilidades"),
@XMSLocale(locale = "en", caption = "Responsibilities") })
private Set<ResponsibilityParty> responsibilities;
[... getters, setters and custom methods ...]
A CLASS WITH SECTIONS (FIELD GROUPS ON THE USER INTERFACE)
@Entity
@Inheritance(strategy = InheritanceType.JOINED)
@XMSSections(value = {
@XMSSection(code = "RISK", locales = {
@XMSLocale(locale = "es", caption = "Riesgo", description = "Información relacionada con la Gestión del Riesgo"),
@XMSLocale(locale = "en", caption = "Risk", description = "Information related to the Management of Risks") }),
@XMSSection(code = "CONTINUITY", locales = {
@XMSLocale(locale = "es", caption = "Continuidad de Negocio", description = "Información relacionada con la Continuidad de Negocio"),
@XMSLocale(locale = "en", caption = "Business Continuity", description = "Information related to the Continuity of the Business Activities and their impact on Customer's Products and Services") }) })
public abstract class AssetAssessment extends AbstractMultiTenantEntity {
@SuppressWarnings("unused")
@Transient
@XMSField(show = false, locales = { @XMSLocale(locale = "es", caption = "Activo") }, section = "RISK")
private XMSAsset asset;
/***** CHARACTERIZATION *****/
@XMSField(locales = { @XMSLocale(locale = "es", caption = "Valoración del Activo") }, section = "RISK")
@Embedded
private AssetAssessmentValuation assetValuation;
@XMSField(locales = { @XMSLocale(locale = "es", caption = "Localización") })
@ManyToOne
private LocationAssessment location;
As you can imagine through the previous code, our framework vision it's quite similar to this one. An important difference is support for multiple languages on some critical annotations.
As you can see previously, de @XMSField is like the @Named one from ISIS, but supporting localization.
The @Description should also support localization. In our case, we are directly generating the help texts from the source files using a custom Doclet.
I'm following the project and email list for the last months, because we have been spending a lot of resources developing our framework but are thinking about evaluating for future Bounded Contexts a mixed approach, using Apache Isis for the Domain Model development, testing and REST API, and our technology for the User Interface and other infrastructure areas.
Migration from JPA to JDO seems quite fast and easy (but directly supporting it would be perfect, despite what I've seen from JDO seems really, really good). As our programming model was also quite similar, it seems also relatively easy to "migrate" our custom annotations to your equivalent ones.
Prior to starting the formal evaluation of the migration process, we want to make a prototype migrating one Bounded Context. For that, we have used the Maven archetype for creating the prototype. Current Archetype is really good exposing really fast the Domain through a web and a REST interface. But we find Testing (Junit mainly but also BDD), "the programmer's interface", is missing and would be perfect to have some test examples with the JUnit viewer and the BDD viewer.
It would also be really good to have a more complex model on the Archetype, showing the proper annotations and use of Entities, ValueObjects, Aggregates, Repositories, Factories, ... It would be ideal to have a model equivalent to the SCRUM one exposed on the "Implementing Design Driven Development", showing how to implement it on Apache Isis. It would also help on identifying "gaps" on the framework or, if different design decisions have been taken, to justify it by comments (for example, the one to not referencing Aggregates by id due to automatic lazy loading on DataNucleus, that was discussed some days ago).
Another design recommendation would be the creation of an annotation, method example, etc. for automatically registering a new service. We are now editing the wicket viewer "isis.properties" file, but we waited for an automatic "convention over configuration" way of doing it.
Is there an example with a more complex Domain, testing, etc. anywhere that we can further analyze?
Thanks a lot in advance,
Oscar
RE: Hi to all. Project introduction and some doubts
Posted by Christian Steinebach <Ch...@marintek.sintef.no>.
Hi!
There is also a less privileged user, Arne / pass
Arne is not allowed to plan (when selecting a TransportDemand)
Christian
________________________________________
From: Mike Burton [mikeb@mycosystems.co.uk]
Sent: Friday, May 03, 2013 4:29 PM
To: users@isis.apache.org
Subject: Re: Hi to all. Project introduction and some doubts
Thanks Christian!
For others wanting to try it remember sven / pass
Best Regards
Mike Burton
On 3 May 2013, at 14:45, Christian Steinebach <Ch...@marintek.sintef.no> wrote:
> Hi!
>
> As Dan mentioned me as a "third party" ;-) here's a link to the demo I did, the 'Transport Planning Manger'
> http://tpmdemo.eidemsnesset.cloudbees.net/
>
> The background is a bit like the example for "Implementing Design Driven Development", but I didn't know about it when I started.
> I had little time to come up with something useful but ISIS has made it possible.
> The demo only uses the in-memory object store. Unfortunately the project has come to an end for now.
>
> The source code can be found here
> git@git.assembla.com:transportplanner.git
>
> Cheers
> Christian
>
>
>
> ________________________________________
> From: Dan Haywood [dan@haywood-associates.co.uk]
> Sent: Friday, May 03, 2013 12:21 AM
> To: users; o.bou@gesconsultor.com
> Subject: Re: Hi to all. Project introduction and some doubts
>
> Hi Oscar,
>
> Thanks for your interest in Isis, and for your very interesting email. I'm
> replying to both you and to the mailing list; you might want to subscribe
> to users@isis.a.o and/or dev@isis.a.o.
>
> I'll reply in line so that I don't miss anything....
>
>
> On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
>>
>> We are using JPA with an Hibernate implementation ...
>
>
> As you probably know, the Hibernate license is incompatible with ASF; this
> is one of the reasons why we use JDO/DN.
>
>
>
>
>>
>> Here are some examples of Domain classes:
>>
>> [snip]
>
>
>
>> As you can imagine through the previous code, our framework vision it's
>> quite similar to this one.
>
>
> Yes, pretty similar. I didn't notice any actions though? Where do you put
> your "know-how-to" responsibilities; do you subscribe to Isis'
> "behaviourally complete" objects?
>
>
>
>> An important difference is support for multiple languages on some critical
>> annotations.
>> As you can see previously, de @XMSField is like the @Named one from ISIS,
>> but supporting localization.
>>
>
>
> In fact, Isis' architecture does support localization. The @Named
> annotation is interpreted by the various FacetFactory's [1] that make up
> Isis' programming model and are part of its metamodel builder. In the case
> of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
> implementation of NamedFacet on the property.
>
> In addition, Isis has an API called FacetDecorator. One implementation is
> I18NFacetDecorator [3]. From this, you'll see that we can provide
> localized names, help text and descriptions.
>
> (As an aside: this FacetDecorator API actually predates the FacetFactorys,
> and we do intend (at least, I would like) to just have the FacetFactory
> API, and have an implementation of FacetFactory that can do the
> localization. Not a big deal).
>
> Just a note on your @XMSField annotation; it seems a bit odd to me to have
> the translations in the text rather than in a resource bundle. But
> presumably it fits your development process well enough, otherwise you
> wouldn't have done it that way. One thing you might want to consider: you
> could if you wanted write your own implementation of NamedFacetFactory that
> understands your @XMSField annotation, if you wanted. In other words,
> teach Isis about your programming model, rather than the other way around.
> (You would still need to translate the JPA stuff into JDO, though).
>
>
>
>
>> The @Description should also support localization. In our case, we are
>> directly generating the help texts from the source files using a custom
>> Doclet.
>>
>> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
>
>
>
>> I'm following the project and email list for the last months, because we
>> have been spending a lot of resources developing our framework but are
>> thinking about evaluating for future Bounded Contexts a mixed approach,
>> using Apache Isis for the Domain Model development, testing and REST API,
>> and our technology for the User Interface and other infrastructure areas.
>>
>>
> That's very interesting to hear. Which makes me ask in turn: is your UI
> stuff proprietary? or could it be open sourced in turn as another viewer
> for Isis?
>
>
>
>
>> Migration from JPA to JDO seems quite fast and easy (but directly
>> supporting it would be perfect, despite what I've seen from JDO seems
>> really, really good). As our programming model was also quite similar, it
>> seems also relatively easy to "migrate" our custom annotations to your
>> equivalent ones.
>>
>> Prior to starting the formal evaluation of the migration process, we want
>> to make a prototype migrating one Bounded Context. For that, we have used
>> the Maven archetype for creating the prototype. Current Archetype is really
>> good exposing really fast the Domain through a web and a REST interface.
>> But we find Testing (Junit mainly but also BDD), "the programmer's
>> interface", is missing and would be perfect to have some test examples with
>> the JUnit viewer and the BDD viewer.
>>
>>
> With respect to the JUnit viewer, at the moment it focuses on testing the
> UI/domain interaction, and just using an in-memory objectstore.
> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
> an Isis runtime for domain/DB integration (via the JDO objectstore)
>
> What I want to do is to combine these frameworks into a single JUnit
> framework, which allows domain/DB integration and optionally allows the
> full-stack UI/domain/DB integration too. This is the main reason I
> haven't released the JUnit viewer yet since us becoming a TLP.
>
> With respect to the BDD viewer, I think this also needs to work the same
> way; and it probably should be made part of the same single framework. So,
> then it's one integration testing stack for domain/DB testing, optionally
> testing the UI interaction through the existing JUnit viewer stuff or
> through the BDD viewer stuff.
>
>
>
>
>> It would also be really good to have a more complex model on the
>> Archetype, showing the proper annotations and use of Entities,
>> ValueObjects, Aggregates, Repositories, Factories, ...
>
>
> As you probably know if you've been following the mailing lists, Jeroen and
> I are both working part-time on a substantial app for his company, building
> an estate management application ("Estatio"). Think of it as the
> calculation engine for rents for tenants in shopping centres and the like,
> and then integrates with a separate general ledger system using the new
> PublishingService that I developed a month or two back.
>
> The intention is for this app to be open sourced when done (later this
> year, we expect). Some parts of it (to do with proprietary calculation
> algorithms) will remain closed source, but we think we can provide suitable
> plugin points such that the vast majority of the app is open sourced. The
> app also has a bunch of integration tests written using the
> IntegSystemForTest.
>
> By all means contact Jeroen or me off-list regarding this.
>
>
>
>> It would be ideal to have a model equivalent to the SCRUM one exposed on
>> the "Implementing Design Driven Development", showing how to implement it
>> on Apache Isis.
>
>
> Yes, that is a nice little domain that one could work up. Don't have the
> bandwidth myself, but if you are doing an evaluation of Isis, perhaps you
> might consider building it as a proof-of-concept and put it on github.
>
> Also, you might want to ping Christian Steinbach, who was very active a
> month or two back on the mailing lists while writing a demonstrator app
> using Isis. He would provide some useful "third-party" feedback for you, I
> would have thought.
>
>
>
>
>> It would also help on identifying "gaps" on the framework or, if different
>> design decisions have been taken, to justify it by comments (for example,
>> the one to not referencing Aggregates by id due to automatic lazy loading
>> on DataNucleus, that was discussed some days ago).
>>
>
> An unsatisfactory exchange... I've never had an answer I could understand
> as to why one would wish to do all that tedious mucking about with Ids if
> one has the power of an ORM to call upon. And all that extra boilerplate
> ultimately impedes being able to develop the ubiquitous language.
>
>
>
>
>>
>> Another design recommendation would be the creation of an annotation,
>> method example, etc. for automatically registering a new service. We are
>> now editing the wicket viewer "isis.properties" file, but we waited for an
>> automatic "convention over configuration" way of doing it.
>>
>
> Yes, I have this on my todo list... to automatically discover services, eg
> using the META-INF/services mechanism (or perhaps CDI).
>
> There is, in fact, a not-at-all-documented API to do this. If you create
> an implementation of ServicesInstaller [5], then you can specify to use it
> by adding a setting in isis.properties:
>
> isis.services-installer=com.foo.bar.MyServicesInstaller
>
>
> Haven't tried this for a good while, but it ought to work...
>
> You could use some code similar to the RegisterEntities domain service [6]
> that we wrote to bootstrap JDO more reliably.
>
>
>>
>> Is there an example with a more complex Domain, testing, etc. anywhere
>> that we can further analyze?
>>
>>
> Estatio would be the best example. When it's done, we do intend to use it
> as a substantive case study. "When it's done" being the operative words in
> that sentence.
>
> Hope that was helpful,
>
> Cheers
> Dan
>
> [1]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
> [2]
> https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
> [3]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
> [4]
> https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
> [5]
> https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
> [6]
> https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
>
>
>
>> Thanks a lot in advance,
>>
>> Oscar
>>
>>
>>
>>
Re: Hi to all. Project introduction and some doubts
Posted by Mike Burton <mi...@mycosystems.co.uk>.
Thanks Christian!
For others wanting to try it remember sven / pass
Best Regards
Mike Burton
On 3 May 2013, at 14:45, Christian Steinebach <Ch...@marintek.sintef.no> wrote:
> Hi!
>
> As Dan mentioned me as a "third party" ;-) here's a link to the demo I did, the 'Transport Planning Manger'
> http://tpmdemo.eidemsnesset.cloudbees.net/
>
> The background is a bit like the example for "Implementing Design Driven Development", but I didn't know about it when I started.
> I had little time to come up with something useful but ISIS has made it possible.
> The demo only uses the in-memory object store. Unfortunately the project has come to an end for now.
>
> The source code can be found here
> git@git.assembla.com:transportplanner.git
>
> Cheers
> Christian
>
>
>
> ________________________________________
> From: Dan Haywood [dan@haywood-associates.co.uk]
> Sent: Friday, May 03, 2013 12:21 AM
> To: users; o.bou@gesconsultor.com
> Subject: Re: Hi to all. Project introduction and some doubts
>
> Hi Oscar,
>
> Thanks for your interest in Isis, and for your very interesting email. I'm
> replying to both you and to the mailing list; you might want to subscribe
> to users@isis.a.o and/or dev@isis.a.o.
>
> I'll reply in line so that I don't miss anything....
>
>
> On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
>>
>> We are using JPA with an Hibernate implementation ...
>
>
> As you probably know, the Hibernate license is incompatible with ASF; this
> is one of the reasons why we use JDO/DN.
>
>
>
>
>>
>> Here are some examples of Domain classes:
>>
>> [snip]
>
>
>
>> As you can imagine through the previous code, our framework vision it's
>> quite similar to this one.
>
>
> Yes, pretty similar. I didn't notice any actions though? Where do you put
> your "know-how-to" responsibilities; do you subscribe to Isis'
> "behaviourally complete" objects?
>
>
>
>> An important difference is support for multiple languages on some critical
>> annotations.
>> As you can see previously, de @XMSField is like the @Named one from ISIS,
>> but supporting localization.
>>
>
>
> In fact, Isis' architecture does support localization. The @Named
> annotation is interpreted by the various FacetFactory's [1] that make up
> Isis' programming model and are part of its metamodel builder. In the case
> of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
> implementation of NamedFacet on the property.
>
> In addition, Isis has an API called FacetDecorator. One implementation is
> I18NFacetDecorator [3]. From this, you'll see that we can provide
> localized names, help text and descriptions.
>
> (As an aside: this FacetDecorator API actually predates the FacetFactorys,
> and we do intend (at least, I would like) to just have the FacetFactory
> API, and have an implementation of FacetFactory that can do the
> localization. Not a big deal).
>
> Just a note on your @XMSField annotation; it seems a bit odd to me to have
> the translations in the text rather than in a resource bundle. But
> presumably it fits your development process well enough, otherwise you
> wouldn't have done it that way. One thing you might want to consider: you
> could if you wanted write your own implementation of NamedFacetFactory that
> understands your @XMSField annotation, if you wanted. In other words,
> teach Isis about your programming model, rather than the other way around.
> (You would still need to translate the JPA stuff into JDO, though).
>
>
>
>
>> The @Description should also support localization. In our case, we are
>> directly generating the help texts from the source files using a custom
>> Doclet.
>>
>> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
>
>
>
>> I'm following the project and email list for the last months, because we
>> have been spending a lot of resources developing our framework but are
>> thinking about evaluating for future Bounded Contexts a mixed approach,
>> using Apache Isis for the Domain Model development, testing and REST API,
>> and our technology for the User Interface and other infrastructure areas.
>>
>>
> That's very interesting to hear. Which makes me ask in turn: is your UI
> stuff proprietary? or could it be open sourced in turn as another viewer
> for Isis?
>
>
>
>
>> Migration from JPA to JDO seems quite fast and easy (but directly
>> supporting it would be perfect, despite what I've seen from JDO seems
>> really, really good). As our programming model was also quite similar, it
>> seems also relatively easy to "migrate" our custom annotations to your
>> equivalent ones.
>>
>> Prior to starting the formal evaluation of the migration process, we want
>> to make a prototype migrating one Bounded Context. For that, we have used
>> the Maven archetype for creating the prototype. Current Archetype is really
>> good exposing really fast the Domain through a web and a REST interface.
>> But we find Testing (Junit mainly but also BDD), "the programmer's
>> interface", is missing and would be perfect to have some test examples with
>> the JUnit viewer and the BDD viewer.
>>
>>
> With respect to the JUnit viewer, at the moment it focuses on testing the
> UI/domain interaction, and just using an in-memory objectstore.
> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
> an Isis runtime for domain/DB integration (via the JDO objectstore)
>
> What I want to do is to combine these frameworks into a single JUnit
> framework, which allows domain/DB integration and optionally allows the
> full-stack UI/domain/DB integration too. This is the main reason I
> haven't released the JUnit viewer yet since us becoming a TLP.
>
> With respect to the BDD viewer, I think this also needs to work the same
> way; and it probably should be made part of the same single framework. So,
> then it's one integration testing stack for domain/DB testing, optionally
> testing the UI interaction through the existing JUnit viewer stuff or
> through the BDD viewer stuff.
>
>
>
>
>> It would also be really good to have a more complex model on the
>> Archetype, showing the proper annotations and use of Entities,
>> ValueObjects, Aggregates, Repositories, Factories, ...
>
>
> As you probably know if you've been following the mailing lists, Jeroen and
> I are both working part-time on a substantial app for his company, building
> an estate management application ("Estatio"). Think of it as the
> calculation engine for rents for tenants in shopping centres and the like,
> and then integrates with a separate general ledger system using the new
> PublishingService that I developed a month or two back.
>
> The intention is for this app to be open sourced when done (later this
> year, we expect). Some parts of it (to do with proprietary calculation
> algorithms) will remain closed source, but we think we can provide suitable
> plugin points such that the vast majority of the app is open sourced. The
> app also has a bunch of integration tests written using the
> IntegSystemForTest.
>
> By all means contact Jeroen or me off-list regarding this.
>
>
>
>> It would be ideal to have a model equivalent to the SCRUM one exposed on
>> the "Implementing Design Driven Development", showing how to implement it
>> on Apache Isis.
>
>
> Yes, that is a nice little domain that one could work up. Don't have the
> bandwidth myself, but if you are doing an evaluation of Isis, perhaps you
> might consider building it as a proof-of-concept and put it on github.
>
> Also, you might want to ping Christian Steinbach, who was very active a
> month or two back on the mailing lists while writing a demonstrator app
> using Isis. He would provide some useful "third-party" feedback for you, I
> would have thought.
>
>
>
>
>> It would also help on identifying "gaps" on the framework or, if different
>> design decisions have been taken, to justify it by comments (for example,
>> the one to not referencing Aggregates by id due to automatic lazy loading
>> on DataNucleus, that was discussed some days ago).
>>
>
> An unsatisfactory exchange... I've never had an answer I could understand
> as to why one would wish to do all that tedious mucking about with Ids if
> one has the power of an ORM to call upon. And all that extra boilerplate
> ultimately impedes being able to develop the ubiquitous language.
>
>
>
>
>>
>> Another design recommendation would be the creation of an annotation,
>> method example, etc. for automatically registering a new service. We are
>> now editing the wicket viewer "isis.properties" file, but we waited for an
>> automatic "convention over configuration" way of doing it.
>>
>
> Yes, I have this on my todo list... to automatically discover services, eg
> using the META-INF/services mechanism (or perhaps CDI).
>
> There is, in fact, a not-at-all-documented API to do this. If you create
> an implementation of ServicesInstaller [5], then you can specify to use it
> by adding a setting in isis.properties:
>
> isis.services-installer=com.foo.bar.MyServicesInstaller
>
>
> Haven't tried this for a good while, but it ought to work...
>
> You could use some code similar to the RegisterEntities domain service [6]
> that we wrote to bootstrap JDO more reliably.
>
>
>>
>> Is there an example with a more complex Domain, testing, etc. anywhere
>> that we can further analyze?
>>
>>
> Estatio would be the best example. When it's done, we do intend to use it
> as a substantive case study. "When it's done" being the operative words in
> that sentence.
>
> Hope that was helpful,
>
> Cheers
> Dan
>
> [1]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
> [2]
> https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
> [3]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
> [4]
> https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
> [5]
> https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
> [6]
> https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
>
>
>
>> Thanks a lot in advance,
>>
>> Oscar
>>
>>
>>
>>
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Many thanks, Christian. I'll put this on the Isis site tonight.
Cheers
Dan
On 7 May 2013 10:06, Christian Steinebach <
Christian.Steinebach@marintek.sintef.no> wrote:
> Hi Dan!
>
> No problem with the "third party" description. I liked it. :-)
> Feel free to add a link from the website.
> I added a 'quick tour' to the Readme.txt file
>
> --------------------------------------
> ...
> A quick tour:
> - log in with chris/pass
> - a user with less privilges is arne/pass (Arne is not allowed to plan. He
> represents a customer who only is able
> to creatae a transport demand)
>
> - System/Install to have some predefined objects. Give it some time to
> complete...
> - Select 'Transport Demands/All Transport Demands' to show a list of
> predefined transport demands, i.e. requests to
> transport a cargo from pickup to delivery.
> The calendar view gets somewhat confused by the dates.
> - Select 'Fiskarstrand-Rotterdam' with the Dried Fish cargo
> - On the left side of the screen some details show up, on the right side
> an empty schedule and no waypoints.
> - Select the 'Plan transport' at the top right corner of the screen
> - You may now enter you criteria for finding a transport. Max price, max
> time and/or 'fastest', 'cheapest', 'cheap and fast' and, as a bonus
> 'expensive and slow' ;-)
> The software uses a shortest-paths-algorithm to look for the best
> solutions according to your criterium
> - When done, click and a list with possible schedules is presented
> - Select one, click the corresponding check box on the left and click
> 'plan and book'
> - The image of the selected schedule changes (a tick mark is placed on top
> of the globe)
> - Select the transport demand again, either from the top menu or click on
> the corresponding bread crumb
> - The schedule is now filled, waypoints may be shown on a google map in
> the widget below
> - Click on 'Cost Pie' and 'Resource Usage' to see some graphs
> - You may now send an Event to the system. Events should in principle come
> from an outside system, but this is a demo...
> - Send a 'Failure event' and select a leg (probably not the last leg)
> - The status in the schedule changes to CANCELD and a red cross icon is
> shown.
> - Selecting replan-transport will give you the possibility to replan the
> transport, starting at the canceled destination.
> - Be sure to select 'REPLAN and book' (plan and book is still shown. It
> should have been hidden...)
>
> - Have a look at all the logistic service providers, all logistic
> services, all destinations etc.
> - See the file TpmFixture.java for how the main domain objects link.
>
> The software is not as streamlined as it should be and it contains bugs.
> ;-)
>
> Some screenshots are here:
>
> https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/TransportDemand.png
>
> https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/TPM_CostPie.png
>
> https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/Tpm_ResourceUsage.png
> -------------------------------------------------------
>
>
> Cheers
> Christian
>
> ________________________________________
> From: Dan Haywood [dan@haywood-associates.co.uk]
> Sent: Monday, May 06, 2013 6:03 PM
> To: users; Christian Steinebach
> Subject: Re: Hi to all. Project introduction and some doubts
>
> On 3 May 2013 14:45, Christian Steinebach <
> Christian.Steinebach@marintek.sintef.no<mailto:
> Christian.Steinebach@marintek.sintef.no>> wrote:
> Hi!
>
> As Dan mentioned me as a "third party" ;-)
>
> sorry, slightly clumsily phrased...!
>
> here's a link to the demo I did, the 'Transport Planning Manger'
> http://tpmdemo.eidemsnesset.cloudbees.net/
>
> [snip]
>
> The source code can be found here
> git@git.assembla.com:transportplanner.git
>
>
> Thanks for making these resource available, Christian. May I add these as
> a link from the Isis website?
>
> Cheers
> Dan
>
>
> Cheers
> Christian
>
>
RE: Hi to all. Project introduction and some doubts
Posted by Christian Steinebach <Ch...@marintek.sintef.no>.
Hi Dan!
No problem with the "third party" description. I liked it. :-)
Feel free to add a link from the website.
I added a 'quick tour' to the Readme.txt file
--------------------------------------
...
A quick tour:
- log in with chris/pass
- a user with less privilges is arne/pass (Arne is not allowed to plan. He represents a customer who only is able
to creatae a transport demand)
- System/Install to have some predefined objects. Give it some time to complete...
- Select 'Transport Demands/All Transport Demands' to show a list of predefined transport demands, i.e. requests to
transport a cargo from pickup to delivery.
The calendar view gets somewhat confused by the dates.
- Select 'Fiskarstrand-Rotterdam' with the Dried Fish cargo
- On the left side of the screen some details show up, on the right side an empty schedule and no waypoints.
- Select the 'Plan transport' at the top right corner of the screen
- You may now enter you criteria for finding a transport. Max price, max time and/or 'fastest', 'cheapest', 'cheap and fast' and, as a bonus 'expensive and slow' ;-)
The software uses a shortest-paths-algorithm to look for the best solutions according to your criterium
- When done, click and a list with possible schedules is presented
- Select one, click the corresponding check box on the left and click 'plan and book'
- The image of the selected schedule changes (a tick mark is placed on top of the globe)
- Select the transport demand again, either from the top menu or click on the corresponding bread crumb
- The schedule is now filled, waypoints may be shown on a google map in the widget below
- Click on 'Cost Pie' and 'Resource Usage' to see some graphs
- You may now send an Event to the system. Events should in principle come from an outside system, but this is a demo...
- Send a 'Failure event' and select a leg (probably not the last leg)
- The status in the schedule changes to CANCELD and a red cross icon is shown.
- Selecting replan-transport will give you the possibility to replan the transport, starting at the canceled destination.
- Be sure to select 'REPLAN and book' (plan and book is still shown. It should have been hidden...)
- Have a look at all the logistic service providers, all logistic services, all destinations etc.
- See the file TpmFixture.java for how the main domain objects link.
The software is not as streamlined as it should be and it contains bugs. ;-)
Some screenshots are here:
https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/TransportDemand.png
https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/TPM_CostPie.png
https://www.assembla.com/code/transportplanner/git/nodes/master/screenshots/Tpm_ResourceUsage.png
-------------------------------------------------------
Cheers
Christian
________________________________________
From: Dan Haywood [dan@haywood-associates.co.uk]
Sent: Monday, May 06, 2013 6:03 PM
To: users; Christian Steinebach
Subject: Re: Hi to all. Project introduction and some doubts
On 3 May 2013 14:45, Christian Steinebach <Ch...@marintek.sintef.no>> wrote:
Hi!
As Dan mentioned me as a "third party" ;-)
sorry, slightly clumsily phrased...!
here's a link to the demo I did, the 'Transport Planning Manger'
http://tpmdemo.eidemsnesset.cloudbees.net/
[snip]
The source code can be found here
git@git.assembla.com:transportplanner.git
Thanks for making these resource available, Christian. May I add these as a link from the Isis website?
Cheers
Dan
Cheers
Christian
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
On 3 May 2013 14:45, Christian Steinebach <
Christian.Steinebach@marintek.sintef.no> wrote:
> Hi!
>
> As Dan mentioned me as a "third party" ;-)
sorry, slightly clumsily phrased...!
> here's a link to the demo I did, the 'Transport Planning Manger'
> http://tpmdemo.eidemsnesset.cloudbees.net/
>
> [snip]
>
> The source code can be found here
> git@git.assembla.com:transportplanner.git
>
>
Thanks for making these resource available, Christian. May I add these as
a link from the Isis website?
Cheers
Dan
> Cheers
> Christian
>
>
Re: Hi to all. Project introduction and some doubts
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
Thanks a lot, Christian.
I've successfully downloaded your project from "git://git.assembla.com/transportplanner.git".
Seems there are some interesting things regarding Services implementation and more.
It's really helpful to have different projects to evaluate and compare.
Thanks,
Oscar
El 03/05/2013, a las 15:45, Christian Steinebach <Ch...@marintek.sintef.no> escribió:
> Hi!
>
> As Dan mentioned me as a "third party" ;-) here's a link to the demo I did, the 'Transport Planning Manger'
> http://tpmdemo.eidemsnesset.cloudbees.net/
>
> The background is a bit like the example for "Implementing Design Driven Development", but I didn't know about it when I started.
> I had little time to come up with something useful but ISIS has made it possible.
> The demo only uses the in-memory object store. Unfortunately the project has come to an end for now.
>
> The source code can be found here
> git@git.assembla.com:transportplanner.git
>
> Cheers
> Christian
>
>
>
> ________________________________________
> From: Dan Haywood [dan@haywood-associates.co.uk]
> Sent: Friday, May 03, 2013 12:21 AM
> To: users; o.bou@gesconsultor.com
> Subject: Re: Hi to all. Project introduction and some doubts
>
> Hi Oscar,
>
> Thanks for your interest in Isis, and for your very interesting email. I'm
> replying to both you and to the mailing list; you might want to subscribe
> to users@isis.a.o and/or dev@isis.a.o.
>
> I'll reply in line so that I don't miss anything....
>
>
> On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
>>
>> We are using JPA with an Hibernate implementation ...
>
>
> As you probably know, the Hibernate license is incompatible with ASF; this
> is one of the reasons why we use JDO/DN.
>
>
>
>
>>
>> Here are some examples of Domain classes:
>>
>> [snip]
>
>
>
>> As you can imagine through the previous code, our framework vision it's
>> quite similar to this one.
>
>
> Yes, pretty similar. I didn't notice any actions though? Where do you put
> your "know-how-to" responsibilities; do you subscribe to Isis'
> "behaviourally complete" objects?
>
>
>
>> An important difference is support for multiple languages on some critical
>> annotations.
>> As you can see previously, de @XMSField is like the @Named one from ISIS,
>> but supporting localization.
>>
>
>
> In fact, Isis' architecture does support localization. The @Named
> annotation is interpreted by the various FacetFactory's [1] that make up
> Isis' programming model and are part of its metamodel builder. In the case
> of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
> implementation of NamedFacet on the property.
>
> In addition, Isis has an API called FacetDecorator. One implementation is
> I18NFacetDecorator [3]. From this, you'll see that we can provide
> localized names, help text and descriptions.
>
> (As an aside: this FacetDecorator API actually predates the FacetFactorys,
> and we do intend (at least, I would like) to just have the FacetFactory
> API, and have an implementation of FacetFactory that can do the
> localization. Not a big deal).
>
> Just a note on your @XMSField annotation; it seems a bit odd to me to have
> the translations in the text rather than in a resource bundle. But
> presumably it fits your development process well enough, otherwise you
> wouldn't have done it that way. One thing you might want to consider: you
> could if you wanted write your own implementation of NamedFacetFactory that
> understands your @XMSField annotation, if you wanted. In other words,
> teach Isis about your programming model, rather than the other way around.
> (You would still need to translate the JPA stuff into JDO, though).
>
>
>
>
>> The @Description should also support localization. In our case, we are
>> directly generating the help texts from the source files using a custom
>> Doclet.
>>
>> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
>
>
>
>> I'm following the project and email list for the last months, because we
>> have been spending a lot of resources developing our framework but are
>> thinking about evaluating for future Bounded Contexts a mixed approach,
>> using Apache Isis for the Domain Model development, testing and REST API,
>> and our technology for the User Interface and other infrastructure areas.
>>
>>
> That's very interesting to hear. Which makes me ask in turn: is your UI
> stuff proprietary? or could it be open sourced in turn as another viewer
> for Isis?
>
>
>
>
>> Migration from JPA to JDO seems quite fast and easy (but directly
>> supporting it would be perfect, despite what I've seen from JDO seems
>> really, really good). As our programming model was also quite similar, it
>> seems also relatively easy to "migrate" our custom annotations to your
>> equivalent ones.
>>
>> Prior to starting the formal evaluation of the migration process, we want
>> to make a prototype migrating one Bounded Context. For that, we have used
>> the Maven archetype for creating the prototype. Current Archetype is really
>> good exposing really fast the Domain through a web and a REST interface.
>> But we find Testing (Junit mainly but also BDD), "the programmer's
>> interface", is missing and would be perfect to have some test examples with
>> the JUnit viewer and the BDD viewer.
>>
>>
> With respect to the JUnit viewer, at the moment it focuses on testing the
> UI/domain interaction, and just using an in-memory objectstore.
> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
> an Isis runtime for domain/DB integration (via the JDO objectstore)
>
> What I want to do is to combine these frameworks into a single JUnit
> framework, which allows domain/DB integration and optionally allows the
> full-stack UI/domain/DB integration too. This is the main reason I
> haven't released the JUnit viewer yet since us becoming a TLP.
>
> With respect to the BDD viewer, I think this also needs to work the same
> way; and it probably should be made part of the same single framework. So,
> then it's one integration testing stack for domain/DB testing, optionally
> testing the UI interaction through the existing JUnit viewer stuff or
> through the BDD viewer stuff.
>
>
>
>
>> It would also be really good to have a more complex model on the
>> Archetype, showing the proper annotations and use of Entities,
>> ValueObjects, Aggregates, Repositories, Factories, ...
>
>
> As you probably know if you've been following the mailing lists, Jeroen and
> I are both working part-time on a substantial app for his company, building
> an estate management application ("Estatio"). Think of it as the
> calculation engine for rents for tenants in shopping centres and the like,
> and then integrates with a separate general ledger system using the new
> PublishingService that I developed a month or two back.
>
> The intention is for this app to be open sourced when done (later this
> year, we expect). Some parts of it (to do with proprietary calculation
> algorithms) will remain closed source, but we think we can provide suitable
> plugin points such that the vast majority of the app is open sourced. The
> app also has a bunch of integration tests written using the
> IntegSystemForTest.
>
> By all means contact Jeroen or me off-list regarding this.
>
>
>
>> It would be ideal to have a model equivalent to the SCRUM one exposed on
>> the "Implementing Design Driven Development", showing how to implement it
>> on Apache Isis.
>
>
> Yes, that is a nice little domain that one could work up. Don't have the
> bandwidth myself, but if you are doing an evaluation of Isis, perhaps you
> might consider building it as a proof-of-concept and put it on github.
>
> Also, you might want to ping Christian Steinbach, who was very active a
> month or two back on the mailing lists while writing a demonstrator app
> using Isis. He would provide some useful "third-party" feedback for you, I
> would have thought.
>
>
>
>
>> It would also help on identifying "gaps" on the framework or, if different
>> design decisions have been taken, to justify it by comments (for example,
>> the one to not referencing Aggregates by id due to automatic lazy loading
>> on DataNucleus, that was discussed some days ago).
>>
>
> An unsatisfactory exchange... I've never had an answer I could understand
> as to why one would wish to do all that tedious mucking about with Ids if
> one has the power of an ORM to call upon. And all that extra boilerplate
> ultimately impedes being able to develop the ubiquitous language.
>
>
>
>
>>
>> Another design recommendation would be the creation of an annotation,
>> method example, etc. for automatically registering a new service. We are
>> now editing the wicket viewer "isis.properties" file, but we waited for an
>> automatic "convention over configuration" way of doing it.
>>
>
> Yes, I have this on my todo list... to automatically discover services, eg
> using the META-INF/services mechanism (or perhaps CDI).
>
> There is, in fact, a not-at-all-documented API to do this. If you create
> an implementation of ServicesInstaller [5], then you can specify to use it
> by adding a setting in isis.properties:
>
> isis.services-installer=com.foo.bar.MyServicesInstaller
>
>
> Haven't tried this for a good while, but it ought to work...
>
> You could use some code similar to the RegisterEntities domain service [6]
> that we wrote to bootstrap JDO more reliably.
>
>
>>
>> Is there an example with a more complex Domain, testing, etc. anywhere
>> that we can further analyze?
>>
>>
> Estatio would be the best example. When it's done, we do intend to use it
> as a substantive case study. "When it's done" being the operative words in
> that sentence.
>
> Hope that was helpful,
>
> Cheers
> Dan
>
> [1]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
> [2]
> https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
> [3]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
> [4]
> https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
> [5]
> https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
> [6]
> https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
>
>
>
>> Thanks a lot in advance,
>>
>> Oscar
>>
>>
>>
>>
RE: Hi to all. Project introduction and some doubts
Posted by Christian Steinebach <Ch...@marintek.sintef.no>.
Hi!
As Dan mentioned me as a "third party" ;-) here's a link to the demo I did, the 'Transport Planning Manger'
http://tpmdemo.eidemsnesset.cloudbees.net/
The background is a bit like the example for "Implementing Design Driven Development", but I didn't know about it when I started.
I had little time to come up with something useful but ISIS has made it possible.
The demo only uses the in-memory object store. Unfortunately the project has come to an end for now.
The source code can be found here
git@git.assembla.com:transportplanner.git
Cheers
Christian
________________________________________
From: Dan Haywood [dan@haywood-associates.co.uk]
Sent: Friday, May 03, 2013 12:21 AM
To: users; o.bou@gesconsultor.com
Subject: Re: Hi to all. Project introduction and some doubts
Hi Oscar,
Thanks for your interest in Isis, and for your very interesting email. I'm
replying to both you and to the mailing list; you might want to subscribe
to users@isis.a.o and/or dev@isis.a.o.
I'll reply in line so that I don't miss anything....
On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
> We are using JPA with an Hibernate implementation ...
As you probably know, the Hibernate license is incompatible with ASF; this
is one of the reasons why we use JDO/DN.
>
> Here are some examples of Domain classes:
>
> [snip]
> As you can imagine through the previous code, our framework vision it's
> quite similar to this one.
Yes, pretty similar. I didn't notice any actions though? Where do you put
your "know-how-to" responsibilities; do you subscribe to Isis'
"behaviourally complete" objects?
> An important difference is support for multiple languages on some critical
> annotations.
> As you can see previously, de @XMSField is like the @Named one from ISIS,
> but supporting localization.
>
In fact, Isis' architecture does support localization. The @Named
annotation is interpreted by the various FacetFactory's [1] that make up
Isis' programming model and are part of its metamodel builder. In the case
of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
implementation of NamedFacet on the property.
In addition, Isis has an API called FacetDecorator. One implementation is
I18NFacetDecorator [3]. From this, you'll see that we can provide
localized names, help text and descriptions.
(As an aside: this FacetDecorator API actually predates the FacetFactorys,
and we do intend (at least, I would like) to just have the FacetFactory
API, and have an implementation of FacetFactory that can do the
localization. Not a big deal).
Just a note on your @XMSField annotation; it seems a bit odd to me to have
the translations in the text rather than in a resource bundle. But
presumably it fits your development process well enough, otherwise you
wouldn't have done it that way. One thing you might want to consider: you
could if you wanted write your own implementation of NamedFacetFactory that
understands your @XMSField annotation, if you wanted. In other words,
teach Isis about your programming model, rather than the other way around.
(You would still need to translate the JPA stuff into JDO, though).
> The @Description should also support localization. In our case, we are
> directly generating the help texts from the source files using a custom
> Doclet.
>
> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
> I'm following the project and email list for the last months, because we
> have been spending a lot of resources developing our framework but are
> thinking about evaluating for future Bounded Contexts a mixed approach,
> using Apache Isis for the Domain Model development, testing and REST API,
> and our technology for the User Interface and other infrastructure areas.
>
>
That's very interesting to hear. Which makes me ask in turn: is your UI
stuff proprietary? or could it be open sourced in turn as another viewer
for Isis?
> Migration from JPA to JDO seems quite fast and easy (but directly
> supporting it would be perfect, despite what I've seen from JDO seems
> really, really good). As our programming model was also quite similar, it
> seems also relatively easy to "migrate" our custom annotations to your
> equivalent ones.
>
> Prior to starting the formal evaluation of the migration process, we want
> to make a prototype migrating one Bounded Context. For that, we have used
> the Maven archetype for creating the prototype. Current Archetype is really
> good exposing really fast the Domain through a web and a REST interface.
> But we find Testing (Junit mainly but also BDD), "the programmer's
> interface", is missing and would be perfect to have some test examples with
> the JUnit viewer and the BDD viewer.
>
>
With respect to the JUnit viewer, at the moment it focuses on testing the
UI/domain interaction, and just using an in-memory objectstore.
Separately, there is IsisSystemForTest [4], which can be used to bootstrap
an Isis runtime for domain/DB integration (via the JDO objectstore)
What I want to do is to combine these frameworks into a single JUnit
framework, which allows domain/DB integration and optionally allows the
full-stack UI/domain/DB integration too. This is the main reason I
haven't released the JUnit viewer yet since us becoming a TLP.
With respect to the BDD viewer, I think this also needs to work the same
way; and it probably should be made part of the same single framework. So,
then it's one integration testing stack for domain/DB testing, optionally
testing the UI interaction through the existing JUnit viewer stuff or
through the BDD viewer stuff.
> It would also be really good to have a more complex model on the
> Archetype, showing the proper annotations and use of Entities,
> ValueObjects, Aggregates, Repositories, Factories, ...
As you probably know if you've been following the mailing lists, Jeroen and
I are both working part-time on a substantial app for his company, building
an estate management application ("Estatio"). Think of it as the
calculation engine for rents for tenants in shopping centres and the like,
and then integrates with a separate general ledger system using the new
PublishingService that I developed a month or two back.
The intention is for this app to be open sourced when done (later this
year, we expect). Some parts of it (to do with proprietary calculation
algorithms) will remain closed source, but we think we can provide suitable
plugin points such that the vast majority of the app is open sourced. The
app also has a bunch of integration tests written using the
IntegSystemForTest.
By all means contact Jeroen or me off-list regarding this.
> It would be ideal to have a model equivalent to the SCRUM one exposed on
> the "Implementing Design Driven Development", showing how to implement it
> on Apache Isis.
Yes, that is a nice little domain that one could work up. Don't have the
bandwidth myself, but if you are doing an evaluation of Isis, perhaps you
might consider building it as a proof-of-concept and put it on github.
Also, you might want to ping Christian Steinbach, who was very active a
month or two back on the mailing lists while writing a demonstrator app
using Isis. He would provide some useful "third-party" feedback for you, I
would have thought.
> It would also help on identifying "gaps" on the framework or, if different
> design decisions have been taken, to justify it by comments (for example,
> the one to not referencing Aggregates by id due to automatic lazy loading
> on DataNucleus, that was discussed some days ago).
>
An unsatisfactory exchange... I've never had an answer I could understand
as to why one would wish to do all that tedious mucking about with Ids if
one has the power of an ORM to call upon. And all that extra boilerplate
ultimately impedes being able to develop the ubiquitous language.
>
> Another design recommendation would be the creation of an annotation,
> method example, etc. for automatically registering a new service. We are
> now editing the wicket viewer "isis.properties" file, but we waited for an
> automatic "convention over configuration" way of doing it.
>
Yes, I have this on my todo list... to automatically discover services, eg
using the META-INF/services mechanism (or perhaps CDI).
There is, in fact, a not-at-all-documented API to do this. If you create
an implementation of ServicesInstaller [5], then you can specify to use it
by adding a setting in isis.properties:
isis.services-installer=com.foo.bar.MyServicesInstaller
Haven't tried this for a good while, but it ought to work...
You could use some code similar to the RegisterEntities domain service [6]
that we wrote to bootstrap JDO more reliably.
>
> Is there an example with a more complex Domain, testing, etc. anywhere
> that we can further analyze?
>
>
Estatio would be the best example. When it's done, we do intend to use it
as a substantive case study. "When it's done" being the operative words in
that sentence.
Hope that was helpful,
Cheers
Dan
[1]
https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
[2]
https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
[3]
https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
[4]
https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
[5]
https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
[6]
https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
> Thanks a lot in advance,
>
> Oscar
>
>
>
>
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi David,
Nice to hear that you're making good progress with your app.
You can use the IntegTest support stuff already for your integration
testing. If you search through the codebase for IsisSystemForTest and
IsisSystemWithFixtures, you should see how it is used in some of our "tck"
tests. It ought to be relatively easy to adapt to your own case.
The JUnit viewer also does work as is (albeit not formally released); it's
just a matter of combining them together into one test framework that needs
to be done.
Cheers
Dan
On 3 May 2013 01:07, David Tildesley <da...@yahoo.co.nz> wrote:
> Hi Dan,
>
> We are building a corporate application using the ISIS framework as is
> (JDO, Wicket viewer) and it is going well.
>
> However the unfinished JUnit wrapper poses a problem for us in the long
> run. Keen to see it completed (that's a vote fromme).
>
>
> Unfortunately I can't publish the source for this particular application
> as it is not mine.
>
>
> Maybe port the "Car Serv" application from your book to ISIS ?
>
> Regards,
> David.
>
>
> > With respect to the JUnit viewer, at the moment it focuses on testing the
> > UI/domain interaction, and just using an in-memory objectstore.
> > Separately, there is IsisSystemForTest [4], which can be used to
> bootstrap
> > an Isis runtime for domain/DB integration (via the JDO objectstore)
>
> > What I want to do is to combine these frameworks into a single JUnit
> > framework, which allows domain/DB integration and optionally allows the
> > full-stack UI/domain/DB integration too. This is the main reason I
> > haven't released the JUnit viewer yet since us becoming a TLP.
>
> > With respect to the BDD viewer, I think this also needs to work the same
> > way; and it probably should be made part of the same single framework.
> So,
> > then it's one integration testing stack for domain/DB testing, optionally
> > testing the UI interaction through the existing JUnit viewer stuff or
> > through the BDD viewer stuff.
>
Re: Hi to all. Project introduction and some doubts
Posted by David Tildesley <da...@yahoo.co.nz>.
Hi Dan,
We are building a corporate application using the ISIS framework as is (JDO, Wicket viewer) and it is going well.
However the unfinished JUnit wrapper poses a problem for us in the long run. Keen to see it completed (that's a vote fromme).
Unfortunately I can't publish the source for this particular application as it is not mine.
Maybe port the "Car Serv" application from your book to ISIS ?
Regards,
David.
> With respect to the JUnit viewer, at the moment it focuses on testing the
> UI/domain interaction, and just using an in-memory objectstore.
> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
> an Isis runtime for domain/DB integration (via the JDO objectstore)
> What I want to do is to combine these frameworks into a single JUnit
> framework, which allows domain/DB integration and optionally allows the
> full-stack UI/domain/DB integration too. This is the main reason I
> haven't released the JUnit viewer yet since us becoming a TLP.
> With respect to the BDD viewer, I think this also needs to work the same
> way; and it probably should be made part of the same single framework. So,
> then it's one integration testing stack for domain/DB testing, optionally
> testing the UI interaction through the existing JUnit viewer stuff or
> through the BDD viewer stuff.
Re: Hi to all. Project introduction and some doubts
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
ok. We will try again with new release.
But now I'm more confident with the refactoring and perhaps will maintain the @PersistenceCapable(identityType=IdentityType.DATASTORE.
Nice to see it will be simply a decission of the user of the framework.
El 14/05/2013, a las 08:43, Dan Haywood <da...@haywood-associates.co.uk> escribió:
> On 13 May 2013 14:19, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
>>
>>
>> Regarding @PersistenceCapable(identityType=IdentityType.APPLICATION)
>> support, I will double-check but as I remember an Apache Isis exception was
>> raised with a message indicating that only
>> @PersistenceCapable(identityType=IdentityType.DATASTORE and
>> @PersistenceCapable(identityType=IdentityType.UNSPECIFIED were supported.
>>
>>
> I definitely removed this exception in the last few months. So, it might
> well be how our current official release works, but using snapshot you
> should find you can use APPLICATION identity type.
>
>
>
>
>>
>> I will ask "my bosses", but I don't expect much problems on publicising
>> that it uses Apache Isis as a case study.
>>
>> Thx. Let's get you into production first, then go round the loop on that.
>
>
> Cheers
> Dan
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
On 13 May 2013 14:19, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
>
> Regarding @PersistenceCapable(identityType=IdentityType.APPLICATION)
> support, I will double-check but as I remember an Apache Isis exception was
> raised with a message indicating that only
> @PersistenceCapable(identityType=IdentityType.DATASTORE and
> @PersistenceCapable(identityType=IdentityType.UNSPECIFIED were supported.
>
>
I definitely removed this exception in the last few months. So, it might
well be how our current official release works, but using snapshot you
should find you can use APPLICATION identity type.
>
> I will ask "my bosses", but I don't expect much problems on publicising
> that it uses Apache Isis as a case study.
>
> Thx. Let's get you into production first, then go round the loop on that.
Cheers
Dan
Re: Hi to all. Project introduction and some doubts
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
The same in our case for many-to-many relationships between Entities / ARs that have attributes. In our case, not "nearly", but always are Entities / ARs undiscovered.
So they can be modeled as a new Entity/AR with 2 many-to-one relationships to its "parents", and with 2 one-to-many relationships form its "parents" to it. I simply mentioned it for completeness.
Regarding @PersistenceCapable(identityType=IdentityType.APPLICATION) support, I will double-check but as I remember an Apache Isis exception was raised with a message indicating that only @PersistenceCapable(identityType=IdentityType.DATASTORE and @PersistenceCapable(identityType=IdentityType.UNSPECIFIED were supported.
We will also change our tests to use JDO with in-memory database, despite we are discovering some bugs in our Apache Isis Domain due to some subtle differences between them. Perhaps we will wait a bit more ... :-)
I will ask "my bosses", but I don't expect much problems on publicising that it uses Apache Isis as a case study.
PD: I'm looking forward the option to see "Estatio"'s way-of-doing things :-)) For its completeness, as it will require for sure latest snapshot, I would recommend to include some JUnit viewer tests as examples also.
Thanks!
El 12/05/2013, a las 15:55, Dan Haywood <da...@haywood-associates.co.uk> escribió:
> Hi Oscar,
> thanks for your various emails on the list, and apols for not answering
> before now. Let me have a go at answering each in turn...
>
>
> On Thursday, 9 May 2013, GESCONSULTOR - Óscar Bou wrote:
>
>>
>> What's the status of the DHTMLX viewer?
>>
>>
> This is Maurizio's baby, so he should probably answer for definite. My
> guess is that there's a month or two more of development required on it,
> though the best way to knock off the rough edges would be to have someone
> start prototyping on it. If this sounds of interest, I suggest you
> contact Maurizio offline about this.
>
> As I'm sure you are aware, the DHTMLX viewer won't ever be integrated into
> Isis proper, because of its dependency on the license of DHTMLX toolkit.
> However, to my mind it seems to be quite inexpensive, so if you found it
> to your liking, I am sure that wouldn't be a blocker for you.
>
> Also, there is some degree of coupling between the DHTMLX viewer and the
> Google App Engine; mostly because this is the target architecture that
> Maurizio works most commonly with. It ought to be straight-forward enough
> to decouple the two, but it isn't a piece of work that's been done. I was
> speaking offline with Maurizio today, and he'll create a branch on the Isis
> codebase to start teasing this out.
>
> (Irrespective of DHTMLX viewer, it would be good to be able to say that
> Isis can run on the GAE, but that isn't something available out of the box).
>
>
>
>
>> Regarding the Domain Model, we are looking at various Apache Isis domain
>> examples available on Git repositories.
>>
>> The point is that some of them do not use the JDO object-store and we are
>> trying to migrate part of our model with some complex Entity relationships
>> (one-to-one, one-to-many, many-to-many with attributes - as 2 one-to-many).
>>
>> It should be possible to implement many-to-many in Isis/JDO, though
> whenever I've done this I've always later found myself teasing out the
> association into a full-blown entity. For example, in Estatio (the app
> that Jeroen and I work on), there is a many-to-many between Lease and
> (shopping precinct) Unit. Although this is still called "LeaseUnit" in the
> domain model, we may well rename it to Occupancy, because this is the
> domain concept that it represents.
>
>
>
>> We used Application Identity, but in order to conform to Apache Isis
>> requirement, we must use
>> "@PersistenceCapable(identityType=IdentityType.DATASTORE)".
>
>
> I'm not sure that's correct; I'm pretty sure I've tested that the JDO
> objectstore works with application identity as well. My uncertainty is
> just that Estatio does use datastore identity throughout.
>
> You should check this then; it may well just work (at least on
> trunk/snapshot).
>
>
>
>> As we used Application Identity, we are changing our Layer SuperType (
>> http://thierryroussel.free.fr/java/books/martinfowler/www.martinfowler.com/isa/layerSupertype.html)
>> to have a Surrogated key and a different Business Key, because it's needed
>> for working with some Set implementations on Collections when the Entities
>> have not been persisted yet.
>>
>> An interesting link related to "Surrogated Key" vs "Business Key", their
>> implications on "equals()" and "hashTo()", is the following one (talks
>> about JPA, but as DataNucleus documentation, it's the same for JDO):
>> http://stackoverflow.com/questions/5031614/the-jpa-hashcode-equals-dilemma
>>
>> There seems to be a problem with the Wicket viewer version referenced by
>> the Quickstart Prototype related to Entity Collections implemented by Sets,
>> showing only one element on the screen despite the Set has more elements.
>> We have not tested it against current Wicket Viewer version.
>>
>
> Please do so, then.
>
> We use SortedSet and TreeSet as the impl, and have our domain entities
> implement Comparable so that they sort correctly. I could quite that this
> has been fixed in trunk/snapshot; there's been a lot of work done in this
> space over the last few months.
>
>
>
>>
>> Also, on our current framework we always made the Tests with an Hibernate
>> repository. But we are trying to use the JUnit Apache Isis support with the
>> "in-memory" repository. That's forcing also to some changes due to "bad
>> practices" (as we always worked with persisted objects Hibernate
>> initialized the Sets. DataNucleus do it also, but working with the
>> "in-memory" implementation seems to not supporting it).
>>
>
> For myself, I'm less and less keen on the in-memory objectstore, precisely
> because one gets these subtle differences in implementation. Certainly, on
> Estatio we pretty much use the JDO objectstore all the time, but configured
> to use an in-memory HSQLDB. It's a bit slower, perhaps, but I prefer the
> predictability.
>
> (Incidentallly, in Naked Objects for .NET, Isis' sort-of sister project
> outside of Apache, they are considering getting rid of their in-memory
> object store. Perhaps we might vote on doing the same in the future).
>
>
>
>>
>> Another point is that our current "WaveMaker viewer" automatically
>> implements default operations against @OneToMany elements and now we need
>> to implement each "addToXXX" and "removeFromXXX" methods (we are using the
>> Apache Isis Eclipse templates available here:
>> http://isis.apache.org/getting-started/editor-templates.html).
>>
>> Some teem has been spent reading DataNucleus documentation regarding
>> "managed relationships" for determining the JDO annotations equivalent to
>> JPA, if it's needed to manually update each @OneToMany collection (in JPA
>> terms), the @ManyToOne field, etc.
>>
>> Yes, JDO/DN doesn't really provide support for managed relationships; they
> are quite clear about that on their web pages. So you need to use the
> mutual registration pattern (as defined in the Eclipse templates). In
> fact, this is one area where the JDO objectstore and in-memory objectstore
> are identical: neither provide support for managed relationships.
>
> An alternative thing you can do, if you want, is to use the
> IsisJdoSupportImpl domain service's refresh() method. You can do a
> DomainObjectContainer#flush() to force JDO/DN to insert/update to the
> database, then reload the impacted object(s). This is less boilerplate
> overall, at the cost of a bit of a loss of performance.
>
>
>
>>
>> Our Domain Model has a lot of Entities (more than 200) so we are
>> constantly creating Repositories and Factories.
>
>
> That's an awful lot of entities. I hope you've organized them into
> modules, and are using a tool such as Structure101 to make sure you don't
> have any cyclic dependencies. Otherwise you might end up with a big ball
> of mud (which would be a shame).
>
> That said, I suspect that your use of Axon (that you mention below) might
> mitigate this/help you to decouple.
>
>
>
>> An annotation for automatically registering them would be really helpful.
>>
>
> Two things you can do.
>
> 1. raise a ticket in JIRA.
> 2. contribute a patch.
>
> If you look at the ServicesInstaller class, you will see that there is an
> API there. So it ought to be easy enough to implement this.
>
> Put a breakpoint on the constructor for ServicesInstallerFromConfiguration
> and look at the stacktrace so you can see how it is currently instantiated.
> But, in brief, you can configure your own implementation by registering in
> isis.properties; the key would be something like:
>
> isis.services-installer=com.mycompany.isis.MyServicesInstallerFromAnnotaition
>
>
>
>
>>
>> Also, our Domain Model publishes (and consumes) Domain Events. We've seen
>> the "Publishing Service" and we are thinking about how to use it within our
>> current architecture.
>>
>> For that we are using the excellent CQRS Java framework by Axon. See:
>> http://www.axonframework.org/.
>>
>> We use it for modeling internal services as @CommandHandlers, so our
>> Entities mainly use only "one Service": a Command Bus, which allows to
>> dispatch Commands synchronously or asynchronously. The @CommandHandler that
>> has been registered for processing the dispatched Command class.
>>
>> @CommandHandler
>> public void handleMonitorServiceFileServerFileCommand(
>> MonitorServiceFileServerFileCommand command) {
>>
>> // Find FTP resource type
>> ResourcePrototype resourcePrototype = vmwExternalAPI
>> .getResourcePrototype("FileServer File");
>>
>>
>>
>> An @EventHandler is simply a method properly annotated.
>>
>> @Component
>> public class TaskEventHandler {
>>
>> @EventHandler
>> public void handle(final AddTaskEvent event) {
>>
>>
>>
>> We are not fully implementing CQRS, but Axon implementation of the Command
>> and Event bus is excellent.
>
>
> Sounds a little bit like Guava's event bus?
>
> As I alluded to above, I can see that this might well be helpful for
> decoupling your system. I can't say that I have much experience of using
> in-process event busses, though; only ever external busses for interacting
> with other systems.
>
> My one concern with an architecture such as this is that you might end up
> with a lot of boilerplate (all those handlers, and commands, and such
> like), and that will slow down your ability to uncover new concepts in your
> ubiquitous language.
>
>
>
>
>> Some kind of similar support inside Apache Isis for Domain Events (and
>> hopefuly Commands) would be great. Current Apache Isis refers to
>> "Auto-publising" a method execution and other options, which is really
>> interesting.
>>
>>
> As you know, Isis uses metamodels, so we try not to reify such things into
> code unless we really need to. Hence, the PublishingService lets us
> publish data with a minimum bit of boilerplate. Speaking for myself, I'm
> rather happy with how the architecture leverages the Restful API in order
> to allow the subscriber be able to pull additional information on receipt
> of the event (as opposed to the event have to bundle up lots of information
> that may or may not be relevant to the subscriber). This can be
> customized: see the PayloadFactory stuff.
>
>
>
>>
>>
>> Following the "dev" email list I've seen a lot of "commits" to the
>> project. Perhaps a newer version should be released to Maven also for easly
>> evaluating with the Quickstart Prototype with all tested commits and new
>> functionalities implemented (and documented) on "snapshots".
>
>
> You are right, a lot of work has been done over the last few months.
>
> My intention is to push out a new release (of Isis code, wicket, JDO, RO
> and the archetype) later this month. It takes about one full day to do
> this (1/2 day before the vote, 1/2 day after), so you can appreciate it
> isn't something I feel inclined to do too often.
>
>
>
>
>> It should also include the JUnit viewer (despite we know it will change in
>> the future) for having a complete development framework ready, avoiding
>> dependencies with not "official" packages.
>>
>
> Hmm. Maybe. I see from your other recent mails on the list that there are
> still some issues with it. So I'm not sure I'm going to commit to that
> just yet.
>
>
>
>>
>> A little more complex domain showing one-to-one, one-to-many and
>> many-to-one relationships would be great, in order to avoid searching for
>> JDO documentation (for all JPA techs).
>>
>> As Jeroen said, we expect that Estatio will be released as open source.
> It isn't as large as your domain (about 50 entities), but is sufficiently
> rich to provide a good resource.
>
>
>
>>
>> After re-modeling the Layer SuperTypes we are going to start evaluating
>> behaviour, etc.
>>
>>
>> I must tell that we are seeing really good things on the framework that
>> can allow us a lot of improvements if leaving our "commodity zone" that
>> it's our custom-made framework :-))
>>
>>
> That's great to hear.
>
>
>
>>
>> Excuse me for all this long email, and thanks a lot in advance to all
>> group members for your effort towards achieving a great framework !!!
>>
>>
> Thanks again. Obviously Isis is still a small community and we're still
> picking up momentum, but it's really encouraging to see you and others
> doing real work with the framework.
>
> Perhaps later on in your project we might be able to create some
> publicisity (a case study, or similar); even if your code is closed-source,
> there's still a lot of value for other prospective users in knowing that
> big, substantive systems can be built with the framework.
>
> Cheers
> Dan
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi Oscar,
thanks for your various emails on the list, and apols for not answering
before now. Let me have a go at answering each in turn...
On Thursday, 9 May 2013, GESCONSULTOR - Óscar Bou wrote:
>
> What's the status of the DHTMLX viewer?
>
>
This is Maurizio's baby, so he should probably answer for definite. My
guess is that there's a month or two more of development required on it,
though the best way to knock off the rough edges would be to have someone
start prototyping on it. If this sounds of interest, I suggest you
contact Maurizio offline about this.
As I'm sure you are aware, the DHTMLX viewer won't ever be integrated into
Isis proper, because of its dependency on the license of DHTMLX toolkit.
However, to my mind it seems to be quite inexpensive, so if you found it
to your liking, I am sure that wouldn't be a blocker for you.
Also, there is some degree of coupling between the DHTMLX viewer and the
Google App Engine; mostly because this is the target architecture that
Maurizio works most commonly with. It ought to be straight-forward enough
to decouple the two, but it isn't a piece of work that's been done. I was
speaking offline with Maurizio today, and he'll create a branch on the Isis
codebase to start teasing this out.
(Irrespective of DHTMLX viewer, it would be good to be able to say that
Isis can run on the GAE, but that isn't something available out of the box).
> Regarding the Domain Model, we are looking at various Apache Isis domain
> examples available on Git repositories.
>
> The point is that some of them do not use the JDO object-store and we are
> trying to migrate part of our model with some complex Entity relationships
> (one-to-one, one-to-many, many-to-many with attributes - as 2 one-to-many).
>
> It should be possible to implement many-to-many in Isis/JDO, though
whenever I've done this I've always later found myself teasing out the
association into a full-blown entity. For example, in Estatio (the app
that Jeroen and I work on), there is a many-to-many between Lease and
(shopping precinct) Unit. Although this is still called "LeaseUnit" in the
domain model, we may well rename it to Occupancy, because this is the
domain concept that it represents.
> We used Application Identity, but in order to conform to Apache Isis
> requirement, we must use
> "@PersistenceCapable(identityType=IdentityType.DATASTORE)".
I'm not sure that's correct; I'm pretty sure I've tested that the JDO
objectstore works with application identity as well. My uncertainty is
just that Estatio does use datastore identity throughout.
You should check this then; it may well just work (at least on
trunk/snapshot).
> As we used Application Identity, we are changing our Layer SuperType (
> http://thierryroussel.free.fr/java/books/martinfowler/www.martinfowler.com/isa/layerSupertype.html)
> to have a Surrogated key and a different Business Key, because it's needed
> for working with some Set implementations on Collections when the Entities
> have not been persisted yet.
>
> An interesting link related to "Surrogated Key" vs "Business Key", their
> implications on "equals()" and "hashTo()", is the following one (talks
> about JPA, but as DataNucleus documentation, it's the same for JDO):
> http://stackoverflow.com/questions/5031614/the-jpa-hashcode-equals-dilemma
>
> There seems to be a problem with the Wicket viewer version referenced by
> the Quickstart Prototype related to Entity Collections implemented by Sets,
> showing only one element on the screen despite the Set has more elements.
> We have not tested it against current Wicket Viewer version.
>
Please do so, then.
We use SortedSet and TreeSet as the impl, and have our domain entities
implement Comparable so that they sort correctly. I could quite that this
has been fixed in trunk/snapshot; there's been a lot of work done in this
space over the last few months.
>
> Also, on our current framework we always made the Tests with an Hibernate
> repository. But we are trying to use the JUnit Apache Isis support with the
> "in-memory" repository. That's forcing also to some changes due to "bad
> practices" (as we always worked with persisted objects Hibernate
> initialized the Sets. DataNucleus do it also, but working with the
> "in-memory" implementation seems to not supporting it).
>
For myself, I'm less and less keen on the in-memory objectstore, precisely
because one gets these subtle differences in implementation. Certainly, on
Estatio we pretty much use the JDO objectstore all the time, but configured
to use an in-memory HSQLDB. It's a bit slower, perhaps, but I prefer the
predictability.
(Incidentallly, in Naked Objects for .NET, Isis' sort-of sister project
outside of Apache, they are considering getting rid of their in-memory
object store. Perhaps we might vote on doing the same in the future).
>
> Another point is that our current "WaveMaker viewer" automatically
> implements default operations against @OneToMany elements and now we need
> to implement each "addToXXX" and "removeFromXXX" methods (we are using the
> Apache Isis Eclipse templates available here:
> http://isis.apache.org/getting-started/editor-templates.html).
>
> Some teem has been spent reading DataNucleus documentation regarding
> "managed relationships" for determining the JDO annotations equivalent to
> JPA, if it's needed to manually update each @OneToMany collection (in JPA
> terms), the @ManyToOne field, etc.
>
> Yes, JDO/DN doesn't really provide support for managed relationships; they
are quite clear about that on their web pages. So you need to use the
mutual registration pattern (as defined in the Eclipse templates). In
fact, this is one area where the JDO objectstore and in-memory objectstore
are identical: neither provide support for managed relationships.
An alternative thing you can do, if you want, is to use the
IsisJdoSupportImpl domain service's refresh() method. You can do a
DomainObjectContainer#flush() to force JDO/DN to insert/update to the
database, then reload the impacted object(s). This is less boilerplate
overall, at the cost of a bit of a loss of performance.
>
> Our Domain Model has a lot of Entities (more than 200) so we are
> constantly creating Repositories and Factories.
That's an awful lot of entities. I hope you've organized them into
modules, and are using a tool such as Structure101 to make sure you don't
have any cyclic dependencies. Otherwise you might end up with a big ball
of mud (which would be a shame).
That said, I suspect that your use of Axon (that you mention below) might
mitigate this/help you to decouple.
> An annotation for automatically registering them would be really helpful.
>
Two things you can do.
1. raise a ticket in JIRA.
2. contribute a patch.
If you look at the ServicesInstaller class, you will see that there is an
API there. So it ought to be easy enough to implement this.
Put a breakpoint on the constructor for ServicesInstallerFromConfiguration
and look at the stacktrace so you can see how it is currently instantiated.
But, in brief, you can configure your own implementation by registering in
isis.properties; the key would be something like:
isis.services-installer=com.mycompany.isis.MyServicesInstallerFromAnnotaition
>
> Also, our Domain Model publishes (and consumes) Domain Events. We've seen
> the "Publishing Service" and we are thinking about how to use it within our
> current architecture.
>
> For that we are using the excellent CQRS Java framework by Axon. See:
> http://www.axonframework.org/.
>
> We use it for modeling internal services as @CommandHandlers, so our
> Entities mainly use only "one Service": a Command Bus, which allows to
> dispatch Commands synchronously or asynchronously. The @CommandHandler that
> has been registered for processing the dispatched Command class.
>
> @CommandHandler
> public void handleMonitorServiceFileServerFileCommand(
> MonitorServiceFileServerFileCommand command) {
>
> // Find FTP resource type
> ResourcePrototype resourcePrototype = vmwExternalAPI
> .getResourcePrototype("FileServer File");
>
>
>
> An @EventHandler is simply a method properly annotated.
>
> @Component
> public class TaskEventHandler {
>
> @EventHandler
> public void handle(final AddTaskEvent event) {
>
>
>
> We are not fully implementing CQRS, but Axon implementation of the Command
> and Event bus is excellent.
Sounds a little bit like Guava's event bus?
As I alluded to above, I can see that this might well be helpful for
decoupling your system. I can't say that I have much experience of using
in-process event busses, though; only ever external busses for interacting
with other systems.
My one concern with an architecture such as this is that you might end up
with a lot of boilerplate (all those handlers, and commands, and such
like), and that will slow down your ability to uncover new concepts in your
ubiquitous language.
> Some kind of similar support inside Apache Isis for Domain Events (and
> hopefuly Commands) would be great. Current Apache Isis refers to
> "Auto-publising" a method execution and other options, which is really
> interesting.
>
>
As you know, Isis uses metamodels, so we try not to reify such things into
code unless we really need to. Hence, the PublishingService lets us
publish data with a minimum bit of boilerplate. Speaking for myself, I'm
rather happy with how the architecture leverages the Restful API in order
to allow the subscriber be able to pull additional information on receipt
of the event (as opposed to the event have to bundle up lots of information
that may or may not be relevant to the subscriber). This can be
customized: see the PayloadFactory stuff.
>
>
> Following the "dev" email list I've seen a lot of "commits" to the
> project. Perhaps a newer version should be released to Maven also for easly
> evaluating with the Quickstart Prototype with all tested commits and new
> functionalities implemented (and documented) on "snapshots".
You are right, a lot of work has been done over the last few months.
My intention is to push out a new release (of Isis code, wicket, JDO, RO
and the archetype) later this month. It takes about one full day to do
this (1/2 day before the vote, 1/2 day after), so you can appreciate it
isn't something I feel inclined to do too often.
> It should also include the JUnit viewer (despite we know it will change in
> the future) for having a complete development framework ready, avoiding
> dependencies with not "official" packages.
>
Hmm. Maybe. I see from your other recent mails on the list that there are
still some issues with it. So I'm not sure I'm going to commit to that
just yet.
>
> A little more complex domain showing one-to-one, one-to-many and
> many-to-one relationships would be great, in order to avoid searching for
> JDO documentation (for all JPA techs).
>
> As Jeroen said, we expect that Estatio will be released as open source.
It isn't as large as your domain (about 50 entities), but is sufficiently
rich to provide a good resource.
>
> After re-modeling the Layer SuperTypes we are going to start evaluating
> behaviour, etc.
>
>
> I must tell that we are seeing really good things on the framework that
> can allow us a lot of improvements if leaving our "commodity zone" that
> it's our custom-made framework :-))
>
>
That's great to hear.
>
> Excuse me for all this long email, and thanks a lot in advance to all
> group members for your effort towards achieving a great framework !!!
>
>
Thanks again. Obviously Isis is still a small community and we're still
picking up momentum, but it's really encouraging to see you and others
doing real work with the framework.
Perhaps later on in your project we might be able to create some
publicisity (a case study, or similar); even if your code is closed-source,
there's still a lot of value for other prospective users in knowing that
big, substantive systems can be built with the framework.
Cheers
Dan
Re: Hi to all. Project introduction and some doubts
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
Thanks, Jeroen for your info.
What's the status of the DHTMLX viewer?
Regarding the Domain Model, we are looking at various Apache Isis domain examples available on Git repositories.
The point is that some of them do not use the JDO object-store and we are trying to migrate part of our model with some complex Entity relationships (one-to-one, one-to-many, many-to-many with attributes - as 2 one-to-many).
We used Application Identity, but in order to conform to Apache Isis requirement, we must use "@PersistenceCapable(identityType=IdentityType.DATASTORE)". As we used Application Identity, we are changing our Layer SuperType (http://thierryroussel.free.fr/java/books/martinfowler/www.martinfowler.com/isa/layerSupertype.html) to have a Surrogated key and a different Business Key, because it's needed for working with some Set implementations on Collections when the Entities have not been persisted yet.
An interesting link related to "Surrogated Key" vs "Business Key", their implications on "equals()" and "hashTo()", is the following one (talks about JPA, but as DataNucleus documentation, it's the same for JDO): http://stackoverflow.com/questions/5031614/the-jpa-hashcode-equals-dilemma
There seems to be a problem with the Wicket viewer version referenced by the Quickstart Prototype related to Entity Collections implemented by Sets, showing only one element on the screen despite the Set has more elements. We have not tested it against current Wicket Viewer version.
Also, on our current framework we always made the Tests with an Hibernate repository. But we are trying to use the JUnit Apache Isis support with the "in-memory" repository. That's forcing also to some changes due to "bad practices" (as we always worked with persisted objects Hibernate initialized the Sets. DataNucleus do it also, but working with the "in-memory" implementation seems to not supporting it).
Another point is that our current "WaveMaker viewer" automatically implements default operations against @OneToMany elements and now we need to implement each "addToXXX" and "removeFromXXX" methods (we are using the Apache Isis Eclipse templates available here: http://isis.apache.org/getting-started/editor-templates.html).
Some teem has been spent reading DataNucleus documentation regarding "managed relationships" for determining the JDO annotations equivalent to JPA, if it's needed to manually update each @OneToMany collection (in JPA terms), the @ManyToOne field, etc.
Our Domain Model has a lot of Entities (more than 200) so we are constantly creating Repositories and Factories. An annotation for automatically registering them would be really helpful.
Also, our Domain Model publishes (and consumes) Domain Events. We've seen the "Publishing Service" and we are thinking about how to use it within our current architecture.
For that we are using the excellent CQRS Java framework by Axon. See: http://www.axonframework.org/.
We use it for modeling internal services as @CommandHandlers, so our Entities mainly use only "one Service": a Command Bus, which allows to dispatch Commands synchronously or asynchronously. The @CommandHandler that has been registered for processing the dispatched Command class.
@CommandHandler
public void handleMonitorServiceFileServerFileCommand(
MonitorServiceFileServerFileCommand command) {
// Find FTP resource type
ResourcePrototype resourcePrototype = vmwExternalAPI
.getResourcePrototype("FileServer File");
An @EventHandler is simply a method properly annotated.
@Component
public class TaskEventHandler {
@EventHandler
public void handle(final AddTaskEvent event) {
We are not fully implementing CQRS, but Axon implementation of the Command and Event bus is excellent. Some kind of similar support inside Apache Isis for Domain Events (and hopefuly Commands) would be great. Current Apache Isis refers to "Auto-publising" a method execution and other options, which is really interesting.
Following the "dev" email list I've seen a lot of "commits" to the project. Perhaps a newer version should be released to Maven also for easly evaluating with the Quickstart Prototype with all tested commits and new functionalities implemented (and documented) on "snapshots". It should also include the JUnit viewer (despite we know it will change in the future) for having a complete development framework ready, avoiding dependencies with not "official" packages.
A little more complex domain showing one-to-one, one-to-many and many-to-one relationships would be great, in order to avoid searching for JDO documentation (for all JPA techs).
After re-modeling the Layer SuperTypes we are going to start evaluating behaviour, etc.
I must tell that we are seeing really good things on the framework that can allow us a lot of improvements if leaving our "commodity zone" that it's our custom-made framework :-))
Excuse me for all this long email, and thanks a lot in advance to all group members for your effort towards achieving a great framework !!!
El 06/05/2013, a las 22:14, Jeroen van der Wal <je...@stromboli.it> escribió:
> Hi Oscar,
>
> First of all welcome to this mailinglist. From the code you showed there's
> quite a good match between your framework and Isis. Together with Dan I'm
> developing a business application for managing and invoicing property
> leases. In the process of building the application Isis matured a lot and I
> think now is the time to have more people joining in developing
> critical business applications.
>
> In regard to your viewer solution I that Maurizio Tavernina is working on a
> DHTMLX viewer with an integrated DSL to develop custom(ised) user
> interfaces. This might be an interesting project for you to watch [1] and
> an a possible alternative to WaveMaker.
>
> Today I discussed open sourcing our codebase (which is still under
> construction) with the client and he agreed to do that. The only decision
> to be made is whether it's under Apache License 2.0 or GPLv3 but I expect
> that to be finalised soon. I will update the mailinglist when we have the
> code online.
>
> Kind regards,
>
>
> Jeroen van der Wal
>
> [1] http://isis.markmail.org/thread/scdyj62aujav7cfi
>
>
>
> On Fri, May 3, 2013 at 10:06 AM, GESCONSULTOR - Óscar Bou <
> o.bou@gesconsultor.com> wrote:
>
>> Hi, Adam and Dan.
>>
>> Thanks a lot for your responses.
>>
>> Adam, I'll look in detail on the project to pointed me and Dan, I (and
>> many others :-) will wait for the "Estatio" code with really, really
>> interest :-))
>>
>> Dan, regarding JPA I've seen on previous posts that LGPL licensing was the
>> reason to choose JDO. These 2-3 days I've seen that it's a really powerful
>> API also, and with more flexible solutions than JPA for @MappedSuperclass,
>> @Embeddable, for example. Also is clearer for specifying indexes, etc. But
>> the matter is that the majority is using JPA, so I think that a JPA
>> implementation compatible with Apache, such as OpenJPA will be needed on
>> the mid-term.
>>
>> ISIS framework implementation is quite more powerful than our framework.
>> That's the reason for change :-)) What I didn't noticed was the
>> Localization-related API. Thanks to point me towards it.
>>
>> Despite the JUnit viewer is not "finished", we will try to use it with the
>> maven archetype generated project. It would be really interesting to have
>> such a complete Domain testing framework fully integrated on ISIS and
>> available on the Maven Archetype, the first point of contact of all
>> evaluators.
>>
>> Regarding the Wavemaker's viewer, currently is propietary technology. If
>> the proof-of-concept goes well (I'm quite confident :-) we will need to
>> migrate it from our framework to Isis.
>> I'll try to convince Management to donate it to ISIS ;-) I'm not sure if
>> we will be able to commit to a full viewer's implementation for our own,
>> but at least the Wavemaker "specific" screen generations, etc. will be
>> done. Let's see how much effort and "ISIS specific knowledge" is needed for
>> a full viewer implementation or if any volunteer is needed. Wavemaker is a
>> really good complement to ISIS, as it's a visual RAD-like tool with User
>> Interface drag-and-drop design, completely developed on Java and DOJO.
>>
>> Regarding the "Ids" and Lazy Loading debate, I vote for "Id" referencing
>> for Aggregates from different Bounded Contexts (in order to limit the
>> dependencies between them, "types" importing, ...) but for references
>> between Aggregates on the same Bounded Context when using an ORM with Lazy
>> Loading support, we prefer referencing the type (as it's been done on ORM
>> since the beginning).
>>
>> The framework is becoming really powerful. Let's see how easy it's to
>> evaluate it :-)
>>
>> Thanks a lot to all the team for the really good work you are doing,
>>
>> Oscar
>>
>>
>>
>>
>>
>>
>>
>>
>> El 03/05/2013, a las 00:21, Dan Haywood <da...@haywood-associates.co.uk>
>> escribió:
>>
>>> Hi Oscar,
>>>
>>> Thanks for your interest in Isis, and for your very interesting email.
>> I'm replying to both you and to the mailing list; you might want to
>> subscribe to users@isis.a.o and/or dev@isis.a.o.
>>>
>>> I'll reply in line so that I don't miss anything....
>>>
>>>
>>> On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>
>> wrote:
>>>
>>> We are using JPA with an Hibernate implementation ...
>>>
>>> As you probably know, the Hibernate license is incompatible with ASF;
>> this is one of the reasons why we use JDO/DN.
>>>
>>>
>>>
>>>
>>> Here are some examples of Domain classes:
>>>
>>> [snip]
>>>
>>>
>>>
>>> As you can imagine through the previous code, our framework vision it's
>> quite similar to this one.
>>>
>>> Yes, pretty similar. I didn't notice any actions though? Where do you
>> put your "know-how-to" responsibilities; do you subscribe to Isis'
>> "behaviourally complete" objects?
>>>
>>>
>>> An important difference is support for multiple languages on some
>> critical annotations.
>>> As you can see previously, de @XMSField is like the @Named one from
>> ISIS, but supporting localization.
>>>
>>>
>>> In fact, Isis' architecture does support localization. The @Named
>> annotation is interpreted by the various FacetFactory's [1] that make up
>> Isis' programming model and are part of its metamodel builder. In the case
>> of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
>> implementation of NamedFacet on the property.
>>>
>>> In addition, Isis has an API called FacetDecorator. One implementation
>> is I18NFacetDecorator [3]. From this, you'll see that we can provide
>> localized names, help text and descriptions.
>>>
>>> (As an aside: this FacetDecorator API actually predates the
>> FacetFactorys, and we do intend (at least, I would like) to just have the
>> FacetFactory API, and have an implementation of FacetFactory that can do
>> the localization. Not a big deal).
>>>
>>> Just a note on your @XMSField annotation; it seems a bit odd to me to
>> have the translations in the text rather than in a resource bundle. But
>> presumably it fits your development process well enough, otherwise you
>> wouldn't have done it that way. One thing you might want to consider: you
>> could if you wanted write your own implementation of NamedFacetFactory that
>> understands your @XMSField annotation, if you wanted. In other words,
>> teach Isis about your programming model, rather than the other way around.
>> (You would still need to translate the JPA stuff into JDO, though).
>>>
>>>
>>>
>>> The @Description should also support localization. In our case, we are
>> directly generating the help texts from the source files using a custom
>> Doclet.
>>>
>>> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
>>>
>>>
>>> I'm following the project and email list for the last months, because we
>> have been spending a lot of resources developing our framework but are
>> thinking about evaluating for future Bounded Contexts a mixed approach,
>> using Apache Isis for the Domain Model development, testing and REST API,
>> and our technology for the User Interface and other infrastructure areas.
>>>
>>>
>>> That's very interesting to hear. Which makes me ask in turn: is your UI
>> stuff proprietary? or could it be open sourced in turn as another viewer
>> for Isis?
>>>
>>>
>>>
>>> Migration from JPA to JDO seems quite fast and easy (but directly
>> supporting it would be perfect, despite what I've seen from JDO seems
>> really, really good). As our programming model was also quite similar, it
>> seems also relatively easy to "migrate" our custom annotations to your
>> equivalent ones.
>>>
>>> Prior to starting the formal evaluation of the migration process, we
>> want to make a prototype migrating one Bounded Context. For that, we have
>> used the Maven archetype for creating the prototype. Current Archetype is
>> really good exposing really fast the Domain through a web and a REST
>> interface. But we find Testing (Junit mainly but also BDD), "the
>> programmer's interface", is missing and would be perfect to have some test
>> examples with the JUnit viewer and the BDD viewer.
>>>
>>>
>>> With respect to the JUnit viewer, at the moment it focuses on testing
>> the UI/domain interaction, and just using an in-memory objectstore.
>> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
>> an Isis runtime for domain/DB integration (via the JDO objectstore)
>>>
>>> What I want to do is to combine these frameworks into a single JUnit
>> framework, which allows domain/DB integration and optionally allows the
>> full-stack UI/domain/DB integration too. This is the main reason I
>> haven't released the JUnit viewer yet since us becoming a TLP.
>>>
>>> With respect to the BDD viewer, I think this also needs to work the same
>> way; and it probably should be made part of the same single framework. So,
>> then it's one integration testing stack for domain/DB testing, optionally
>> testing the UI interaction through the existing JUnit viewer stuff or
>> through the BDD viewer stuff.
>>>
>>>
>>>
>>> It would also be really good to have a more complex model on the
>> Archetype, showing the proper annotations and use of Entities,
>> ValueObjects, Aggregates, Repositories, Factories, ...
>>>
>>> As you probably know if you've been following the mailing lists, Jeroen
>> and I are both working part-time on a substantial app for his company,
>> building an estate management application ("Estatio"). Think of it as the
>> calculation engine for rents for tenants in shopping centres and the like,
>> and then integrates with a separate general ledger system using the new
>> PublishingService that I developed a month or two back.
>>>
>>> The intention is for this app to be open sourced when done (later this
>> year, we expect). Some parts of it (to do with proprietary calculation
>> algorithms) will remain closed source, but we think we can provide suitable
>> plugin points such that the vast majority of the app is open sourced. The
>> app also has a bunch of integration tests written using the
>> IntegSystemForTest.
>>>
>>> By all means contact Jeroen or me off-list regarding this.
>>>
>>>
>>> It would be ideal to have a model equivalent to the SCRUM one exposed on
>> the "Implementing Design Driven Development", showing how to implement it
>> on Apache Isis.
>>>
>>> Yes, that is a nice little domain that one could work up. Don't have
>> the bandwidth myself, but if you are doing an evaluation of Isis, perhaps
>> you might consider building it as a proof-of-concept and put it on github.
>>>
>>> Also, you might want to ping Christian Steinbach, who was very active a
>> month or two back on the mailing lists while writing a demonstrator app
>> using Isis. He would provide some useful "third-party" feedback for you, I
>> would have thought.
>>>
>>>
>>>
>>> It would also help on identifying "gaps" on the framework or, if
>> different design decisions have been taken, to justify it by comments (for
>> example, the one to not referencing Aggregates by id due to automatic lazy
>> loading on DataNucleus, that was discussed some days ago).
>>>
>>> An unsatisfactory exchange... I've never had an answer I could
>> understand as to why one would wish to do all that tedious mucking about
>> with Ids if one has the power of an ORM to call upon. And all that extra
>> boilerplate ultimately impedes being able to develop the ubiquitous
>> language.
>>>
>>>
>>>
>>>
>>> Another design recommendation would be the creation of an annotation,
>> method example, etc. for automatically registering a new service. We are
>> now editing the wicket viewer "isis.properties" file, but we waited for an
>> automatic "convention over configuration" way of doing it.
>>>
>>> Yes, I have this on my todo list... to automatically discover services,
>> eg using the META-INF/services mechanism (or perhaps CDI).
>>>
>>> There is, in fact, a not-at-all-documented API to do this. If you
>> create an implementation of ServicesInstaller [5], then you can specify to
>> use it by adding a setting in isis.properties:
>>>
>>> isis.services-installer=com.foo.bar.MyServicesInstaller
>>>
>>>
>>> Haven't tried this for a good while, but it ought to work...
>>>
>>> You could use some code similar to the RegisterEntities domain service
>> [6] that we wrote to bootstrap JDO more reliably.
>>>
>>>
>>> Is there an example with a more complex Domain, testing, etc. anywhere
>> that we can further analyze?
>>>
>>>
>>> Estatio would be the best example. When it's done, we do intend to use
>> it as a substantive case study. "When it's done" being the operative words
>> in that sentence.
>>>
>>> Hope that was helpful,
>>>
>>> Cheers
>>> Dan
>>>
>>> [1]
>> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
>>> [2]
>> https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
>>> [3]
>> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
>>> [4]
>> https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
>>> [5]
>> https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
>>> [6]
>> https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
>>>
>>>
>>> Thanks a lot in advance,
>>>
>>> Oscar
>>>
>>>
>>>
>>>
>>
>>
Re: Hi to all. Project introduction and some doubts
Posted by Jeroen van der Wal <je...@stromboli.it>.
Hi Oscar,
First of all welcome to this mailinglist. From the code you showed there's
quite a good match between your framework and Isis. Together with Dan I'm
developing a business application for managing and invoicing property
leases. In the process of building the application Isis matured a lot and I
think now is the time to have more people joining in developing
critical business applications.
In regard to your viewer solution I that Maurizio Tavernina is working on a
DHTMLX viewer with an integrated DSL to develop custom(ised) user
interfaces. This might be an interesting project for you to watch [1] and
an a possible alternative to WaveMaker.
Today I discussed open sourcing our codebase (which is still under
construction) with the client and he agreed to do that. The only decision
to be made is whether it's under Apache License 2.0 or GPLv3 but I expect
that to be finalised soon. I will update the mailinglist when we have the
code online.
Kind regards,
Jeroen van der Wal
[1] http://isis.markmail.org/thread/scdyj62aujav7cfi
On Fri, May 3, 2013 at 10:06 AM, GESCONSULTOR - Óscar Bou <
o.bou@gesconsultor.com> wrote:
> Hi, Adam and Dan.
>
> Thanks a lot for your responses.
>
> Adam, I'll look in detail on the project to pointed me and Dan, I (and
> many others :-) will wait for the "Estatio" code with really, really
> interest :-))
>
> Dan, regarding JPA I've seen on previous posts that LGPL licensing was the
> reason to choose JDO. These 2-3 days I've seen that it's a really powerful
> API also, and with more flexible solutions than JPA for @MappedSuperclass,
> @Embeddable, for example. Also is clearer for specifying indexes, etc. But
> the matter is that the majority is using JPA, so I think that a JPA
> implementation compatible with Apache, such as OpenJPA will be needed on
> the mid-term.
>
> ISIS framework implementation is quite more powerful than our framework.
> That's the reason for change :-)) What I didn't noticed was the
> Localization-related API. Thanks to point me towards it.
>
> Despite the JUnit viewer is not "finished", we will try to use it with the
> maven archetype generated project. It would be really interesting to have
> such a complete Domain testing framework fully integrated on ISIS and
> available on the Maven Archetype, the first point of contact of all
> evaluators.
>
> Regarding the Wavemaker's viewer, currently is propietary technology. If
> the proof-of-concept goes well (I'm quite confident :-) we will need to
> migrate it from our framework to Isis.
> I'll try to convince Management to donate it to ISIS ;-) I'm not sure if
> we will be able to commit to a full viewer's implementation for our own,
> but at least the Wavemaker "specific" screen generations, etc. will be
> done. Let's see how much effort and "ISIS specific knowledge" is needed for
> a full viewer implementation or if any volunteer is needed. Wavemaker is a
> really good complement to ISIS, as it's a visual RAD-like tool with User
> Interface drag-and-drop design, completely developed on Java and DOJO.
>
> Regarding the "Ids" and Lazy Loading debate, I vote for "Id" referencing
> for Aggregates from different Bounded Contexts (in order to limit the
> dependencies between them, "types" importing, ...) but for references
> between Aggregates on the same Bounded Context when using an ORM with Lazy
> Loading support, we prefer referencing the type (as it's been done on ORM
> since the beginning).
>
> The framework is becoming really powerful. Let's see how easy it's to
> evaluate it :-)
>
> Thanks a lot to all the team for the really good work you are doing,
>
> Oscar
>
>
>
>
>
>
>
>
> El 03/05/2013, a las 00:21, Dan Haywood <da...@haywood-associates.co.uk>
> escribió:
>
> > Hi Oscar,
> >
> > Thanks for your interest in Isis, and for your very interesting email.
> I'm replying to both you and to the mailing list; you might want to
> subscribe to users@isis.a.o and/or dev@isis.a.o.
> >
> > I'll reply in line so that I don't miss anything....
> >
> >
> > On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>
> wrote:
> >
> > We are using JPA with an Hibernate implementation ...
> >
> > As you probably know, the Hibernate license is incompatible with ASF;
> this is one of the reasons why we use JDO/DN.
> >
> >
> >
> >
> > Here are some examples of Domain classes:
> >
> > [snip]
> >
> >
> >
> > As you can imagine through the previous code, our framework vision it's
> quite similar to this one.
> >
> > Yes, pretty similar. I didn't notice any actions though? Where do you
> put your "know-how-to" responsibilities; do you subscribe to Isis'
> "behaviourally complete" objects?
> >
> >
> > An important difference is support for multiple languages on some
> critical annotations.
> > As you can see previously, de @XMSField is like the @Named one from
> ISIS, but supporting localization.
> >
> >
> > In fact, Isis' architecture does support localization. The @Named
> annotation is interpreted by the various FacetFactory's [1] that make up
> Isis' programming model and are part of its metamodel builder. In the case
> of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
> implementation of NamedFacet on the property.
> >
> > In addition, Isis has an API called FacetDecorator. One implementation
> is I18NFacetDecorator [3]. From this, you'll see that we can provide
> localized names, help text and descriptions.
> >
> > (As an aside: this FacetDecorator API actually predates the
> FacetFactorys, and we do intend (at least, I would like) to just have the
> FacetFactory API, and have an implementation of FacetFactory that can do
> the localization. Not a big deal).
> >
> > Just a note on your @XMSField annotation; it seems a bit odd to me to
> have the translations in the text rather than in a resource bundle. But
> presumably it fits your development process well enough, otherwise you
> wouldn't have done it that way. One thing you might want to consider: you
> could if you wanted write your own implementation of NamedFacetFactory that
> understands your @XMSField annotation, if you wanted. In other words,
> teach Isis about your programming model, rather than the other way around.
> (You would still need to translate the JPA stuff into JDO, though).
> >
> >
> >
> > The @Description should also support localization. In our case, we are
> directly generating the help texts from the source files using a custom
> Doclet.
> >
> > You mean @DescribedAs? Also supported by the I18NFacetDecorator.
> >
> >
> > I'm following the project and email list for the last months, because we
> have been spending a lot of resources developing our framework but are
> thinking about evaluating for future Bounded Contexts a mixed approach,
> using Apache Isis for the Domain Model development, testing and REST API,
> and our technology for the User Interface and other infrastructure areas.
> >
> >
> > That's very interesting to hear. Which makes me ask in turn: is your UI
> stuff proprietary? or could it be open sourced in turn as another viewer
> for Isis?
> >
> >
> >
> > Migration from JPA to JDO seems quite fast and easy (but directly
> supporting it would be perfect, despite what I've seen from JDO seems
> really, really good). As our programming model was also quite similar, it
> seems also relatively easy to "migrate" our custom annotations to your
> equivalent ones.
> >
> > Prior to starting the formal evaluation of the migration process, we
> want to make a prototype migrating one Bounded Context. For that, we have
> used the Maven archetype for creating the prototype. Current Archetype is
> really good exposing really fast the Domain through a web and a REST
> interface. But we find Testing (Junit mainly but also BDD), "the
> programmer's interface", is missing and would be perfect to have some test
> examples with the JUnit viewer and the BDD viewer.
> >
> >
> > With respect to the JUnit viewer, at the moment it focuses on testing
> the UI/domain interaction, and just using an in-memory objectstore.
> Separately, there is IsisSystemForTest [4], which can be used to bootstrap
> an Isis runtime for domain/DB integration (via the JDO objectstore)
> >
> > What I want to do is to combine these frameworks into a single JUnit
> framework, which allows domain/DB integration and optionally allows the
> full-stack UI/domain/DB integration too. This is the main reason I
> haven't released the JUnit viewer yet since us becoming a TLP.
> >
> > With respect to the BDD viewer, I think this also needs to work the same
> way; and it probably should be made part of the same single framework. So,
> then it's one integration testing stack for domain/DB testing, optionally
> testing the UI interaction through the existing JUnit viewer stuff or
> through the BDD viewer stuff.
> >
> >
> >
> > It would also be really good to have a more complex model on the
> Archetype, showing the proper annotations and use of Entities,
> ValueObjects, Aggregates, Repositories, Factories, ...
> >
> > As you probably know if you've been following the mailing lists, Jeroen
> and I are both working part-time on a substantial app for his company,
> building an estate management application ("Estatio"). Think of it as the
> calculation engine for rents for tenants in shopping centres and the like,
> and then integrates with a separate general ledger system using the new
> PublishingService that I developed a month or two back.
> >
> > The intention is for this app to be open sourced when done (later this
> year, we expect). Some parts of it (to do with proprietary calculation
> algorithms) will remain closed source, but we think we can provide suitable
> plugin points such that the vast majority of the app is open sourced. The
> app also has a bunch of integration tests written using the
> IntegSystemForTest.
> >
> > By all means contact Jeroen or me off-list regarding this.
> >
> >
> > It would be ideal to have a model equivalent to the SCRUM one exposed on
> the "Implementing Design Driven Development", showing how to implement it
> on Apache Isis.
> >
> > Yes, that is a nice little domain that one could work up. Don't have
> the bandwidth myself, but if you are doing an evaluation of Isis, perhaps
> you might consider building it as a proof-of-concept and put it on github.
> >
> > Also, you might want to ping Christian Steinbach, who was very active a
> month or two back on the mailing lists while writing a demonstrator app
> using Isis. He would provide some useful "third-party" feedback for you, I
> would have thought.
> >
> >
> >
> > It would also help on identifying "gaps" on the framework or, if
> different design decisions have been taken, to justify it by comments (for
> example, the one to not referencing Aggregates by id due to automatic lazy
> loading on DataNucleus, that was discussed some days ago).
> >
> > An unsatisfactory exchange... I've never had an answer I could
> understand as to why one would wish to do all that tedious mucking about
> with Ids if one has the power of an ORM to call upon. And all that extra
> boilerplate ultimately impedes being able to develop the ubiquitous
> language.
> >
> >
> >
> >
> > Another design recommendation would be the creation of an annotation,
> method example, etc. for automatically registering a new service. We are
> now editing the wicket viewer "isis.properties" file, but we waited for an
> automatic "convention over configuration" way of doing it.
> >
> > Yes, I have this on my todo list... to automatically discover services,
> eg using the META-INF/services mechanism (or perhaps CDI).
> >
> > There is, in fact, a not-at-all-documented API to do this. If you
> create an implementation of ServicesInstaller [5], then you can specify to
> use it by adding a setting in isis.properties:
> >
> > isis.services-installer=com.foo.bar.MyServicesInstaller
> >
> >
> > Haven't tried this for a good while, but it ought to work...
> >
> > You could use some code similar to the RegisterEntities domain service
> [6] that we wrote to bootstrap JDO more reliably.
> >
> >
> > Is there an example with a more complex Domain, testing, etc. anywhere
> that we can further analyze?
> >
> >
> > Estatio would be the best example. When it's done, we do intend to use
> it as a substantive case study. "When it's done" being the operative words
> in that sentence.
> >
> > Hope that was helpful,
> >
> > Cheers
> > Dan
> >
> > [1]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
> > [2]
> https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
> > [3]
> https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
> > [4]
> https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
> > [5]
> https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
> > [6]
> https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
> >
> >
> > Thanks a lot in advance,
> >
> > Oscar
> >
> >
> >
> >
>
>
Re: Hi to all. Project introduction and some doubts
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
Hi, Adam and Dan.
Thanks a lot for your responses.
Adam, I'll look in detail on the project to pointed me and Dan, I (and many others :-) will wait for the "Estatio" code with really, really interest :-))
Dan, regarding JPA I've seen on previous posts that LGPL licensing was the reason to choose JDO. These 2-3 days I've seen that it's a really powerful API also, and with more flexible solutions than JPA for @MappedSuperclass, @Embeddable, for example. Also is clearer for specifying indexes, etc. But the matter is that the majority is using JPA, so I think that a JPA implementation compatible with Apache, such as OpenJPA will be needed on the mid-term.
ISIS framework implementation is quite more powerful than our framework. That's the reason for change :-)) What I didn't noticed was the Localization-related API. Thanks to point me towards it.
Despite the JUnit viewer is not "finished", we will try to use it with the maven archetype generated project. It would be really interesting to have such a complete Domain testing framework fully integrated on ISIS and available on the Maven Archetype, the first point of contact of all evaluators.
Regarding the Wavemaker's viewer, currently is propietary technology. If the proof-of-concept goes well (I'm quite confident :-) we will need to migrate it from our framework to Isis.
I'll try to convince Management to donate it to ISIS ;-) I'm not sure if we will be able to commit to a full viewer's implementation for our own, but at least the Wavemaker "specific" screen generations, etc. will be done. Let's see how much effort and "ISIS specific knowledge" is needed for a full viewer implementation or if any volunteer is needed. Wavemaker is a really good complement to ISIS, as it's a visual RAD-like tool with User Interface drag-and-drop design, completely developed on Java and DOJO.
Regarding the "Ids" and Lazy Loading debate, I vote for "Id" referencing for Aggregates from different Bounded Contexts (in order to limit the dependencies between them, "types" importing, ...) but for references between Aggregates on the same Bounded Context when using an ORM with Lazy Loading support, we prefer referencing the type (as it's been done on ORM since the beginning).
The framework is becoming really powerful. Let's see how easy it's to evaluate it :-)
Thanks a lot to all the team for the really good work you are doing,
Oscar
El 03/05/2013, a las 00:21, Dan Haywood <da...@haywood-associates.co.uk> escribió:
> Hi Oscar,
>
> Thanks for your interest in Isis, and for your very interesting email. I'm replying to both you and to the mailing list; you might want to subscribe to users@isis.a.o and/or dev@isis.a.o.
>
> I'll reply in line so that I don't miss anything....
>
>
> On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com> wrote:
>
> We are using JPA with an Hibernate implementation ...
>
> As you probably know, the Hibernate license is incompatible with ASF; this is one of the reasons why we use JDO/DN.
>
>
>
>
> Here are some examples of Domain classes:
>
> [snip]
>
>
>
> As you can imagine through the previous code, our framework vision it's quite similar to this one.
>
> Yes, pretty similar. I didn't notice any actions though? Where do you put your "know-how-to" responsibilities; do you subscribe to Isis' "behaviourally complete" objects?
>
>
> An important difference is support for multiple languages on some critical annotations.
> As you can see previously, de @XMSField is like the @Named one from ISIS, but supporting localization.
>
>
> In fact, Isis' architecture does support localization. The @Named annotation is interpreted by the various FacetFactory's [1] that make up Isis' programming model and are part of its metamodel builder. In the case of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an implementation of NamedFacet on the property.
>
> In addition, Isis has an API called FacetDecorator. One implementation is I18NFacetDecorator [3]. From this, you'll see that we can provide localized names, help text and descriptions.
>
> (As an aside: this FacetDecorator API actually predates the FacetFactorys, and we do intend (at least, I would like) to just have the FacetFactory API, and have an implementation of FacetFactory that can do the localization. Not a big deal).
>
> Just a note on your @XMSField annotation; it seems a bit odd to me to have the translations in the text rather than in a resource bundle. But presumably it fits your development process well enough, otherwise you wouldn't have done it that way. One thing you might want to consider: you could if you wanted write your own implementation of NamedFacetFactory that understands your @XMSField annotation, if you wanted. In other words, teach Isis about your programming model, rather than the other way around. (You would still need to translate the JPA stuff into JDO, though).
>
>
>
> The @Description should also support localization. In our case, we are directly generating the help texts from the source files using a custom Doclet.
>
> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
>
>
> I'm following the project and email list for the last months, because we have been spending a lot of resources developing our framework but are thinking about evaluating for future Bounded Contexts a mixed approach, using Apache Isis for the Domain Model development, testing and REST API, and our technology for the User Interface and other infrastructure areas.
>
>
> That's very interesting to hear. Which makes me ask in turn: is your UI stuff proprietary? or could it be open sourced in turn as another viewer for Isis?
>
>
>
> Migration from JPA to JDO seems quite fast and easy (but directly supporting it would be perfect, despite what I've seen from JDO seems really, really good). As our programming model was also quite similar, it seems also relatively easy to "migrate" our custom annotations to your equivalent ones.
>
> Prior to starting the formal evaluation of the migration process, we want to make a prototype migrating one Bounded Context. For that, we have used the Maven archetype for creating the prototype. Current Archetype is really good exposing really fast the Domain through a web and a REST interface. But we find Testing (Junit mainly but also BDD), "the programmer's interface", is missing and would be perfect to have some test examples with the JUnit viewer and the BDD viewer.
>
>
> With respect to the JUnit viewer, at the moment it focuses on testing the UI/domain interaction, and just using an in-memory objectstore. Separately, there is IsisSystemForTest [4], which can be used to bootstrap an Isis runtime for domain/DB integration (via the JDO objectstore)
>
> What I want to do is to combine these frameworks into a single JUnit framework, which allows domain/DB integration and optionally allows the full-stack UI/domain/DB integration too. This is the main reason I haven't released the JUnit viewer yet since us becoming a TLP.
>
> With respect to the BDD viewer, I think this also needs to work the same way; and it probably should be made part of the same single framework. So, then it's one integration testing stack for domain/DB testing, optionally testing the UI interaction through the existing JUnit viewer stuff or through the BDD viewer stuff.
>
>
>
> It would also be really good to have a more complex model on the Archetype, showing the proper annotations and use of Entities, ValueObjects, Aggregates, Repositories, Factories, ...
>
> As you probably know if you've been following the mailing lists, Jeroen and I are both working part-time on a substantial app for his company, building an estate management application ("Estatio"). Think of it as the calculation engine for rents for tenants in shopping centres and the like, and then integrates with a separate general ledger system using the new PublishingService that I developed a month or two back.
>
> The intention is for this app to be open sourced when done (later this year, we expect). Some parts of it (to do with proprietary calculation algorithms) will remain closed source, but we think we can provide suitable plugin points such that the vast majority of the app is open sourced. The app also has a bunch of integration tests written using the IntegSystemForTest.
>
> By all means contact Jeroen or me off-list regarding this.
>
>
> It would be ideal to have a model equivalent to the SCRUM one exposed on the "Implementing Design Driven Development", showing how to implement it on Apache Isis.
>
> Yes, that is a nice little domain that one could work up. Don't have the bandwidth myself, but if you are doing an evaluation of Isis, perhaps you might consider building it as a proof-of-concept and put it on github.
>
> Also, you might want to ping Christian Steinbach, who was very active a month or two back on the mailing lists while writing a demonstrator app using Isis. He would provide some useful "third-party" feedback for you, I would have thought.
>
>
>
> It would also help on identifying "gaps" on the framework or, if different design decisions have been taken, to justify it by comments (for example, the one to not referencing Aggregates by id due to automatic lazy loading on DataNucleus, that was discussed some days ago).
>
> An unsatisfactory exchange... I've never had an answer I could understand as to why one would wish to do all that tedious mucking about with Ids if one has the power of an ORM to call upon. And all that extra boilerplate ultimately impedes being able to develop the ubiquitous language.
>
>
>
>
> Another design recommendation would be the creation of an annotation, method example, etc. for automatically registering a new service. We are now editing the wicket viewer "isis.properties" file, but we waited for an automatic "convention over configuration" way of doing it.
>
> Yes, I have this on my todo list... to automatically discover services, eg using the META-INF/services mechanism (or perhaps CDI).
>
> There is, in fact, a not-at-all-documented API to do this. If you create an implementation of ServicesInstaller [5], then you can specify to use it by adding a setting in isis.properties:
>
> isis.services-installer=com.foo.bar.MyServicesInstaller
>
>
> Haven't tried this for a good while, but it ought to work...
>
> You could use some code similar to the RegisterEntities domain service [6] that we wrote to bootstrap JDO more reliably.
>
>
> Is there an example with a more complex Domain, testing, etc. anywhere that we can further analyze?
>
>
> Estatio would be the best example. When it's done, we do intend to use it as a substantive case study. "When it's done" being the operative words in that sentence.
>
> Hope that was helpful,
>
> Cheers
> Dan
>
> [1] https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
> [2] https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
> [3] https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
> [4] https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
> [5] https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
> [6] https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
>
>
> Thanks a lot in advance,
>
> Oscar
>
>
>
>
Re: Hi to all. Project introduction and some doubts
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi Oscar,
Thanks for your interest in Isis, and for your very interesting email. I'm
replying to both you and to the mailing list; you might want to subscribe
to users@isis.a.o and/or dev@isis.a.o.
I'll reply in line so that I don't miss anything....
On 2 May 2013 17:36, GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>wrote:
>
> We are using JPA with an Hibernate implementation ...
As you probably know, the Hibernate license is incompatible with ASF; this
is one of the reasons why we use JDO/DN.
>
> Here are some examples of Domain classes:
>
> [snip]
> As you can imagine through the previous code, our framework vision it's
> quite similar to this one.
Yes, pretty similar. I didn't notice any actions though? Where do you put
your "know-how-to" responsibilities; do you subscribe to Isis'
"behaviourally complete" objects?
> An important difference is support for multiple languages on some critical
> annotations.
> As you can see previously, de @XMSField is like the @Named one from ISIS,
> but supporting localization.
>
In fact, Isis' architecture does support localization. The @Named
annotation is interpreted by the various FacetFactory's [1] that make up
Isis' programming model and are part of its metamodel builder. In the case
of @Named, it is NamedAnnotationOnMemberFacetFactory [2], which installs an
implementation of NamedFacet on the property.
In addition, Isis has an API called FacetDecorator. One implementation is
I18NFacetDecorator [3]. From this, you'll see that we can provide
localized names, help text and descriptions.
(As an aside: this FacetDecorator API actually predates the FacetFactorys,
and we do intend (at least, I would like) to just have the FacetFactory
API, and have an implementation of FacetFactory that can do the
localization. Not a big deal).
Just a note on your @XMSField annotation; it seems a bit odd to me to have
the translations in the text rather than in a resource bundle. But
presumably it fits your development process well enough, otherwise you
wouldn't have done it that way. One thing you might want to consider: you
could if you wanted write your own implementation of NamedFacetFactory that
understands your @XMSField annotation, if you wanted. In other words,
teach Isis about your programming model, rather than the other way around.
(You would still need to translate the JPA stuff into JDO, though).
> The @Description should also support localization. In our case, we are
> directly generating the help texts from the source files using a custom
> Doclet.
>
> You mean @DescribedAs? Also supported by the I18NFacetDecorator.
> I'm following the project and email list for the last months, because we
> have been spending a lot of resources developing our framework but are
> thinking about evaluating for future Bounded Contexts a mixed approach,
> using Apache Isis for the Domain Model development, testing and REST API,
> and our technology for the User Interface and other infrastructure areas.
>
>
That's very interesting to hear. Which makes me ask in turn: is your UI
stuff proprietary? or could it be open sourced in turn as another viewer
for Isis?
> Migration from JPA to JDO seems quite fast and easy (but directly
> supporting it would be perfect, despite what I've seen from JDO seems
> really, really good). As our programming model was also quite similar, it
> seems also relatively easy to "migrate" our custom annotations to your
> equivalent ones.
>
> Prior to starting the formal evaluation of the migration process, we want
> to make a prototype migrating one Bounded Context. For that, we have used
> the Maven archetype for creating the prototype. Current Archetype is really
> good exposing really fast the Domain through a web and a REST interface.
> But we find Testing (Junit mainly but also BDD), "the programmer's
> interface", is missing and would be perfect to have some test examples with
> the JUnit viewer and the BDD viewer.
>
>
With respect to the JUnit viewer, at the moment it focuses on testing the
UI/domain interaction, and just using an in-memory objectstore.
Separately, there is IsisSystemForTest [4], which can be used to bootstrap
an Isis runtime for domain/DB integration (via the JDO objectstore)
What I want to do is to combine these frameworks into a single JUnit
framework, which allows domain/DB integration and optionally allows the
full-stack UI/domain/DB integration too. This is the main reason I
haven't released the JUnit viewer yet since us becoming a TLP.
With respect to the BDD viewer, I think this also needs to work the same
way; and it probably should be made part of the same single framework. So,
then it's one integration testing stack for domain/DB testing, optionally
testing the UI interaction through the existing JUnit viewer stuff or
through the BDD viewer stuff.
> It would also be really good to have a more complex model on the
> Archetype, showing the proper annotations and use of Entities,
> ValueObjects, Aggregates, Repositories, Factories, ...
As you probably know if you've been following the mailing lists, Jeroen and
I are both working part-time on a substantial app for his company, building
an estate management application ("Estatio"). Think of it as the
calculation engine for rents for tenants in shopping centres and the like,
and then integrates with a separate general ledger system using the new
PublishingService that I developed a month or two back.
The intention is for this app to be open sourced when done (later this
year, we expect). Some parts of it (to do with proprietary calculation
algorithms) will remain closed source, but we think we can provide suitable
plugin points such that the vast majority of the app is open sourced. The
app also has a bunch of integration tests written using the
IntegSystemForTest.
By all means contact Jeroen or me off-list regarding this.
> It would be ideal to have a model equivalent to the SCRUM one exposed on
> the "Implementing Design Driven Development", showing how to implement it
> on Apache Isis.
Yes, that is a nice little domain that one could work up. Don't have the
bandwidth myself, but if you are doing an evaluation of Isis, perhaps you
might consider building it as a proof-of-concept and put it on github.
Also, you might want to ping Christian Steinbach, who was very active a
month or two back on the mailing lists while writing a demonstrator app
using Isis. He would provide some useful "third-party" feedback for you, I
would have thought.
> It would also help on identifying "gaps" on the framework or, if different
> design decisions have been taken, to justify it by comments (for example,
> the one to not referencing Aggregates by id due to automatic lazy loading
> on DataNucleus, that was discussed some days ago).
>
An unsatisfactory exchange... I've never had an answer I could understand
as to why one would wish to do all that tedious mucking about with Ids if
one has the power of an ORM to call upon. And all that extra boilerplate
ultimately impedes being able to develop the ubiquitous language.
>
> Another design recommendation would be the creation of an annotation,
> method example, etc. for automatically registering a new service. We are
> now editing the wicket viewer "isis.properties" file, but we waited for an
> automatic "convention over configuration" way of doing it.
>
Yes, I have this on my todo list... to automatically discover services, eg
using the META-INF/services mechanism (or perhaps CDI).
There is, in fact, a not-at-all-documented API to do this. If you create
an implementation of ServicesInstaller [5], then you can specify to use it
by adding a setting in isis.properties:
isis.services-installer=com.foo.bar.MyServicesInstaller
Haven't tried this for a good while, but it ought to work...
You could use some code similar to the RegisterEntities domain service [6]
that we wrote to bootstrap JDO more reliably.
>
> Is there an example with a more complex Domain, testing, etc. anywhere
> that we can further analyze?
>
>
Estatio would be the best example. When it's done, we do intend to use it
as a substantive case study. "When it's done" being the operative words in
that sentence.
Hope that was helpful,
Cheers
Dan
[1]
https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/progmodels/dflt/ProgrammingModelFacetsJava5.java
[2]
https://github.com/apache/isis/tree/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facets/members/named/annotation
[3]
https://github.com/apache/isis/blob/master/core/metamodel/src/main/java/org/apache/isis/core/progmodel/facetdecorators/i18n/I18nFacetDecorator.java
[4]
https://github.com/apache/isis/tree/master/core/integtestsupport/src/main/java/org/apache/isis/core/integtestsupport
[5]
https://github.com/apache/isis/tree/master/core/runtime/src/main/java/org/apache/isis/core/runtime/services
[6]
https://github.com/apache/isis/tree/master/component/objectstore/jdo/jdo-datanucleus/src/main/java/org/apache/isis/objectstore/jdo/service
> Thanks a lot in advance,
>
> Oscar
>
>
>
>
Re: Hi to all. Project introduction and some doubts
Posted by Adam Howard <ho...@gmail.com>.
Hi Oscar,
I don't know of any open source projects using Isis that you could look at
but I did start (and never finished) a port of the dddsample[1] app to
Isis. The code is on GitHub[2] but I don't know how much help it will be
since it's so incomplete. I hope to make more progress this summer. I did
raise one ticket related to something you mentioned your framework handles
related to "field groups"[3]. Hopefully I'll finish that too. You can see
what I intend it to look like by selecting one of the Cargos from the list
here[4].
Hope it helps.
--
Adam
[1] http://dddsample.sourceforge.net/
[2] https://github.com/adamhoward/onaboat
[3] https://issues.apache.org/jira/browse/ISIS-348
[4]
http://immense-brook-7613.herokuapp.com/wicket/wicket/bookmarkable/org.apache.isis.viewer.wicket.ui.pages.action.ActionPage?pageType=ACTION&actionSingleResultsMode=REDIRECT&objectOid=onaboat.domain.model.cargo.CargoRepository:1&actionType=USER&actionOwningSpec=onaboat.domain.model.cargo.CargoRepository&actionId=findAll%28%29&pageTitle=Find+All&actionMode=RESULTS
On Thu, May 2, 2013 at 11:36 AM, GESCONSULTOR - Óscar Bou <
o.bou@gesconsultor.com> wrote:
>
> Hi to all!
>
> My name is Oscar and I'm the Team Leader of a software solution that is
> implemented with a vision really similar to Isis and we are also using some
> DDD patterns.
>
> We are using JPA with an Hibernate implementation and custom annotations
> for defining field groups, localized names on the fields, field help texts
> extracted from the source Java help, etc.
>
> All entity forms are generated automatically by a custom generator over
> Wavemaker technology stack (Spring + Hibernate + Java + JavaScript + DOJO).
>
> Here are some examples of Domain classes:
>
> A PARTY CLASS
>
> @XMSEntityNames({
> @XMSEntityName(locale = "es", name = "Organización /
> Persona"),
> @XMSEntityName(locale = "en", name = "Party") })
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @DiscriminatorColumn(discriminatorType = DiscriminatorType.STRING, name =
> "DTYPE", length = 64)
> public abstract class Party extends AbstractMultiTenantEntity {
>
> @XMSField(locales = { @XMSLocale(locale = "es", caption = "Es
> Externa"),
> @XMSLocale(locale = "en", caption = "Is External")
> })
> private Boolean isExternal;
>
> private String userName;
>
> @OneToMany(mappedBy = "party", cascade = CascadeType.REMOVE)
> @XMSField(locales = { @XMSLocale(locale = "es", caption =
> "Direcciones"),
> @XMSLocale(locale = "en", caption = "Addresses") })
> private Set<AddressParty> addresses;
>
> @OneToMany(mappedBy = "party", cascade = CascadeType.REMOVE)
> @XMSField(locales = {
> @XMSLocale(locale = "es", caption =
> "Responsabilidades"),
> @XMSLocale(locale = "en", caption =
> "Responsibilities") })
> private Set<ResponsibilityParty> responsibilities;
>
>
> [... getters, setters and custom methods ...]
>
> A CLASS WITH SECTIONS (FIELD GROUPS ON THE USER INTERFACE)
>
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @XMSSections(value = {
> @XMSSection(code = "RISK", locales = {
> @XMSLocale(locale = "es", caption =
> "Riesgo", description = "Información relacionada con la Gestión del
> Riesgo"),
> @XMSLocale(locale = "en", caption =
> "Risk", description = "Information related to the Management of Risks") }),
> @XMSSection(code = "CONTINUITY", locales = {
> @XMSLocale(locale = "es", caption =
> "Continuidad de Negocio", description = "Información relacionada con la
> Continuidad de Negocio"),
> @XMSLocale(locale = "en", caption =
> "Business Continuity", description = "Information related to the Continuity
> of the Business Activities and their impact on Customer's Products and
> Services") }) })
> public abstract class AssetAssessment extends AbstractMultiTenantEntity {
>
> @SuppressWarnings("unused")
> @Transient
> @XMSField(show = false, locales = { @XMSLocale(locale = "es",
> caption = "Activo") }, section = "RISK")
> private XMSAsset asset;
>
> /***** CHARACTERIZATION *****/
>
> @XMSField(locales = { @XMSLocale(locale = "es", caption =
> "Valoración del Activo") }, section = "RISK")
> @Embedded
> private AssetAssessmentValuation assetValuation;
>
> @XMSField(locales = { @XMSLocale(locale = "es", caption =
> "Localización") })
> @ManyToOne
> private LocationAssessment location;
>
>
>
>
> As you can imagine through the previous code, our framework vision it's
> quite similar to this one. An important difference is support for multiple
> languages on some critical annotations.
> As you can see previously, de @XMSField is like the @Named one from ISIS,
> but supporting localization.
> The @Description should also support localization. In our case, we are
> directly generating the help texts from the source files using a custom
> Doclet.
>
> I'm following the project and email list for the last months, because we
> have been spending a lot of resources developing our framework but are
> thinking about evaluating for future Bounded Contexts a mixed approach,
> using Apache Isis for the Domain Model development, testing and REST API,
> and our technology for the User Interface and other infrastructure areas.
>
> Migration from JPA to JDO seems quite fast and easy (but directly
> supporting it would be perfect, despite what I've seen from JDO seems
> really, really good). As our programming model was also quite similar, it
> seems also relatively easy to "migrate" our custom annotations to your
> equivalent ones.
>
> Prior to starting the formal evaluation of the migration process, we want
> to make a prototype migrating one Bounded Context. For that, we have used
> the Maven archetype for creating the prototype. Current Archetype is really
> good exposing really fast the Domain through a web and a REST interface.
> But we find Testing (Junit mainly but also BDD), "the programmer's
> interface", is missing and would be perfect to have some test examples with
> the JUnit viewer and the BDD viewer.
>
> It would also be really good to have a more complex model on the
> Archetype, showing the proper annotations and use of Entities,
> ValueObjects, Aggregates, Repositories, Factories, ... It would be ideal to
> have a model equivalent to the SCRUM one exposed on the "Implementing
> Design Driven Development", showing how to implement it on Apache Isis. It
> would also help on identifying "gaps" on the framework or, if different
> design decisions have been taken, to justify it by comments (for example,
> the one to not referencing Aggregates by id due to automatic lazy loading
> on DataNucleus, that was discussed some days ago).
>
> Another design recommendation would be the creation of an annotation,
> method example, etc. for automatically registering a new service. We are
> now editing the wicket viewer "isis.properties" file, but we waited for an
> automatic "convention over configuration" way of doing it.
>
> Is there an example with a more complex Domain, testing, etc. anywhere
> that we can further analyze?
>
> Thanks a lot in advance,
>
> Oscar
>
>
>
>