Hey guys,
It feels like a right time to resume the discussion around Java 9. The adoption
of modules is slowly but is taking
off. I run into this article
https://www.javaadvent.com/2017/12/automatic-module-name-calling-java-library-maintainers.html
by
Sander Mak (co-author of Java 9 Modularity
@Sergey, thanks for clarification. @Romain Deltaspike is worth looking I think
(as to validate
the approach), thanks for pointing it out. The only concern I have about it is
the fact it is 100%
CDI-only library while for CXF CDI is just one of the options. Anyway,
something to learn here.
RMB
Something like deltaspike where it is on by default and deactivable by
config is not bad for such modules. Issue is: what is config? For spring it
is obvious but for cdi it must be the 2 mentionned solution and maybe a 3rd
fallback with a cxf specific solution - or system props.
An alternate more
Well, was not clear what you meant, the whole conversation was about
optionally choosing whether to auto-load a given provider or not with
CDI and you referred to SpringBoot which could do some magic and CXF
having the related module and possibly getting some ideas from there and
I thought I'd
Le 23 déc. 2017 18:15, "Andriy Redko" a écrit :
Aha moment, so there are limitations, that's why I was unsure about that.
Regarding deltaspike / microprofile
config, we can look it up, if you have some examples / snippets to point
out right away, would be great. Thanks.
Can help middle of next
Aha moment, so there are limitations, that's why I was unsure about that.
Regarding deltaspike / microprofile
config, we can look it up, if you have some examples / snippets to point out
right away, would be great. Thanks.
RMB> Le 23 déc. 2017 16:15, "Andriy Redko" a écrit :
RMB> I have kind
Le 23 déc. 2017 16:15, "Andriy Redko" a écrit :
I have kind of disagree here, beans.xml has a dedicated section for
discovery (, spec section 12.4. Type and Bean
discovery). I am trying not to (re)invent our own activation / discovery
mechanisms but find the right way to deligate that to
the fram
I have kind of disagree here, beans.xml has a dedicated section for discovery
(, spec section 12.4. Type and Bean
discovery). I am trying not to (re)invent our own activation / discovery
mechanisms but find the right way to deligate that to
the framework in question. Not only CXF would benefit fr
Scanning us unrelated to issue guys. Issue is: how to auto configure
activation or not for not app code. A cdi-cxf.xml can be an easy way and
the cdi extension can pick up the new beans no? Beans.xml doesnt handle the
scanning at all (bda vs global config).
Le 23 déc. 2017 00:15, "Andriy Redko"
