[jboss-dev-forums] [Design of EJB 3.0] - Re: ejb3 user transaction and serlvets
adrian@jboss.org
do-not-reply at jboss.com
Mon Dec 1 10:12:59 EST 2008
"wolfc" wrote : The ejb3 logic shouldn't contain the determination whether this function is available or not.
| If we continue that logic than everybody who wants some service needs to have optional checks. Now we install 1 dummy service containing no logic.
| That's why I want the EJB3UserTransactionProvider depend on UserTransactionRegistry.
You're not listening. If you do that then its very hard to make the transactional
stuff optional or on-demand. Your way requires everything to be installed at
the start which isn't what we want further down the road for jboss5.
Things should only be created if they are actually needed/used.
e.g. No outbound connection factories means no CCM means no listeners on user transactions.
There should be no dummy/mock anything.
All if you to do is write:
if (blah != null)
like any normal programmer does around optional/configurable behaviour.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193477#4193477
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193477
More information about the jboss-dev-forums
mailing list