From ooo_saturn7 at mail.ru Thu Jan 4 11:53:33 2018 From: ooo_saturn7 at mail.ru (=?UTF-8?B?QWxleCBTdmlyaWRvdg==?=) Date: Thu, 04 Jan 2018 19:53:33 +0300 Subject: [weld-dev] =?utf-8?q?Weld=2C_Jetty_and_JPMS?= Message-ID: <1515084813.428347496@f478.i.mail.ru> Hi all Let me first explain what I want to do. I want to have the following tree of JPMS layers: ??????????????????????????? Site 1 layer ?????????????????????????? / WebServer layer - Site M layer ????????????????????????? \ ?????????????????????????? Site N layer As we see WebServer layer has access to all site layers and every site layer has access to WebServer layer. Any site layer can be added and removed dynamically. Every site layer has one .war file and some .jar files. For every site I need two java ee technologies: servlets and cdi. So, for servlet container I plan to use Jetty and for cdi container I want to use weld. Could anyone answer the following questions: 1) can weld be used this way? 2) how should I use weld - should I create container for every layer or ...? I would appreciate any help and ideas. Best regards,? Alex Sviridov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20180104/8f14ef42/attachment.html From john.d.ament at gmail.com Sat Jan 13 10:17:35 2018 From: john.d.ament at gmail.com (John D. Ament) Date: Sat, 13 Jan 2018 15:17:35 +0000 Subject: [weld-dev] Flat Deployment mode & beans.xml Message-ID: Hi, If I'm using Weld SE in a flat deployment mode, is a beans.xml required still in all JARs? I would assume that with the beans.xml's being merged, any JAR that didn't have a beans.xml would inherit the "merged" one. John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20180113/f9a3c210/attachment.html From manovotn at redhat.com Mon Jan 15 02:04:15 2018 From: manovotn at redhat.com (Matej Novotny) Date: Mon, 15 Jan 2018 02:04:15 -0500 (EST) Subject: [weld-dev] Flat Deployment mode & beans.xml In-Reply-To: References: Message-ID: <1854007752.6614406.1515999855498.JavaMail.zimbra@redhat.com> Hi John, what you say makes sense, there shouldn't be need for multiple beans.xml. Does it give you any errors? Matej ----- Original Message ----- > From: "John D. Ament" > To: "Weld" > Sent: Saturday, January 13, 2018 4:17:35 PM > Subject: [weld-dev] Flat Deployment mode & beans.xml > > Hi, > > If I'm using Weld SE in a flat deployment mode, is a beans.xml required still > in all JARs? I would assume that with the beans.xml's being merged, any JAR > that didn't have a beans.xml would inherit the "merged" one. > > John > > _______________________________________________ > weld-dev mailing list > weld-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev From manovotn at redhat.com Mon Jan 15 02:16:25 2018 From: manovotn at redhat.com (Matej Novotny) Date: Mon, 15 Jan 2018 02:16:25 -0500 (EST) Subject: [weld-dev] Flat Deployment mode & beans.xml In-Reply-To: <1854007752.6614406.1515999855498.JavaMail.zimbra@redhat.com> References: <1854007752.6614406.1515999855498.JavaMail.zimbra@redhat.com> Message-ID: <1134251759.6616871.1516000585319.JavaMail.zimbra@redhat.com> Actually, now that I think of it I was wrong. You may have a set of JARs in your deployment and you don't want to pick up beans from all JARs (it might even lead to ambiguous dep for example). Therefore, beans.xml, even empty one, would be required to mark an archive which is to be considered a bean archive. I also found this test which can be easily fiddled with to verify what I said above - https://github.com/weld/core/blob/master/environments/se/tests/src/test/java/org/jboss/weld/environment/se/test/discovery/isolation/IsolationDisabledTest.java E.g. if you change `bda1` to be a JavaArchive (no beans.xml added), it will fail with unsatisfied dep. Matej ----- Original Message ----- > From: "Matej Novotny" > To: "John D. Ament" > Cc: "Weld" > Sent: Monday, January 15, 2018 8:04:15 AM > Subject: Re: [weld-dev] Flat Deployment mode & beans.xml > > Hi John, > > what you say makes sense, there shouldn't be need for multiple beans.xml. > Does it give you any errors? > > Matej > > ----- Original Message ----- > > From: "John D. Ament" > > To: "Weld" > > Sent: Saturday, January 13, 2018 4:17:35 PM > > Subject: [weld-dev] Flat Deployment mode & beans.xml > > > > Hi, > > > > If I'm using Weld SE in a flat deployment mode, is a beans.xml required > > still > > in all JARs? I would assume that with the beans.xml's being merged, any JAR > > that didn't have a beans.xml would inherit the "merged" one. > > > > John > > > > _______________________________________________ > > weld-dev mailing list > > weld-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/weld-dev > _______________________________________________ > weld-dev mailing list > weld-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > From john.d.ament at gmail.com Mon Jan 15 07:34:59 2018 From: john.d.ament at gmail.com (John D. Ament) Date: Mon, 15 Jan 2018 12:34:59 +0000 Subject: [weld-dev] Flat Deployment mode & beans.xml In-Reply-To: <1134251759.6616871.1516000585319.JavaMail.zimbra@redhat.com> References: <1854007752.6614406.1515999855498.JavaMail.zimbra@redhat.com> <1134251759.6616871.1516000585319.JavaMail.zimbra@redhat.com> Message-ID: Yes, that test is basically why I'm asking the question. Also, if I am using implicit bean archives (per the CDI spec, the system flag) and have flat deploymnet mode in Weld, what bean discovery should I be seeing? The result of the merged beans.xml? John On Mon, Jan 15, 2018 at 2:16 AM Matej Novotny wrote: > Actually, now that I think of it I was wrong. > You may have a set of JARs in your deployment and you don't want to pick > up beans from all JARs (it might even lead to ambiguous dep for example). > Therefore, beans.xml, even empty one, would be required to mark an archive > which is to be considered a bean archive. > > I also found this test which can be easily fiddled with to verify what I > said above - > https://github.com/weld/core/blob/master/environments/se/tests/src/test/java/org/jboss/weld/environment/se/test/discovery/isolation/IsolationDisabledTest.java > E.g. if you change `bda1` to be a JavaArchive (no beans.xml added), it > will fail with unsatisfied dep. > > Matej > > ----- Original Message ----- > > From: "Matej Novotny" > > To: "John D. Ament" > > Cc: "Weld" > > Sent: Monday, January 15, 2018 8:04:15 AM > > Subject: Re: [weld-dev] Flat Deployment mode & beans.xml > > > > Hi John, > > > > what you say makes sense, there shouldn't be need for multiple beans.xml. > > Does it give you any errors? > > > > Matej > > > > ----- Original Message ----- > > > From: "John D. Ament" > > > To: "Weld" > > > Sent: Saturday, January 13, 2018 4:17:35 PM > > > Subject: [weld-dev] Flat Deployment mode & beans.xml > > > > > > Hi, > > > > > > If I'm using Weld SE in a flat deployment mode, is a beans.xml required > > > still > > > in all JARs? I would assume that with the beans.xml's being merged, > any JAR > > > that didn't have a beans.xml would inherit the "merged" one. > > > > > > John > > > > > > _______________________________________________ > > > weld-dev mailing list > > > weld-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/weld-dev > > _______________________________________________ > > weld-dev mailing list > > weld-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/weld-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20180115/03a7001f/attachment.html