Community
Participate
Working Groups
Build Identifier: 20100617-1415 I noticed that the New JavaServer Faces (JSF) Page (xhtml, xml syntax) template has ISO-8859-1 hard-coded into the template instead of having ${encoding} where the encoding is specified. This is inconvenient who have set their default encoding to UTF-8 or their local encoding standard (e.g. an author could use Shift-JIS or UTF-8 for Japanese text, but will get mojibake served up if the encoding is set to ISO-8859-1). Reproducible: Always Steps to Reproduce: 1.Right click and hold on any dynamic web project's root node or the WebContent folder for that project in the project explorer. 2.A menu appears. 3.Select New->JSP File. 4.Give any name ending in .jsp in the file name line. 5.Click the Next button. 6.Click New JavaServer Faces (JSF) Page (xhtml, xml syntax) in the template list. 7.You will notice that ISO-8859-1 is hard-coded where ${encoding} should be located.
Checked into HEAD (3.2.2 and 3.3)
_
* 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. See description * Is there a work-around? If so, why do you believe the work-around is insufficient? None * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Manual * Give a brief technical overview. Who has reviewed this fix? See description * What is the risk associated with this fix? none-low
This failed to make this week's build because of spurious junit failures in local testing.
