<HTML><BODY>Hi Matej<br><br>Thank you for your answer, but I couldn't make it work. I opened my package,<br>but Weld (see my previous message at the end), as I understand, wants to get<br>access to hidden fields and methods of classes in java.base module and JPMS doesn't<br>allow it.<br><br>So, I gave up - as I don't know what to do else. If you can make it work, please, report.<br>It would be very interesting.<br><br>Best regards, Alex<br><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
Вторник, 19 сентября 2017, 10:22 +03:00 от Matej Novotny <manovotn@redhat.com>:<br>
<br>
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<base target="_self" href="https://e.mail.ru/">
<div id="style_15058057590000000942_BODY">> 1) Please, take a look at the second table (module overview) here<br>
> <a href="https://labs.consol.de/development/2017/02/13/getting-started-with-java9-modules.html" target="_blank">https://labs.consol.de/development/2017/02/13/getting-started-with-java9-modules.html</a><br>
<br>
Did that, the article looks like there is finally some solid material on modules.<br>
<br>
> 2) Weld is not unnamed module but automatic module as it is on module path<br>
> and I use it by name.<br>
<br>
Yea, you are right, my bad. I meant automatic module OFC.<br>
<br>
> 3) From that table (module overview) we see that both automatic and unnamed<br>
> modules can read application modules. If so, then why it doesn't?<br>
<br>
I suppose you already got your answer on StackOverflow[1], right?<br>
To add on top of that, if you `exports` package - you only expose public things in there.<br>
For Weld to create proxies of your beans, we need to go deeper and allow reflections access which may mean accessing private/protected stuff (such as your @Inject private NewBean bean).<br>
Java 9 doesn't like that and requires you to `opens` the package for this kind of work.<br>
<br>
> And got the following (see below). It seems that Weld can't now work with<br>
> JPMS.<br>
> What will Weld developers say?<br>
<br>
From the SO question I guess you got it working in the end.<br>
If you have any other questions, feel free to contact us again.<br>
I'll try to test some JDK 9 project myself to refresh my memory so that I can be of more help next time :)<br>
<br>
Matej<br>
<br>
_________________________________________________________________________-<br>
[1] <a href="https://stackoverflow.com/questions/46282509" target="_blank">https://stackoverflow.com/questions/46282509</a><br>
<br>
----- Original Message -----<br>
> From: "Alex Sviridov" <<a href="mailto:ooo_saturn7@mail.ru">ooo_saturn7@mail.ru</a>><br>
> To: "weld-dev" <<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a>><br>
> Sent: Monday, September 18, 2017 5:23:30 PM<br>
> Subject: Re: [weld-dev] Weld and Java 9 JPMS<br>
> <br>
> So, here I am.<br>
> I changed my.module from<br>
> my.module {<br>
> requires weld.se.shaded;<br>
> exports com.foo;<br>
> }<br>
> to<br>
> my.module {<br>
> requires weld.se.shaded;<br>
> opens com.foo;<br>
> }<br>
> <br>
> And got the following (see below). It seems that Weld can't now work with<br>
> JPMS.<br>
> What will Weld developers say?<br>
> <br>
> Exception in thread "main" org.jboss.weld.exceptions.WeldException:<br>
> WELD-001524: Unable to load proxy class for bean Implicit Bean<br>
> [javax.enterprise.event.Event] with qualifiers [@Default] with class<br>
> interface javax.enterprise.event.Event using classloader<br>
> jdk.internal.loader.ClassLoaders$AppClassLoader@6b2fad11<br>
> at<br>
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native<br>
> Method)<br>
> at<br>
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<br>
> at<br>
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<br>
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)<br>
> at<br>
> java.base/java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:587)<br>
> at java.base/java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:996)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.checkForExceptions(AbstractExecutorServices.java:72)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:58)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:66)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer.doAfterBeanDiscovery(ConcurrentBeanDeployer.java:88)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.BeanDeployment.afterBeanDiscovery(BeanDeployment.java:268)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:466)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.environment.se.Weld.initialize(Weld.java:789)<br>
> at my.module/com.foo.NewMain.main(NewMain.java:47)<br>
> Caused by: org.jboss.weld.exceptions.WeldException: WELD-001524: Unable to<br>
> load proxy class for bean Implicit Bean [javax.enterprise.event.Event] with<br>
> qualifiers [@Default] with class interface javax.enterprise.event.Event<br>
> using classloader jdk.internal.loader.ClassLoaders$AppClassLoader@6b2fad11<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:389)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.builtin.AbstractFacadeBean.initializeAfterBeanDiscovery(AbstractFacadeBean.java:61)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:111)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:102)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)<br>
> at<br>
> java.base/java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1431)<br>
> at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:283)<br>
> at<br>
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1603)<br>
> at<br>
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)<br>
> Caused by: java.lang.ExceptionInInitializerError<br>
> at<br>
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native<br>
> Method)<br>
> at<br>
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<br>
> at<br>
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<br>
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.proxy.ProxyFactory.newClassFile(ProxyFactory.java:496)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:455)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:381)<br>
> ... 9 more<br>
> Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make<br>
> protected final java.lang.Class<br>
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int) throws<br>
> java.lang.ClassFormatError accessible: module java.base does not "opens<br>
> java.lang" to module weld.se.shaded<br>
> at<br>
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:337)<br>
> at<br>
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:281)<br>
> at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198)<br>
> at java.base/java.lang.reflect.Method.setAccessible(Method.java:192)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.classfilewriter.ClassFile$1.run(ClassFile.java:256)<br>
> at java.base/java.security.AccessController.doPrivileged(Native Method)<br>
> at<br>
> weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.classfilewriter.ClassFile.<clinit>(ClassFile.java:251)<br>
> ... 16 more<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Понедельник, 18 сентября 2017, 16:39 +03:00 от Matej Novotny<br>
> <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>>:<br>
> <br>
> From the exception you are getting, this line is important:<br>
> <br>
> "Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make<br>
> field private com.foo.NewBean com.foo.NewClass.bean accessible: module<br>
> my.module does not "opens com.foo" to module weld.se.shaded"<br>
> <br>
> Basically, Weld is not modularized (== lands in unnamed module) and it needs<br>
> access to your module so that it can create beans. E.g. you need to make<br>
> sure unnamed module has access to your module.<br>
> I think that by default in JDK 9 the access is intended so that all modules<br>
> can read unnamed module, but unnamed module can only read itself (simplified<br>
> version).<br>
> Hence you want to break a few rules and force this to work in the opposite<br>
> direction for your module.<br>
> <br>
> Matej<br>
> <br>
> <br>
> ----- Original Message -----<br>
> > From: "Alex Sviridov" < <a href="mailto:ooo_saturn7@mail.ru">ooo_saturn7@mail.ru</a> ><br>
> > To: "weld-dev" < <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a> ><br>
> > Sent: Monday, September 18, 2017 1:46:36 PM<br>
> > Subject: Re: [weld-dev] Weld and Java 9 JPMS<br>
> > <br>
> > Thank you for your answer.<br>
> > <br>
> > Could anyone give any suggestion about the following?<br>
> > <br>
> > I have my named module and weld-se-shaded as unnamed module.<br>
> > In my module I have<br>
> > <br>
> > module my.module {<br>
> > requires weld.se.shaded;<br>
> > exports com.foo;<br>
> > }<br>
> > <br>
> > #################################<br>
> > package com.foo;<br>
> > <br>
> > import javax.enterprise.context.ApplicationScoped;<br>
> > import javax.inject.Inject;<br>
> > <br>
> > @ApplicationScoped<br>
> > public class NewClass {<br>
> > <br>
> > @Inject<br>
> > private NewBean bean;<br>
> > <br>
> > public void doIt() {<br>
> > bean.doIt();<br>
> > }<br>
> > <br>
> > }<br>
> > <br>
> > #################################<br>
> > package com.foo;<br>
> > <br>
> > import javax.enterprise.context.Dependent;<br>
> > <br>
> > @Dependent<br>
> > public class NewBean {<br>
> > <br>
> > public void doIt() {<br>
> > System.out.println("I am doing it);<br>
> > }<br>
> > }<br>
> > <br>
> > And this is the result<br>
> > <br>
> > Sep 18, 2017 2:33:12 PM org.jboss.weld.bootstrap.WeldStartup <clinit><br>
> > INFO: WELD-000900: 3.0.2 (2017-09-18 08:49)<br>
> > Sep 18, 2017 2:33:12 PM<br>
> > org.jboss.weld.environment.deployment.discovery.ReflectionDiscoveryStrategy<br>
> > processAnnotatedDiscovery<br>
> > INFO: WELD-ENV-000014: Falling back to Java Reflection for<br>
> > bean-discovery-mode="annotated" discovery. Add org.jboss:jandex to the<br>
> > classpath to speed-up startup.<br>
> > Sep 18, 2017 2:33:12 PM org.jboss.weld.bootstrap.WeldStartup startContainer<br>
> > INFO: WELD-000101: Transactional services not available. Injection of<br>
> > @Inject<br>
> > UserTransaction not available. Transactional observers will be invoked<br>
> > synchronously.<br>
> > Exception in thread "main" java.lang.reflect.InaccessibleObjectException<br>
> > at<br>
> > java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native<br>
> > Method)<br>
> > at<br>
> > java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<br>
> > at<br>
> > java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<br>
> > at<br>
> > java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)<br>
> > at<br>
> > java.base/java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:590)<br>
> > at java.base/java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:996)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.checkForExceptions(AbstractExecutorServices.java:72)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:58)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.AbstractExecutorServices.invokeAllAndCheckForExceptions(AbstractExecutorServices.java:66)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer.createClassBeans(ConcurrentBeanDeployer.java:65)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:256)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:422)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.environment.se.Weld.initialize(Weld.java:789)<br>
> > at my.module/com.foo.NewMain.main(NewMain.java:47)<br>
> > Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make<br>
> > field private com.foo.NewBean com.foo.NewClass.bean accessible: module<br>
> > my.module does not "opens com.foo" to module weld.se.shaded<br>
> > at<br>
> > java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:337)<br>
> > at<br>
> > java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:281)<br>
> > at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)<br>
> > at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.security.GetAccessibleCopyOfMember.of(GetAccessibleCopyOfMember.java:38)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.security.GetAccessibleCopyOfMember.run(GetAccessibleCopyOfMember.java:44)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.security.GetAccessibleCopyOfMember.run(GetAccessibleCopyOfMember.java:26)<br>
> > at java.base/java.security.AccessController.doPrivileged(Native Method)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.FieldInjectionPoint.<init>(FieldInjectionPoint.java:65)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.InjectionPointFactory.createFieldInjectionPoint(InjectionPointFactory.java:141)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.InjectionPointFactory.addFieldInjectionPoint(InjectionPointFactory.java:226)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:211)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.producer.DefaultInjector.<init>(DefaultInjector.java:56)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.producer.ResourceInjector.<init>(ResourceInjector.java:57)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:48)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.producer.BeanInjectionTarget.<init>(BeanInjectionTarget.java:63)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:139)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:88)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.ManagedBean.<init>(ManagedBean.java:100)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:280)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:221)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:68)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:65)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)<br>
> > at<br>
> > weld.se.shaded@3.0.2-SNAPSHOT/org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)<br>
> > at<br>
> > java.base/java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1431)<br>
> > at<br>
> > java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:283)<br>
> > at<br>
> > java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1603)<br>
> > at<br>
> > java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Понедельник, 18 сентября 2017, 14:18 +03:00 от Matej Novotny<br>
> > < <a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a> >:<br>
> > <br>
> > Hi,<br>
> > <br>
> > if you are in SE, you should only need 'weld-se-shaded' artifact (as a<br>
> > JAR).<br>
> > As it is "shaded", it brings along all the other parts of Weld you might<br>
> > need.<br>
> > <br>
> > Matej<br>
> > <br>
> > <br>
> > ----- Original Message -----<br>
> > > From: "Alex Sviridov" < <a href="mailto:ooo_saturn7@mail.ru">ooo_saturn7@mail.ru</a> ><br>
> > > To: "weld-dev" < <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a> ><br>
> > > Sent: Monday, September 18, 2017 12:17:28 PM<br>
> > > Subject: Re: [weld-dev] Weld and Java 9 JPMS<br>
> > > <br>
> > > Hi Matej<br>
> > > <br>
> > > I am just trying to make Weld work in Java 9 (JavaSE + JPMS).<br>
> > > <br>
> > > I use the following jars as automatic modules:<br>
> > > <br>
> > > weld-environment-common-3.0.2-SNAPSHOT.jar<br>
> > > weld-se-core-3.0.2-SNAPSHOT.jar<br>
> > > weld-se-shaded-3.0.2-SNAPSHOT.jar<br>
> > > weld-spi-3.0.SP1.jar<br>
> > > weld-core-impl-3.0.2-SNAPSHOT.jar<br>
> > > <br>
> > > Is this right configuration? Or should I add/remove something.<br>
> > > <br>
> > > Best regards, Alex<br>
> > > <br>
> > > <br>
> > > <br>
> > > Понедельник, 18 сентября 2017, 12:41 +03:00 от Matej Novotny<br>
> > > < <a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a> >:<br>
> > > <br>
> > > Uhm, is there anything blocking you from placing it where you would in<br>
> > > Java<br>
> > > 8?<br>
> > > E.g. src/main/resources/META-INF?<br>
> > > <br>
> > > I don't think I have tried this combination (or I do not recall).<br>
> > > From the top of my head I don't know any JDK 9 limitation which would<br>
> > > forbid<br>
> > > to use XML descriptors in this way.<br>
> > > I might be a bit rusty though; been a while since I played with Java 9.<br>
> > > <br>
> > > Please do report back with how this works for you :)<br>
> > > Matej<br>
> > > <br>
> > > ----- Original Message -----<br>
> > > > From: "Alex Sviridov" < <a href="mailto:ooo_saturn7@mail.ru">ooo_saturn7@mail.ru</a> ><br>
> > > > To: "Matej Novotny" < <a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a> ><br>
> > > > Sent: Monday, September 18, 2017 10:28:11 AM<br>
> > > > Subject: Re[2]: [weld-dev] Weld and Java 9 JPMS<br>
> > > > <br>
> > > > Thank you for your answer. I will try. But where should I place<br>
> > > > beans.xml<br>
> > > > to make Weld read it if I use Java SE+ JPMS?<br>
> > > > <br>
> > > > Best regards, Alex<br>
> > > > <br>
> > > > <br>
> > > > >Понедельник, 18 сентября 2017, 8:10 +03:00 от Matej Novotny<br>
> > > > >< <a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a> >:<br>
> > > > > <br>
> > > > >Hi Alex<br>
> > > > > <br>
> > > > >Back there we did some tests with earlier versions of Java 9 and<br>
> > > > >eliminated<br>
> > > > >some crucial problems.<br>
> > > > >I think it should be possible to take *existing* app and run it on<br>
> > > > >Java<br>
> > > > >9.<br>
> > > > > <br>
> > > > >However, creating a whole new modular project might present some<br>
> > > > >additional<br>
> > > > >challenges.<br>
> > > > >Weld itself is not modularized (since it needs to run on Java 8),<br>
> > > > >therefore<br>
> > > > >you would need to list some extra "requires" in module-info.java for<br>
> > > > >Weld.<br>
> > > > >You also need to have reflection access allowed (we need to<br>
> > > > >instantiate<br>
> > > > >proxies etc) but last time I checked, it was by default enabled in JDK<br>
> > > > >9<br>
> > > > >wi<br>
> > > > >th just warning showing up.<br>
> > > > >Other than that, it might just work.<br>
> > > > > <br>
> > > > >To answer your other question - no, there is no tutorial, for there is<br>
> > > > >no<br>
> > > > >special difference between Weld and many other projects in regard to<br>
> > > > >JDK<br>
> > > > >9.<br>
> > > > > <br>
> > > > >Matej<br>
> > > > > <br>
> > > > >----- Original Message -----<br>
> > > > >> From: "Alex Sviridov" < <a href="mailto:ooo_saturn7@mail.ru">ooo_saturn7@mail.ru</a> ><br>
> > > > >> To: "weld-dev" < <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a> ><br>
> > > > >> Sent: Sunday, September 17, 2017 3:25:49 PM<br>
> > > > >> Subject: [weld-dev] Weld and Java 9 JPMS<br>
> > > > >> <br>
> > > > >> Hi all<br>
> > > > >> <br>
> > > > >> Could anyone provide information how weld works (if works) with Java<br>
> > > > >> 9<br>
> > > > >> JPMS?<br>
> > > > >> Is there any tutorial?<br>
> > > > >> <br>
> > > > >> Best regards, Alex<br>
> > > > >> <br>
> > > > >> _______________________________________________<br>
> > > > >> weld-dev mailing list<br>
> > > > >> <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> > > > >> <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
> > > > <br>
> > > > <br>
> > > > --<br>
> > > > Alex Sviridov<br>
> > > > <br>
> > > <br>
> > > <br>
> > > --<br>
> > > Alex Sviridov<br>
> > > <br>
> > > _______________________________________________<br>
> > > weld-dev mailing list<br>
> > > <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> > > <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
> > <br>
> > <br>
> > --<br>
> > Alex Sviridov<br>
> > <br>
> > _______________________________________________<br>
> > weld-dev mailing list<br>
> > <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
> <br>
> <br>
> --<br>
> Alex Sviridov<br>
> <br>
> _______________________________________________<br>
> weld-dev mailing list<br>
> <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
</div>
<base target="_self" href="https://e.mail.ru/">
</div>
</div>
</div>
</blockquote>
<br>
<br>-- <br>Alex Sviridov<br></BODY></HTML>