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.
Consider two BPEL files in a bpel project that have the same provisioning endpoints as shown below name="samesync1" targetNamespace="http://enterprise.netbeans.org/bpel/samesync1" xmlns:ns1="http://j2ee.netbeans.org/wsdl/sync1"> <partnerLinks> <bpws:partnerLink name="PartnerLink1" partnerLinkType="ns1:sync1Partner" myRole="sync1PortTypeRole"/> </partnerLinks> name="sync1" targetNamespace="http://enterprise.netbeans.org/bpel/sync1" xmlns:ns1="http://j2ee.netbeans.org/wsdl/sync1"> <partnerLinks> <bpws:partnerLink name="PartnerLink1" partnerLinkType="ns1:sync1Partner" myRole="sync1PortTypeRole"/> </partnerLinks> building the bpel project results in the jbi.xml having only one 'provides' entry as show below. <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:ns0="http://enterprise.netbeans.org/bpel/samesync1" xmlns:ns1="http://j2ee.netbeans.org/wsdl/sync1" xmlns:ns2="http://enterprise.netbeans.org/bpel/sync1" version="1.0"> <services binding-component="false"> <provides endpoint-name="sync1PortTypeRole_myRole" interface-name="ns1:sync1PortType" service-name="ns0:PartnerLink1"/> </services> </jbi> This is a bug in our bpel project code generator. The bpel project should create a jbi.xml with two provides entries as listed below. The service-names are different if you fully qualify them. <provides endpoint-name="sync1PortTypeRole_myRole" interface-name="ns1:sync1PortType" service-name="{http://enterprise.netbeans.org/bpel/samesync1}:PartnerLink1"/> <provides endpoint-name="sync1PortTypeRole_myRole" interface-name="ns1:sync1PortType" service-name="{http://enterprise.netbeans.org/bpel/sync1}:PartnerLink1"/>
Created attachment 39315 [details] The BPEL project file zip that was used to produce the issue
Could not find the schema for jbi.xml. Assuming that the attribute "service-name" is accepting qualified name, the valid jbi.xml should look like the following: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:ns0="http://enterprise.netbeans.org/bpel/samesync1" xmlns:ns1="http://j2ee.netbeans.org/wsdl/sync1" xmlns:ns2="http://enterprise.netbeans.org/bpel/sync1" version="1.0"> <services binding-component="false"> <provides endpoint-name="sync1PortTypeRole_myRole" interface-name="ns1:sync1PortType" service-name="ns0:PartnerLink1"/> <provides endpoint-name="sync1PortTypeRole_myRole" interface-name="ns1:sync1PortType" service-name="ns2:PartnerLink1"/> </services> </jbi> pvarghese, please, confirm. Also, need to make sure that other jbi module projects (such as xslt project) follow the same rule (cc'ing Vitaly aka 'lativ' as he's in charge for xslt project).
zgursky, what you stated is accurate.
Fixed in trunk: Checking in Provider.java; /cvs/enterprise/bpel/project/antsrc/org/netbeans/modules/bpel/project/anttasks/jbi/Provider.java,v <-- Provider.java new revision: 1.5; previous revision: 1.4 done Checking in Consumer.java; /cvs/enterprise/bpel/project/antsrc/org/netbeans/modules/bpel/project/anttasks/jbi/Consumer.java,v <-- Consumer.java new revision: 1.5; previous revision: 1.4 done
Verified in build 200709031200.