[jboss-dev-forums] [Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

[weston.price@jboss.com]

anonymous wrote : 
  | The other part is whether this should be optional
  | 

I think it definitely should be. Note, this is the only provider that is exhibiting this behavior. I follow the rule of 'Always be able to shut it off' in JCA. 

anonymous wrote : 
  | The most optimal way of doing it (and also the most generic) 
  | would be store an "inExecute" reference count inside the WrappedStatement 
  | for the number of times the execute method is being invoked concurrently. 
  | 

Yep. I agree. 

anonymous wrote : 
  | Another issue is whether we should force a rollback of the transaction 
  | when somebody tries to commit but there are statements still being executed. 
  | 

Tricky because we would effectively be asserting that we *know* how to handle this situation better than the RDBMS. Again, perhaps a config option? 



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025524#4025524

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025524