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.
NB Build:NB IDE Dev 200805150003 Appserver Build:GF2.1(b33) JDK:jdk1.5.0_13 Steps to reproduce: 1.Install NB IDE and GF 2.1 2.Start IDE. 3.Register remote domain 4.Create a simple web application(Hello world) 5.Deploy the application. 6.Right click on the deployed application select Disable(services/server/GF V2/Applications/Webapplication/) 7.Run the application. NOTE: I tried above steps with registering default local domain and registering local domain. On running the application shows message as: HTTP Status 503 - type Status report message descriptionThe requested service () is not currently available.
From the description, it appears that you deploy an application and then disable it on the server. Then when you execute the application, the server gives a HTTP Status 503 and cannot find the application. Which is correct, since the application is disabled. So what do you mean by the application runs successfully after disabling? Are you referring to the NB menu item, Run in the project? And that action can be executed?
Yes, I deployed the application and disabled it on the server.Selecting run on the project(Right click on the project and select run)should show HTTP Status 503 in the browser out put, since it is disabled.But its not happening.Even disabling the application on the server and selecting run(Right click on the application and select run) it showing "Hello World" out put in the browser.This is happening on registering remote domain. The same I did by registering default local domain and local domain. I disabled the application on the server and selected run (Right click on the project select run), it shows HTTP Status 503 in the browser out put.
this is kind of what we expect... actually. for the local domains... the web app is directory deployed. Since the app is directory deployed, the call to Run after a Deploy and disable does not do a deploy... so the disabled "bit" is not reset. And the run will behave in the way you describe. If there is a change that forces a deploy... like a servlet change, the disabled bit will get unset. In the case of a remote domain, the call to Run must do a deploy... which will always unset the disabled bit. I would advocate for removing the 'Disable' item, since it really makes little sense to disable an app that you are actively developing. I am lowering this issue to p4.
I guess a better fix is to make sure that the following sequence always works... new project, run project, disable app, run project should not generate a 503 under any circumstances... reason; the last thing the user told the IDE to do was Run the project. I am going to push this back up to p3 and resolve it.
I filed issue 146993 to track some of the changes that need to happen in other plugins and j2eeserver for this to be resolved
match target milestone for j2eeserver changes.
this needs to get worked for 7.0, but probably is not a stopper.
started thread in nbusers to discuss removing the ability to enable/disable a deployed component.
http://hg.netbeans.org/main/rev/788291dbe69d
forgot to mark as fixed
Integrated into 'main-golden', will be available in build *200812121401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/788291dbe69d User: vince kraemer <vkraemer@netbeans.org> Log: #135393 : can Run disbaled apps. remove the ability to disable a module/app
Bug was verified as fixed with NB6.7 trunk build (3/01/2009) on winXP machine.
Correct, today build (03/02/2009)