Hi, JEE is probably outlived as are heavy weight application servers.
I don't know Spring Boot too well and have perceived it more like a competitive solution, alongside with *rails. And I hope it doesn't enforce to scan the classpath for components. If it doesn't impair Apache Isis' clean approach it may give some boost. -j -----Ursprüngliche Nachricht----- Von: Óscar Bou [mailto:[email protected]] Gesendet: Mittwoch, 6. Juli 2016 10:34 An: [email protected] Betreff: Re: Is JEE a good bet ?! Hi, Martin and Dan. I also think it’s a really good choice. Currently, Spring only has a scaffolding-based solution for the UI (Spring Roo) so a Naked Objects implementation (among many other things) like Apache Isis could be seen as a really good choice for the Spring community on many use cases. HTH, Oscar > El 6 jul 2016, a las 8:07, Dan Haywood <[email protected]> > escribió: > > Thanks for those thoughts, Martin. > > It's a very good question... and yes, I have seen the rumblings about > Oracle's non involvement with JEE. They've promised to say something > at JavaOne, I believe, so I suppose we'll see. > > I think you are right that if we aligned ourselves with some more of > the new-and-shiny, then we'd build up more mindshare and community. > To my mind Spring does seem to be re-energized with the success of > Spring Boot, so it does deserve serious consideration. > > I suspect that JDO is probably one of the larger "turn-offs". It is > intention to also enable JPA as an alternative API; DataNucleus > supports both, of course. > > Regarding Spring Data, my perception is that it was initially > originally a fancy way of using javassist to automatically infer > repository implementations from the names of methods in repository > interfaces. I guess the automatically generated impl has to take to > some sort of provided, so the "-jpa" bit I'm guessing is what it > delegates to. Am I write about that? Do we know if the JPA > implementation is pluggable? If it is, then I guess we ought to be able to > slot DN in underneath? > > Thx > Dan > > > > > > > > On 6 July 2016 at 06:47, Martin Grigorov <[email protected]> wrote: > >> Hi Dan, >> >> I guess you have heard of the complains from the communities that >> Oracle has abandoned Java EE. There is no any work on JEE 8 specs in >> the last year. >> >> I know that you want to move to CDI based configuration since a while. >> My personal feeling is that Spring (Boot [1]) is much better bet. >> There is a lot of new development in Spring and there are a lot of >> developers with Spring experience out there already. >> Recently someone asked how to use difference profiles for development >> and production - this is very simple with plain Spring and a >> no-brainer with Spring Boot. >> Another example is the integration with Flyway or LiquiBase in Spring >> Boot >> - just add Flyway in the classpath and your migrations are >> automatically found and executed without any additional work. >> I don't know how good is the integration with JDO/DN though. But >> maybe this is another topic for discussion: Did JDO prove itself ? >> IMO it didn't succeed very well to gain community and market share. >> Spring Data [2] does not provide as transparent APIs as JDO or >> Hibernate OGM but its conventions and consistency make it very easy >> to adopt a new data store. E.g. in my team we use mainly Spring Data >> JPA and Spring Data Elasticsearch, and now maybe we will need to use >> Redis and the iniitial learning curve and cost to setup is almost 0. >> I know that DeltaSpike also provides such module [3] but they don't have the >> man-power and community as Spring Data. >> >> Just my 2c against few of the technologies used by Isis :-) >> >> 1. http://projects.spring.io/spring-boot/ >> 2. http://projects.spring.io/spring-data/ >> 3. https://deltaspike.apache.org/documentation/data.html >> >> Martin >> >> On Wed, Jul 6, 2016 at 7:01 AM, Dan Haywood >> <[email protected]> >> wrote: >> >>> Hi folks, >>> >>> below is the draft of the quarterly report we provide to the ASF board. >>> Yell if there's anything you'd llke changing, otherwise I'll submit >>> in a couple of days. >>> >>> Thanks >>> Dan >>> >>> >>> >>> >>> ## Description: >>> >>> Apache Isis is a framework for rapidly developing domain-driven apps >>> in Java. >>> >>> ## Issues: >>> >>> There are no issues requiring board attention at this time. >>> >>> ## Activity: >>> >>> Since the last report we have made two small bug fix releases, >>> v1.12.1 >> [1] >>> and v1.12.2 [2]. (The next release is imminent but hasn't quite >>> made it for this status report). >>> >>> (As reported last quarter), a couple of conference have now taken place. >>> The outputs of one of these - an all-day workshop - is available has >>> been provided on github [3]. >>> >>> A comment was also made against last quarter's report regarding the >>> slow speed of loading up the screencasts page [4]; this has now been >>> reworked and now loads much faster. >>> >>> ## Health report: >>> >>> Project activity (#mails, tickets, commits etc) are all healthy. >>> >>> The main development activity (for 1.13.0) has been removing >>> technical >> debt >>> and simplifying the code base, with a long-term view of leveraging >>> more >> of >>> the JEE platform (eg CDI) and moving to Java 8 as the minimum >>> requirement around the time that Java 9 is released (mid next year). >>> The rationale >> is >>> that the simpler the codebase, the more likely it will encourage >>> contributions. >>> >>> ## PMC changes: >>> >>> - Currently 11 PMC members. >>> - No new PMC members added in the last 3 months >>> - Last PMC addition was Martin Grigorov on Tue Dec 23 2014 >>> >>> ## Committer base changes: >>> >>> - Currently 11 committers. >>> - No new committers added in the last 3 months >>> - Last committer addition was Martin Tzvetanov Grigorov at Thu Dec >>> 11 >> 2014 >>> >>> ## Releases: >>> >>> - 1.12.1 was released on Tue Apr 12 2016 >>> - 1.12.2 was released on Mon Jun 06 2016 >>> >>> ## Mailing list activity: >>> >>> Compared to lsat quarter when new subscriptions was flat, the >>> number of mailing list subscribers has now resumed its upward >>> trend. The new screencasts page [4] and a twitter campaign related >>> to that may be part of the explanation. >>> >>> - [email protected]: >>> - 171 subscribers (up 16 in the last 3 months): >>> - 423 emails sent to list (266 in previous quarter) >>> >>> - [email protected]: >>> - 77 subscribers (up 3 in the last 3 months): >>> - 832 emails sent to list (759 in previous quarter) >>> >>> >>> ## JIRA activity: >>> >>> - 101 JIRA tickets created in the last 3 months >>> - 109 JIRA tickets closed/resolved in the last 3 months >>> >>> >>> [1] http://isis.apache.org/release-notes.html#r1.12.1 >>> [2] http://isis.apache.org/release-notes.html#r1.12.2 >>> [3] https://github.com/danhaywood/spa2016-workshop-outputs >>> [4] http://isis.apache.org/screencasts.html >>> >> Kühne + Nagel (AG & Co.) KG Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE 812773878. Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Yngve Ruud (Vors.), Martin Brinkmann, Matthias Heimbach, Jan-Hendrik Köstergarten, Nicholas Minde, Michael Nebel, Lars Wedel. Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform: Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745, Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt. Geschäftsleitung Region Westeuropa: Yngve Ruud (Vors.), Diederick de Vroet, Dominic Edmonds, Uwe Hött, Richard Huhn, Björn Johansson, Holger Ketz, Jan Kunze. Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen Spediteurbedingungen 2016 (ADSp 2016). Die ADSp 2016 beschränken in Ziffer 23 die gesetzliche Haftung für Güterschäden in Höhe von 8,33 SZR/kg je Schadenfall bzw. je Schadenereignis auf 1 Million bzw. 2 Millionen Euro oder 2 SZR/kg, je nachdem, welcher Betrag höher ist, und bei multimodalen Transporten unter Einschluss einer Seebeförderung generell auf 2 SZR/kg. Den vollständigen Text der ADSp 2016 übersenden wir Ihnen gerne auf Anfrage und können Sie auch unter http://www.kuehne-nagel.com einsehen.
