*** Is a separate issue needed for each project type under soa - ie
bpel, iep, compapp, sql, workflow, xslt ? If so, please file under
each of those subcats and then this one could be closed or used as an umbrella
issue for all under enterprise.
The new SPI FileEncodingQueryImplementation allows IDE components like editor,
search, etc to handle correctly encoding of files. The implementation of
FileEncodingQueryImplementation should be provided in the project's lookup.
The typical implementation of this query uses a project property with encoding
and returns a Charset.forName (evaluator.getProperty(name_of_encoding_property).
The project should also provide a control in the project's customizer to allow
user to change the encoding of the project.
Issues have been filed on all project types about this.
all the project types, if they are not derived from others, should
implement FileEncodingQuery. Also data types (DataObjects)
which have some special encoding requirements, like properties, should
For more info see issue: #42638
Tomas Zezula could tell you more about this.
*** Please also add to umbrella task on this item, 97848 , the bug id of this
one and others that need to be filed under enterprise.
Will this be done for nb6 ? all other project types have implemented or are finishing implementation
of it thus to be consistent for users, it seems that enterprise projects would need to do it also.
Am assuming this issue covers all enterprise project types and file types - but if separate issue
needed for each soa/bpel project and/or file type, please file those and use this as umbrella issue.
Ken, I've removed 109434 from dependency list since it's IEP issue and IEP is not partof NB 6.0 anymore
Update: For NB6: compapp, bpel, xslt and sql projects need to be fixed
currently compapp, bpel and xslt have been fixed so far.
All related tickets are now fixed.