mybatis-cdi: 1.0.1, 1.0.2 not working in all cases in TomEE 7.0.4, 1.0.0 does
I am working on a project that incorporates Apache Camel into
Apache TomEE, both with CDI extensions utilized.
With mybatis-cdi 1.0.2 I have the problem, that beans which have
been looked up through Apache Camel raise a NameNotFoundException
for BeanManager in CDIUtils. I read through the source and found
out, that after mybatis cdi 1.0.0, which used
CDI.current().getBeanManager() a change  was made to use JNDI,
because of course CDI.current().getBeanManager() is only available
in CDI 1.1 upwards.
Unfortunally it seems that the BeanManager via JNDI is only
available in EJBs in TomEE 7.0.4. AFAIK that is so by
specification. So I would like to ask, what the general road for
mybatis CDI is and if CDI 1.0 support is going to be dropped any
time soon. For now I use mybatis cdi 1.0.0 but I would like to get
all the improvements that came after this release.
You received this message because you are subscribed to the Google Groups "mybatis-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.