Re: [seam-dev] Porting package for Seam
On 22 Apr 2009, at 10:16, Shane Bryzak wrote:
SeamLoginModule for example.
You need to access identity from here I think? Making this kind of
association is harder using shared classloading, and you have to
investigate each case individually - normally the best way to do it is
to pass it using some context. In this case, I think you could
probably use Configuration for this purpose. Anyway, point is, you
can't safely use statics for wiring in modules anymore.
An alternative, if the lifecycle of a thing you need to wire in is
well defined, is to use a ThreadLocal static and try/finally semantics.
And how do we implement our static <component>.instance()
methods?
We should avoid implementing these in new modules. In the emulation
layer, we will impl it assuming an isolated classloader.
Pete Muir wrote:
> And what sort of classes aren't bean classes?
>
> On 22 Apr 2009, at 08:51, Pete Muir wrote:
>
>> Why do you need to do this? I can't see any reason for it.
>>
>> On 22 Apr 2009, at 02:18, Shane Bryzak wrote:
>>
>>> It seems that we need something like the webbeans porting package
>>> but for Seam, since we need to be able to get a reference to the
>>> current manager statically from non-bean classes. Any thoughts
>>> on this Pete?
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>> --
>> Pete Muir
>> http://www.seamframework.org
>> http://in.relation.to/Bloggers/Pete
>>
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete