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.
The bpel project failed to identify endpoints with the same name but using different namespaces, see enclosed eamil from Murali. To reproduce this problem, - use the enclosed project from Murali - change PartnerLink2 to PartnerLink1 in bp2.bpel - build the bpel project - the jbi.xml from the bpel project has only 1 endpoint <provides endpoint-name="duplicateSvcPortTypeRole_myRole" interface- name="ns1:duplicateSvcPortType" service-name="ns0:PartnerLink1"/> --------------------------------------------------------------- Murali Pottlapelli wrote: Tien/Jun: In the project attached I have a WSDL with one PT, on PLT and two services/ports. This PT is implemented two BPs. After editing connections in CASA editor, it works as expected but build shows following warnings. I am not sure why these warning are showing up even after editing. copying Sub-Assembly: C:\openEsb\open-jbi-components\driver- tests\bpelse\dynamicpartnerlink\DuplicateSvcApp\build\DuplicateSvc.jar ***Warning: 2 ports and 2 providers [{http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcPortType] Port[0]: : duplicateSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Port[1]: : alternativeSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Provider[0]: : {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp1} PartnerLink1, duplicateSvcPortTypeRole_myRole Provider[1]: : {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp2} PartnerLink2, duplicateSvcPortTypeRole_myRole When partner link name is "PartnerLink1" on both BP1 and BP2 it did not identify them as two provisioning endpoints. Is that a bug? Regards Murali
Created attachment 42655 [details] Murali's test project
Created attachment 45431 [details] jbi.xml from bpel project
Tried with build: Product Version: NetBeans IDE Dev (Build 070720) Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-b03 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) File jbi.xml (see attachment id=45431) from the bpel project has 2 endpoints (not 1 as it was written in the description of the issue). So, bpel project provides correct information. While building of DuplicateSvcApp I see warning: jbi-build: copying Sub-Assembly: C:\Documents and Settings\v1v\My Documents\NetBeansProjects\DuplicateSvcApp\build\DuplicateSvc.jar ***WARNING: 2 ports and 2 providers [{http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcPortType] Port[0]: duplicateSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Port[1]: alternativeSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Provider[0]: {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp1}PartnerLink1.duplicateSvcPortTypeRole_myRole Provider[1]: {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp2}PartnerLink2.duplicateSvcPortTypeRole_myRole C:\Documents and Settings\v1v\My Documents\NetBeansProjects\DuplicateSvcApp\nbproject\build-impl.xml:188: java.lang.AssertionError BUILD FAILED (total time: 0 seconds) Comp app project should identify endpoints correctly.
Good, so the bpel project problem is fixed.. However, I am not sure why this ticket is forward to compapp? Can you identify those incorrect endpoints referred to in the comment? "Comp app project should identify endpoints correctly." Thanks,
Assertion Error should be fixed in comp app project. See: C:\Documents and Settings\v1v\My Documents\NetBeansProjects\DuplicateSvcApp\nbproject\build-impl.xml:188: java.lang.AssertionError BUILD FAILED (total time: 0 seconds)
The DuplicateSvcApp project had bad reference to endpoints in bpel project caused by the earlier problem. One can clean up the compapp project configuration and regenerate these connections using the following steps: - Right click DuplicateSvcApp and select "Clean application configuration" - Open DuplicateSvcApp in CASA - Click on the bpel SU and select "Load WSDL ports" to load the two wsdl ports - make two connections - rebuild the DuplicateSvcApp project (It should build successfully) jbi-build: Building jar: E:\a2k7\bugs\104533\DuplicateSvcApp\build\BCDeployment.jar copying Sub-Assembly: E:\a2k7\bugs\104533\DuplicateSvcApp\build\DuplicateSvc.jar ***WARNING: 2 ports and 2 providers [{http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcPortType] Port[0]: duplicateSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Port[1]: alternativeSvcPort, {http://j2ee.netbeans.org/wsdl/duplicateSvc}duplicateSvcBinding Provider[0]: {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp1}PartnerLink1.duplicateSvcPortTypeRole_myRole Provider[1]: {http://enterprise.netbeans.org/bpel/DuplicateSvc/bp2}PartnerLink2.duplicateSvcPortTypeRole_myRole Create E:\a2k7\bugs\104533\DuplicateSvcApp\build/sun-http-binding.jar for binding component sun-http-binding Writing out to file: E:\a2k7\bugs\104533\DuplicateSvcApp\src\jbiServiceUnits\sun-http-binding\jbi.xml Deleting: E:\a2k7\bugs\104533\DuplicateSvcApp\build\BCDeployment.jar Building jar: E:\a2k7\bugs\104533\DuplicateSvcApp\dist\DuplicateSvcApp.zip BUILD SUCCESSFUL (total time: 2 seconds) However, I think we should generate a better error message than java.lang.AssertionError in this case. Jun, Can you add an error message to suggest the uer to check for project configuration problems that may causing this type of error? Thanks,
Sure, I could add some error message to alert the user any configuration problem, but I'd like to understand what was going on. yaroslavskiy, could you please tell me how to reproduce the AssertionError? Which NB build? I am not able to reproduce the problem with the latest build. I also tried to reproduce this with a NB build from 7/10 (hopefully before the BPEL project fix?) but didn't succeed either. Thanks,
I tried with several builds and could not reproduce it. There is no assertion error at all. I think that issue can be closed as fixed. Agree?
Agree. Thanks for testing it out.
tested and verified using Build 200810130101 and was able to build and deploy the projects successfully and test runtime. after following the steps The DuplicateSvcApp project had bad reference to endpoints in bpel project caused by the earlier problem. One can clean up the compapp project configuration and regenerate these connections using the following steps: - Right click DuplicateSvcApp and select "Clean application configuration" - Open DuplicateSvcApp in CASA - Click on the bpel SU and select "Load WSDL ports" to load the two wsdl ports - make two connections - rebuild the DuplicateSvcApp project (It should build successfully)