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.

Bug 111954 - I18N - invalid mbyte in newly created BPEL process
Summary: I18N - invalid mbyte in newly created BPEL process
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 6.x
Hardware: All Solaris
: P2 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords: I18N
Depends on: 97872
Blocks:
  Show dependency tree
 
Reported: 2007-08-03 20:36 UTC by kaa
Modified: 2007-08-22 19:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
image (102.35 KB, image/jpeg)
2007-08-03 20:37 UTC, kaa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kaa 2007-08-03 20:36:21 UTC
build 0727, Solaris 10 with ja locale non utf-8

1. Create BPEL Module
2. Create BPEL process using wizard, using ja chars in the process name

There are invalid mbyte in navigator, design and properties windows.
When adding new components, etc with mbyte, they looks ok.
Comment 1 kaa 2007-08-03 20:37:13 UTC
Created attachment 46139 [details]
image
Comment 2 kaa 2007-08-03 20:56:27 UTC
I didn't change project encoding property.
Comment 3 Nikita Krjukov 2007-08-08 16:52:57 UTC
Could you clarify what is the "mbyte"? 
I can't understand what is wrong with the navigator from the attached picture. 
Comment 4 Nikita Krjukov 2007-08-14 15:36:39 UTC
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
Comment 5 Ken Frank 2007-08-14 16:08:22 UTC
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.
(developers who implemented the file encoding handling for jsp and html files can tell more on this)

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.

But this does seem to be a valid issue.

and if those 2 issues below are needed, please add to comments in those issues.

ken.frank@sun.com
Comment 6 Nikita Krjukov 2007-08-17 13:21:33 UTC
I can't check the issue on Solaris but I hope it is fixed. 
The changes in code are related to the issue #111955 
Please, reopen the issue if necessary.
Comment 7 kaa 2007-08-22 19:31:28 UTC
verified: build 0819, ja non utf-8, Solaris10