Community
Participate
Working Groups
Build Identifier: M-3.2.5-20110922064510 When the jsfFacetConfigurationEnabled field is false it produces a RuntimeException during a JSF project creation because the WEBCONTENT_DIR property does not exist (this property is created only when the jsfFacetConfigurationEnabled is true), the propertyChanged method located in the JSFFacetInstallPage class tries to set a value to this property without checking if the property exists. Proposed solution is to add a check for JsfFacetConfigurationUtil.isJsfFacetConfigurationEnabled() in the propertyChanged before trying to set the WEBCONTENT_DIR property. Reproducible: Always Steps to Reproduce: it does not fail on WTP but is making a consuming product fail because it is not using the jsfFacetConfigurationEnabled.
Created attachment 204227 [details] Adding a new check to avoid the RuntimeException
IBM is asking that this bug be addressed in the WTP 3.2.5 timeframe. This bug is causing our adopter product to fail, as per Gloria's description. We have provided a patch and would like it reviewed and committed/released.
We will review and target the M build on 10/7
Committed to 3.2.5 stream at 2011/10/03 01:50PM PDT.
Committed to HEAD (3.4 stream) at 2011/10/03 01:58PM PDT.