Hi, is it possible to use transaction annotations on a method of a SFSB to make it to not be part of the transaction?
The thing is I've got a login functionality that has some built in security that prevents login calls for 24 hours for a user that has failed to login more than X times in a row. If anything goes wrong in the login method, the transaction rollbacks the modified data as it should. But for when the user has submitted the wrong password for the username an integer should be incremented and a date for the last failed login should be filled in and written to persistance storage (db). As an application exception is thrown from the login method the integer and date fields are never filled in due to the transaction rollback. As I see it now, the only possible (horrible) solution is to make the client (web app) trigger the writing of the incremented data after receiving and interpreting the exception. Yikes. There has to be a better solution. Am I forced to use Bean Managed Transactions? Regards! /Henrik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932804#3932804 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932804 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
