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.
Was trying out bluprints - 1 each of the 3 sample project types - ajax, web, web services - running in asian locale. for the one with web services, used the doc-attachment - building it gave error in attachment in output window if project lived in a dir path that had mbyte as part of it, but if project lived in dirpath without mbyte, it built ok. the error message in output window refers to that an encoding definition might be missing. messages.log has nothing related to this.
Created attachment 28049 [details] output window info
Hi Ken, we discussed this in Prague and we think that this could be waived for NB 5.0. Would you agree?
Agree it can be waived if can be release noted - something like user should not use mbyte in project dir path ? Since these are samples and thus visible to user, think that would be helpful. ken.frank@sun.com
Could someone in dev make sure that for regular ejb/j2ee project with web service, similar to this, that path with mbyte is really ok; it seemed that way in some testing but would like to be sure. ken.frank@sun.com
I tested several things and found out:- o endpoint There's a bug in bpcatalog(java.net) which is not handling this case. This is easy to fix by just adding encoding="utf-8" when copying the wscompile config file. o client We also have the same problem in the client side. It's not blueprints specific. To reproduce, do:- 1. Projectize StringWebService from BluePrints solutions catalog and "Run" it. 2. Create new project (web app) under the project location contains multi byte characters 3. Do "New->Web Service Client" 4. Set "http://localhost:8080/webservice/StringPurchaseOrderService?WSDL" in "WSDL URL", "Retrive WSDL" 5. Enter a package name and hit "finish" Then, you'll see the same error. The problem is, generated nbproject/build-impl.xml has the code something like:- ==== <copy filtering="on" tofile="${build.generated.dir}/wsclient/wsdl/StringPurchaseOrderService-config.xml" file="${web.docbase.dir}/WEB-INF/wsdl/StringPurchaseOrderService-config.xml"> <filterset> <filter value="${config_target}" token="CONFIG_ABSOLUTE_PATH"/> </filterset> </copy> ==== The <copy> task must have encoding="UTF-8" as well. I'll fix the endpoint side, and reassign to the appropriate party once it's finished.
Fixed in the trunk. ============= Checking in external/blueprints-solutions-catalog.zip; /cvs/j2ee/external/blueprints-solutions-catalog.zip,v <-- blueprints-solutions-catalog.zip new revision: 1.5; previous revision: 1.4 done ============= Again, this check-in only fixes the WS endpoing issue.
mark this as fixed. - the issue on the client side should be reported separately.
this fix is OK for me on the bp solution side.
integrated in release50.
Ken, can you verify the fix? Thanks, Petr
Build 200601042030 I tried to create (and run) all Java BluePrintSolutions, everything went well, except following two: J2EE Client of Document Oriented Services and Standalone Client of Document Oriented Services (see attachments - output window) Is this related to issue #70966?
Created attachment 28196 [details] J2EE Client of Document Oriented Services
Created attachment 28197 [details] Standalone Client of Document Oriented Services
Both clients are ok with the latest fix of 70966, but there's a minor bug in stand alone swing client, which may cause the "Run" error. I checked in the fix to the trunk.
verified