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.

Bug 121312 - error in the sun-web.xml
Summary: error in the sun-web.xml
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-06 17:10 UTC by moonknight
Modified: 2007-11-08 20:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log from the IDE (229.13 KB, text/plain)
2007-11-06 17:12 UTC, moonknight
Details
My server log (412.60 KB, text/plain)
2007-11-08 20:21 UTC, moonknight
Details

Note You need to log in before you can comment on or make changes to this bug.
Description moonknight 2007-11-06 17:10:41 UTC
error in the sun-web.xml in my Visual Application
field where the error is : localeCharsetInfo
error is : java.lang.ClassCastException: org.netbeans.modules.j2ee.sun.share.configbean.WebAppRoot cannot be cast to 
org.netbeans.modules.j2ee.sun.share.config.ConfigBeanStorage
Comment 1 moonknight 2007-11-06 17:12:02 UTC
Created attachment 52612 [details]
log from the IDE
Comment 2 _ potingwu 2007-11-06 17:26:38 UTC
I think it's from the serverplugin. Please evaluate.
Comment 3 Vince Kraemer 2007-11-06 18:23:58 UTC
Filer: what is 1.1 for Java EE SDK U3?
Comment 4 _ pcw 2007-11-06 18:45:41 UTC
Log is for NB 5.5.1.

This is a duplicate (I have to look up the number...) and does not impact 6.0.  Only 5.5.1 and earlier.

The problem is that VWP is installed and leaves the properties window open all the time (different that basic NB install).

The DConfigBeans used by the sun-web.xml configuration editor inadvertently expose properties that the properties window
tries to manipulate but some of the properties aren't correctly type (hence the exception - they were never intended to
be used in this way.)

One work around is to close the properties window before opening sun-web.xml (and close sun-web.xml before reopening it).
Comment 5 moonknight 2007-11-06 18:49:16 UTC
So this is not a big deal that could lead to deployment errors ?
Comment 6 _ pcw 2007-11-06 18:58:49 UTC
It shouldn't.
Comment 7 moonknight 2007-11-08 19:42:20 UTC
I did several tests and it seems to lead to deployment error.
I have created a new simple Visual Web project and tried to deploy it : it failed. It let a process in the Processes 
list and the error message was :

Distributing C:\ROOT\Devel\Java\Test1\dist\Test1.war to [172.25.81.12:4848_server]
Start registering the project's server resources
Finished registering server resources
C:\ROOT\Devel\Java\Test1\nbproject\build-impl.xml:465: Deployment error:
The module has not been deployed.
See the server log for details.
BUILD FAILED (total time: 2 minutes 32 seconds)
Comment 8 _ potingwu 2007-11-08 20:14:31 UTC
>See the server log for details.

Please attach your server log. I think it will help to investigate further.
Comment 9 moonknight 2007-11-08 20:20:31 UTC
OK.
I can also say that each time it happens, I need to undeploy what's on the server, stop the server and restart it. 
Then I can deploy from the AdminConsole.
Comment 10 moonknight 2007-11-08 20:21:40 UTC
Created attachment 52756 [details]
My server log
Comment 11 _ pcw 2007-11-08 20:29:53 UTC
Your deploy problem is probably caused by this error:

[#|2007-11-08T14:55:35.988-0500|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Thread-35;_RequestID=5433fbe7-8934-424e-846e-080c02248153;|Exception
occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Cannot deploy. Module directory is locked and cannot be
deleted: E:\Sun\SDK\domains\domain1\applications\j2ee-modules\BoxSell
	at
com.sun.enterprise.deployment.backend.ModuleDeployer.liquidateModuleDirAndStubsDirIfTheyHappenToExist(ModuleDeployer.java:783)
	at com.sun.enterprise.deployment.backend.WebModuleDeployer.preDeploy(WebModuleDeployer.java:106)
	at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:152)
	at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
	at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
	at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
	at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
	at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
|#]

You are running on windows, so a locked module folder is probably because of an open file handle.  Some part of your
application (or a jar used by your application) may be causing this.  Generally if this happens, the only way to
redeploy is to restart the server, which will unlock the folder.

This is completely unrelated to the original issue filed here (which I'm going to close as "fixed in 6.0".  For your
problem, I recommend you ask for assistance in the glassfish forums
(http://forums.java.net/jive/forum.jspa?forumID=56&start=0).
Comment 12 moonknight 2007-11-08 20:34:25 UTC
Yes, I did realise it wasbeacause of locked files. I thought it was related to the first error because it only happens 
when I deploy a Visual Web project...
Anyway thanks a lot for your help. I will contact the reference you gave !
Comment 13 _ potingwu 2007-11-08 20:41:02 UTC
> only happens when I deploy a Visual Web project...

If you are running a simple JSP only web project, you may not see this issue. But after you added more servlet/...
stuffs, you will reach the similar problem. I.e., it's not specific to visual web that it initially has some Java Bean
files.