[
http://jira.jboss.com/jira/browse/JBSEAM-3085?page=comments#action_12417924 ]
Chris Lowe commented on JBSEAM-3085:
------------------------------------
This issue also appears to affect the sending of Seam templated emails via Flamingo.
There is a workaround detailed here:
http://groups.google.com/group/exadel-flamingo-users/browse_thread/thread...
Unfortunately this workaround only applies Flaming calls, I don't think it will work
with asynchronous method calls outlined in the OP.
Renderer is only partially functional when used asynchronously
--------------------------------------------------------------
Key: JBSEAM-3085
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3085
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Fix For: 2.1.0.GA
Attachments: JBSEAM-3085-branch20-v1.txt
Original Estimate: 1 week
Remaining Estimate: 1 week
The Renderer, which is used to render Facelet templates, is partially crippled when used
asynchronously. First of all, it throws an exception while setting up the
MockFacesContext() because it tries to retrieve an Application from the real JSF
FactoryFinder. That isn't going to work because JSF is not properly initialized. That
leads to the second problem, which is that if the template has any JSF component tags,
they aren't rendered because its not a real JSF environment.
I think the solution is to use JSFUnit to emulate a JSF environment so that the Renderer
can be used asynchronous. Otherwise, we cannot send email messages that use JSF components
in the background. The second solution is to document that you cannot render JSF markup in
your email if used asynchronously.
This affects the /examples/mail demo application.
--
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