From jharting at redhat.com  Thu Apr  3 10:06:13 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Thu, 03 Apr 2014 16:06:13 +0200
Subject: [weld-dev] Weld 2.2.0.CR1
Message-ID: <533D6AD5.3090608@redhat.com>

Weld 2.2.0.CR1 is now released. See 
https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&version=12324466 
for details.

No official way of getting Weld 2.2 to WildFly yet but expect one very soon!

From ooo_saturn7 at mail.ru  Fri Apr  4 03:01:17 2014
From: ooo_saturn7 at mail.ru (=?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCh0LLQuNGA0LjQtNC+0LI=?=)
Date: Fri, 04 Apr 2014 11:01:17 +0400
Subject: [weld-dev] =?utf-8?q?BUG_-_CDI_inside_budnle_doesn=27t_see_bean?=
Message-ID: <1396594877.226990836@f137.i.mail.ru>

 I have two OSGI bundles:
The first contains: service, servlet, pojo
The second contains: consumer (of the service).
FACTS:
A) I inject service (bundle 1) to consumer (bundle 2) via CDI (@OSGiService) - everything is OK. 
B) I inject pojo to servlet via CDI (manually using beanManager.getBeans,beanManager.resolve) - everything is OK.
C) I inject pojo to service via CDI (manually using beanManager.getBeans,beanManager.resolve) - Error - can't locate the bean.
The reason why I use manual injection is that that I couldn't get it to work with @Inject and started googling. And I found  this
>CDI allows injection into non-component classes, but the instances must still be created by CDI. Your activator is instantiated by OSGi framework and CDI has no way to hook into that process. You can programmatically get hold of the CDI injection manager and request an instance from it instead of using @Inject in your main class.
I think that (C) must work, because instance is created via CDI but it doesn't. Is this a bug? How can it be fixed?



-- 
????????? ????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20140404/d8543a53/attachment-0001.html 

From jharting at redhat.com  Mon Apr  7 10:37:54 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Mon, 07 Apr 2014 16:37:54 +0200
Subject: [weld-dev] Weld 2.2.0.CR2 released
Message-ID: <5342B842.70500@redhat.com>

This time with an easy-to-apply patch for WildFly 8!

See https://community.jboss.org/thread/239640 for more information.

From jharting at redhat.com  Tue Apr 15 11:04:33 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Tue, 15 Apr 2014 17:04:33 +0200
Subject: [weld-dev] Weld 2.2.0.Final
Message-ID: <534D4A81.3050303@redhat.com>

http://weld.cdi-spec.org/news/2014/04/15/weld-220-final/

From jharting at redhat.com  Thu Apr 17 10:21:21 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Thu, 17 Apr 2014 16:21:21 +0200
Subject: [weld-dev] Weld 2.2.0.SP1 released
Message-ID: <534FE361.6090907@redhat.com>

As is sometimes happens, there is an important issue that fell through 
the cracks in the 2.2.0.Final release. Therefore, we release 2.2.0.SP1 
which addresses it. See http://weld.cdi-spec.org/download/

Jozef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20140417/b89204f8/attachment.html