[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()
2:11 p.m.
Built-in async mechanism always returns null for Future.get()
-------------------------------------------------------------
Key: JBSEAM-3641
URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
Project: Seam
Issue Type: Bug
Components: Async
Affects Versions: 2.1.0.GA, 2.0.2.SP1
Environment: Linux, JBoss 4.2.2 GA
Reporter: toto titi
When trying to use the built-in async mechanism, I'm unable to obtain the result of
the asynchronous task using Future.get(). This always returns null.
TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No
error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
Code, observations and bug are detailed here:
http://www.seamframework.org/Community/AsynchronousFuturegetNull
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()
[
https://jira.jboss.org/jira/browse/JBSEAM-3641?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-3641.
-----------------------------
Resolution: Rejected
Assignee: Pete Muir
You return null from your method.
Built-in async mechanism always returns null for Future.get()
-------------------------------------------------------------
Key: JBSEAM-3641
URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
Project: Seam
Issue Type: Bug
Components: Async
Affects Versions: 2.0.2.SP1, 2.1.0.GA
Environment: Linux, JBoss 4.2.2 GA
Reporter: Gabriel Goïc
Assignee: Pete Muir
When trying to use the built-in async mechanism, I'm unable to obtain the result of
the asynchronous task using Future.get(). This always returns null.
TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No
error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
Code, observations and bug are detailed here:
http://www.seamframework.org/Community/AsynchronousFuturegetNull
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()
[
https://jira.jboss.org/jira/browse/JBSEAM-3641?page=com.atlassian.jira.pl...
]
Gabriel Goïc reopened JBSEAM-3641:
----------------------------------
From 2.1 GA's documentation (chapter 22 p. 396):
return timer; //note that return value is completely ignored
If it was due to my method returning null (Future is the returned type), I would not have
been able to do Future.get(), which returns null by the way.
As nothing is said about managing futures, I can only guess that it's just like
managing timers, apart from configuring components.xml.
However, injecting an EJB3 timer or a Future as documentation suggests:
@In Timer timer; or @In Future timer;
only fails with this error:
org.jboss.seam.RequiredException with message: "In attribute requires non-null value:
anyBean.timer"
so I can't return anything other than null to make the compiler happy. Either my
application lacks something that is not in the documentation, or this return value is not
that much ignored.
Built-in async mechanism always returns null for Future.get()
-------------------------------------------------------------
Key: JBSEAM-3641
URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
Project: Seam
Issue Type: Bug
Components: Async
Affects Versions: 2.0.2.SP1, 2.1.0.GA
Environment: Linux, JBoss 4.2.2 GA
Reporter: Gabriel Goïc
Assignee: Pete Muir
When trying to use the built-in async mechanism, I'm unable to obtain the result of
the asynchronous task using Future.get(). This always returns null.
TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No
error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
Code, observations and bug are detailed here:
http://www.seamframework.org/Community/AsynchronousFuturegetNull
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()
[
https://jira.jboss.org/jira/browse/JBSEAM-3641?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3641:
------------------------------
Fix Version/s: 2.1.2.CR1
Assignee: (was: Pete Muir)
Yes, there is a fundamental mismatch of ideas here.
1) java.util.concurrent expects you to return a real value from your async method which
can be got from Future.get()
2) Runnable can't return a result, whilst callable can.
Built-in async mechanism always returns null for Future.get()
-------------------------------------------------------------
Key: JBSEAM-3641
URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
Project: Seam
Issue Type: Bug
Components: Async
Affects Versions: 2.0.2.SP1, 2.1.0.GA
Environment: Linux, JBoss 4.2.2 GA
Reporter: Gabriel Goïc
Fix For: 2.1.2.CR1
When trying to use the built-in async mechanism, I'm unable to obtain the result of
the asynchronous task using Future.get(). This always returns null.
TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No
error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
Code, observations and bug are detailed here:
http://www.seamframework.org/Community/AsynchronousFuturegetNull
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()
[
https://jira.jboss.org/jira/browse/JBSEAM-3641?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3641:
------------------------------
Fix Version/s: The future
(was: 2.2.1.CR1)
Built-in async mechanism always returns null for Future.get()
-------------------------------------------------------------
Key: JBSEAM-3641
URL: https://jira.jboss.org/jira/browse/JBSEAM-3641
Project: Seam
Issue Type: Bug
Components: Async
Affects Versions: 2.0.2.SP1, 2.1.0.GA
Environment: Linux, JBoss 4.2.2 GA
Reporter: Gabriel Goïc
Fix For: The future
When trying to use the built-in async mechanism, I'm unable to obtain the result of
the asynchronous task using Future.get(). This always returns null.
TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No
error or misconfiguration has been seen even running in DEBUG or TRACE logging mode.
Code, observations and bug are detailed here:
http://www.seamframework.org/Community/AsynchronousFuturegetNull
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5373
days inactive
5822
days old
4 comments
3 participants
participants (3)
-
Gabriel Goïc (JIRA) -
Pete Muir (JIRA)
-
toto titi (JIRA)