2:51 a.m.
Hi all
Half a year has passed since Java 9 release. Can anyone say if there are any
documentation,
solutions etc how to work with JPMS in Weld?
--
Alex Sviridov
6:54 a.m.
Hi Alex,
in short, there is no official documentation on that because Weld runs in "classpath
mode".
JDK 9 and 10 are short-termed releases and will have no special support.
JDK 11 is something we should be looking at and we are doing that (lately we added support
to avoid illegal access there for instance).
When it comes to JPMS itself, the question is, in what environment are you running?
If it's EE (e.g. in a server like WildFly), then all magic needs to be worked on
server side, pretty much.
I know WildFly already has some of it, but I am pretty sure at this point most servers
won't fully support JPMS.
If in SE, then Weld itself is not defined as JPMS module and hence will end up in an
unnamed module (Weld has no module-info).
There is no way we can avoid deep reflection on your classes (for instance to be able to
intercept non-public methods), therefore you need to make sure your classes
allow us to do that (or rather to unnamed module where Weld resides ATM). Having done
that, it should work.
Matej
----- Original Message -----
From: "Alex Sviridov" <ooo_saturn7(a)mail.ru>
To: "weld-dev" <weld-dev(a)lists.jboss.org>
Sent: Tuesday, May 8, 2018 9:51:38 AM
Subject: [weld-dev] Weld and JPMS
Hi all
Half a year has passed since Java 9 release. Can anyone say if there are any
documentation,
solutions etc how to work with JPMS in Weld?
--
Alex Sviridov
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
7:09 a.m.
Hi Matej,
Thank you for such a detailed answer. If I understand you right Weld in not modular
according to JPMS specs.
If so, then are there any plans (opened issues) to make it modular?
Besides, one question is very interesting for me - will Weld create separate container for
every JPMS module
or Weld will create one container for all JPMS modules?
Best regards, Alex
Среда, 9 мая 2018, 14:54 +03:00 от Matej Novotny
<manovotn(a)redhat.com>:
Hi Alex,
in short, there is no official documentation on that because Weld runs in "classpath
mode".
JDK 9 and 10 are short-termed releases and will have no special support.
JDK 11 is something we should be looking at and we are doing that (lately we added support
to avoid illegal access there for instance).
When it comes to JPMS itself, the question is, in what environment are you running?
If it's EE (e.g. in a server like WildFly), then all magic needs to be worked on
server side, pretty much.
I know WildFly already has some of it, but I am pretty sure at this point most servers
won't fully support JPMS.
If in SE, then Weld itself is not defined as JPMS module and hence will end up in an
unnamed module (Weld has no module-info).
There is no way we can avoid deep reflection on your classes (for instance to be able to
intercept non-public methods), therefore you need to make sure your classes
allow us to do that (or rather to unnamed module where Weld resides ATM). Having done
that, it should work.
Matej
----- Original Message -----
> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
> To: "weld-dev" < weld-dev(a)lists.jboss.org >
> Sent: Tuesday, May 8, 2018 9:51:38 AM
> Subject: [weld-dev] Weld and JPMS
>
> Hi all
>
> Half a year has passed since Java 9 release. Can anyone say if there are any
> documentation,
> solutions etc how to work with JPMS in Weld?
>
>
> --
> Alex Sviridov
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Alex Sviridov
7:38 a.m.
Comments inline
Matej
----- Original Message -----
From: "Alex Sviridov" <ooo_saturn7(a)mail.ru>
To: "Matej Novotny" <manovotn(a)redhat.com>, "weld-dev"
<weld-dev(a)lists.jboss.org>
Sent: Wednesday, May 9, 2018 2:09:56 PM
Subject: Re[2]: [weld-dev] Weld and JPMS
Hi Matej,
Thank you for such a detailed answer. If I understand you right Weld in not
modular according to JPMS specs.
If so, then are there any plans (opened issues) to make it modular?
There are no opened issues at the moment, feel free to create one, however I cannot
guarantee you any time-bound implementation.
Weld is (as as a reference implementation of CDI) mainly looking at EE and there we need
to see how EE-world deals with the burden that is called JPMS.
When it comes to SE, the problem is we will need to come up with something that, in the
same time, won't break EE behaviour (SE is re-using same core as is in EE and so
forth).
Besides, one question is very interesting for me - will Weld create separate
container for every JPMS module
or Weld will create one container for all JPMS modules?
Not sure I understand you correctly, but I see no benefit in running parallel Weld
containers?
Weld will have to behave as it did until now (backward compatibility), which effectively
means one container for all JPMS modules in that deployment.
Best regards, Alex
>Среда, 9 мая 2018, 14:54 +03:00 от Matej Novotny <manovotn(a)redhat.com>:
>
>Hi Alex,
>
>in short, there is no official documentation on that because Weld runs in
>"classpath mode".
>
>JDK 9 and 10 are short-termed releases and will have no special support.
>JDK 11 is something we should be looking at and we are doing that (lately we
>added support to avoid illegal access there for instance).
>
>When it comes to JPMS itself, the question is, in what environment are you
>running?
>If it's EE (e.g. in a server like WildFly), then all magic needs to be
>worked on server side, pretty much.
>I know WildFly already has some of it, but I am pretty sure at this point
>most servers won't fully support JPMS.
>
>If in SE, then Weld itself is not defined as JPMS module and hence will end
>up in an unnamed module (Weld has no module-info).
>There is no way we can avoid deep reflection on your classes (for instance
>to be able to intercept non-public methods), therefore you need to make
>sure your classes
>allow us to do that (or rather to unnamed module where Weld resides ATM).
>Having done that, it should work.
>
>Matej
>
>
>----- Original Message -----
>> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
>> To: "weld-dev" < weld-dev(a)lists.jboss.org >
>> Sent: Tuesday, May 8, 2018 9:51:38 AM
>> Subject: [weld-dev] Weld and JPMS
>>
>> Hi all
>>
>> Half a year has passed since Java 9 release. Can anyone say if there are
>> any
>> documentation,
>> solutions etc how to work with JPMS in Weld?
>>
>>
>> --
>> Alex Sviridov
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Alex Sviridov
7:43 a.m.
Thank you again. I opened an issue https://issues.jboss.org/browse/WELD-2493
Среда, 9 мая 2018, 15:38 +03:00 от Matej Novotny
<manovotn(a)redhat.com>:
Comments inline
Matej
----- Original Message -----
> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
> To: "Matej Novotny" < manovotn(a)redhat.com >, "weld-dev"
< weld-dev(a)lists.jboss.org >
> Sent: Wednesday, May 9, 2018 2:09:56 PM
> Subject: Re[2]: [weld-dev] Weld and JPMS
>
> Hi Matej,
>
> Thank you for such a detailed answer. If I understand you right Weld in not
> modular according to JPMS specs.
> If so, then are there any plans (opened issues) to make it modular?
There are no opened issues at the moment, feel free to create one, however I cannot
guarantee you any time-bound implementation.
Weld is (as as a reference implementation of CDI) mainly looking at EE and there we need
to see how EE-world deals with the burden that is called JPMS.
When it comes to SE, the problem is we will need to come up with something that, in the
same time, won't break EE behaviour (SE is re-using same core as is in EE and so
forth).
>
> Besides, one question is very interesting for me - will Weld create separate
> container for every JPMS module
> or Weld will create one container for all JPMS modules?
Not sure I understand you correctly, but I see no benefit in running parallel Weld
containers?
Weld will have to behave as it did until now (backward compatibility), which effectively
means one container for all JPMS modules in that deployment.
>
> Best regards, Alex
>
> >Среда, 9 мая 2018, 14:54 +03:00 от Matej Novotny < manovotn(a)redhat.com >:
> >
> >Hi Alex,
> >
> >in short, there is no official documentation on that because Weld runs in
> >"classpath mode".
> >
> >JDK 9 and 10 are short-termed releases and will have no special support.
> >JDK 11 is something we should be looking at and we are doing that (lately we
> >added support to avoid illegal access there for instance).
> >
> >When it comes to JPMS itself, the question is, in what environment are you
> >running?
> >If it's EE (e.g. in a server like WildFly), then all magic needs to be
> >worked on server side, pretty much.
> >I know WildFly already has some of it, but I am pretty sure at this point
> >most servers won't fully support JPMS.
> >
> >If in SE, then Weld itself is not defined as JPMS module and hence will end
> >up in an unnamed module (Weld has no module-info).
> >There is no way we can avoid deep reflection on your classes (for instance
> >to be able to intercept non-public methods), therefore you need to make
> >sure your classes
> >allow us to do that (or rather to unnamed module where Weld resides ATM).
> >Having done that, it should work.
> >
> >Matej
> >
> >
> >----- Original Message -----
> >> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
> >> To: "weld-dev" < weld-dev(a)lists.jboss.org >
> >> Sent: Tuesday, May 8, 2018 9:51:38 AM
> >> Subject: [weld-dev] Weld and JPMS
> >>
> >> Hi all
> >>
> >> Half a year has passed since Java 9 release. Can anyone say if there are
> >> any
> >> documentation,
> >> solutions etc how to work with JPMS in Weld?
> >>
> >>
> >> --
> >> Alex Sviridov
> >>
> >> _______________________________________________
> >> weld-dev mailing list
> >> weld-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> --
> Alex Sviridov
>
--
Alex Sviridov
8:24 a.m.
Hi Matej
I reread your answer, and have another question - can Weld run in module path as auto
module?
Среда, 9 мая 2018, 14:54 +03:00 от Matej Novotny
<manovotn(a)redhat.com>:
Hi Alex,
in short, there is no official documentation on that because Weld runs in "classpath
mode".
JDK 9 and 10 are short-termed releases and will have no special support.
JDK 11 is something we should be looking at and we are doing that (lately we added support
to avoid illegal access there for instance).
When it comes to JPMS itself, the question is, in what environment are you running?
If it's EE (e.g. in a server like WildFly), then all magic needs to be worked on
server side, pretty much.
I know WildFly already has some of it, but I am pretty sure at this point most servers
won't fully support JPMS.
If in SE, then Weld itself is not defined as JPMS module and hence will end up in an
unnamed module (Weld has no module-info).
There is no way we can avoid deep reflection on your classes (for instance to be able to
intercept non-public methods), therefore you need to make sure your classes
allow us to do that (or rather to unnamed module where Weld resides ATM). Having done
that, it should work.
Matej
----- Original Message -----
> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
> To: "weld-dev" < weld-dev(a)lists.jboss.org >
> Sent: Tuesday, May 8, 2018 9:51:38 AM
> Subject: [weld-dev] Weld and JPMS
>
> Hi all
>
> Half a year has passed since Java 9 release. Can anyone say if there are any
> documentation,
> solutions etc how to work with JPMS in Weld?
>
>
> --
> Alex Sviridov
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Alex Sviridov
1:42 a.m.
Hi Alex
technically speaking it should - this is implied by how jigsaw works.
However, it will be very difficult to set up and use due to auto-module naming.
You will need your crystal ball to guess what are the module names to which you need to
allow deep reflection.
And likewise what auto-modules do you need to depend on.
I haven't tried this though, so take what I say with a pinch of salt.
If you do some testing, I'll be glad to hear the results as well.
Matej
----- Original Message -----
From: "Alex Sviridov" <ooo_saturn7(a)mail.ru>
To: "Matej Novotny" <manovotn(a)redhat.com>, "weld-dev"
<weld-dev(a)lists.jboss.org>
Sent: Tuesday, May 15, 2018 3:24:35 PM
Subject: Re[2]: [weld-dev] Weld and JPMS
Hi Matej
I reread your answer, and have another question - can Weld run in module path
as auto module?
>Среда, 9 мая 2018, 14:54 +03:00 от Matej Novotny <manovotn(a)redhat.com>:
>
>Hi Alex,
>
>in short, there is no official documentation on that because Weld runs in
>"classpath mode".
>
>JDK 9 and 10 are short-termed releases and will have no special support.
>JDK 11 is something we should be looking at and we are doing that (lately we
>added support to avoid illegal access there for instance).
>
>When it comes to JPMS itself, the question is, in what environment are you
>running?
>If it's EE (e.g. in a server like WildFly), then all magic needs to be
>worked on server side, pretty much.
>I know WildFly already has some of it, but I am pretty sure at this point
>most servers won't fully support JPMS.
>
>If in SE, then Weld itself is not defined as JPMS module and hence will end
>up in an unnamed module (Weld has no module-info).
>There is no way we can avoid deep reflection on your classes (for instance
>to be able to intercept non-public methods), therefore you need to make
>sure your classes
>allow us to do that (or rather to unnamed module where Weld resides ATM).
>Having done that, it should work.
>
>Matej
>
>
>----- Original Message -----
>> From: "Alex Sviridov" < ooo_saturn7(a)mail.ru >
>> To: "weld-dev" < weld-dev(a)lists.jboss.org >
>> Sent: Tuesday, May 8, 2018 9:51:38 AM
>> Subject: [weld-dev] Weld and JPMS
>>
>> Hi all
>>
>> Half a year has passed since Java 9 release. Can anyone say if there are
>> any
>> documentation,
>> solutions etc how to work with JPMS in Weld?
>>
>>
>> --
>> Alex Sviridov
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Alex Sviridov
2427
days inactive
2435
days old
6 comments
2 participants
participants (2)
-
Alex Sviridov -
Matej Novotny