Community
Participate
Working Groups
OS : RHEL 3.1 Must fix Severity 2: Build date: 20050720 Blocking: NO Language: CHS Bitmap Location: Z:\defects\zh\WTP_26003150.jpg Tester Name: Denver Dang Problem Description: 1. Select a WSDL file in the Project Navigator view. 2. Right-click the WSDL file, and select Validate WSDL file. 3. Validation failed, problem box appear on the bottom of screen A large part of message are not translated.
Created attachment 25219 [details] WTP_26003150.jpg
Up the severity from minor to major. This bug has been identified as must fix by tester.
The warning messages highlighted in the screenshot are from the JDT, not from the WSDL validator. These messages are not related to the WSDL file in question. The error right above these in the screenshot clearly shows that it is generated for the WSDL file. These messages are for some other resource(s) that are located in the JavaSource directory. You can set what error/warning messages the problems view should display by selecting filters.
Cam, should this be reopened or do we expect Java compiler warnings to not be translated?
Thank you Steven for catching this. Per the WTP request, bug has been rerouted to the JDT team. Please let us know if these error/warning messages are to be translated or not (see screen capture).
Moving to JDT/Core since error messages are generated by the compiler.
Cam: as all compiler diagnostics, these have to be translated. All these new messages are inside the same message catalog as in the past. i.e. /org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/problem/messages.properties This defect rather belongs to you than to us. Could you pls adopt it ?
Side question Cam-Thu: While you are looking at re-translating the compiler error msg catalog for 3.1.1, would you tolerate one more edit ? I would like to rephrase messages (543) and (544) into: 543 = Bound mismatch: The generic method {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}> 544 = Bound mismatch: The generic constructor {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}>
It's not a problem. When will you be able to give us the new English file ? Can it be this week ?
Thank you for your input. Bug closed as invalid. Problem verified by Chinese and Japanese testers. Concerning the update of messages 543 and 544, please make sure the updates are in this week's build. Thank you.
This week's build already occurred, however the file is released into the 3.1 maintenance branch. Also note that the edit also touched another 2 related messages: 850 & 855. So the following 4 messages got updated. 543 = Bound mismatch: The generic method {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}> 544 = Bound mismatch: The generic constructor {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}> 850 = Bound mismatch: The generic method {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}> 855 = Bound mismatch: The generic constructor {0}({1}) of type {2} is not applicable for the arguments ({3}). The inferred type {4} is not a valid substitute for the bounded parameter <{5} extends {6}>
To clarify, the build occurred prior to releasing these changes (I was holding them back until confirmation)
If you let me know the Integration build number, I can get it from eclipse.org.
