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.
Build: NB 5.5 dev build 060710 Failed to deploy SynchronousSampleApplication. Get the following message in the build.xml(run) output window: ... run-jbi-deploy: Retrieving settings from C:\Documents and Settings\Hong\.netbeans\5.5dev/config/J2EE/InstalledServers/.nbattrs [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=C:\Documents and Settings\Hong\SynchronousSample2\SynchronousSample2Application/dist/SynchronousSampleApplication.zip Deploy service assembly succeeded. [start-service-assembly] Starting a service assembly... host=localhost port=4848 name=01000000-A80FC0D80A0100-81925636-01 Start service assembly failed. MESSAGE: (JBIMA1207) Unable to execute lifecycle operation for service assembly 01000000-A80FC0D80A0100-81925636-01. Service assembly does not exist in the system. C:\Documents and Settings\Hong\SynchronousSample2\SynchronousSample2Application\nbproject\build-impl.xml:207: Service assembly deployment failed. BUILD FAILED (total time: 3 seconds)
Created attachment 31719 [details] build-impl.xml file
A workaround and a question: Workaround: Steps for Synchronous sample project: - Open file "SynchronousSampleApplication/nbproject/project.properties". - Change value of property 'org.netbeans.modules.compapp.projects.jbi.descriptor.uuid.assembly-unit' from '01000000-A80FC0D80A0100-81925636-01' to 'SynchronousSampleApplication'. - Deploy now working ... Question 1: Is this a problem for TRS sample and AsynchronousSample also? If so, we can adjust all 3 samples. If not, we have to understand why only one has this problem.
Yes, three samples (Sync, Async, TRS) have the same behavior.
I created a new Composite Application "CompositeApp". Added JBI Module with the same "SynchronousSample" project. Deployed this new CompositeApp without error.
I just checked with Andre and this appears to work fine today. Probably CAPS team made changes. Now the org.netbeans.modules.compapp.projects.jbi.descriptor.uuid.assembly-unit property will auto adjust when the JBI module is added to the CAPS project. At that point the entry will look similar to that recommended by workaround. So it looks like this is fixed.
verified the fix is in build 200607130000