-
1. Re: Should we disable weld subsystem if CDI is not using?
jamezp Jul 22, 2015 1:26 PM (in response to valsaraj007)You should be able to, but I don't really think you need to. If you're not using CDI the only overhead should be during deployment when it scans for beans or configuration files. That overhead should be rather low though.
--
James R. Perkins
-
2. Re: Should we disable weld subsystem if CDI is not using?
valsaraj007 Jul 22, 2015 11:33 PM (in response to jamezp)I found this reported issue: [WFLY-4210] Very Slow performance for larger JSF 2 pages. - JBoss Issue Tracker
It's related to runtime performance, right?
-
3. Re: Should we disable weld subsystem if CDI is not using?
jaikiran Jul 23, 2015 9:01 AM (in response to valsaraj007)valsaraj viswanathan wrote:
I found this reported issue: [WFLY-4210] Very Slow performance for larger JSF 2 pages. - JBoss Issue Tracker
It's related to runtime performance, right?
That issue appears to be in JSF subsystem rather than Weld subsystem.
-
4. Re: Should we disable weld subsystem if CDI is not using?
valsaraj007 Jul 23, 2015 9:52 AM (in response to jaikiran)Yes, the committed fix is in JSF but there is a workaround which suggests to add empty beans.xml to resolve this issue - [WFLY-4210] Very Slow performance for larger JSF 2 pages. - JBoss Issue Tracker
I am wondering whether I should disable weld which is not using now or add beans.xml?