Results 1 to 2 of 2

Thread: Should I create a Class path job locator ?

  1. Jun 17th, 2008, 11:13 PM #1
    stephenbute
    stephenbute is offline Junior Member
    Join Date
    Jan 2008
    Posts
    10

    Question Should I create a Class path job locator ?

    My case is that I am using a MDB to call the JobLauncher to launch jobs.

    And I want to separate the MDB , the JobLauncher config with the jobs config.

    And the jobs config folder is set in the MDB descriptor (ejb-jar.xml) .

    User may dynamic upload the job definition config into that folder. The job locator will be aware of the change of that folder.

    By all this, I want to deploy new job without restarting the MDB.

    It seems the current MapJobRegistry and ReferenceJobFactory can not fulfill my requirement.

    So should I create a class path job locator to load the jobs config ? Any suggestion from Spring ?

    Am I wrong ?

    thanks in advance.
    Last edited by stephenbute; Jun 18th, 2008 at 01:26 AM.
    Reply With Quote Reply With Quote
  2. Jun 18th, 2008, 06:20 AM #2
    Dave Syer
    Dave Syer is offline Senior Member
    Join Date
    Jun 2005
    Posts
    4,230

    Default

    You are right. The samples contain a ClasspathXmlApplicationContextJobFactory for this purpose (promoted to core in 1.1).
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules