My turn to quote javadoc :-)
"The SystemException is thrown by the transaction manager to indicate that it has encountered an unexpected error condition that prevents future transaction services from proceeding."
Not really appropriate for a transient failure wrapped in an SQLExecption because
the tx has timed out or there's been a setRollbackOnly() due to an application
throwing a RuntimeException.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137846#4137846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137846
> SystemException is for serious failure isn't it?
Like being unable to determine the current timeout? :-)
int getTransactionTimeout() throws SystemException;
I picked SystemException to keep the API consistent, but I guess we could ignore that, or change getTransactionTimeout to throw IllegalStateException too.
Speaking of consistency, why does getTransactionTimeout() return int whilst getTimeLeftBeforeTransactionTimeout returns long?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137844#4137844
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137844
"ALRubinger" wrote : "adrian(a)jboss.org" wrote : No we should use constraints (version ranges). But we need to understand how that interacts with the release process and reproducability of tagged versions.
|
| Brian had this to say about current support for ranges:
|
| "#maven" wrote : ALR: Brian: Don't know if you're interested, we've been running into some conflicts regarding versioning and transitive dependencies in JBossAS build.
| | Brian: ugh
| | ALR: Some use cases are documented: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131748
| | Brian: FWIW, i never used ranges in my corp builds
| | ALR: Brian: Is that a vote for "don't Mavenize"? :)
| | Brian: no, just don't use ranges
|
| S,
| ALR
Is that confirmation that it doesn't understand 1.0.1 > 1.0.0 like I said above.
Or is that just his preference.
There's no way we can fix dependencies at single version given the number
of projects/releases we have.
It reminds me of when I started working on the JBossAS source code using
eclipse and wondered why it was so slow.
It had never been considered that the tool should scale to such a large project. ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137842#4137842
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137842