This content has been marked as final.
Show 6 replies
-
1. Re: ConversationAwareViewHandler causing performance problems
wangliyu Aug 9, 2010 9:03 AM (in response to p.tommassen)the BeanProvider.conversation is calling BeanManager.resolve() to get the single bean instance, it actually using google collection class (MapMaker().makeComputingMap(new BeanDisambiguation(beanManager));) to get the ConcurrentMap, I guess it might be the concurrent issue, can you give some details like Env (server, version, JEE or servlet) & how many concurrent calls? I'm worry about this too. -
2. Re: ConversationAwareViewHandler causing performance problems
nickarls Aug 9, 2010 10:57 AM (in response to p.tommassen)I think the entire handler is about to be killed off as it appends too much if I recall correctly (e.g. links). The spec talks about using f:param for propagation (again, without checking)
-
3. Re: ConversationAwareViewHandler causing performance problems
pmuir Aug 10, 2010 6:26 AM (in response to p.tommassen)Please create an issue with all the details you can about your environment, and ideally provide a sample app. Link the issue to this one - https://jira.jboss.org/browse/WELD-89
-
4. Re: ConversationAwareViewHandler causing performance problems
marcelkolsteren Sep 16, 2010 6:09 AM (in response to p.tommassen) -
5. Re: ConversationAwareViewHandler causing performance problems
nickarls Sep 16, 2010 6:12 AM (in response to p.tommassen)If you want to insta-drop it, you could edit it out from the faces-config.xml under the weld deployer on the AS.
-
6. Re: ConversationAwareViewHandler causing performance problems
marcelkolsteren Sep 16, 2010 6:22 AM (in response to p.tommassen)I'm afraid that dropping the ConversationAwareViewHandler will also disable the automatic propagation of the conversation for JSF postbacks, redirects and Ajax requests. See my comment on WELD-549.