-
1. Re: Definition of parameter org.jboss.weld.conversation.concurrentAccessTimeout not recognized
manovotn Sep 4, 2017 2:35 AM (in response to abdoul.m.zorome)Hello,
The property setting you have seem correct.
What's blocking you is that Weld 2.2.13 didn't have this configuration option (yet), at least according to the documentation - Weld 2.2.13.Final - CDI Reference Implementation
And that state of source code at that point also confirms it (the option is not there yet).
Therefore, you might try to update Weld in your GF, but I am not sure how easy/possible that it.
Matej
-
2. Re: Definition of parameter org.jboss.weld.conversation.concurrentAccessTimeout not recognized
mkouba Sep 4, 2017 4:04 AM (in response to manovotn)Matej is right. The global configuration of concurrentAccessTimeout got added in 2.3.4.Final. See also WELD-2113. However, the injection should still work in Weld 2.2+. The difference between Weld 1.1 (CDI 1.0) and Weld 2 (CDI 1.2) conversations is that since CDI 1.1 conversations are not limited to JSF only, instead any servlet request has associated conversation. What was the original environment where
@Initialized(ConversationScoped.class)
approach works?