[jbosscache-dev] Re: JBossCache_1_4_1_SP1 tagged
Manik Surtani
manik at jboss.org
Wed Jan 31 12:04:44 EST 2007
When did you introduce this use of non-serializable objects? The
exception on line 318 in the TreeCacheMarshaller has been around
since 1.4.0.GA.
Anyway, I can change this in TCM based on whether jboss serialization
is being used, it's easy enough and does make sense.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik at jboss.org
Telephone: +44 7786 702 706
MSN: manik at surtani.org
Yahoo/AIM/Skype: maniksurtani
On 31 Jan 2007, at 15:23, Ben Wang wrote:
> Manik,
>
> Upon a closer look, the reason that it is failing now is because
> from PojoCache, we allow to replicate non-Seriliazable object if we
> use JBossSerialization. But it seems now that
> TreeCacheMarshaller140 (line 318) has tightened up the criteria to
> throw exception when it is non-Serializable. So what's your
> suggestion?
>
> -Ben
>
> -----Original Message-----
> From: Manik Surtani [mailto:manik at jboss.org]
> Sent: Wednesday, January 31, 2007 10:14 AM
> To: jbosscache-dev at lists.jboss.org; Ben Wang
> Subject: JBossCache_1_4_1_SP1 tagged
>
> Tagged and *almost* ready for QA.
>
> There are 2 AOP tests that seem to fail quite consistently, apart
> from that it is looking pretty stable.
>
> Ben, do you think you'd have a moment to have a quick look? I
> can't imagine what has changed on the AOP side of things on this
> branch.
>
> The tests are
>
> org.jboss.cache.aop.collection.CachedListImplAopTest
> org.jboss.cache.aop.ReplicatedSerializableAopTest
>
> Thanks,
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik at jboss.org
> Telephone: +44 7786 702 706
> MSN: manik at surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
>
>
More information about the jbosscache-dev
mailing list