StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8073664
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-10T00:33:40.583
FavoriteCount
0
LastActivityDate
2011-11-10T00:38:41.280
LastEditDate
2017-05-23T12:29:12.327
LastEditorUserId
-1
OwnerUserId
157882
ParentId
8073408
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Yes, that's definitely a good idea. You should only do it with an extreme care. Here's some food for thought: <ul> <li><a href="https://stackoverflow.com/questions/6149919/is-it-safe-to-start-a-new-thread-in-a-jsf-managed-bean">Is it safe to start a new thread in a JSF managed bean?</a></li> <li><a href="https://stackoverflow.com/questions/7499534/applicationscope-bean-that-uses-a-timertask-sheduler-good-or-bad">Spawning threads in a JSF managed bean for scheduled tasks using a timer</a></li> </ul> As you're using Tomcat, which does not support EJB out the box (and thus <code>@Asynchronus</code> <code>@Singleton</code> is out of question), I'd create an application scoped bean which holds an <a href="http://download.oracle.com/javase/6/docs/api/java/util/concurrent/ExecutorService.html" rel="nofollow noreferrer"><code>ExecutorService</code></a> to process the mail tasks. Here's a kickoff example: <pre><code>@ManagedBean(eager=true) @ApplicationScoped public class TaskManager { private ExecutorService executor; @PostConstruct public void init() { executor = Executors.newSingleThreadExecutor(); } public <T> Future<T> submit(Callable<T> task) { return executor.submit(task); } // Or just void submit(Runnable task) if you want fire-and-forget. @PreDestroy public void destroy() { executor.shutdown(); } } </code></pre> This creates a single thread and puts the tasks in a queue. You can use it in normal beans as follows: <pre><code>@ManagedBean @RequestScoped public class Register { @ManagedProperty("#{taskManager}") private TaskManager taskManager; public void submit() { // ... taskManager.submit(new MailTask(mail)); // You might want to hold the return value in some Future<Result>, but // you should store it in view or session scope in order to get result // later. Note that the thread will block whenever you call get() on it. // You can just ignore it altogether (as the current example is doing). } } </code></pre> To learn more about <code>java.util.concurrent</code> API, refer the <a href="http://download.oracle.com/javase/tutorial/essential/concurrency/index.html" rel="nofollow noreferrer">official tutorial</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMail Sending with a special thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USBalusC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMail Sending with a special thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.