I'm operating off 20081029. Do I have an old version?
The spec still talks about destroying a context e.g. in 8.5...
On 3 Nov 2008, at 15:47, Gavin King wrote:
> There is not really any such thing as a "destroyed context" anymore.
> (Context destruction is an event that sometimes occurs before a
> object moves into the inactive state.)
> So I'm not quite sure what you mean....
> On Mon, Nov 3, 2008 at 2:17 AM, Nicklas Karlsson
> <nickarls(a)gmail.com> wrote:
>> I didn't see anything in the Web Beans specs regarding what the
>> state of a destroyed context is if someone
>> happens to hold a reference. Throws a ContextNotActiveException?
> Gavin King
In case you have a minute or five, it would be good to start hearing what
kind of tooling we should consider adding for webbeans in the next rev of
Pete and I already did a few suggestions while we were in Copenhagen you
can see here:
If you got some concrete ones add them to jira directly or put the
suggestions on this list for dicsussion.
Here's the article i've been writing about web beans for developers.
It's almost finished, but I would appreciate a proofread/suggestions.
This has been done in docbook, so I'm thinking it can evolve into the
documentation for the RI (with addition of some new RI-specific
I've also attached the latest spec, which has some various fixes.
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?