You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Weaver, Scott" <we...@ugs.com> on 2007/10/11 18:48:45 UTC
PortletWindowImpl is inconsistent after deserialization.
PortletWindowImpl marks its instance of PortletEntity as transient so as
to be serializable. Unfortunately, if PortletWindowImpl were to be
reserialized, it would be inconsistent as it has no PortletEntity
reference. I think we need to look at making PortletEntityImpl
serializable, or else I doubt our caching is going work very well.
-scott
RE: PortletWindowImpl is inconsistent after deserialization.
Posted by "Weaver, Scott" <we...@ugs.com>.
Well, when the portal running it seems everything is fine. I am
guessing as long as we aren't having the cache writing to disk (which is
the way I have the portletWindowCache configured) we will be ok with
non-serializable a PortletEntity.
-scott
> -----Original Message-----
> From: Weaver, Scott [mailto:weavers@ugs.com]
> Sent: Thursday, October 11, 2007 1:01 PM
> To: Jetspeed Developers List
> Subject: RE: PortletWindowImpl is inconsistent after deserialization.
>
> After looking at PortletEntityImpl, I realize make PortletEntityImpl
> serailizable is far from trivial as it contains quite a bit of
> non-serializable references itself. We probably should take a close
> look at refactoring this in 2.2.
>
> So, I guess I will need to do something fancy (fancy == nasty hack) in
> the EhPortletWindowCache to work around this.
>
>
> -scott
>
> > -----Original Message-----
> > From: Weaver, Scott [mailto:weavers@ugs.com]
> > Sent: Thursday, October 11, 2007 12:49 PM
> > To: Jetspeed Developers List
> > Subject: PortletWindowImpl is inconsistent after deserialization.
> >
> > PortletWindowImpl marks its instance of PortletEntity as transient
so
> as
> > to be serializable. Unfortunately, if PortletWindowImpl were to be
> > reserialized, it would be inconsistent as it has no PortletEntity
> > reference. I think we need to look at making PortletEntityImpl
> > serializable, or else I doubt our caching is going work very well.
> >
> >
> >
> >
> >
> > -scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: PortletWindowImpl is inconsistent after deserialization.
Posted by "Weaver, Scott" <we...@ugs.com>.
After looking at PortletEntityImpl, I realize make PortletEntityImpl
serailizable is far from trivial as it contains quite a bit of
non-serializable references itself. We probably should take a close
look at refactoring this in 2.2.
So, I guess I will need to do something fancy (fancy == nasty hack) in
the EhPortletWindowCache to work around this.
-scott
> -----Original Message-----
> From: Weaver, Scott [mailto:weavers@ugs.com]
> Sent: Thursday, October 11, 2007 12:49 PM
> To: Jetspeed Developers List
> Subject: PortletWindowImpl is inconsistent after deserialization.
>
> PortletWindowImpl marks its instance of PortletEntity as transient so
as
> to be serializable. Unfortunately, if PortletWindowImpl were to be
> reserialized, it would be inconsistent as it has no PortletEntity
> reference. I think we need to look at making PortletEntityImpl
> serializable, or else I doubt our caching is going work very well.
>
>
>
>
>
> -scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org