This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
build 0417 I'm running in the ja locale, using a pseudo localized netbeans. 1. Create Web App using this the following tutorial http://www.netbeans.org/kb/55/quickstart-webapps.html or use the project from attach 2. Deploy it to AS 3. Entere some Ja text in the form on web page and press submit button. It won't be shown properly like with eng text. Changing encoding in browser or using IE takes no effect. On solars there is NPE on adding elements from HTML Forms and the IDE hangs for a while. With 0424 I couldn't build the project.
Created attachment 41928 [details] page before. See ja text in red
Created attachment 41929 [details] jsp after submit. Entered wasn't shown properly
Created attachment 41930 [details] changing encoding in browser didn't help
Created attachment 41931 [details] HelloWeb project
This happens when the project is a web application with the jsf faces framework chosen in the third panel. Does not happen when choosing vwp jsf as framework (at least does not happen using normal vwp activity using the pallette and dropping components onto design area and running that. User should not need to add language or preferred locales to browser options for this to work; the encoding information of the web app should handle that.
previous information about this issue using jsf faces framework was not correct - the demo used for this did not use any frameworks chosen from wizard. running the jastrologer demo, kb/articles/Astrologer-intro.html - that project does show multibyte ok; I realize using jsf framework is different than perhaps doing the demo project described in this issue. ken.frank@sun.com
Maybe I don't understand this issue but why was it reported against the web project? Web project is responsible for the project infrastructure, for building and deploying the application, not for the runtime. If you enter Japanese text in a running application and it is not displayed correctly, I would say it is a problem with defined encoding in the web page or with the browser but not web project problem. Did I miss something?
As far as it also happens with IE it doesn't depend on the browser. May be the problem is in the transfer of input data from jsp page. What type of subcomponents will be the best for it?
This is not NetBeans issue - the fact that JA text is not properly shown is because tutorial code is basic and simply does not handle that. I'm not expert in area of JSP encoding, but after playing a bit with the test case you provided and googling the issue I found this thread worth reading: <http://www.theserverside.com/discussions/thread.tss?thread_id=28944>. Applying advice given by BrandonM in <http://www.theserverside.com/discussions/thread.tss?thread_id=28944#213812> fixed the problem.
Could web and other samples that have jsp pages and servlets include such encoding tags in their tutorials or other docs and in sample projects ? the default tags could be utf-8. We have so many users who might want to use other characters than ascii and since no tag defaults to iso-8859-1 means that won't work. But the simple putting in of these defaulttags as an example along with some brief comment could really help. (or applicable servlet code). We could file separate issues if needed - please let me know what iz categories/subcats to use. This could apply to sample projects also included in ide, besides those tutorials on web site. ken.frank@sun.com
Ken, in this case user followed <http://www.netbeans.org/kb/55/quickstart-webapps.html> tutorial so that's the place which could be improved. Re. examples - web comes with 'Servlet Examples' sample project which contains (besides other things) filter/SetCharacterEncodingFilter.java class which perhaps should be used from tutorial and that would make the application run smoothly with non-european charsets. Re. issuezilla comp/subcomp - I have not idea which one is right one. David
Btw. this link is older but explains a lot too: <http://weblogs.java.net/blog/joconner/archive/2005/07/charset_traps.html>