Hi,
I've made a test and I've got the same behavior. On the Cache injection
point I've got a warning saying that "no bean is eligible for injection".
Which classes/annotations are missing?
I've just seen that I've missed to mention that *@ConfigureCache* annotation
is only available since Infinispan 5.1.0.ALPHA1 (this annotation was
previously named *@Infinispan *in 5.0/5.0.1).
--Kevin
On 22 September 2011 11:51, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
Kevin, can you see what happens for you with the latest JBoss Tools
and
your example as well (when you have a minute!)
On 22 Sep 2011, at 11:49, Pete Muir wrote:
> Ok, so then I'm not really sure why Alexey is seeing this problem ;-)
>
> What version of Infinispan did you use?
>
> On 22 Sep 2011, at 11:47, Max Rydahl Andersen wrote:
>
>>> The default cache manager is produced using a standard CDI producer,
and the default cache is produced by a generic bean from Solder. How far
along is your support for generic beans from Solder?
>>
>> Was done for M2 and a few bugfixes/improvements in M3:
>>
>> See
http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M3.html
>>
http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M2.html look
for "Solder" and "Generic"
>>
>> "CDI tools now supports generic beans. You can use generic beans in your
project and CDI Tools won't be confused. So you will be able to use the
general CDI Tools features such as validation, code completion, hyperlinks,
refactoring, etc. to develop applications using generic beans as well as
plan ones."
>>
https://issues.jboss.org/browse/JBIDE-8674
>>
>> /max
>>
>>> The only thing that Infinispan does programmatically is bridge
Infinispan events to CDI events. However this isn't working right now ;-) It
also registers some of the JSR-107 annotations as CDI interceptors, which
shouldn't cause errors at least (we might just loose some info for the
user).
>>>
>>> On 22 Sep 2011, at 11:14, Max Rydahl Andersen wrote:
>>>
>>>> Alexey - exactly what I wanted to hear/see ;)
>>>>
>>>> Pete/Kevin - wanted to let you know about the below thread concerning
how
>>>> the CDI tooling picks up the infinispan integration and *almost* works
out of the box with it.
>>>>
>>>> Was wondering if you guys tried it out and had ideas/suggestions to it
>>>> and especially how/if we could get info from the integration to
support the
>>>> things that are contributed purely programmatically and thus not
visible to the tools ?
>>>>
>>>> Thanks,
>>>> Max
>>>>
>>>> On Sep 21, 2011, at 20:51, Alexey Kazakov wrote:
>>>>
>>>>> I played with infinispan cdi module and tried to use that blog to
test
>>>>> our CDI Tools.
>>>>> First at all it seems that the blog is not consistent with
Infinispan
>>>>> CDI Module 5.0.1.Final (the latest final version). Some
>>>>> classes/annotations mentioned in the blog are missing.
>>>>> But in general CDI Tools works with infinispan CDI artifacts which
use
>>>>> usual ways of declaration covered by JSR-299. But infinispan also
uses
>>>>> its own CDI extension for registering some artifacts
programmatically.
>>>>> Our CDI Tools doesn't support such dynamic stuff out of the box.
We
have
>>>>> to create a CDI Tools extension to provide a full support of
infinispan
>>>>> cdi module.
>>>>> To do so, we need a good documentation to make sure we know how it
>>>>> should work in runtime or at least we need to have a stable source
code
>>>>> which we can research to replicate it logic in our extension.
>>>>>
>>>>> For example:
>>>>>
>>>>> @Inject
>>>>> EmbeddedCacheManager defaultCacheManager; // Works in CDI Tools
>>>>> since EmbeddedCacheManager is produced by standard CDI producer in
>>>>> infinispan cdi module.
>>>>>
>>>>> @Inject
>>>>> Cache<String, String> defaultCache; // Can't be resolved
by CDI
>>>>> Tools. This bean is registered by
org.infinispan.cdi.InfinispanExtension
>>>>> programmatically.
>>>>>
>>>>>
>>>>>
>>>>> On 09/21/2011 06:49 AM, Max Rydahl Andersen wrote:
>>>>>> Hi Alexey et.al,
>>>>>>
>>>>>> Just saw this blog
http://infinispan.blogspot.com/2011/09/when-infinispan-meets-cdi.html
>>>>>>
>>>>>> Looks like a great example app to try out if our tooling picks
up
their annotations properly or
>>>>>> if we or they need to do something differently ?
>>>>>>
>>>>>> /max
>>>>>>
http://about.me/maxandersen
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev(a)lists.jboss.org
>>>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>> /max
>>>>
http://about.me/maxandersen
>>>>
>>>>
>>>>
>>>
>>
>> /max
>>
http://about.me/maxandersen
>>
>>
>>
>