[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2657) Seam-mail fails when invoked from custom servlet bound with web:context-filter

Seam-mail fails when invoked from custom servlet bound with web:context-filter ------------------------------------------------------------------------------ Key: JBSEAM-2657 URL: http://jira.jboss.com/jira/browse/JBSEAM-2657 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Environment: Seam 2.0.1 and 2.0.2-SNAPSHOT from 13 feb 2008, plain Tomcat 6.0, JSF RI 1.2_07. Reporter: Przemyslaw Jaskierski (Reporting as FR as requested by Pete. Please, read linked thread for the full context). I try to send an email from one of services. The same code: renderer.render(/WEB-INF/emailTemplates/test.xhtml); invoked from application-scoped component with method annotated as @Observer(foo) 1. works when a synchronous event is invoked in JSF action using Events.instance().raiseEvent(foo) 2. fails when invoked using Events.instance().raiseAsynchronousEvent(foo) from the same JSF action 3. fails when invoked as both synchronous and asynchronous events from custom servlet bound with web:context-filter. Case 2. and 3. both lead to this exception: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) at org.jboss.seam.mock.MockFacesContext.<init>(MockFacesContext.java:60) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.init(FaceletsRenderer.java:95) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.run(FaceletsRenderer.java:77) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:169) Pete's response: (2) is untested and I wouldn't necessarily expect (3) to work. File a JIRA feature request for (3) please - but it will require some redesign on how we render mails (hopefully make it much more robust) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira