| Summary: | [NLS] Clean up LogValStart and LogValEnd strings | ||
|---|---|---|---|
| Product: | [WebTools] WTP Common Tools | Reporter: | Nitin Dahyabhai <thatnitind> |
| Component: | wst.validation | Assignee: | Nitin Dahyabhai <thatnitind> |
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | trivial | ||
| Priority: | P3 | CC: | david_williams, keith.chong.ca |
| Version: | 3.2.3 | Flags: | david_williams:
pmc_approved+
thatnitind: pmc_approved? (raghunathan.srinivasan) thatnitind: pmc_approved? (naci.dai) thatnitind: pmc_approved? (deboer) thatnitind: pmc_approved? (neil.hauge) thatnitind: pmc_approved? (kaloyan) thatnitind: pmc_approved? (cbridgha) |
| Target Milestone: | 3.3 M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | PMC_approved | ||
* 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 wording with all of our validators named "XYZ Validator" is amatuerish. * Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround. Removing "Validator" from our validator names wouldn't improve things, and would be a larger change. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Ad-hoc. * Give a brief technical overview. Who has reviewed this fix? Changes to values in properties files. Binding placeholders remain. * What is the risk associated with this fix? None, but mea culpa, I forgot to get it approved before I checked it in and released it two days ago. Changed. |
Currently the LogValStart string, for example, is "Validator {0} starting to validate: {1}" which, since we name our validators "XYZ Validator", results in "Validator XYZ Validator starting to validate:" {1}. That would look better without the leading word.