Hi, can you share any snippet of code?
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/11/20 Howard W. Smith, Jr. <smithh032...@gmail.com> > Prior to migrating from JSF managed to CDI (and currently in production), > my web app is using @Asynchronous on @SessionScoped bean to push data to > and keep Google Calendar updated with specific data from the database. > > Honestly, I don't think I coded it correctly. What I mean by that, I don't > think I'm handling or capturing the return value of @Asynchronous methods, > and honestly, I don't know where execution is ending after some or most of > the calls to @Asynchronous methods. > > Currently, in production, the @Asynchronous method calls seem to be working > fine (production = MyFaces Core 2.1.9, JSF managed beans, Glassfish > 3.1.2.2). Now that I'm migrating to TomEE/CDI, it seems as though > @Asynchronous is breaking my app; of course, I don't mind accepting > responsibility and calling it a developer error. @Asynchronous seems to > result with the following error: > > Target Unreachable, identifier resolved to null > > I've read the following: > > > http://www.andrejkoelewijn.com/wp/2010/03/05/jee-cdi-tip-target-unreachable-identifier-resolved-to-null/ > > > http://stackoverflow.com/questions/4845041/target-unreachable-identifier-resolved-to-null > > but I have an empty beans.xml in WEB-INF and I have no JARs of my own (so > no need to add beans.xml to META-INF, and please note, a lot of the xhtml > pages in the app are working as designed. Also, I read something about > cyclic references (below) > > "injection points in one bean deployment archive cannot be satisfied by a > bean in a separate bean archive, even when they are from libraries in the > same module (web > archive)"< > http://java.net/jira/browse/GLASSFISH-15721?focusedCommentId=301147&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_301147 > > > > but I'm sure that is not the cause of the error that I'm experiencing. > > So, would you all recommend me to consider CDI Events instead of > @Asynchronous, both, or should I just fix @Asynchronous to work in the CDI > app? > > Thanks, > Howard >
