StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POImplementation of ApplicationListener<ContextRefreshedEvent> prevents registration of @Scheduled & @Async methods
primarykey
Id
16809812
data
AcceptedAnswerId
16809979
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-29T09:09:06.223
FavoriteCount
0
LastActivityDate
2013-05-29T09:23:32.440
LastEditDate
2013-05-29T09:17:24.413
LastEditorUserId
1105946
OwnerUserId
1105946
ParentId
0
PostTypeId
1
Score
1
ViewCount
1131
LastEditorDisplayName
text
Body
I have a Service class in which I wish to invoke a method after the application context has been initialized and ALL the beans & annotations have been initialized and registered respectively: <pre><code> @Service public class EventGenerator implements ApplicationListener<ContextRefreshedEvent>{ static Logger logger = Logger.getLogger(EventGenerator.class); @Autowired private JsonQueryService service; @Override public void onApplicationEvent(ContextRefreshedEvent event) { generateFlights(); } @Async private void generateFlights(){ while(true){ try{ List<FlightJson> jsons = service.parseJSONFeed(); checkHexcodeAndMappings(jsons); updateSquark(jsons); Thread.sleep(10000); }catch(InterruptedException e){ e.printStackTrace(); } } } } </code></pre> I also have other @Scheduled and @Async annotations in the application. What I don't understand is why when I call the generateFlights() method, ALL the @Scheduled and @Async annotations in the application are not registered. If I do not call the generatFlights() method within the onApplicationEvent(ContextRefreshedEvent event) method, then the annotated methods are registered normally and the respective cron tasks / asynchronous methods run normally. Here is the root application context body (without namespace declarations): <pre><code><context:component-scan base-package="com.atlaschase.product.core"> <context:exclude-filter type="regex" expression="com.atlaschase.product.core.bootstrap.populators.*" /> <context:exclude-filter type="regex" expression="com.atlaschase.product.core.services.jms.*" /> <context:exclude-filter type="regex" expression="com.atlaschase.product.core.services.processor.*" /> <context:exclude-filter type="regex" expression="com.atlaschase.product.core.services.remote.*" /> </context:component-scan> <import resource="classpath:core-properties.xml" /> <import resource="classpath:core-datasource.xml" /> <import resource="classpath:core-task-scheduler.xml" /> </code></pre> Here is the core-task-scheduler.xml application context which contains details of executor configuration (again, namespaces ommitted): <pre><code><task:annotation-driven executor="executor" scheduler="scheduler"/> <task:executor id="executor" pool-size="1"/> <task:scheduler id="scheduler" pool-size="5"/> </code></pre> Any insight into why this might be happening would be appreciated. Thanks
Tags
<spring>
Title
Implementation of ApplicationListener<ContextRefreshedEvent> prevents registration of @Scheduled & @Async methods
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. UStotalcruise
UserOwnerUserId
1. UStotalcruise
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POImplementation of ApplicationListener<ContextRefreshedEvent> prevents registration of @Scheduled & @Async methods
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.