After further reading, the problem probably lies in the method that jsf uses to create/lookup the Converter class.
With variables Seam is able to plug-in a SeamVariableResolver which allows Seam to intercept the call to Seam components and do the appropriate actions. However on a converter object, myfaces/jsf has an internal hashmap of converters that it looks up in via the converterid (which it creates at deployement time). This means Seam does not have an opportunity to manage the instantiation of the Converter object, and therefore @In(create=true) EntityManager em; does not work. Therefore the only way of fetching seam components or the persistence context would be to use a manual referencing technique, byassing the seam framework. This should not be a problem architecturaly if it is pratical. If anyone has anything to correct/clarify please chip in. Thanks, James View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918957#3918957 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918957 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
