isis-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Nišević <>
Subject Re: New and better view models coming in 1.11.0-SNAPSHOT
Date Sat, 21 Nov 2015 20:25:18 GMT
Hi Dan, thank you, this is a really cool feature! The applications I'm
building, have often legacy systems and some parts of my domain models are
built on service calls to that legacy systems - in that case we build
domain models with view models to hold the data from multiple backends and
implement the core domain logic in them. Until now we have primarily used
this domain models to expose REST services to other systems, but I believe
this could be the way to implement some wicket based UI's.

Additionaly, here some ideas I'd like to share, maybe to see some of them
in the future in the Apache Isis framework:

1. Search capability based on e.g. Elasticsearch [1], where the
Elasticsearch could act as a kind of "external index" for the parts of
domain model. Developer could mark which fields should be searchable, this
fields would be updated in elasticsearch instance after database
insert/update/delete. User can search thru Elasticsearch and retreive the
entity OID's as results and in the second step use them to retreive the
entities from main repository (thru datanucleus container). I could
contribute to this feature since we have integrated Elasticsearch with
Apache Isis.

2. An add-on to support system-wide and/or user-specific notifications
(similar to Atlassian Confluence [2}). An Isis user could receive such
"notifications" - they would appear on his desktop, he could mark them
 "readed". Some notifications could be system-wide and controlled by e.g.
system without a possibility to remove them until e.g. administrator
decides that. We use such features  to e.g. notify application users there
is a newer version of the application and they should finish their work and
log off /logon in order to switch to that new version.

3. In a world of collaboration systems there could be an interest extension
to your incode-module-note feature, the capability not only to add the
notes to an entity, but also to add infinite comments to that note (in
other words to add the comment threads to the entity). In combination with
text search capability (idea #1) I thinks we could build really great




2015-11-20 11:30 GMT+01:00 Dan Haywood <>:

> Hi folks,
> just a heads-up that in the next version we have support for JAXB-annotated
> view models, meaning that a view model's memento is basically derived from
> the XML serialization of its state.  We also have (bar one tiny JAXB
> annotation) more or less transparent references to underlying domain
> objects, and we also can support collections of objects in the graph.
> Other new stuff: there's a JaxbService, and a UrlEncodingService.  There's
> also a Dto role interface so that XML and XSDs can be downloaded from view
> models using some new mixins.  There's also - in the user guide - a new
> section describing all the different types of view models.
> Also in 1.11.0 we will also have three new "UI" events; rather than write
> title() or iconName() in your domain object, you can instead provide this
> metadata via a subscriber.  And I added some "postForDefault" config
> properties so that UI or domain events can be suppressed rather than always
> posted as is currently.
> Finally, I also got around to documenting the common and aim schemas.
> These were introduced in 1.9.0, but never had any formal documentation
> before now.
> Useful links below
> Cheers
> Dan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message