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.
I've downloaded the latest nightly build of GF ESB v2.1 and first three of four tests for TRS sample are failing. All of them return a fault, which look salmost identical in all cases. Below is the output from the first test: <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode xmlns="">SOAP-ENV:Server</faultcode> <faultstring xmlns="">BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP Status-Code 404: Not Found - Not Found&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance</faultstring> <faultactor xmlns="">sun-bpel-engine</faultactor> <detail xmlns=""> <detailText>BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;HTTP Status-Code 404: Not Found - Not Found&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=Airline, portType={http://www.sun.com/javaone/05/AirlineReservationService}AirlineReservationPortType, operation=reserveAirline) BPCOR-6129: Line Number is 204 BPCOR-6130: Activity Name is ReserveAirline Caused by: HTTP Status-Code 404: Not Found - Not Found</detailText> </detail> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
I was testing on Ubuntu 8.04, but heard that similar behavior was seen on windows as well.
tried with the latest nightly GlassFish ESB, Product Version: NetBeans IDE 6.5.1 (Build 200904061800) on Windows XP: all results are green.
The real cause of this particular issue was in my not knowing that the EJB module in TRS should be deployed separately. I expected it to be part of the composite application and hence be deployed automatically. This was not the case. The funny thing is that even if I add it to the composite application and deploy, the tests fail. All tests pass if and only if I deploy the EJB module separately.