|
From: <jue...@we...> - 2004-11-12 21:56:29
|
FYI, I've modified the TransactionProxyFactoryBean definitions in = Petclinic back to the simple direct version. The version with a = "baseTransactionProxy" in case of a single transaction proxy arguably = obscured the intent, at least in this simple sample = application.Petclinic is meant to be as bare bones and trivial as = possible, being useful as an example in introductory workshops that = illustrate very basic principles of a Spring middle tier. =20 On numerous occasions, I showed a Petclinic applicationContext.xml file = without having explained parent/child bean definitions before. I always = had to argue that this was using a parent bean definition here, but that = this parent/child stuff wasn't important for our current discussion. My = slides showed a direct TransactionProxyFactoryBean definition too.... = I'm convinced now that it is better for the intended Petclinic audience = to show the simple direct case. =20 I've left the "baseTransactionProxy" separation in JPetStore, though, = which is generally somewhat more sophisticated in its middle tier, with = multiple fine-grained DAOs etc. IMO, it is sufficient to show the = separation there; we don't need to build this into more than one sample = application. A parent/child TransactionProxyFactoryBean definition is = harder to understand than the simple direct case, after all, even it's = recommended for advanced usages. =20 Juergen |