[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

[adrian@jboss.org]

"timfox" wrote : What shouldn't happen is the system silently fails in subtle ways, as it does now.
  | 
  | Inferring whether the user wants to use XA on the basis of whether the CF implements the XA CF interfaces is not valid - there's nothing in the spec that says the the same class can't implement both the XA and non XA interfaces.
  | 

Like I said above. There's no way for the resource adapter to know that the administrator
configured a local connection manager. So there's no way for us avoid the
subtle failures when things get misconfigured.

ASIDE 

Well actually there is, you can try to make the **guess** based on whether
getXAResource()/getLocalTransaction() or nothing was invoked,
but you'd have to jump through a lot of hoops to delay initializing the connection
for as a long as possible so you can decide which api to use based on that call.

END-ASIDE

I don't consider a "workaround" a real use case.
We could add all sorts of config options to enable users to workaround potential 
bugs in other peoples code. 

But the YAGNI princple applies.
i.e. We'll do it when we really have to, e.g. all the Oracle jdbc driver workarouds we have.
Otherwise lets not over complicate the configuration with useless options which
only means the users can't see the wood for the trees.

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

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