[jboss-jira] [JBoss JIRA] Commented: (JBAS-6504) Hot redeploy fails on existing VirtualFile root

[Ales Justin (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12452687#action_12452687 ] 

Ales Justin commented on JBAS-6504:
-----------------------------------

It looks like the old VirtualFile refs (and its corresponding (zip) vfs contexts) are still there.

Where I would expect them to be re-initialized with every navigation;
either hitting old cache in FileHandler or checkIfModified in ZipEntryContext.


> Hot redeploy fails on existing VirtualFile root
> -----------------------------------------------
>
>                 Key: JBAS-6504
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6504
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: VFS
>    Affects Versions: JBossAS-5.0.0.GA
>            Reporter: Ales Justin
>            Assignee: Ales Justin
>            Priority: Blocker
>             Fix For: JBossAS-5.0.1.GA
>
>
> Failing re-deploy on existing VirtualFile root ref.
> e.g.
> * comment deployers\seam.deployer\META-INF\seam-deployers-jboss-beans.xml 2nd bean (the one that makes deployment as a temp)
> * jboss-seam-booking.ear --> unpack
> You have the structure:
> * jboss-seam-booking.ear (unpacked)
> ** lib (dir)
> ** META-INF (dir)
> ** jboss-seam.jar (packed)
> ** jboss-seam-booking.jar (packed)
> ** jboss-seam-booking.war (packed)
> jboss-seam-booking.war has WEB-INF/lib:
> * few nested lib jars
> The war gets VFSUtils::unjar-ed in AbstractWebDeployer - the need for partly exploded strucutre --> tmp/<guid-dir>/jboss-seam-booking.war
> 1st deploy -- all is fine
> Change some .xml in .ear/META-INF --> re-deploy --> clears up temps
> ==> failure:
> Caused by: com.sun.faces.config.ConfigurationException:
>   Source Document: jndi:/localhost/seam-booking/WEB-INF/faces-config.xml
>   Cause: Unable to find class 'com.sun.facelets.FaceletViewHandler'
>         at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:248)
>         at com.sun.faces.config.processor.ApplicationConfigProcessor.setViewHandler(ApplicationConfigProcessor.java:382)
>         at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:231)
>         at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:108)
>         at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:119)
>         at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:108)
>         at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:132)
>         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
> Looks like the temps are properly restored,
> but the existing ZipEntryHandler/Context is not re-populated / initialized.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira