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 78085 - 2 partnerlinks of same partnerlinktype but different names & roles cannot be used from same BP
Summary: 2 partnerlinks of same partnerlinktype but different names & roles cannot be ...
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-16 14:34 UTC by bugbridge
Modified: 2006-09-30 14:22 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
test project (690 bytes, application/octet-stream)
2006-06-16 14:38 UTC, Michael Frisino 		Details
test bpel (809 bytes, application/octet-stream)
2006-06-16 14:38 UTC, Michael Frisino 		Details
virtual assign test (1.69 KB, application/octet-stream)
2006-06-16 14:38 UTC, Michael Frisino 		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 bugbridge 2006-06-16 14:34:35 UTC 
Original status: 1-Dispatched; Suggested Status: NEW

Description:
In building a test for the new BPEL 2.0 virtual assign construct I built a
simple Parent BP invking a child-sub BP. (All files from this test are attached)

The parent BPEL has structure: 

1.receive
2.invoke -> child sub BP
3.reply

Parent uses the same 'PartnerLink_for_receive_and_reply' for the receive and reply. 
Parent uses different second 'PartnerLink_for_invoke_out_to_subbp' BUT of the
same partnerlinktype as the first which is 'wsdlNS:virtualAssignLinkType1'.

The child sub BP has structure:

1.receive (receives invoke from parent on PartnerLink_for_invoke_out_to_subbp)
2.reply (replies on the same partnerlink PartnerLink_for_invoke_out_to_subbp)


When building this project I get the following error:

C:\Documents and
Settings\saslam-mir\VARcvInvokeRply\src\VARcvInvokeRply_1.bpel:29: Error:
duplicate operation structure implementation. operation xxx@xxxx version="1.0"
encoding="utf-8" ?>
<wsdl:operation name="virtualAssignOperation1">
    <wsdl:input message="tns:virtualAssignSimpleStringMessage"></wsdl:input>
    <wsdl:output message="tns:virtualAssignSimpleStringMessage"></wsdl:output>
</wsdl:operation>}
is also implemented by receive 
xxx@xxxx version="1.0" encoding="utf-8" ?>
<receive name="receive_call_in_subbp"
         partnerLink="PartnerLink_for_invoke_out_to_subbp"
         portType="wsdlNS:virtualAssignPortType1"
         operation="virtualAssignOperation1"
         variable="var1"
         createInstance="yes">
    <!-- remove variable -->
    <!-- fromPart part="simpleStringPart" toVariable="var1"/> --></receive>}
of process
file:/C:/Documents%20and%20Settings/saslam-mir/VARcvInvokeRply/src/SUBBP.bpel
BUILD FAILED (total time: 3 seconds)

Description (Entry 2):
Multiple partnerlinks connecting a BP to outside entities of the same
ParternlinkType is a common scenario.
Comment 1 Michael Frisino 2006-06-16 14:38:04 UTC 
Created attachment 31112 [details]
test project
Comment 2 Michael Frisino 2006-06-16 14:38:25 UTC 
Created attachment 31113 [details]
test bpel
Comment 3 Michael Frisino 2006-06-16 14:38:40 UTC 
Created attachment 31114 [details]
virtual assign test
Comment 4 Michael Frisino 2006-07-16 22:12:50 UTC 
This looks like a validation issue. Since this bug was filed in June, it is
probably using the older validation system. 

Should be re-tested with the new validation system to see if messages still
appear. It is only a bug if the messsages appear incorrectly. If the messages
are correct this is not a bug.
Comment 5 Denis Anisimov 2006-07-18 12:56:41 UTC 
QA, could someone recheck this issue ?
Comment 6 Denis Anisimov 2006-07-20 15:10:38 UTC 
Anyway - this is again build system validation. It doesn't have relation
to "validation feature". 
So this is not mine responsibility and I don't know responsible person.
I just reassign bug to "issues".
Comment 7 Michael Frisino 2006-07-21 10:30:49 UTC 
assigning to srini, as I believe he is working on moving build validation to use
common validation system.
Comment 8 Sreenivasan Genipudi 2006-07-25 01:33:16 UTC 
There is a problem in the test project. The test bpel is trying to refer the 
XSD defined locally inside another WSDL. Instead save the XSD schema in a file 
and import in the BPEL and use it...

Test project BPEL is  trying to use "simpleStringType" 
 
     <variable name="var1"
                  type="wsdlNS:simpleStringType"></variable>

that is defined locally inside (inline schema) the WSDL
(virtualAssignTest_1.wsdl).. 

BPEL cannot access schema types that are defined in a WSDL inline.
Save the XSD schema in a file and import in the BPEL and use it.
Comment 9 Ritesh Adval 2006-07-25 19:41:16 UTC 
Ok, the original issue of project build failing due use of old validator is 
fixed since now we are using the new validator api in project build.

Now when trying to build the project using virtualAssignTest_1.wsdl and 
VARcvInvokeRply_1.bpel, build fails with errors in resolving inline xsd defined 
in wsdl from bpel.

so this looks like a bug in bpelmodel which can not access inline xsd defined 
in wsdl in the bpel file.

I see following errors:

C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:23: 
column:8 ERROR: Unknown schema type "wsdlNS:simpleStringType" in 
variable "var1".Make sure the WSDL or schema document that defines the schema 
type is imported.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:27: 
column:8 ERROR: Unknown schema type "wsdlNS:simpleStringType" in 
variable "var3".Make sure the WSDL or schema document that defines the schema 
type is imported.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:29: 
column:8 ERROR: Unknown schema type "wsdlNS:simpleStringType" in 
variable "var4".Make sure the WSDL or schema document that defines the schema 
type is imported.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:25: 
column:8 ERROR: Unknown schema type "wsdlNS:simpleStringType" in 
variable "var2".Make sure the WSDL or schema document that defines the schema 
type is imported.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:2: 
column:1 WARNING: Model source provides no javax.xml.transform.Source in 
lookup, relative resource resolving if needed will not be available.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:25: 
column:8 ERROR: Element "variable" has reference to external "xsd" element ( 
via "type" attribute value ) and this element cannot be found.Please check 
namespace declarations, "import" elements, attribute value or name of 
referenced element.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:29: 
column:8 ERROR: Element "variable" has reference to external "xsd" element ( 
via "type" attribute value ) and this element cannot be found.Please check 
namespace declarations, "import" elements, attribute value or name of 
referenced element.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:27: 
column:8 ERROR: Element "variable" has reference to external "xsd" element ( 
via "type" attribute value ) and this element cannot be found.Please check 
namespace declarations, "import" elements, attribute value or name of 
referenced element.
C:\Documents and Settings\radval\BpelModule5\src\VARcvInvokeRply_1.bpel:23: 
column:8 ERROR: Element "variable" has reference to external "xsd" element ( 
via "type" attribute value ) and this element cannot be found.Please check 
namespace declarations, "import" elements, attribute value or name of 
referenced element.
C:\Documents and Settings\radval\BpelModule5\src\virtualAssignTest_1.wsdl:4: 
column:1 WARNING: Model source provides no javax.xml.transform.Source in 
lookup, relative resource resolving if needed will not be available.

assign this bug to bpelapi.
Comment 10 Denis Anisimov 2006-07-26 10:52:56 UTC 
There was no algorithm for identifying inline schemas ( inside wsdl ).
Now it is implemented.

But now algorithm could take more time because I need to look at EACH wsdl file
for possible inline schema.
Comment 11 Mikhail Kondratyev 2006-09-30 14:22:08 UTC 
Verified with build from 2006.09.25
The project consisting of the attached files compiles successfully