Uhh,
The use case is quite common actually to have one spring configuration xml and have
property files for your different environments like test,
production etc to minimize the configuration data and make for easy
deployment of a spring app. So nothing unusual there really...
But to stay on topic we just use the EJB timerservice with our spring
app and jBPM works fine.
Regards,
Leo
"kukeltje" wrote : anonymous wrote : That way no values would be "hard
coded" in the XML, but rather defined in the properties file. Ahhh cool...
"hardcoded" in a properties file instead of an xml file....
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184362#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...