Thanks Oscar,
I believe I can see some benefits in implementing a custom solution of
DI for Apache Isis. And since it works I'm fine with it.
Still I'm curious about what you guys think about the relevance of Java
EE as a target platform. Is our community likely to grow if we support
the EE platform via docs and example artifacts? Or is it not worth the
effort ...
Cheers, Andi
On 11.10.2017 12:44, Óscar Bou wrote:
Hi Andy,
Completely agree that we should support standards to ease adoption.
Regarding Dependency Injection, Dan introduced Guice time ago and if I remember
it well, he argued about the motivation to implement a custom solution (but
can’t remember now why).
Also I think he also mentioned that current injection behaviour could be
refactored to support CDI, but he could better explain.
Sorry to not give more detail on this.
Cheers,
Oscar
El 11 oct 2017, a las 11:25, Andi Huber <[email protected]> escribió:
On 10.10.2017 14:11, Andi Huber wrote:
Hi all!
These are very exciting times for the Java enthusiast. As James Governor points
out in his JavaOne 2017 keynotes talk:
'Things have changed in the Java ecosystem probably more in the past 3 weeks,
than they have in the previous 13 years.' [1]
And since Java EE is going open source [2], Java EE is probably on the upswing
again.
Also on JavaOne this year, there was this great talk by Adam Bien 'Java EE
Heavyweigth or Lightweigth -- Mythbusters', where he demonstrated in a very
entertaining way, the lack of reason for going 'lightweight'.
Personally I'm a fan of Java EE and there are 3 main reasons why:
1) The technology is very mature and production proven.
2) It is a standard technology, and there are good reasons to stick to a
standard and anticipate all its best-practice patterns [4].
3) You get a bundle of features for free, especially monitoring, which is
interesting for productive use.
How does this relate to Apache Isis?
I believe we could do better in honoring those, that are potentially interested
in using Isis on top of Java EE infrastructure.
I think I need to clarify:
Apache Isis currently very well runs on Servlet Containers, but it does not
(out of the box) on (certified) Java EE (full or web-profile) servers.
Main problem being dependency injection issues. So if you are interested in
using Java EE's Contexts and Dependency Injection (CDI) or Enterprise JavaBeans
(EJBs) within your business logic, you need to overcome some hurdles.
I would like to motivate a discussion about what you think regarding the
relevance of Java EE for Apache Isis.
Cheers, Andi
[1] https://www.youtube.com/watch?v=UNg9lmk60sg?t=47m40s
<https://www.youtube.com/watch?v=UNg9lmk60sg?t=47m40s>
[2] https://projects.eclipse.org/projects/ee4j/charter
<https://projects.eclipse.org/projects/ee4j/charter>
[3] https://www.youtube.com/watch?v=LwimkQQDhio
<https://www.youtube.com/watch?v=LwimkQQDhio>
[4] http://realworldpatterns.com/ <http://realworldpatterns.com/>
