So, what you are saying is that in the case of Informix, the statement should be attempted twice? This can be accomplished via coding. There is nothing to prevent your code from catching the exception, evaluating the code, and attempting to execute the statement a second time.
JCA is agnostic in terms of DB exceptions, coding for this particular case would imply that we 'know' of a specific INFORMIX error and attempt to execute the query again. Sorry, but it just doesn't seem to be a valid use case in this context. I can rework the INFORMIX exception sorter to not fail in the case of this particular error, effectively putting it back the way it was. The connection would still be valid in this case allowing you to execute the statement again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950963#3950963 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950963 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
