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.
Currently, the CompApp build process does not support the use case of external modification of casa file. However, there are several scenarios that requires such support, e.g., 1. In a multi-user environment, a compapp project may be changed by different users. 2. In SCAD, the casa file is generated outside of the compapp project. In order to fix this, the content of casa needs to be loaded earlier in the compapp build process.
Please attach the SCAD project that exposes this problem.
Created attachment 75154 [details] scad project, needs to replace camelHome in profiles.xml
Created attachment 75155 [details] casa image showing 1 consume to 2 provides
Fixed in soa-dev: http://hg.netbeans.org/soa-dev/rev/6fd872f378b0
Jun, Looks like there is another problem with this test case. There is a new connection (from monitorPort to orderPT), not in the scad design, but generated by CompApp. This connection created an infinit loop, file -> xslt -> iep -> xslt -> file, after the first write. -- Tientien Li
Created attachment 75195 [details] extra connection generated by compapp
To support the scad use case, we can add a command line flag asking compapp to skip the connection generation step and to use connections from casa instead. This will ensure that the resulting SA generated by compapp has only scad connections.
The flag should probably be set as a compapp project properties so that scad generated compapp projects will not auto- generate new connections.
Sure.
Fixed in soa-dev: http://hg.netbeans.org/soa-dev/rev/d745b75bb9c3 Introduced a new compapp project property ('com.sun.jbi.routing.bc.autoconnect') to control auto connection generation involving BC endpoints. This property is set to false for SCAD-generated compapp projects.
Checked with Developer Jun Qian on this issue. The property added is for supporting SCAD which is currently on hold. Not available in GF ESB v2.1. Reopening ticket.