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.

Bug 82614 - Blueprint projects can't be deployed when project name was changed
Summary: Blueprint projects can't be deployed when project name was changed
Status: VERIFIED FIXED
Alias: None
Product: usersguide
Classification: Unclassified
Component: SOA (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Praveen Savur
URL:
Keywords:
: 85428 (view as bug list)
Depends on: 85451
Blocks:
  Show dependency tree
 
Reported: 2006-08-14 13:57 UTC by Mikhail Kondratyev
Modified: 2006-10-12 14:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kondratyev 2006-08-14 13:57:40 UTC
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
Comment 1 Michael Frisino 2006-08-14 15:36:02 UTC
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.
Comment 2 Praveen Savur 2006-08-14 18:40:48 UTC
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.
Comment 3 Ryan Kennedy 2006-09-20 23:40:26 UTC
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.
Comment 4 Ryan Kennedy 2006-09-21 18:21:37 UTC
*** Issue 85428 has been marked as a duplicate of this issue. ***
Comment 5 Jun Qian 2006-09-22 08:17:36 UTC
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...
Comment 6 Praveen Savur 2006-09-22 22:42:54 UTC
Manish suggested I look at this.
Comment 7 Praveen Savur 2006-09-22 23:38:58 UTC
checkin blueprint composite application projects so that it does not have any
reference to the BPEL module.
Comment 8 Mikhail Kondratyev 2006-09-29 11:44:13 UTC
Can'r verify because of 85451
Comment 9 Ryan Kennedy 2006-10-05 04:19:24 UTC
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.
Comment 10 Mikhail Kondratyev 2006-10-12 14:43:50 UTC
Verified in m22