During application startup, a component named scheduleController starts the jobs by calling an @Asynchronous method on component c1.
The other application uses another component named c1 for completely different purposes, it even isn't a job.
Now after redeploying the second application when Quartz want's to start the job of the first application, we get a NoSuchMethodException as the c1 of the second app is injected in the scheduler of the first app.
There seems to be some serious flaws either in our design or in seam or in tomcat in conjunction with seam...
Any help would be appreciated.