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.
Steps to reproduce: - go to New->Project->Samples->Service Oriented Architecture->BPEL Blueprints - select a blueprint project, click Next - change the suggested project name to any other valid name - create project - try to deploy the project Deployment will fail
This is probably the same issue we had a long time ago with the other BPEL samples. I suppose there is project.properties (or other metadata) that is not being properly adjusted to be consistent with the user specified project name. This should be an easy fix if this is considered showstopper.
Blueprint samples have the same renaming in place as the other samples. On checking I see that the actual issue is that the checked-in JBI composite applications have a reference to the BPEL module in the build script. JBI composite applications have to be checked-in so that it has no reference to the BPEL module. So to resolve this issue the JBI composite applications would have to be refreshed/repackaged. Assigning to Ryan.
When changing project name from "BluePrint2" to "AsynchBluePrint2", the generated project.properties file produces the following. We should only see a single entry (first line). reference.AsynchBluePrint2.dist_se=${project.AsynchBluePrint2}/build/SEDeployment.jar reference.BluePrint2.dist_se=${project.BluePrint2}/build/SEDeployment.jar There may be other entries where the replacement might not have happened accurately. Project.properties should be generated correctly for renaming of blueprint projects to work correctly.
*** Issue 85428 has been marked as a duplicate of this issue. ***
As Praveen said, this is a sample project packaging issue. The blueprint compapp project shouldn't contain any reference to the bpel project when initially created. Assigning back...
Manish suggested I look at this.
checkin blueprint composite application projects so that it does not have any reference to the BPEL module.
Can'r verify because of 85451
In light of dependency on bug 85451 (recently resolved with new BPEL BluePrint build-impl files added to release55 branch), please verify that BluePrint samples 1-5 can be deployed when project name is changed to something other than default value.
Verified in m22