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 83126 - InsuranceClaimProject fails to start BPEL component for service assembly
Summary: InsuranceClaimProject fails to start BPEL component for service assembly
Status: VERIFIED WORKSFORME
Alias: None
Product: usersguide
Classification: Unclassified
Component: SOA (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-22 00:40 UTC by lchang
Modified: 2006-09-15 23:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Insurance Claim Project (282.12 KB, application/octet-stream)
2006-08-22 00:42 UTC, lchang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lchang 2006-08-22 00:40:53 UTC
Steps to reproduce:
1.  Open all attached projects in your Netbeans environment
    (InsuranceClaim, InsuranceClaimBpel, InsuranceClaimJbi)
2.  Deploy InsuranceClaim project
3.  Build and deploy InsuranceClaimJbi
4.  Right-click InsuranceClaimJbi and select "Test Project"
5.  Test will pass,  but verify the output "Unable to located activated 
endpoint for service connection"
6.  Go to Sun Java Application Server > JBI > Service Assemblies > 
InsuranceClaimJbi.

Result:  You will notice the the bpel component is stopped and you cannot start 
it or shut it down.
Comment 1 lchang 2006-08-22 00:42:12 UTC
Created attachment 33140 [details]
Insurance Claim Project
Comment 2 Jun Qian 2006-09-06 00:40:28 UTC
I couldn't reproduce the problem with build060905 (both NB EP and App Server).

I had to comment out bpel validation in order to build the project. Other than
that, I didn't have problem running the test.

The test failed as expected because the expected output.xml file is incorrect:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Header/>
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Server</faultcode>
      <faultstring>Unable to located activated endpoint for service connection
{http://j2ee.netbeans.org/wsdl/InsuranceClaim}fileClaimService
FileClaimPortName.</faultstring>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

This is the actual output I got:

<?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/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
  <SOAP-ENV:Header/>
  <SOAP-ENV:Body>
    <fileClaimResponse xmlns="http://insuranceClaim.blueprints.jbi.sun.com/">
      <claimNumber>123456789::Chevrolet_Cavalier_2001::PersonalUse</claimNumber>
    </fileClaimResponse>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

I didn't see problem with Sun Java Application Server > JBI > Service Assemblies
> InsuranceClaimJbi after running the test.
Comment 3 lchang 2006-09-15 23:00:08 UTC
see comment abovew
Comment 4 lchang 2006-09-15 23:08:02 UTC
works for me too