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.
1. Create a new sample project, say, SynchronousSample 2. Clean & build the compapp project Got the following: ... jbi-build: Copied 1 empty directory to 1 empty directory under C:\TEMP\SynchronousSample5\SynchronousSample5Application\src\jbiServiceUnits Created dir: C:\TEMP\SynchronousSample5\SynchronousSample5Application\build\META-INF Warning: skipping jar archive C:\TEMP\SynchronousSample5\SynchronousSample5Application\build\BCDeployment.jar because no files were included. Building MANIFEST-only jar: C:\TEMP\SynchronousSample5\SynchronousSample5Application\build\BCDeployment.jar Error: Missing project Sub-Assembly: C:\TEMP\SynchronousSample5\SynchronousSample5/build/SEDeployment.jar ERROR: Invalid service unit name: SynchronousSample5 Deleting: C:\TEMP\SynchronousSample5\SynchronousSample5Application\build\BCDeployment.jar Created dir: C:\TEMP\SynchronousSample5\SynchronousSample5Application\dist Building jar: C:\TEMP\SynchronousSample5\SynchronousSample5Application\dist\SynchronousSampleApplication.zip or a more ugly NPE documented in 99925. Looks like the compapp project is not generated correctly because its build-impl.xml doesn't contain instructions on how to build the BPEL project. Removing the BPEL module from compapp and re-add it back doesn't seem to fix compapp's build-impl.xml. The current workaround is to delete compapp's build-impl.xml and genfiles.properties, close and reopen the compapp project.
Previously (in NB 5.5.1), the sample module does not depend on changes in CompApp's build script template. Whevener a new sample project is created by the user, the compapp project's build-impl.xml always gets refreshed based on the latest compapp project system in NetBeans. It is possible that the current sample implementation in NB 6.0 assumes the pre-packaged sample projects always contain the latest project system changes and therefore no build-impl.xml refresh is needed when a sample project is instantiated. The above is just my guess. If this is the case, then every time we update CompApp, we need to update sample projects, which is a burden to us. The old ways seems to work better.
fixed.
Sample projects are broken again in build 070416_23 (due to recent ide8 to java1 cluster change).
*** Issue 101249 has been marked as a duplicate of this issue. ***
*** Issue 101188 has been marked as a duplicate of this issue. ***
Fixed in build 070417_7: AsynchronousSample, SynchronousSample: deploy and test are fine TRS: deploy only. For TRS testing see another issue 100773.
TRS failed in build 070417_18.. It looks like all test cases needed to be regenerated. The test cases has destination, e.g.,: http://localhost:18181/TravelReservation/buildItinerary but wsdl specifies: http://localhost:18181/TravelReservationService/buildItinerary
Tests in TRS has been fixed.
Fix is confirmed.