Re: FW: Caching XMLResourceBundle in a disk persistent store not possible

[Joerg Heinicke <jo...@gmx.de>]

 From what I see the only reason for not implementing Serializable is 
that XMLResourceBundle will miss its dependencies after deserialization, 
which is only the Logger which has to be injected by the component 
manager. So every call to getLogger() would return null after the 
deserialization. In 2.2 this is probably no longer a problem since there 
the logger is instantiated with the object.

Joerg

On 21.10.2008 17:57, Laurent Medioni wrote:
> Hi, as I did not have many answers on the users list, maybe the dev side
> has a better idea ?
> Thanks.
> 
> -----Original Message-----
> From: Laurent Medioni [mailto:lmedioni@odyssey-group.com] 
> Sent: mercredi, 15. octobre 2008 13:33
> To: users@cocoon.apache.org
> Subject: Caching XMLResourceBundle in a disk persistent store not
> possible
> 
> Hi,
> Our process of assembling a XMLResourceBundle being quite costly, I
> tried to use the core store, configured to be disk persistent.
> That is when I realised that XMLResourceBundle is not Serialisable
> (well, one of the log files told me first...).
> 
> Do you see any reason why XMLResourceBundle could not be Serialisable ?
> (quite weird as it is supposed to represent a serialized file ;))


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org