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 0727, WinXP, ja locale 1. Create BPEL Module 2. Add new BPEL process using ja chars in its name There is an err message. It is shown correct but the Design view is unable to show diagram.
Created attachment 46140 [details] image
using ja_JP err message is always shown on design view for any name of the process/project. using en_US err message appears if mbyte is in the bpel process name.
I didn't change project encoding property.
Now the issue isn't reproduced in case the encoding property of the project is specified to UTF-8 If a wrong encoding is specified, then it can come to problems. Actually, this problems is common for all XML files. See issues #107911 and #97872
its true the 2 issues mentioned below have not been implemented, but things should work ok in any case, since things should fallback to using the project encoding value. and with new project encoding property, users can use other encodings than utf-8; so that it does not show when encoding or locale is utf-8 does not mean its not a problem. Am reopening - but if I have misunderstood, please reclose it. and if those 2 issues below are needed, please add to comments in those issues. ken.frank@sun.com
Now the encoding of the BPEL file is taken not from the project, but from the file itself. So the file is opened well irrespective of what encoding is assigned for the project. I made such modifications for BPEL and WSDL files. Such way I fixed the issue #97872 partly. For other kinds of XML files it's necessary to provide the XmlFileEncodingQueryImpl object in the lookup of the corresponding DataObject.
would the fix handle whats described in 112099 ? if so, could you note about it in that issue so dev assigned to it can see. as to other kinds of xml files, that will need to provide the XmlFileEncodingQueryImpl object in the lookup of the corresponding DataObject. I think that 97872/107911 needs to be fixed first before those other xml files can do it ? or will fix to 97872 be enough so that all project created xml files (vs just user created) will handle the encoding ok as to feq ? if projects still need to do other things even if 97872 is fixed, I guess I need to make a list of other kinds of project specific xml files (vs user created xml files) and then file issue on those project types ken.frank@sun.com
verified: build 0819, ja_JP Bpel doc was shown correctly.
verified
The issue is reproducible: build 0927, ja_JP. In eng locale looks ok.
I can't reproduce the issue with a newer build 071003
I'll try with next build
looks ok: build 1010