The Web Bean manager is essentially a singleton - stick it in a
static :)
As for the Bean object, give it a unique id and look it up in a Map.
Sent from my iPhone
On Nov 1, 2008, at 6:56 AM, "Nicklas Karlsson" <nickarls(a)gmail.com>
wrote:
HI,
I was looking at client proxy implementation and passivating scopes
and tried a javassist approach with a MethodHandler that
takes a Bean and a Manager as parameters in order to acquire the
current instance of the bean to execute methods on. The
problem is that Bean is not Serializable. Should it be or is the
approach wrong altogether?
The Manager isn't serializable either but it could be transient and
then looked up if it has become null but what would the
recommended way in the RI to reconstruct it? Take it from JNDI and
populate it with stuff stored away (in ThreadLocals?)
or some other way?
---
Nik
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev