in my case, i want keep the Timer at the Hypersonic because: 1. The production database is very busy, and sometimes the database is off (I mean, its avaliable "only" 98% of the time, but I cant trust on 98%, and the hypersonic is 99,99% avaliable, because it is used only for the timers, in fact, untill now the hypersonic is 100% avaliable)
2. I wont need change the default jboss configurations (the DatabaseTimer at ejb-deployer.xml) and I have discovered another thing: the suggestion about calling the "shedule" method trough the @Local interface does not work! I thought it had worked, but now I can see the difference: when the method "contextInitialized" of my servlet class is called, this method isnt in a EJB Transaction... thats why it can call the "schedule" method without problems.... so, now, inside a method managed by the container I want to use two datasources, this is the main problem first, one datasource to get the interval then, persist the timer is there a simple way to complete the first transaction before call the "schedule" method? I thought using interceptors to schedule the method after the execution of the first method, but then I read the docs and it says that the interceptors use the same transaction I am thinking about just changing the jta aspect to allow multiple datasources.... because I can trust my data wont be corrupted (because they are two different transactions in fact) thanks again for your help regards, RRR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139634#4139634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139634 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
