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.
Redeploying same Composite App Project twice(i.e. CompApp project already deployed and running on the domain and doing a redeployment of the same CompApp on the same domain ) on Sun Java System Application Server 9.1 is not throwing any alert message. Expected Behaviour: "Appserver should throw an alert that project already deployed" JBIMGR Version is : App Server details: App Server version = Sun Java System Application Server 9.1 (build b34) App Server build date = Tue Jan 30 23:48:00 GMT+05:30 2007 JBI details: _____________________________________________________________________________ Running at 16 February 2007 01:16:33 PM on Windows XP 5.1 [x86] using Java 1.5.0_09-b03 from c:\Progra~1\Java\jdk1.5.0_09\jre app server type = GLASSFISH (sub-type = CLUSTER version = 91) app server domains = 1 (instances = 0 cluster = ) java.io.tmpdir = C:\WINDOWS\TEMP\ jbi port = 17888 (secure = true) installed product build = 070215_1 installed product variant = Kenai installed product kit type = image JBI build details: JBI Framework build date = Thu Feb 15 10:47:26 GMT+05:30 2007 [source: C:/Kenai/gf91/jbi/lib/jbi_framework.jar] HTTP SOAP Binding build date = Mon Feb 12 20:54:40 GMT+05:30 2007 [source: C:/Kenai/gf91/jbi/components/com.sun.httpsoapbc-1.0-2/httpsoapbc.j ar] BPEL Engine build date = Mon Feb 12 20:55:26 GMT+05:30 2007 [source: C:/Kenai/gf91/addons/jbi-components/bpelserviceengine.jar] NetBeans build details: Netbeans IDE build = 070215 Netbeans IDE version = 200702140600 [source: C:/Kenai/netbeans/5.5.1/build_info] Netbeans IDE build date = Wed Feb 14 08:49:08 GMT+05:30 2007 [source: C:/Kenai/netbeans/5.5.1/platform6/core/core.jar] CAPS Modules build date = Thu Feb 15 02:43:54 GMT+05:30 2007 [source: C:/Kenai/netbeans/5.5.1/soa1/ant/nblib/org-netbeans-modules-compap p-projects-jbi.jar]
I can't agree this is a bug. Currently, according to the messages in the log file the following is done: deployed service assembly stopped, shutdown, undeployed and only after these steps IDE starts deploying it. This is actually what I expect as a user. This is also consistent with NetBeans Java EE applications deployment behavior.
If some other user is deploying a project having different scinereo with existing project name (i.e which is already deployed on the same application server) then Old project gets undeployed and User doesn't know that his project is undeployed from the application server and new project is running with different result.
Justification from Venkat: we will evaluate and add a warning dialog for fcs No Objections in 48 hours. Waived.
Agreed with mikk 100%. The log message is very clear about the undeployment. If the user knows it is the first time she deploys a particular application and she sees undeployment going on in the log, she should understand she has just undeployed another running application by accident. A warning dialog will be annoying for 99% of the users and it is also hard to implement. A warning message could be added to the log but the undeployment message already serves this purpose.
Removed EP551_WAIVER_APPROVED
verified
Verified long back closing