...

I hope this makes sense.... 

-- Patrick

Kevin's Notes

from Kevin

(Written at the conference and first posted to the private mailing list [only because the notes were incomplete])

Dear all,

Some interesting topics are being identified at the Apache Isis "IsisCon 2017". In order to try ensure that no-one is left out, I will be listing the topics and ideas, to give you the opportunity to hear what is being talked about and offer your own input.

• How much "bleed through" annotations are acceptable?

The Apache Isis POJOs currently have many annotations that provide ?

• Cleaning up the Framework code

On the horizon is support for JPA with the associated dependence (via DataNucleus) on Java 8. This is an opportunity to remove obsolete/deprecated methods/annotations/etc and consolidate (bump the major version number, if we still intend to honour semantic versioning).

• What is Apache Isis's responsibility on a naked class?

The framework assumes defaults (according to a defined convention). With no additional annotations, how should the framework treat POJOs? It could, for example, assuming that all public classes are entities, and all public methods are actions. Any other desire would be communicated with additional annotations (is a service, mixin or non-entity).

• Prototype to Production

The "bare" vs "meta annotation" vs "full fat" (production) route. When starting a new application, the developer can start with naked, non-annotated classes. They can use this quickly put together the initial application. Eventually they will want to go to full production. Apache Isis (v2) would have value-adds (like add-ons) that switch on more and more checks that perform sanity checks that require additional meta-data (annotations or XML, etc).

• Wrap (v2)

All objects will be wrapped. There will still be an "unwrap" WrapperFactory method for when it is programmatically justifiable.(Kevin has posted some notes to private@ , I've asked him if he would be happy to move them here)

Jorg's "Framework Qualities"

...