Hi!

Tilmann Ludwig wrote:
> I've tested the new passivating caches for statefull session beans in Beta
> Pr 3 with
> some beans. These beans worked perfectly in weblogic 5.1 (also with
> passivation).
> In JBOSS 2.0, only the public memeber attributes of the beans were saved and
> restored
> through serialization where in weblogic, also the private member attributes
> were restored.
> In the ejb spec, there's only a note about transient fields and nothing
> about private/public specifier.
> >From the source code of jboss, it is clear that only public fields were
> accepted, so is this a bug or a feature
> or missed i something?

It's a bug, or rather it was a bug. I have located and fixed it
(StatefulSessionFilePersistenceManager was badly coded).

The fix is in CVS. Thanks for pointing this out :-)

regards,
  Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to