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 83965 - cannot assign new service engine to a service assembly
Summary: cannot assign new service engine to a service assembly
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-31 22:08 UTC by lchang
Modified: 2006-09-07 00:04 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
sample project to use (142.81 KB, application/octet-stream)
2006-08-31 22:11 UTC, lchang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lchang 2006-08-31 22:08:20 UTC
Steps to reproduce:
1.  In AppServer, install a second BPEL Service Engine and start it
2.  Unzip attached project
3.  Right-click on SampleProjectsMultiDepJBI and select 'Properties'
4.  In the Project Properties Window, select 'Packaging Project'
5.  Click on the Update button
6.  Select the SynchronousSample.jar Service Assembly artifact.  
7.  Assign the new BPEL SE you just installed to it, so that it is using a 
different BPEL SE than the others.
8.  Click OK - window will close
9.  Reopen the window by right-clicking on the JBI project and 
select 'Properties'

Result:  When you go back to the Packaging Project screen, you will notice that 
none of the updates you made were saved.  In addition the jbi.xml was not saved 
to reflect any of the changes that were previously made.

Expected Result:  The SynchronousSample.jar Deploymnet Target Component should 
have been saved to the BPEL SE chosen.
Comment 1 lchang 2006-08-31 22:11:40 UTC
Created attachment 33485 [details]
sample project to use