Closed glassfishrobot closed 14 years ago
@glassfishrobot Commented @sivakumart said: Targetting fix for MS6.
@glassfishrobot Commented @sivakumart said: Analysis
We cannot remove the dependency from weld-integration to JSF implementation as this is an integral part of the CDI functionality. Making the relationship between weld-integration and jsf-impl lazy would give us very little benefit and would not be useful as the weld implementation would be non-compliant without a JSF implementation.
So, the recommendation is that we can't do much in the weld-integration bundle's side and hence I am closing this issue.
@glassfishrobot Commented @sivakumart said: Created an attachment (id=5149) status of glassfish modules after startup
@glassfishrobot Commented @sivakumart said: Created an attachment (id=5150) analysis of weld, jsf and web bundle status after startup
@glassfishrobot Commented File: module-status.txt Attached By: @sivakumart
@glassfishrobot Commented File: weld-jsf-web-analysis.txt Attached By: @sivakumart
@glassfishrobot Commented Issue-Links: blocks GLASSFISH-12022
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-13813
@glassfishrobot Commented Reported by tmueller
@glassfishrobot Commented Marked as incomplete on Thursday, October 14th 2010, 4:39:39 pm
This issue tracks the work being done to understand why the JSF implementation resolved by weld when the domain is started, and to see if this dependency can be made "lazy", i.e., that JSF would not actually be brought in until it is actually used.
Environment
Operating System: All Platform: All
Affected Versions
[3.1]