StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2269177
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-02-15T21:50:51.047
FavoriteCount
0
LastActivityDate
2010-02-15T21:50:51.047
LastEditDate
LastEditorUserId
0
OwnerUserId
21234
ParentId
2269126
PostTypeId
2
Score
46
ViewCount
0
LastEditorDisplayName
text
Body
The <code>TaskExecutor</code> interface is a fire-and-forget interface, for use when you don't care when the task finishes. It's the simplest async abstraction that Spring offers. There is , however, an enhanced interface, <a href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/core/task/AsyncTaskExecutor.html#submit(java.lang.Runnable)" rel="noreferrer"><code>AsyncTaskExecutor</code></a>, which provides additional methods, including <code>submit()</code> methods that return a <code>Future</code>, which let you wait on the result. Spring provides the <a href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/scheduling/concurrent/ThreadPoolTaskExecutor.html" rel="noreferrer"><code>ThreadPoolTaskExecutor</code></a> class, which implement both <code>TaskExecutor</code> and <code>AsyncTaskExecutor</code>. In your specific case, I would re-implement the <code>Runnable</code> as a <code>Callable</code>, and return the <code>commandResults</code> from the <code>Callable.call()</code> method. The <code>getCommandResults</code> method can then be reimplemented as: <pre><code>public List<String> getCommandResults(String command) { Future<List<String>> futureResults = taskExecutor.submit(new CommandTask(command)); return futureResults.get(); } </code></pre> This method will submit the task asynchronously, and then wait for it to complete before returning the results returned from the <code>Callable.call()</code> method. This also lets you get rid of the <code>commandResults</code> field.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Spring threading and TaskExecutor, how do I know when a thread is finished?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USskaffman
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COA very helpful answer. It was the final answer above that completed the fix, but I wouldn't have fully understood it with out your answer, thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USBill

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.