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
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.
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?