[jira] [Commented] (ROL-1962) "RuntimeConfigProperty cannot be cast to RuntimeConfigProperty" error when redeploying Roller trunk on GlassFish

["Glen Mazza (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ROL-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667929#comment-13667929 ] 

Glen Mazza commented on ROL-1962:
---------------------------------

Forgot to mention, the process I followed to deploy the WAR is precisely as I've documented in latest trunk version of the Install Guide, GlassFish chapter:
http://svn.apache.org/viewvc/roller/trunk/weblogger-docs/installguide/
                
> "RuntimeConfigProperty cannot be cast to RuntimeConfigProperty" error when redeploying Roller trunk on GlassFish
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: ROL-1962
>                 URL: https://issues.apache.org/jira/browse/ROL-1962
>             Project: Roller
>          Issue Type: Bug
>          Components: Installation
>    Affects Versions: 5.1
>            Reporter: Glen Mazza
>            Assignee: Roller Unassigned
>
> Using GlassFish 3.1.2.2 (most recent release) on Ubuntu 12.04, JDK 7, MySQL 5.5 and the j2ee version of the Roller WAR, obtainable from weblogger-war-assembly after running the build-javaee-release.sh.    The WAR will usually deploy fine, and once it deploys fine, Roller will work without error.  
> However, if I disable and then enable the WAR, within the first couple of iterations of doing so I'll get the "**LifecycleException: java.lang.RuntimeException: java.lang.ClassCastException: org.apache.roller.weblogger.**pojos.RuntimeConfigProperty cannot be cast to org.apache.roller.weblogger.**pojos.RuntimeConfigProperty" error message, normally requiring me to shut down GlassFish and restart it with a new deploy of the Roller WAR for Roller to work again (a WAR redeploy without a GlassFish shutdown only infrequently works.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira