7:18 p.m.
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?
1:51 a.m.
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
1:52 a.m.
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
3:16 a.m.
SeamLoginModule for example. And how do we implement our static
<component>.instance() methods?
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
5:29 a.m.
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
1:57 p.m.
On Wed, Apr 22, 2009 at 6:29 AM, Pete Muir <pmuir(a)redhat.com> wrote:
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.
Amen. That's what made testing the internals of Seam so tricky.
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
3:32 p.m.
On 22 Apr 2009, at 20:57, Dan Allen wrote:
On Wed, Apr 22, 2009 at 6:29 AM, Pete Muir <pmuir(a)redhat.com>
wrote:
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.
Amen. That's what made testing the internals of Seam so tricky.
For example, Sun just made a contribution to Web Beans that no longer
requires us to use Web Beans as an isolated jar (use of singleton
statics) but instead use a shared library - we'll probably switch to
this mode in JBoss in the next release...
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than
a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a
message if
you feel that it did not reach my attention.
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
5728
days inactive
5728
days old
6 comments
3 participants
participants (3)
-
Dan Allen -
Pete Muir -
Shane Bryzak