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.
There is an error message saying that 'Failed node parse; reason=Trailing junk after last child' while Decoding an XML schema(attached: test22.xsd) which has three levels in structure, has group, delimited and fixed length nodes. And it has CR,LF as delimiters. Please find the test22.xsd and screenshots in the attachment. NOTE: This is a platform specific bug. The same Schema is Decoding and Encoding fine in WinXP SP2/SP3. But, this abnormal behavior is occuring in RetHat Linux 4 AS64. Details: Build : 20081012-0703 OS : Win XP SP2/SP3 = PASS RedHat Linux 4 AS64 = FAIL
Created attachment 71747 [details] Error Msg - screenshot
Created attachment 71748 [details] Exception_inDetail - file
Created attachment 71749 [details] XML Schema file
Created attachment 71750 [details] decoded_expected .xml file
Created attachment 71751 [details] input file
This abnormal behavior is occuring in Mac OS also... Verified in Mac Leopard Intel 32 bit using 20081014-1633 build.
This same abnormal behavior is occuring in Solaris 10 Sparc also...
1. Can you pl. attach your attachment as image/JPEG. Right now, it opens as plain text. 2. Also what do you mean by "decoding a schema"? 3. It'll help if you give us a step-by-step instruction to reproduce the issue, as I may not be familiar with what you're saying.
Created attachment 72173 [details] re-sending Error.JPG file
Please find the screen-shot (.jpg) file in the attachment(Error_msg.JPG) Decoding an XML Schema means, Decoding Serialized Custom Data Format(input file) to Normalized XML Data(Decoded output file) STEPS to reproduce: 1) Open Netbeans IDE 2) Create a BPEL Module project 3) Create/Copy the attached XML Schema(test22.xsd)...(this schema should be placed under project-name/process tree) 4) right-click on the Schema, choose Encoding -> Test 5) make sure, 'Decoding' option is checked(since we are going to test Decoding function) 6) Browse the input file(test22_decode_input.txt) and enter the Decoded output file name in the wizard. 7) click on 'Process' button. - note that, there is an exception while decoding. Please let me know, if you are not clear the steps provided.
Sorry, I mistakenly updated this one. This one should go to enterprise. I'm not sure who owns encoder/decoder stuff.
Again, this sounds like the OS has changed your input txt file on the \r\n. Please set debug level to FINE or FINER or FINEST, and provide the encoding log file. In the log, please look for the following line (usually the first line): Decode from input byte array, total bytes=91, ..... If you see total bytes is not 91, that means your input data is corrupted.
To make sure you have valid input data, use an editor to open your input file, view the file in "BINARY" mode, you should see "0D 0A" together as shown in attached screen shot. If you don't see "0D 0A" bytes, then your input data is corrupted.
Created attachment 73336 [details] view input data in binary mode to ensure 0D 0A bytes together
verified the scenario by copying the input data in BINARY mode. Observed that the Decoding process is working fine. My Observation is, Verified in Solaris Sparc During normal copy - the log says total bytes=89 (input data corrupted) - decode fails During BINARY mode copy - total bytes=91 Hence it is an Invalid bug.
verified the scenario by copying the input data in BINARY mode. Observed that the Decoding process is working fine. My Observation is, Verified in Solaris Sparc During normal copy - the log says total bytes=89 (input data corrupted) - decode fails During BINARY mode copy - total bytes=91 Closing the ticket since it is an Invalid bug.