[ http://issues.apache.org/jira/browse/JS2-155?page=history ]
Ate Douma closed JS2-155:
-------------------------
Resolution: Fixed
Fix Version: 2.0-M2
The latest cvs head seems to have this fixed by using a more appropriate
cross-context dispatch implementation. The problem was a cross-context invoked
pa still received the portal session.
Now that that is over, hotdeployment doesn't throw these class cast exceptions
anymore.
> Redeploy causes class cast exceptions
> -------------------------------------
>
> Key: JS2-155
> URL: http://issues.apache.org/jira/browse/JS2-155
> Project: Jetspeed 2
> Type: Bug
> Versions: 2.0-dev/cvs
> Reporter: David Sean Taylor
> Assignee: David Sean Taylor
> Fix For: 2.0-dev/cvs, 2.0-M2
>
> Redeploying causes class cast exceptions because of data stored in the
> session.
> I've seen this happen specifically with the MyFaces portlet and another
> scenario. We need to capture this and try to remove the old object from the
> session and replace it with a new one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
