StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11695266
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-27T20:32:32.670
FavoriteCount
0
LastActivityDate
2012-07-27T20:32:32.670
LastEditDate
LastEditorUserId
0
OwnerUserId
971423
ParentId
5113239
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Another way of doing this is to implement the org.jboss.soa.esb.schedule.ScheduledEventListener class. As such your jboss-esb.xml would look like so: <pre><code><?xml version="1.0"?> <jbossesb parameterReloadSecs="5" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.0.xsd"> <providers> <schedule-provider name="myDaemonProvider"> <cron-schedule cronExpression="0 */1 * * * ?" scheduleid="my-daemon-trigger"/> </schedule-provider> </providers> <services> <service category="Cron" description="My Cron Daemon" name="MyDaemon"> <listeners> <scheduled-listener event-processor="com.myCompany.esb.myDaemon.main.MyDaemonScheduledEventListener" name="my-daemon-listener" scheduleidref="my-daemon-trigger"/> </listeners> </service> </services> </jbossesb> </code></pre> And then your com.myCompany.esb.myDaemon.main.MyDaemonScheduledEventListener would look like: <pre><code>package com.myCompany.esb.myDaemon.main; import org.jboss.soa.esb.ConfigurationException; import org.jboss.soa.esb.helpers.ConfigTree; import org.jboss.soa.esb.schedule.ScheduledEventListener; import org.jboss.soa.esb.schedule.SchedulingException; public class MyDaemonScheduledEventListener implements ScheduledEventListener { public void initialize(ConfigTree arg0) throws ConfigurationException { System.out.println("Initializing the Cron Daemon..."); } public void uninitialize() { System.out.println("Uninitializing the Cron Daemon..."); } public void onSchedule() throws SchedulingException { System.out.println("Scheduled Execution!"); } } </code></pre> So when you deploy this, it will cause the onSchedule() to run every minute.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to make an extremely simple cron job on JBoss ESB
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWelsh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to make an extremely simple cron job on JBoss ESB
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.