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.
nb6 has new project encoding property and now enterprise modules have or are in progress of implementing for that. but samples are from previous release, and it was advised to have them regenerated as nb6 projects; issues have been filed on other sample components as well. Tomas Zezula can tell you more about it. ALSO, creating enterprise sample or blueprint, it actually causes the global project encoding value to be set to the utf-8 encoding that the sample project is created with -- this is a problem as its not supposed to change this value unless user does - and it causes all new projects after that to use utf-8 -- thus please fix this now even if wont regenerate the samples until later. (other samples that have not been regeneaated use utf-8 or system locale now instead of global value of enc, but they dont cause the global value to be changed)
Regenerated SOA samples.
reopening using 0912 build; running in solaris ja locale BUT the project encoding is gb18030, so expectation is that any new created projects would use that encoding. the encoding properties of the ejb and web app created when create enterprise sample, are that of x-eucJP-OPEN, which is the encoding of the locale the user is in, not the current global project encoding value. creating a regular ejb, the project encoding is that of gb18030, the current project encoding value. ken.frank@sun.com
last comment is about enterprise samples category like annotation override. but also the soa samples still have same problem as in original description. QUESTION - should problem with the enterprise category be filed in some other iz category, and this issue is just for soa samples ? even if this is just for soa samples, the reopening is valid since original problem still happens. ken.frank@sun.com
Removed source.encoding=UTF-8 from project.properties.
still not fixed in 0927 - uses encoding of locale vs feq project encoding value (and also it changes global feq value for new projects to be its encoding, which also is not what user wants. please verify using actual nb before resolving this - create some initial java project for example, that is utf-8 project encoding, and look at is enc property; then create the soa sample, and you'll see, at least on solaris, its proj encoding is euc-jp instead of utf-8. ken.frank@sun.com
Default value UTF-8 was removed from project properties in SOA samples. The samples is BPEL project with encoding functionality, so they have the same behavior. The encoding functionality (implementation) comes from comp app project and bug is in comp app. Reassign...
when i create bpel module project, the project encoding does seem to follow that of the current global encoding - ie if i change some other project encoding to Big5, then create bpel project, its enc is big 5, and if i change that proj encoding to something else, the next new project of any type besides the samples, is created with that new encoding property. but the behavior of the samples was not like this. ken.frank@sun.com
changing summary to indicate this is about soa sample projects. ken.frank@sun.con
Jun, do you agree with Vladimir's evaluation. If not please reassign to more appropriate category.
please fix this very soon;as it makes the feq and project encoding not valid and user wont know about it. ken.frank@sun.com
IDE: [10/9/07 6:39 PM] Committing "JbiProjectProperties.java" started Checking in JbiProjectProperties.java; /cvs/enterprise/compapp/projectjbi/src/org/netbeans/modules/compapp/projects/jbi/ui/customizer/JbiProjectProperties.java,v <-- JbiProjectProperties.java new revision: 1.14; previous revision: 1.13 done IDE: [10/9/07 6:39 PM] Committing "JbiProjectProperties.java" finished
verified: build 1016, XP.ja_JP: UTF-8 Created Java app, then changed its encoding to win-31j Enterprise samples are using this value.
Andrey, did you also verify that when changing the encoding of the sample project, that new soa or j2se projects, for example, use the encoding that was changed to in the soa sample ? ken.frank@sun.com
rechecked again with 1109, ctreated Ent Samples then changed encoding: SOA and Enterprise projects are using it.