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.
See umbrella ticket #100312
This ticket semi-depends on #109429
Vitaly will fix it with xslt project.
what about encoding handling of .bpel files -part of the encoding work is to make sure about encoding handling for file types as well; for example in progress or done is file encoding handling for jsp/html/xml/properties files. these would be separate issues if needed. I don't know if its needed for .bpel since when click on src tab, its in xml format -- so is it really an xml file ? what about .wsdl, are they really an xml file ? and the sql project .sql file ? I think it is a text file - I don't know if the running of it uses the same api or functionality of other db queries created in nb - nor do I know how in general the db query is handled - I'll ask db team. ken.frank@sun.com
Fixed.
Ken If I'm right understand you mean e.g. next scenario: if project encoding properties is UTF-8, but xml file inside these project has encoding="windows-1251" then this xml file should be stored with encoding "windows-1251" If so then Ken please fill issues against encoding support for different type of files. It would be nice to have one umbrella issue for it.
Ken If I'm right understand you mean e.g. next scenario: if project encoding properties is UTF-8, but xml file inside these project has encoding="windows-1251" then this xml file should be stored with encoding "windows-1251" --> I'm not sure of the answer since the xml impelementation of the feq has not been completed - see issues 97872 and 107911 - from some info from developer on xml files already created: if file encoding tag exists, it will be used instead of project encoding - file enc has higher priority what if no enc tag in the file or user removes it ? For xml files the encoding can be defined according specification also in the first two bytes of the file stream. You are not able to see these bytes in the editor, but the encoding is defined in the the file itself. Of course the encoding can be also defined in the <?xml encoding="xxx"?> processing instruction. So there two ways how the encoding in xml files can be stored. If the xml file doesn't contain any encoding than the project encoding should be used. But i'm not 100% sure, because I think that the W3C xml specification defines and default encoding as well. question - if a bpel or wsdl is just another xml file, then perhaps no additional issue is needed ? but if your modules need to change code to work with that new behavior, then it might need issues ? one thing is we dont know if/when the 2 xml issues mentioned will be fixed. also, if you need sep issues, please list on what file types they should be on, ie bpel, wsdl, sql, etc . ken.frank@sun.com
am using build 0727 - is this fix in that one ? I am not seeing the ok behavior for this or for the xslt project - instead it is using the encoding of the locale the user is in as default; whether its the first project created in the session or being created after some other non soa project has changed encoding to something other than utf-8, which is the default. as to the encoding of xml files vs project encoding - the xml feq issues are not done yet, 97872 and 107911; so things could change in your projects use of it when that happens - can you talk with owners of those bugs to see if your team needs to do anything about it once they are fixed (and to see if sep issues are needed in enterprise) ken.frank@sun.com
reopening - the global project encoding is not being used when create the project - the encoding of the locale user is in is being used; and when changing the project encoding of this project, it does not cause next created project like j2se project, to use that encoding. ken.frank@sun.com
Fixed in trunk: /cvs/enterprise/bpel/project/src/org/netbeans/modules/bpel/project/BpelproProject.java,v <-- BpelproProject.java new revision: 1.18; previous revision: 1.17 /cvs/enterprise/bpel/project/src/org/netbeans/modules/bpel/project/BpelproProjectGenerator.java,v <-- BpelproProjectGenerator.java new revision: 1.12; previous revision: 1.11
verified: build 0812, Bpel Module has project encoding property in project properties.