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 92746 - One-way invoke generates unnecessary warning about NOT needing "outputVariable" attribute.
Summary: One-way invoke generates unnecessary warning about NOT needing "outputVariabl...
Status: CLOSED DUPLICATE of bug 91984
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P4 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-18 01:08 UTC by kevan1138
Modified: 2007-09-03 14:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 kevan1138 2007-01-18 01:08:54 UTC 
One-way invoke generates the following unnecessary warning:
For <invoke>, one-way invocation requires only the inputVariable (or its
equivalent <toPart>?s) since a response is not expected as part of the
operation. The outputVariable (or its equivalent <fromPart>?s) must be only
specified for request-response invocations.

The defined invoke (pasted below) SHOULDN'T have an output variable. Why is
there a warning for doing the right thing?

Here's the invoke:
<invoke name="Invoke1" partnerLink="InvokePLT"
                operation="ForEachInvokeOp" portType="wsdlNS:InvokePortType"
                inputVariable="output1"/>
Comment 1 Mikhail Kondratyev 2007-01-18 07:47:31 UTC 
What do you mean by warning? If you mean the validation error badge and message
displayed in callout window than this bug is a duplicate of 91984 and also 91930.
These bugs are already fixed.

Please check and close this issue as duplicate if appropriate.
Comment 2 kevan1138 2007-01-18 18:36:45 UTC 
Might be a duplicate of 91984.  In which build is this issue fixed?
Comment 3 Mikhail Kondratyev 2007-01-19 07:16:45 UTC 
I have now build from 17th and validation works fine.
But I think this was fixed starting from the build from January 14
Comment 4 Vladimir Yaroslavskiy 2007-03-15 14:23:59 UTC 

*** This issue has been marked as a duplicate of 91984 ***