[weld-issues] [JBoss JIRA] Commented: (WELDSERVLET-6) Conversation should work on AppEngine
[
https://jira.jboss.org/jira/browse/WELDSERVLET-6?page=com.atlassian.jira....
]
Paul Bakker commented on WELDSERVLET-6:
---------------------------------------
Turns out I was looking at old source code. I checked out weld-servlet from the trunk, but
I just found in the pom.xml that there is a dependency to weld-core 1.0.1-FINAL instead of
1.0.2-SNAPSHOT. I'm not sure this is intended, but to my opinion it would be more
logical to depend on the snapshot. Anyway, this is not related to this issue.
After changing the dependency it works like you said, so I can confirm it works. Thanks
for looking at it again.
Conversation should work on AppEngine
-------------------------------------
Key: WELDSERVLET-6
URL: https://jira.jboss.org/jira/browse/WELDSERVLET-6
Project: Weld Servlet
Issue Type: Feature Request
Environment: Google AppEngine 1.3
Reporter: Paul Bakker
Assignee: Matija Mazi
Priority: Optional
Weld works pretty well on GAE, which is of course great in combination with JSF 2. The
only problem I've ran into so far is that conversations don't work. GAE
doesn't allow threading, and the cleanup scheduler in Weld brakes this rule.
The problem is in
org.jboss.weld.conversation.AbstractConversationManager.scheduleForTermination(AbstractConversationManager.java:204)
This is obviously not a bug, it's just a GAE problem. I'm not sure how this
should be solved in a clean way, disabling the cleanup task when running on GAE seems like
a bad idea (memory leaks). It might be an idea to create a GAE task queue for cleanup, but
this would require GAE specific code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira