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.
The localization of binding customization annotation should be provided. (1)The annotation can be added to provide grouping of attributes of an binding element; ex: <xs:element name="operation" type="jms:tOperation"> <xs:annotation> <xs:documentation> "operation" indicates a JMS protocol based operation. </xs:documentation> <xs:appinfo> <prop:ElementProperties xmlns:prop="http://xml.netbeans.org/schema/wsdlui/property"> <prop:PropertyGroup name="Common" groupOrder="1" /> <prop:PropertyGroup name="Consumer" groupOrder="2" /> <prop:PropertyGroup name="Provider" groupOrder="3" /> The groups created in property sheet will have names Common,Consumer,Provider. We need to allow this name to be localized. So proposed solution could be like this: Use spi to get optional bundle. use following key format: group name key=<element name>_groupName_displayName (2) create a localized name for a grouped property customizer. The group property customizer is something like element or type chooser. GroupedProperty name key=<element name>_<displayName attribute value of GroupedProperty>_displayName Also for documentation of a grouped property the key could be: GroupedProperty documentation key=<element name>_<displayName attribute value of GroupedProperty>_documentation
As to what gets actually translated, those words/strings will still be in a Bundle.properties file ? (since we dont have xsl or xml files translated) And where in ide are these strings seen; this will help in testing this solution. Finally, can this be made p2 since that is more appropriate for issues about words/strings to translate since its important for user in other locale. ken.frank@sun.com
please clarify about questions in previous comment as this seems like a p2 issue if relates to strings/msgs that will be translatable. ken.frank@sun.com
Localization is supported, if keys are added as follows in the bundle.properties 1. For property category names to be LBL_GRP_$(PropertyGroup.Name) 2. for grouped property the key in the bundle should be LBL_${GroupedProperty.displayName) Added key/value in bundle.properties wherever used.
Thanks for fixing it. please let me know what product jar(s) have these values in which bundle files in each so I can be sure to pseudo localize it ok for our verification. (and in what build the fix that has these new key/values in the bundle files of those jars) ? ken.frank@sun.com
Its still not clear what the fix is and how its done as to the bundle files - see original quesitons below, so it can't be verified yet. please provide that information. ken.frank@sun.com
Created attachment 51933 [details] JMS Operation property sheet
Andrey, here are the msgs that need to be verified org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Basic=Basic org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_JNDI=JNDI org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Common=Common org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Consumer=Consumer org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Provider=Provider org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Message=Message org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_Encoding=Encoding org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_ReadWriteMessageHeaders=Read-Write Message Headers org-netbeans-modules-wsdlextensions-jms/Bundle.properties.1:LBL_GRP_ReadOnlyMessageHeaders=Read-Only Message Headers ken.frank@sun.com
There are two use cases here: 1. On the property sheet of any extensibility elements, I18N of category names in a property sheet. 2. I18N of property names, which do not correspond to the schema element names. In some case, two or more elements are combined if they are mutually exclusive. For first case, the steps are as follows: (See screen shot "JMS Operation property sheet") 1. Create a new WSDL Document 2. In the concrete configuration pane, select the JMS protocol. 3. Under Bindings, click on jms:operation, in the properties see category names such as Common, Consumer etc. For second case, the steps are as follows: (See screen shot "bpel Property properties sheet") 1. Right click on Extensibility Elements folder. 2. Add Property 3. In the property sheet, see "Element or Type" or add a property alias, in property sheet see "Element or Type or Message part"
Created attachment 51940 [details] bpel Property property sheet
Skini, thanks for the information and gifs. Andrey, it looks ok to me in following the steps but please verify also since you are the expert in this area. ken.frank@sun.com
verified: messages from steps are looking ok with build 1106, ja_JP.