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.

Bug 81118 - output.xml is empty
Summary: output.xml is empty
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: JBI Test Driver (show other bugs)
Version: 5.x
Hardware: PC All
: P1 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on: 80779
Blocks:
  Show dependency tree
 
Reported: 2006-07-25 23:10 UTC by Sherry Barkodar
Modified: 2006-08-04 23:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
SynchronousSample.zip is added (45.80 KB, application/octet-stream)
2006-07-25 23:11 UTC, Sherry Barkodar 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sherry Barkodar 2006-07-25 23:10:32 UTC 
created the SynchronousSample from scratch the output.xml is empty.
Comment 1 Sherry Barkodar 2006-07-25 23:11:26 UTC 
Created attachment 32201 [details]
SynchronousSample.zip is added
Comment 2 Jeff Stein 2006-07-25 23:39:37 UTC 
While doing the SynchronousSample tutorial, I ran into the same problem as 
Sherry. A java.io.FileNotFoundException occurs, and the Output.xml file is 
empty.
Comment 3 _ hong_lin 2006-07-25 23:41:49 UTC 
See also IZ 80779
Comment 4 Jun Qian 2006-07-26 21:57:26 UTC 
Praveen, it looks like the default testcase is not created when you
regenerate/repackage the sample project. Is that an oversight or is that because
you had this problem that you reported in 81018? 

FYI, the problem you reported in 81018 is fixed now.
Comment 5 Praveen Savur 2006-07-26 22:14:13 UTC 
 Jun, This bug is not related to the bundled/packaged Synchronous Sample.

This is related to a tutorial which lists all steps the user needs to follow to
build a synchronous sample from 'scratch'. Thats when this FileNotFoundException
is being reported.

 I am changing category back to jbi test driver.
Comment 6 Jun Qian 2006-07-27 00:25:58 UTC 
This is related to the problem Praveen reported in 81018, which was fixed on 7/25.
Comment 7 Sherry Barkodar 2006-07-28 17:04:47 UTC 
 nightly build 060727_3
This bug is not fixed and I don't think fixing bug 81018 has anything to do with
empty output file.
Create a simple hellowworld from scratch.
Create a simple test.
Run the test. It fails giving the following msg:
Test NewTestcase1\Concurrent.properties Failed.
java.lang.RuntimeException: unable to parse WSDL 1.1 wrapper
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.constructJBIMessage(JBIMessageImpl.java:310)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.<init>(JBIMessageImpl.java:124)
        at com.sun.jbi.engine.bpel.EngineHelper.getInMessage(EngineHelper.java:603)
        at com.sun.jbi.engine.bpel.EngineHelper.getInMessage(EngineHelper.java:519)
        at
com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:416)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:229)
Caused by: java.lang.NullPointerException
        at
com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.importNode(CoreDocumentImpl.java:1478)
        at
com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.importNode(CoreDocumentImpl.java:1444)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.constructJBIMessage(JBIMessageImpl.java:297)
        ... 5 more
|#]
caught exception while processing message
java.lang.RuntimeException: unable to parse WSDL 1.1 wrapper
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.constructJBIMessage(JBIMessageImpl.java:310)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.<init>(JBIMessageImpl.java:124)
        at com.sun.jbi.engine.bpel.EngineHelper.getInMessage(EngineHelper.java:603)
        at com.sun.jbi.engine.bpel.EngineHelper.getInMessage(EngineHelper.java:519)
        at
com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:416)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:229)
Caused by: java.lang.NullPointerException
        at
com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.importNode(CoreDocumentImpl.java:1478)
        at
com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.importNode(CoreDocumentImpl.java:1444)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.JBIMessageImpl.constructJBIMessage(JBIMessageImpl.java:297)
        ... 5 more
|#]
Comment 8 Sherry Barkodar 2006-07-28 19:24:35 UTC 
I tried installer build 060728 and the output looks Ok. Hong, please after you
are done with your testing with  060728 verify this bug.
Comment 9 Jun Qian 2006-07-28 19:34:16 UTC 
I just tried the 060728 build too without any problem. Looks like the BPEL
runtime bug you reported has been fixed.
Comment 10 lchang 2006-08-04 23:58:05 UTC 
synchronous sample is fine now, output.xml is not empty, and you can create it 
from scratch fine.