| Summary: | Errors logged while loading JSP tag registry | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Gerry Kessler <gerry.kessler> | ||||
| Component: | JSF Tools | Assignee: | Gerry Kessler <gerry.kessler> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cameron.bateman, david_williams, kaloyan, neil.hauge, raghunathan.srinivasan, yurykats | ||||
| Version: | 3.2 | Flags: | david_williams:
pmc_approved+
raghunathan.srinivasan: pmc_approved? (naci.dai) raghunathan.srinivasan: pmc_approved? (deboer) neil.hauge: pmc_approved+ kaloyan: pmc_approved+ cameron.bateman: review+ raghunathan.srinivasan: review+ |
||||
| Target Milestone: | 3.2 RC4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Gerry Kessler
It should be pointed out that, depending on the tag libraries, there will be multiple (we have seen 10) exceptions logged per project per session. Created attachment 170693 [details]
Fix
A simple fix that logs the exception only when a trace option (which already exists) is enabled. Since the log entry is really only useful for debugging, this is a consistent solution.
* 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. This is a hotbug request. Adopter product shows multiple instances of an exception being logged for each project in the workspace. * Is there a work-around? If so, why do you believe the work-around is insufficient? No reasonable workaround * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Code review and manual testing. * Give a brief technical overview. Who has reviewed this fix? See comment 2 * What is the risk associated with this fix? none Approving based on adopter request and low risk nature. 10 per project per session is very bad. And looks safe enough. That new Throwable()); looks pretty odd. Then I saw you are just passing it to the status logger ... to have a stack trace? Up to you. David, I was just wrapping what had originally been there. I agree with your comment and I have removed the throwable for the checkin. |