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.
We’ve encountered a critical bug within the Netbeans IDE. There is a difference between command-line builds using ANT scripts and when we compile BPEL projects from within the Netbeans IDE for GlassfishESB. The differences is the JBI.xml file that is generated in build\META_INF. When compiled from the Netbeans IDE, the jbi.xml file correctly contains all of the Service Endpoints. When compiled from the command line using ANT scripts, the JBI.xml file contains NO Service Endpoints. The attached files, jbi_NB.xml and jbi_CL.xml contain the outputted files from the Netbeans and command-line builds respectively. The missing information in JBI.xml prevents us from deploying the applications generated from our build server, forcing us to manually compile and deploy. The problem seems to only affect BPEL projects, EJB and POJO projects appear to be ok. A sample project has been made available on our FTP site, and can be accessed here: ftp://ftp.agilexhealth.com/Outgoing/Sun/Compile_JBI_Issue/ Username: FTPGuestHC Password: Ag1l3xHC99$ EntityBPEL.zip: contains the Netbeans BPEL project. build_dirs.zip: contains the generated build directory from both compilation methods. The only noticeable difference was the jbi.xml files. Build.win.properties: property file needed to run the command-line scripts. jbi_NB.xml: same as the file attached to this email, provided as a courtesy. jbi_CL.xml: “ “ Steps to reproduce: 1. Download EntityBPEL.zip 2. Extract contents of Zip file to local disk. {ProjectDir} 3. Download build.win.properties to local disk, and place in the same directory EntityBPEL was extracted to. 4. Open EntityBPEL project in Netbeans IDE. 5. Right-click on project from Projects tab, select “Clean and Build”. 6. Note jbi.xml in {ProjectDir}\build\META_INF. Size should be 12K, and contain the Service Endpoints for the BPEL project. 7. Open Command Prompt, navigate to the directory EntityBPEL was extracted to in step 2 above. 8. Issue the following command: ant clean,dist_se –propertyfile build.win.properties. 9. Note jbi.xml in {ProjectDir}\build\META_INF. Size should be 1K, and NOT contain any of the Service Endpoints for the BPEL project.
A quick update. While investigating this, I came across a delta between the compile times for BPELS when compiled in the IDE vs. the command line. It takes exactly 5 minutes longer for the BPEL to compile when it’s called from the command line. This is consistent across multiple projects. The slow down occurs inside the –do-dist ant target, specially these steps: <generate-catalog-xml buildDirectory="${basedir}/${build.dir}" sourceDirectory="${basedir}/${src.dir}" projectClassPath="${javac.classpath}" classpathRef="ant.task.classpath"/> <generate-jbi-xml buildDirectory="${basedir}/${build.dir}" sourceDirectory="${basedir}/${src.dir}" projectClassPath="${javac.classpath}" classpathRef="ant.task.classpath"/> This is also the area where the output differs between the two compile methods. All variables are the same between the two compile methods except the value for ant.task.classpath. From the command line, it is set in the init-taskdefs ant target. I am not sure where it is set when compiled from the IDE. Can you explain where this value is set when compiling from the IDE? I believe this is the source of the problem.
Vladimir, take a look.
Note that the project EntityBPEL refers to other project Interfaces which is absent, so I can't reproduce the issue on your project. I tried with the SOA sample: TravelReservationService, I build with IDE and commandline, in both cases the jbi.xml file has all endpoints and identical. I use the latest GlassFish ESB v2.1 Nightly build (Unstable) from https://open-esb.dev.java.net/Downloads.html
Created attachment 78514 [details] jbi.xml
QA has reproduce Vladimir's successful build of the SOA sample: TravelReservationService project with both the CLI and the IDE. With the inability to create the customers issue with their project, QA declares the issue closed with the SOA Build of 4/26/09, included with the NetBeans IDE 6.5.1 (Build 200904151427).