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.
Original status: 3-Accepted; Suggested Status: NEW These items should be added to the Keywords: RELNOTE Description: Tested build: Build 060120 The project that uses a data source with multi byte name cannot be reployed to a remote server. in non UTF-8 locale. When the same project is reployed in the bundled AS, this problem does not occur. 1. Run IDE in non UTF-8 locale (ex. ja) 2. Add a remote server 3. Create a new project 4. Create a data source with multi byte name 5. Create the page using the data souorce created in the step 3 (6367978 was fixed in Thresher.) 6. Run to the remote server added in the step 2 At this point, the following error occurs in the Output window. [Fatal Error] :10:24: Invalid byte 1 of 1-byte UTF-8 sequence. Deployment error: file handling issues. See the server log file for details. Exception=Deployment error: file handling issues. See the server log file for details. Deployment error: file handling issues. See the server log file for details. at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198) at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeTarget(Project.java:1214) at org.apache.tools.ant.Project.executeTargets(Project.java:1062) at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234) at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125) Caused by: java.lang.IllegalStateException: file handling issues at org.netbeans.modules.j2ee.sun.share.SunDeploymentManager.getInternalPlanFile(SunDeploymentManager.java:251) at org.netbeans.modules.j2ee.sun.share.SunDeploymentManager.distribute(SunDeploymentManager.java:350) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:604) at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:188) ... 10 more Caused by: java.io.IOException: plan file issue at org.netbeans.modules.j2ee.sun.share.plan.Util.giveUp(Util.java:164) at org.netbeans.modules.j2ee.sun.share.plan.Util.convert(Util.java:143) at org.netbeans.modules.j2ee.sun.share.SunDeploymentManager.getInternalPlanFile(SunDeploymentManager.java:244) ... 13 more Caused by: org.netbeans.modules.schema2beans.Schema2BeansRuntimeException: Failed to create the XML-DOM Dcument. Check your XML to make sure it is correct. Invalid byte 1 of 1-byte UTF-8 sequence. at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:381) at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:325) at org.netbeans.modules.j2ee.sun.share.plan.Util.convert(Util.java:134) ... 14 more Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct. Invalid byte 1 of 1-byte UTF-8 sequence. at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:422) at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:378) ... 16 more Caused by: org.xml.sax.SAXParseException: Invalid byte 1 of 1-byte UTF-8 sequence. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:418) ... 17 more C:\Documents and Settings\ohsumi\My Documents\Creator\Projects\sanitywin2k\nbproject\build-impl.xml:471: Deployment error: file handling issues. See the server log file for details. BUILD FAILED (total time: 9 seconds) I have attached some log files with ja messages. If you need to localize the log files, please let me know. Evaluation: Yes, there might still be some issue. That needs to looked at after the NB migration. Workaround: Not use multi byte to a data source name in non UTF-8. *** (#1 of 1): [ UNSAVED ] xxx@xxxx
It's fixed in NetBeans 6.0.
reproducible: build 1010, ja_JP the exception exists in output dialog. I used data table with ja char in its name (Derby). Simple WebApp with mbyte name and without db usage was deployed ok.
Reassign to the database team for evaluate.
Could you attach the server log file .
this was filed on earlier releases and taken from bug traq so this might not be valid anymore 1. I created datasource with name with mbyte in it and ran the project and it ran ok solaris, sparc, ja loacle for this experiment used sample javadb dbase that did not have mbyte in name of dbase or table or col name, but that is ok since this issue is about datasource name. 2. also, created different javadb dbase with ascii name for dbase and mbyte for table name and gave it also datasource name with mbyte and project ran ok also. 3. next step will be create javadb with mbyte in dbase, table,col name as well as datasource name, although that is not related to this issue, and also depends on if dbase itself allows mbyte in these areas;javadb does not allow it for dbase name, and perhaps not for table/col names. Am viewing datasource name as that is what is asked for when dropping the db table on table component, having checked prompt for name in the options, and what shows on vwp project under Data Source References. If it has a different definition let me know and can see if that is an issue. Will resolve this as fixed and if further problems, a new nb6 issue can be opened; and if this issue still exists in previous creator, which is where original issue from then the bt issue can be reopened. ken.frank@sun.com
Can't verify. The issue 136822 doesn't fixed at this moment and it blocks the process.
Andrey, can you just use local Derby server? If not, then I can provide you with other databases to use