Community
Participate
Working Groups
The tag registry was not listening for changes on the classpath that added jar files. For example, if you drop a jar file with .taglib.xml files into WEB-INF/lib or remove them, it was not detecting these conditions.
Created attachment 168059 [details] Adds a classpath listener mechanism that causes the FaceletTagRegistry to respond to jars being added and removed from the classpath
Created attachment 168060 [details] Test coverage for changes
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. The defect results in the tool not recognizing the addition or removal of composite components that are packaged in Jars. This will frustrate the end-user since they won't be able to use the components that they have added in the current session. * Is there a work-around? If so, why do you believe the work-around is insufficient? The workaround is to re-start the workbench or close and open the project * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? The patch includes a comprehensive set of Junit tests * Give a brief technical overview. Who has reviewed this fix? See comment 1 * What is the risk associated with this fix? Medium.
Patches applied to HEAD (3.2RC1).
Fixed.
