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 81896 - BPEL Variables uses generic and part name
Summary: BPEL Variables uses generic and part name
Status: VERIFIED WORKSFORME
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Alexander Zgursky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-04 02:42 UTC by lchang
Modified: 2006-09-16 00:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
bpel file (1.76 KB, application/octet-stream)
2006-08-04 02:42 UTC, lchang 		Details
wsdl file (4.21 KB, application/octet-stream)
2006-08-04 02:43 UTC, lchang 		Details
input file (257 bytes, application/octet-stream)
2006-08-04 02:43 UTC, lchang 		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 lchang 2006-08-04 02:42:28 UTC 
When you debug the BPEL code, the variables show up with generic jbi:message 
and jbi:part, so you cannot tell which part of the message you are tracking.

Steps to reproduce:
1.  Import the following .bpel and .wsdl into an existing BPEL Module project
2.  create compApp, build and deploy
3.  Enable debugging
4.  Attach debugger.
5.  Run the project with the attached input.
6.  While debugging, open the BPEL Variables window.  

Result:  Under the messagename, all the parts are listed as jbi:part, even 
though they are defined with unique names in the .wsdl

    <message name="RequestMessage">
        <part name="input1" type="xsd:boolean"/>
        <part name="input2" type="xsd:boolean"/>
    </message>
    <message name="ResponseMessage">
        <part name="output1" type="xsd:boolean"/>
        <part name="output2" type="xsd:boolean"/>
        <part name="booleanOutput" type="xsd:boolean"/>
Comment 1 lchang 2006-08-04 02:42:52 UTC 
Created attachment 32521 [details]
bpel file
Comment 2 lchang 2006-08-04 02:43:01 UTC 
Created attachment 32522 [details]
wsdl file
Comment 3 lchang 2006-08-04 02:43:25 UTC 
Created attachment 32523 [details]
input file
Comment 4 Michael Frisino 2006-08-04 07:42:34 UTC 
is this a regression or is this the way it was it TPR3?
Comment 5 lchang 2006-08-04 17:03:31 UTC 
I don't think this is a regression.  This bug was filed as a result of another 
fix in which BPEL Variables were not even displaying before.
Comment 6 Alexander Zgursky 2006-08-09 13:05:55 UTC 
I'm not sure what is the expected behaivor for this bug? Currently, the value
for the message type variable is represented as an xml element - the value's
structure is the structure of the underlying xml. That's why you see jbi:part as
the nodes, and you can always find a part name in the jbi:part Attributes.
Comment 7 lchang 2006-09-15 22:44:17 UTC 
before it was not showing the message names, RequestMessage and 
ResponseMessage, it would only show jbi:part as the root node.

I retested this and the root nodes now show RequestMessage and ResponseMessage 
and jbi:part is a sub-node of that.

Closing as can not reproduce.
Comment 8 lchang 2006-09-16 00:22:40 UTC 
see comment above