Originally posted by Manish Hatwalne:
Exactly!!!
Couldn't agree more. In fact, such naive "best" questions often show that you're perceiving things without realizing the various frames of references & preferences.
Originally posted by Tim Holloway:
.....
Unlike cats, which must have meat to survive, human beings are quite capable of thriving on a meatless diet, and no few of us would certainly do better cutting back on the Big Macs. My own personal bent is that animals don't like to be killed any more than I would, so I try to oblige them. I can't classify myself as vegetarian, but I do prefer to keep the body count down. And frankly, this idea that people crave meat is purely psychological. While I can enjoy the occasional well-prepared meat dish, if I never had meat again it wouldn't ruin my gustatory life. Plus, I don't have to work as hard to keep my cholesterol down.
So, in short, don't let your diet constrain you. If you try, you'll probably find enough meat, and who knows - you might even discover you like the vegetarian life.
Now I have few questions:
A) Are the above mentioned, supported in weblogic 9.2 application server? If so, are there any deployment descriptor settings involved?
B) Is executing local/non-jta transaction SLOW in an application server that supports only JTA environment.
C) Does Spring's non-jta transaction manager usage overrides the default support of weblogic for JTA transactions?
If not what is the benefit of using Spring in weblogic in my application scenario, apart from the configuration based Dependency injection?
Decorators are often used when subclassing requires a large number of subclasses to support every possible combination needed – so many that subclassing becomes impractical. The Java IO library requires many different combinations of features which is why the decorator pattern is a good approach.