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 174787 - Regression: No longer able to obtain the Property Values for Message Parts for TransformMap
Summary: Regression: No longer able to obtain the Property Values for Message Parts f...
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: XSLT (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vitaly Bychkov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-17 00:18 UTC by rpoon
Modified: 2009-12-07 16:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Test Project and Description file (19.73 KB, application/octet-stream)
2009-10-17 00:19 UTC, rpoon
Details
verified screen shot (13.30 KB, application/x-zip-compressed)
2009-12-07 16:52 UTC, rpoon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rpoon 2009-10-17 00:18:19 UTC
Build: 20091016-0734

While creating a new XSLT Service with Service Bridge, the application fails to obtain the property value for message 
part variables.

To recreate:
1) Open the attached project.
2) Create a new XLST Service with ‘Service Bridge’
3) Select ‘SoapInOperation’ for ‘Implements’ and ‘write’ for ‘Calls’
4) Select the ‘rpNameInGroup.xsl’ for the Xsl File (in the XSLT configuration screen)
5) Proceed to save the XSTL Service

Once done, open the Transformmap editor, under ‘Service1/Operation’, right click to open the ‘InTransform1’ properties 
screen.

Note that values are missing from ‘Source’ and ‘Result’ entries

(see attached project and description files)
Comment 1 rpoon 2009-10-17 00:19:09 UTC
Created attachment 89646 [details]
Test Project and Description file
Comment 2 Vitaly Bychkov 2009-11-23 06:51:01 UTC
I cann't reproduce it.
Were there any exceptions warnings in console or netbeans log file (<nbuserdir>/var/log/messages.log)?
Comment 3 Vitaly Bychkov 2009-11-24 06:05:24 UTC
There is one step is missing in description:
after step 4:
4) Select the ‘rpNameInGroup.xsl’ for the Xsl File (in the XSLT configuration
screen)

perform additional step:
4_1) uncheck "Transform Reply". This step is required because both ‘SoapInOperation’ and ‘write’ operations doesn't have output messages i.e. it is one way opeartion and resulted XSLT Service data flow looks like this:

-> [SoapInOperation] -- [T (rpNameInGroup.xsl)] --> [write]
Comment 4 Sergey Lunegov 2009-11-30 06:15:47 UTC
Richard, reopen if still reproducible.
Comment 5 rpoon 2009-12-07 16:49:54 UTC
Verified with build:  20091207-0721

With the described scenario above, user no longer encountered the "error getting properties value" as reported above.
Comment 6 rpoon 2009-12-07 16:52:39 UTC
Created attachment 92240 [details]
verified screen shot