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.
Failed to deploy Web Module Application Listener with having Context Listener and Context Attribute Listener Steps To Reproduce: 1. Install NB 6.7 Trunk (4/08/2009) on WinXP with jdk1.6.0_12 2. Start IDE with GlassFish V3 experimental option 3. Activate and Register GlassFish V3 by downloading it 4. Create a Web Module project with having GlassFish V3 as runtime 5. Right-click at the web project, select New > other > Web > Web Application Listener > Next > select Context and Context Attribute Listener > click Finish 6. Select to run the project BUG: -The IDE was looking for files under directory "E:/Documents%20and%20Settings" not "E:/Documents and Settings" -UnsupportedOperationException occurs in the server.log file
Created attachment 79695 [details] messages.log
Created attachment 79696 [details] server.log
Created attachment 79697 [details] Listener Context App
The problem does not happen if run with GlassFish V3 prelude
please attach the source of NewServletListener.java Also... does the war file deploy using asadmin deploy onto v3 Prelude? does the war file deploy using asadmin deploy onto v3?
-The application was deploy successfully with asadmin command for GF V3 prelude -The application failed to deploy with asadmin command for GF V3 experimental . Below is the error message appeared when I deploy the app "E:\Documents and Settings\Administrator\GlassFish_v3\bin>asadmin deploy WebApplication4.war remote failure: Exception while loading the app : java.lang.Exception: java.lang.UnsupportedOperationException: Not supported yet. Command deploy failed."
I could not get the app to run in v3 Prelude either. Since the code of the new file is full of 'throws UnsupportedOperationException', I would be surprised if it did. So, this really looks like an inconsistent change in the server's behavior... file a bug against glassfish and see how the server team responds... either the v3 Prelude behavior is 'right' and v3 has a bug or the other way around. The plugin is not going to do deep analysis of code in a web app to prevent the deploy from working in both cases.
see https://glassfish.dev.java.net/issues/show_bug.cgi?id=7554 for server issue resolution