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