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.
[nb36beta] There is a problem with webmodule deployment when there are more webmodules with the some context. To reproduce [given from a NetCAT member feedback] 1) create directories on you filesystem like these: /home/you/web1/webapp /home/you/web2/webapp 2) mount these in the IDE 3) convert both to webmodules (both has set /webapp context) 4) execute the first one => works fine 5) execute the second one - nothing is changed - the first module remains deployed. The problem is caused with the some contexts of the webmodules. Easy workaround would be to change the context via corresponding property of the webmodule, unfortunatelly its not working due to #38819 Since we agreed to simply replace deployed webmodule with the some context the behaviour should be following: - we allow more webmodules with the some context - when a webmodule is deployed and another one is already deployed, it should be replaced silently.
This bug was originally reported by Stavros S. Kounis, NetCAT program participant.
*** Issue 39881 has been marked as a duplicate of this issue. ***
Is that really a problem of j2eeserver ?
I think there is a missing option regarding web modules: "Deploy application". Seems like the IDE is remembering thinks we don't want anymore. An example: I imported a web application from 3.5 version. Due to errors in taglibs "String" -> "java.lang.String" I had some problems running the application. The deployer window froze... but I could see the application in the browser. No messages, no errors... I tried removing the project, starting a new project and copying the files. The same. I could see the application in the browser but the deployer window was frozen. After some more tries I removed the project, started a new project, CREATED A NEW WEB MODULE and then copied the old files over the new ones. Creating the new web module, with the same project name, was the key to make the deployer window finish her task.
Lluis, which build did you use? Regarding the "String" -> "java.lang.String" change in taglibs, this will be fixed in Tomcat 5.0.19, which we are planning to bundle. Petr
Lluis, I am not sure if this bug is exactly the source of your problems. I have encountered similar problem when I had tried to import a project from 3.5, unfortunatelly I am not able to reproduce it. I would appreciate if you provide more information about the frozen deployer progress bar. At least which build of the IDE do you use. If it is the nb36 beta, could you please try to do the import with the current trunk build? Marek
As I completed implement auto-undeploy, sharing webapp directory name or root context is now supported.
verified