Hi
Thanks for the quick reply. But if you look at the following snippet of our
xml file, we have kept the xsd files (spring-beans.xsd and
servicemix-quartz.xsd) in local file system and giving the local reference
to the xsd files in the quartz.xml
xsi:schemaLocation="
http://www.springframework.org/schema/beans
file:///d:/deploy/spring-beans.xsd
http://servicemix.apache.org/quartz/1.0
file:///d:/deploy/servicemix-quartz.xsd"
and this works fine when we are placing the quartz.xml after making sure
that servicemix is running.
What I am suspecting is that ...
when I'm placing the quartz.xml file in the deploy directory then servicemix
is trying to register my quartz service "b:schedulerService" and to register
this service servicemix requires it's own system service "servicemix-quartz"
to be up.
So, when servicemix is up (meaning all it's system services are also up) and
then I'm placing my quartz.xml file in the deploy directory then my quartz
service is getting registered successfully.
But when I'm stoping and then starting the servicemix again without clearing
the deploy directory then my quartz.xml file remains there in the deploy and
servicemix is trying to register my quartz service "b:schedulerService" even
before servicemix's system service "servicemix-quartz" is up. And as I said
my quartz service might be dependent on "servicemix-quartz" so it's giving
the error.
Can you pls verify if I'm correct. And if so how to make sure that
servicemix will try to register my quartz.xml after all it's system services
are up.
If my understanding is not correct then also give me some guideline as to
how to proceed to solve my problem.
Thanks
in advance
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Problem-registering-quartz-service-tp3313453p3314808.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
