Aaaah that one: I've fallen for that one several times in JEE projects too :-) The file is used as a marker for CDI so it doesnt have to scan all JARs
Am Montag, 22. Mai 2017 16:28:42 UTC+2 schrieb Pavel: > > It was necessary to put in bundlA META-INF folder beans.xml file. > I thought that beans.xml is required only in bundle for which container > is created. However, it turned out that this file is also required > for bundles for which container is not created but which contain > CDI beans. > > On 22.05.2017 16:55, Marc Schlegel wrote: > > What was the problem? > > > > Maybe somebody else has the same issue and could learn from this thread. > > > > Am Montag, 22. Mai 2017 13:26:34 UTC+2 schrieb Pavel: > >> Hi Marc > >> > >> Thank you for your suggestion. I have solved that problem. > >> > >> Best regards, Pavel > >> > >> понедельник, 22 мая 2017 г., 13:39:24 UTC+3 пользователь Marc Schlegel > >> написал: > >>> I remember that I had a example which pretty much covered your > use-case > >>> and it was working with RC1. > >>> > >>> Maybe you can share your two Beans as well as your manifest. > >>> > >>> regards > >>> Marc > >>> > >>> Am Samstag, 20. Mai 2017 20:16:16 UTC+2 schrieb Pavel: > >>>> Hi all > >>>> > >>>> I have two bundles - A and B. > >>>> > >>>> In bundleA I have an cdi Bean (@Dependent) in package com.temp. For > >>>> bundleA cdi container is not created. > >>>> > >>>> For bundleB cdi container is created. BundleB imports package > com.temp. > >>>> However, bundleB cdi container > >>>> doesn't find bean from bundleA. > >>>> > >>>> Could anyone say if it is possible to do and if possible then how? > >>>> > >>>> Best regards, Pavel > >>>> > > -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
