Announcement Announcement Module
Collapse
No announcement yet.
NoSuchJobException: No job configuration with the name Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Nothing jumps out at me. Is the JobRegistryBeanPostProcessor in the same ApplicationContext as the "myJob" bean? It wouldn't work if it was in a parent context and the job was in a child context for instance (you'd have to install the post processor in both).

    Comment


    • #17
      Yes, it's in the same app context as the 'myJob' bean (names may have been changed in postings here to protect the our competitive advantage ) .

      Brian

      Comment


      • #18
        Does it work if you put depends-on="myJob" in your JobDetailsBean definition? The reference to the Job is through a bean id in the JobDetails, not an actual reference, so that won't force it to actually be instantiated. As far as I can see it can still only go wrong if the Quartz job runs before the Job has been registered. Can you put a debug breakpoint in the JobRegistry (or the bean processor) and see if it actually being called (unfortunately there is no logging there)?

        Comment

        Working...
        X