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.
ja locale solaris pseudo localized utf8 and euc-jp project encodings 10/10 build 2 parts to this issue: A. Steps: a) Establish connection with sample db. (Services tab) b) Create BPEL Module. c) Open file new wizard: SOA -> WSDL From Database. d) Select a table from db. e) Follow the wizard until select datasource and table objects panel appears choose a table and add it f) press next Exception appears - see first attachement. and sometimes cannot keep going in the wizard, need to cancel it. If you can keep going, it does not show the select operation specific attributes panel but goes to the enter jndi pane also and there is another exception as well. in this case, the .wsdl file is empty, which is not the case if this happens in en locale or in another loale without pseudo localization. the xsd file looks like it might be ok compared to english one but not sure howo to tell about this. B. If the soa1/modules/locale/org-netbeans-modules-jdbcwizard_ja.jar is removed, then the first exception does not happen, but the second one does and again, the wsdl file is empty. This second exception attached has as part of it: WSDLException: faultCode=OTHER_ERROR: WSDLException: faultCode=CONFIGURATION_ERROR: Unsupported Java encoding for writing wsdl file: 'EUC_JP_Solaris' nb view of encoding user is in is eucJP_open project encodings used are euc-jp (which is the default encoding of solaris ja locale) and also utf-8. I don't recall seeing such a message about unsupported java encoding before. C. attached also is the pseudo localized jar file - perhaps there is something translated that should not be (either that is obvious not to be or that is ok to translate and some code is doing a comparison assuming english value) D. for the second exception, which happens also when the jar is removed, it might mean some other jar has a message not to be translated that is not skipped or that assumes english value in comparison or it could be completely unrelated. E. in progress now is the seeding of various bpel and wsdl xml based files with the project encoding vs utf-8, but I don't think this is related to that, but perhaps there is some other project or file encoding assumptions happening. F. this part from message log is same for english or ja locales so I don't think this is part of the problems here: \276\360\312\363 [org.netbeans.modules.jdbcwizard.builder.model.DerbyQueryGenerator]: Ge nerated Insert Query insert into "APP"."CUSTOMER" ("PHONE","STATE","NAME","ZIP","ADDRESS LINE1","ADDRESSLINE2","CREDIT_LIMIT","EMAIL","CUSTOMER_ID","CITY","FAX","DISCOUNT_CODE") values (?,?,?,?,?,?,?,?,?,?,?,?) \276\360\312\363 [org.netbeans.modules.jdbcwizard.builder.model.DerbyQueryGenerator]: Ge nerated Update Query update "APP"."CUSTOMER" set "CUSTOMER"."PHONE" = ?,"CUSTOMER"."STA TE" = ?,"CUSTOMER"."NAME" = ?,"CUSTOMER"."ZIP" = ?,"CUSTOMER"."ADDRESSLINE1" = ?,"CU STOMER"."ADDRESSLINE2" = ?,"CUSTOMER"."CREDIT_LIMIT" = ?,"CUSTOMER"."EMAIL" = ?,"CUST OMER"."CUSTOMER_ID" = ?,"CUSTOMER"."CITY" = ?,"CUSTOMER"."FAX" = ?,"CUSTOMER"."DISCOU NT_CODE" = ? \276\360\312\363 [org.netbeans.modules.jdbcwizard.builder.model.DerbyQueryGenerator]: Ge nerated Delete Query delete from "APP"."CUSTOMER" \276\360\312\363 [org.netbeans.modules.jdbcwizard.builder.model.DerbyQueryGenerator]: Ge nerated Find Query select "PHONE","STATE","NAME","ZIP","ADDRESSLINE1","ADDRESSLINE2","CR EDIT_LIMIT","EMAIL","CUSTOMER_ID","CITY","FAX","DISCOUNT_CODE" from "APP"."CUSTOMER" \276\360\312\363 [org.netbeans.modules.jdbcwizard.builder.model.DerbyQueryGenerator]: Ge nerated Pool Query select "PHONE","STATE","NAME","ZIP","ADDRESSLINE1","ADDRESSLINE2","CR EDIT_LIMIT","EMAIL","CUSTOMER_ID","CITY","FAX","DISCOUNT_CODE" from "APP"."CUSTOMER"
Created attachment 50870 [details] exception
Created attachment 50871 [details] exception
Created attachment 50872 [details] pseudo localized jar
Venkat, please reaasign to correct person.
comments to the case A: build 1010, XP.ja_JP When I closed the exception dialog (after adding a table from database) I could proceed in wizard. WSDL doc was created.
Pls look into this.
Not able to Reproduce the issue. Verified in the build NetBeans IDE Dev (Build 071015).
am reopening until know that you are using pseudo localized nb and running in other locale, and following the steps noted. if not, then you won't see the problem. ken.frank@sun.com
assigned engineer mentioned that they have not run in ja locale and this is needed to work with the issue, so the reopening seems to be valid. ken.frank@sun.com
checked-in changes for locale
am reopening I am assuming that there is nothing in the bundle file of attached jar that should not be translated and I have not removed it. I can go thru the wizard now , but as reported below, the wsdl file is empty and there is exception from the 2nd attached exception. the project encoding is euc-jp which is valid since am in solaris ja locale, and that is encoding for it, although any encoding should be allowed. but even if project encoding is utf-8, the same exception appears since exception is probably referring to some view of locale user is running in but something is not recognizing that value as valid.
please add info below to the issue and clarify about your comments in this mail " Regarding the 118769, I could create the WSDL with all the supported encodings I m just giving x-Big5-Solaris on my machine as a sample which is equivalent to the " EUC_JP_Solaris" mentioned in the bug." "create wsdl with all supported encodings" - there are a lot of project encodings - were all of them tried ? also, Big5 is not same as euc-jp solaris; its a different locale also, are you using a pseudo localized jdbc jar file ? if not then you are not really emulating the situation in which the issue was filed. ken.frank@sun.com
Verified with the encodings that are available with the Windows-XP version and the WSDL is generating with out exceptions. Also verified running the NetBeans in the ja (Japanese version) and tried with the encodings. I could get the WSDL without exception.
as mentioned, if you are not emulating the situation a real user using translated nb would do, why is this issue being re-resolved; that is, using pseudo localized jar files installed in correct locations ? ken.frank@sun.com
I am reopening until dev has operated in real environment using pseudolocalized that has been sent and being in real ja locale, not using --locale option ken.frank@sun.com
Works for me in even without --locale option with the localization bundle.
is not translating a certain bundle file in jdbc jar part of the fix ? I see a bundle in the kl10n kit that says do not translate but not in product jar of 1030 -- is this some thing new ? ken.frank@sun.com
1. solaris ja locale - get the exception whether the project has utf-8 or euc-jp project encoding exception, as shown in bug starts as WSDLException: faultCode=OTHER_ERROR: WSDLException: faultCode=CONFIGURATION_ERROR: Unsupported Java encoding for writing wsdl file: 'EUC_JP_Solaris'.: at org.netbeans.modules.jdbcwizard.builder.wsdl.WSDLGenerator.writeWsdl(WSDLGenerator.java:960) at org.netbeans.modules.jdbcwizard.builder.wsdl.WSDLGenerator.generateWSDL(WSDLGenerator.java:280) at org.netbeans.modules.jdbcwizard.builder.wsdl.GenerateWSDL.execute(GenerateWSDL.java:189) at org.netbeans.modules.jdbcwizard.wizards.JNDINamePanel.storeSettings(JNDINamePanel.java:234) at org.netbeans.modules.jdbcwizard.wizards.JNDINameFinishPanel.storeSettings(JNDINameFinishPanel.java:111) 2. starting in soalris ja_JP.UTF-8 locale, no problems, the wsdl shows ok, no exceptions whether project encoding is utf-8 or euc-jp. seems like there is some parsing or interpretation of EUC_JP_Solaris perhaps. 3. does not seem related to the bundle file in which it states not to translate it; we still need to know why that file is asked not to be translated.
Created attachment 52426 [details] JDBCWSDL gen on Solaris
Created attachment 52427 [details] JDBC WSDL after generation on Solaris
Created attachment 52428 [details] SQL SE WSDL Generation
Created attachment 52429 [details] SQL SE Generated WSDL
WSDLGenerator has been fixed to work for a different locale on any platform.
verified: build 1106. WSDL from DB was created ok without exceptions.