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 59232 - JspConfig ClassCastException deploying to sjas 8.1
Summary: JspConfig ClassCastException deploying to sjas 8.1
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-24 21:54 UTC by kevinha
Modified: 2006-03-24 13:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kevinha 2005-05-24 21:54:42 UTC
hi,

a servlet 2.4/jsp 2.0 web app that deploys fine to tomcat 5.5.7 throws up when
deployed to sjas 8.1 with 
java.lang.ClassCastException:
org.netbeans.modules.j2ee.sun.dd.impl.web.model_2_4_0.JspConfig
        at
org.netbeans.modules.j2ee.sun.dd.impl.web.model_2_4_1.SunWebApp.setJspConfig(SunWebApp.java:850)
        at
org.netbeans.modules.j2ee.sun.dd.impl.web.SunWebAppProxy.setJspConfig(SunWebAppProxy.java:342)
        at
org.netbeans.modules.j2ee.sun.share.configBean.WebAppRoot$1.getDDSnippet(WebAppRoot.java:301)
        at
org.netbeans.modules.j2ee.sun.share.configBean.Base.addToGraphs(Base.java:625)
        at
org.netbeans.modules.j2ee.sun.share.configBean.SunONEDeploymentConfiguration.saveDConfigBean(SunONEDeploymentConfiguration.java:349)
        at
org.netbeans.modules.j2ee.sun.share.configBean.SunONEDeploymentConfiguration.save(SunONEDeploymentConfiguration.java:317)
        at
org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.getDeploymentPlanFileForDistribution(ConfigSupportImpl.java:248)
        at
org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.getConfigurationFile(ConfigSupportImpl.java:224)
        at
org.netbeans.modules.j2ee.deployment.impl.projects.DeploymentTargetImpl.getConfigurationFile(DeploymentTargetImpl.java:180)
        at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:615)
        at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:129)
        at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:62)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
        at
org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
        at
org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)

please advise what further info is required.

rgds
kev
Comment 1 Sherold Dev 2005-05-25 08:21:17 UTC
Moving to sunappserv.
Comment 2 kevinha 2005-06-01 11:53:21 UTC
problem is due to using a sun-web.xml that references the app server 8.0 DTD.
changing the reference to the app server 8.1 DTD fixes the issue.
Comment 3 _ pcw 2005-06-01 18:26:47 UTC
Yes, but actually this should have been handled anyway (silent migration of 8.0
sun-web.xml to 8.1 sun-web.xml).  It will be investigated and fixed.
Comment 4 kevinha 2005-06-07 10:29:50 UTC
fyi, i rsync the source between home and work. if there is some project metadata
somewhere that says that the project has already been migrated from 8.0 to 8.1
(as opposed to always attempting the migration whenever the 8.0 sun-web.xml is
found) then it is possible that the synch has screwed this up.
Comment 5 _ pcw 2005-06-07 17:19:31 UTC
Interesting.  Are both home and work NB installations the release build of 4.1?  

The version of sun-web.xml is determined by the DOCTYPE declaration at the top
of the sun-web.xml file and this would be updated from 8.0 DOCTYPE to 8.1
DOCTYPE the first time the file is opened and saved.  If it wasn't saved, it
should still get silently upgraded each time it is opened.

Do you know how you obtained an SJSAS 8.0 sun-web.xml in the first place?  (i.e.
migration of an application from NB 3.6, web project created in NB 4.1, etc.)
Comment 6 kevinha 2005-06-08 19:52:58 UTC
both home and work are nb 4.1. however, at one point i tried unsuccessfully to
register an external sjas instance. i suspect that this may have been an 8.0 one
that i had not uninstalled properly. maybe this had an effect.
Comment 7 _ pcw 2005-09-13 01:50:29 UTC
This will be fixed for beta.
Comment 8 _ pcw 2005-09-20 08:18:07 UTC
This is fixed for upcoming 5.0.
Comment 9 _ pcw 2005-09-20 08:19:16 UTC
By the way, best work around is to manually change the doctype from 8.0 to 8.1
-- see an existing 8.1 file for details.
Comment 10 Michal Mocnak 2005-11-03 13:42:30 UTC
Verified