Should we disable weld subsystem if CDI is not using?

[valsaraj007]

My application is built on JSF 2.2.4 and EJB 3.2. It is not using CDI. Application is running on WildFly 8.2. Should we disable weld subsystem if CDI is not using?

[jamezp]

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

[valsaraj007]

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?

[jaikiran]

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.

[valsaraj007]

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

[WFLY-4210] Very Slow performance for larger JSF 2 pages. - Issue is with how the JSF and CDI integration is performed

I am wondering whether I should disable weld which is not using now or add beans.xml?