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.
Summary: | Redeploying CompApp project with out undeploying is working, which is not expected. | ||
---|---|---|---|
Product: | soa | Reporter: | srinivaschintalapati <srinivaschintalapati> |
Component: | Composite Application | Assignee: | Jun Qian <jqian> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | Other | ||
OS: | Windows XP x64 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
srinivaschintalapati
2007-02-16 07:57:09 UTC
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 |