7:22 a.m.
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks.
Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which
prevents Cron from running properly with Weld. I have been able to carry on developing
Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module
it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions
will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will
work with the version of Weld already deployed in JBoss AS and Glassfish, which will
contain the bug. The workaround mentioned in the bug report is to deep copy the
InvocationContext. I attempted to do this by serialising and unserialising the
InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any
advice for me about how I might be able to work around this bug to support existing
versions of Weld?
Cheers,
Pete R
11:31 a.m.
Pete,
Creating a separate thread from an @AroundInvoke interceptor and using that to proceed()
is not actually supported by the Interceptors spec.
"Around-invoke methods run in the same Java call stack as the associated target
method." (page 6) - which is clearly not the case here
Nevertheless, I'll try to improve the handling in jboss-interceptors (which is used by
weld) to handle this use case properly. The invocationcontext is not serializable, but it
can be cloned using specific stuff from jboss-interceptors, so we can activate that as a
workaround for extant versions of JBoss/Glasssfish/Weld. I'll send a patch on how to
do that on the issue itself.
Hope this helps,
Marius
----- Original Message -----
From: "Peter Royle" <howardmoon(a)screamingcoder.com>
To: "Weld-Dev" <weld-dev(a)lists.jboss.org>
Cc: "Seam-Dev" <seam-dev(a)lists.jboss.org>
Sent: Friday, May 13, 2011 8:22:54 AM
Subject: [weld-dev] WELD-862 and Seam Cron
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks.
Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which
prevents Cron from running properly with Weld. I have been able to carry on developing
Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module
it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions
will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will
work with the version of Weld already deployed in JBoss AS and Glassfish, which will
contain the bug. The workaround mentioned in the bug report is to deep copy the
InvocationContext. I attempted to do this by serialising and unserialising the
InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any
advice for me about how I might be able to work around this bug to support existing
versions of Weld?
Cheers,
Pete R
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
1:15 a.m.
Hi Marius,
Thanks, that's hugely helpful. I hadn't realised that my implementation was
outside the Interceptors spec. I guess in that case the ideal solution is one which works
within the bounds of the spec (ie: the deep-copy "workaround"). I will try that
out as soon as you are able to provide the patch/sample for how to do so (I had a dig
around but couldn't work it out unfortunately). If I notice any significant
performance implications with that approach I'll report back here for further advice.
Cheers,
Pete R.
On 14/05/2011, at 2:31 AM, Marius Bogoevici wrote:
Pete,
Creating a separate thread from an @AroundInvoke interceptor and using that to proceed()
is not actually supported by the Interceptors spec.
"Around-invoke methods run in the same Java call stack as the associated target
method." (page 6) - which is clearly not the case here
Nevertheless, I'll try to improve the handling in jboss-interceptors (which is used
by weld) to handle this use case properly. The invocationcontext is not serializable, but
it can be cloned using specific stuff from jboss-interceptors, so we can activate that as
a workaround for extant versions of JBoss/Glasssfish/Weld. I'll send a patch on how to
do that on the issue itself.
Hope this helps,
Marius
From: "Peter Royle" <howardmoon(a)screamingcoder.com>
To: "Weld-Dev" <weld-dev(a)lists.jboss.org>
Cc: "Seam-Dev" <seam-dev(a)lists.jboss.org>
Sent: Friday, May 13, 2011 8:22:54 AM
Subject: [weld-dev] WELD-862 and Seam Cron
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks.
Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which
prevents Cron from running properly with Weld. I have been able to carry on developing
Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module
it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future
versions will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will
work with the version of Weld already deployed in JBoss AS and Glassfish, which will
contain the bug. The workaround mentioned in the bug report is to deep copy the
InvocationContext. I attempted to do this by serialising and unserialising the
InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any
advice for me about how I might be able to work around this bug to support existing
versions of Weld?
Cheers,
Pete R
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
1:46 a.m.
Hi Pete,
NP - I'll try to put up a patch today (Monday EDT). It's going to be a bit
cumbersome for the current versions of Weld, as we need to use reflection - unfortunately
the current implementation of jboss-interceptors simply doesn't account for this use
case, but at least we can get something working.
Hopefully, future versions of Weld will be able to support this in a much smoother
fashion.
----- Original Message -----
From: "Peter Royle" <howardmoon(a)screamingcoder.com>
To: "Marius Bogoevici" <mariusb(a)redhat.com>
Cc: "Seam-Dev" <seam-dev(a)lists.jboss.org>, "Weld-Dev"
<weld-dev(a)lists.jboss.org>
Sent: Monday, May 16, 2011 2:15:49 AM
Subject: Re: [weld-dev] WELD-862 and Seam Cron
Hi Marius,
Thanks, that's hugely helpful. I hadn't realised that my implementation was
outside the Interceptors spec. I guess in that case the ideal solution is one which works
within the bounds of the spec (ie: the deep-copy "workaround"). I will try that
out as soon as you are able to provide the patch/sample for how to do so (I had a dig
around but couldn't work it out unfortunately). If I notice any significant
performance implications with that approach I'll report back here for further advice.
Cheers,
Pete R.
On 14/05/2011, at 2:31 AM, Marius Bogoevici wrote:
Pete,
Creating a separate thread from an @AroundInvoke interceptor and using that to proceed()
is not actually supported by the Interceptors spec.
"Around-invoke methods run in the same Java call stack as the associated target
method." (page 6) - which is clearly not the case here
Nevertheless, I'll try to improve the handling in jboss-interceptors (which is used by
weld) to handle this use case properly. The invocationcontext is not serializable, but it
can be cloned using specific stuff from jboss-interceptors, so we can activate that as a
workaround for extant versions of JBoss/Glasssfish/Weld. I'll send a patch on how to
do that on the issue itself.
Hope this helps,
Marius
----- Original Message -----
From: "Peter Royle" < howardmoon(a)screamingcoder.com >
To: "Weld-Dev" < weld-dev(a)lists.jboss.org >
Cc: "Seam-Dev" < seam-dev(a)lists.jboss.org >
Sent: Friday, May 13, 2011 8:22:54 AM
Subject: [weld-dev] WELD-862 and Seam Cron
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks.
Currently there is an outstanding issue ( https://issues.jboss.org/browse/WELD-862 ) which
prevents Cron from running properly with Weld. I have been able to carry on developing
Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module
it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions
will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will
work with the version of Weld already deployed in JBoss AS and Glassfish, which will
contain the bug. The workaround mentioned in the bug report is to deep copy the
InvocationContext. I attempted to do this by serialising and unserialising the
InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any
advice for me about how I might be able to work around this bug to support existing
versions of Weld?
Cheers,
Pete R
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
5:37 p.m.
Hi Marius,
I have seen the patch and thorough explanation you put on the JIRA, thanks a lot for that.
I am also talking with Stuart Douglas on IRC about a possible portable solution using
ThreadLocal. I will refer probably try both ways and see which suits best just to be sure.
Will report how it goes.
Thanks,
Pete R
On 16/05/2011, at 4:46 PM, Marius Bogoevici wrote:
Hi Pete,
NP - I'll try to put up a patch today (Monday EDT). It's going to be a bit
cumbersome for the current versions of Weld, as we need to use reflection - unfortunately
the current implementation of jboss-interceptors simply doesn't account for this use
case, but at least we can get something working.
Hopefully, future versions of Weld will be able to support this in a much smoother
fashion.
From: "Peter Royle" <howardmoon(a)screamingcoder.com>
To: "Marius Bogoevici" <mariusb(a)redhat.com>
Cc: "Seam-Dev" <seam-dev(a)lists.jboss.org>, "Weld-Dev"
<weld-dev(a)lists.jboss.org>
Sent: Monday, May 16, 2011 2:15:49 AM
Subject: Re: [weld-dev] WELD-862 and Seam Cron
Hi Marius,
Thanks, that's hugely helpful. I hadn't realised that my implementation was
outside the Interceptors spec. I guess in that case the ideal solution is one which works
within the bounds of the spec (ie: the deep-copy "workaround"). I will try that
out as soon as you are able to provide the patch/sample for how to do so (I had a dig
around but couldn't work it out unfortunately). If I notice any significant
performance implications with that approach I'll report back here for further advice.
Cheers,
Pete R.
On 14/05/2011, at 2:31 AM, Marius Bogoevici wrote:
Pete,
Creating a separate thread from an @AroundInvoke interceptor and using that to proceed()
is not actually supported by the Interceptors spec.
"Around-invoke methods run in the same Java call stack as the associated target
method." (page 6) - which is clearly not the case here
Nevertheless, I'll try to improve the handling in jboss-interceptors (which is used
by weld) to handle this use case properly. The invocationcontext is not serializable, but
it can be cloned using specific stuff from jboss-interceptors, so we can activate that as
a workaround for extant versions of JBoss/Glasssfish/Weld. I'll send a patch on how to
do that on the issue itself.
Hope this helps,
Marius
From: "Peter Royle" <howardmoon(a)screamingcoder.com>
To: "Weld-Dev" <weld-dev(a)lists.jboss.org>
Cc: "Seam-Dev" <seam-dev(a)lists.jboss.org>
Sent: Friday, May 13, 2011 8:22:54 AM
Subject: [weld-dev] WELD-862 and Seam Cron
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks.
Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which
prevents Cron from running properly with Weld. I have been able to carry on developing
Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module
it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future
versions will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will
work with the version of Weld already deployed in JBoss AS and Glassfish, which will
contain the bug. The workaround mentioned in the bug report is to deep copy the
InvocationContext. I attempted to do this by serialising and unserialising the
InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any
advice for me about how I might be able to work around this bug to support existing
versions of Weld?
Cheers,
Pete R
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
8:34 p.m.
Hi Pete,
I see that now. Stuart's idea of is much better than cloning the
invocation context, as it will guarantee that the whole chain is
processed correctly. Cloning the invocation context will still result in
issues with decorators, in the least I can tell that for Weld.
Marius
Peter Royle wrote:
Hi Marius,
I have seen the patch and thorough explanation you put on the JIRA,
thanks a lot for that. I am also talking with Stuart Douglas on IRC
about a possible portable solution using ThreadLocal. I will refer
probably try both ways and see which suits best just to be sure. Will
report how it goes.
Thanks,
Pete R
On 16/05/2011, at 4:46 PM, Marius Bogoevici wrote:
> Hi Pete,
>
> NP - I'll try to put up a patch today (Monday EDT). It's going to be
> a bit cumbersome for the current versions of Weld, as we need to use
> reflection - unfortunately the current implementation of
> jboss-interceptors simply doesn't account for this use case, but at
> least we can get something working.
>
> Hopefully, future versions of Weld will be able to support this in a
> much smoother fashion.
>
> ------------------------------------------------------------------------
> *From: *"Peter Royle" <howardmoon(a)screamingcoder.com
> <mailto:howardmoon@screamingcoder.com>>
> *To: *"Marius Bogoevici" <mariusb(a)redhat.com
<mailto:mariusb@redhat.com>>
> *Cc: *"Seam-Dev" <seam-dev(a)lists.jboss.org
> <mailto:seam-dev@lists.jboss.org>>, "Weld-Dev"
> <weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>>
> *Sent: *Monday, May 16, 2011 2:15:49 AM
> *Subject: *Re: [weld-dev] WELD-862 and Seam Cron
>
> Hi Marius,
>
> Thanks, that's hugely helpful. I hadn't realised that my
> implementation was outside the Interceptors spec. I guess in that
> case the ideal solution is one which works within the bounds of the
> spec (ie: the deep-copy "workaround"). I will try that out as soon as
> you are able to provide the patch/sample for how to do so (I had a
> dig around but couldn't work it out unfortunately). If I notice any
> significant performance implications with that approach I'll report
> back here for further advice.
>
> Cheers,
>
> Pete R.
>
>
> On 14/05/2011, at 2:31 AM, Marius Bogoevici wrote:
>
> Pete,
>
> Creating a separate thread from an @AroundInvoke interceptor and
> using that to proceed() is not actually supported by the
> Interceptors spec.
>
> "Around-invoke methods run in the same Java call stack as the
> associated target method." (page 6) - which is clearly not the
> case here
>
> Nevertheless, I'll try to improve the handling in
> jboss-interceptors (which is used by weld) to handle this use
> case properly. The invocationcontext is not serializable, but it
> can be cloned using specific stuff from jboss-interceptors, so we
> can activate that as a workaround for extant versions of
> JBoss/Glasssfish/Weld. I'll send a patch on how to do that on the
> issue itself.
>
> Hope this helps,
> Marius
>
> ------------------------------------------------------------------------
> *From: *"Peter Royle" <howardmoon(a)screamingcoder.com
> <mailto:howardmoon@screamingcoder.com>>
> *To: *"Weld-Dev" <weld-dev(a)lists.jboss.org
> <mailto:weld-dev@lists.jboss.org>>
> *Cc: *"Seam-Dev" <seam-dev(a)lists.jboss.org
> <mailto:seam-dev@lists.jboss.org>>
> *Sent: *Friday, May 13, 2011 8:22:54 AM
> *Subject: *[weld-dev] WELD-862 and Seam Cron
>
> Hi,
>
> I'm aiming to make a release of Seam Cron available within the
> next two weeks. Currently there is an outstanding issue
> (https://issues.jboss.org/browse/WELD-862) which prevents Cron
> from running properly with Weld. I have been able to carry on
> developing Cron by testing it against OpenWebBeans, but obviously
> if we are to release a Seam module it should work against Weld.
>
> It would be nice if WELD-862 could be fixed as soon a possible so
> that all future versions will work well with Cron.
>
> But more importantly I also probably need to do something special
> in Cron so that it will work with the version of Weld already
> deployed in JBoss AS and Glassfish, which will contain the bug.
> The workaround mentioned in the bug report is to deep copy the
> InvocationContext. I attempted to do this by serialising and
> unserialising the InvocationContext but couldn't due to
> UnserializableExceptions. Does anyone have any advice for me
> about how I might be able to work around this bug to support
> existing versions of Weld?
>
> Cheers,
>
> Pete R
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
>
------------------------------------------------------------------------
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
2:51 a.m.
Hey, en lisant tout ce truc technique, je me suis rendu compte que j’avais besoin d’une
pause pour me détendre un peu. J’ai essayé https://play-jonny-casino.com/fr-fr/ pour me
changer les idées. Mes premiers tours ont été quelques petites pertes, ce qui était un peu
frustrant, mais après avoir pris un risque un peu plus grand, j’ai eu un gain correct qui
m’a vraiment remonté le moral. Pour les joueurs de France, le service offre aussi des
bonus spéciaux, ce qui rend l’expérience encore plus agréable et motivante.
7:56 a.m.
16027 N State Road 156, Patriot, IN 47038
The most well-known cryptocurrency in the world, Bitcoin, has become extremely popular in
recent years. More people and companies are adopting Bitcoin and other cryptocurrencies as
a form of investment due to their anarchic framework and high return potential.
Nevertheless, the emergence of Bitcoin has also given rise to a number of security issues,
resulting in instances of lost or unreachable Bitcoins. Consequently, there is an enormous
increase in demand for expert Bitcoin recovery services. Ever felt like your heart sinks
when you realise you can’t get to your Bitcoin? There is a bigger demand than ever for
trustworthy Bitcoin recovery services due to the rising popularity of Bitcoin and other
cryptocurrency. The security risks connected with Bitcoin are growing along with its value
and use. There are several possibilities for consumers to lose access to their priceless
digital assets, including device malfunctions, cyberattacks, and forgotten passwords and
wallet seeds. smith white hack service can help in this situation. smith white hack
service is the legitimate sidekick when it comes to obtaining your unidentified or
unaccessible Bitcoins back. Years of experience and unmatched knowledge have allowed them
to assist many people in regaining access to their digital assets. smith white hack
service provides specialized solutions that increase your chances of getting your Bitcoins
back by analyzing your particular circumstances and using cutting-edge recovery methods. I
will suggest your urgent request for support from smith white hack services team through:
Do not get left behind. Contact smith white hack service through
Email:SMITHWHITEHACKSERVICE@GMAIL COM And also on WhatsApp +1 559 - 508 - 2403
27
days inactive
5390
days old
7 comments
5 participants
participants (5)
-
Alex Henry -
Marius Bogoevici -
Marius Bogoevici -
Nixia Silvia -
Peter Royle