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.
Summary: | I18N - Using Mbyte in BPEL Project Name results in incorrect mbyte display in editor screens | ||
---|---|---|---|
Product: | soa | Reporter: | sunlit <sunlit> |
Component: | BPEL Project | Assignee: | Sreenivasan Genipudi <sreenigv> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | kfrank, praveensavur |
Priority: | P2 | Keywords: | I18N |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
invalid mbyte
screenshot screenshot screenshot |
Description
sunlit
2006-06-23 13:04:58 UTC
Created attachment 31334 [details]
invalid mbyte
Some of this may not be a problem now that project wizards are being simplified. Maybe some problem reamins however. Also, similar problem may be in BPEL file wizard. That is why I am cc'ing praveen savur I am not able to reproduce this problem in the recent enterprise pack build. Adding "\" or "/" is prohibited to the project name. build 0509, the issue is still visible - steps to reproduce: open bundled travel reservation, choose new - BPEL process, and name it using mbyte characters (ja charachers, ja locale in my case). Open this file for editing - observe invalid mbyte dispayed in various places, e.g., visual editor, properties editor, navigator. Please see gifs attached. Created attachment 33824 [details]
screenshot
Created attachment 33825 [details]
screenshot
Created attachment 33826 [details]
screenshot
Cause: new bpel file is created using local character encoding (e.g. for Russia
it is Windows-1251). Then this file is read using UTF-8 character encoding.
Here we loose local characters.
It seems that problem is in class
org.netbeans.modules.bpel.core.wizard.NewBpelFileIterator, near line 244.
Probably, this bug can be fixed just by replacing stings
line 243> OutputStream outputStream = new FileOutputStream(file);
line 244> PrintWriter writer = new PrintWriter(outputStream);
with string
> PrintWriter writer = new PrintWriter(file, "UTF-8");
After this change bpel wizard and bpel designer will read
and write bpel file in same encoding (UTF-8).
That was a correct assumption. Fixed. verified in 1013 |