Why are the Java Pet Store Demos configuration files so complicated?
A. They are complicated for the same reason that the dashboard of a fighter jet is more complicated than your car’s dashboard: because you’re controlling a lot more power and functionality. Deployment descriptors are complicated because they configure J2EE technology components and their containers. J2EE containers provide a high level of standard services (transactions, security, persistence, thread safety, etc.) to the components they manage, but the interface between the components and their container, as well as the container behavior, need to be configured. They’re also extremely flexible. These factors make J2EE deployment descriptors somewhat complex. Because deployment descriptors are XML documents, they can be edited manually. Most developers shouldn’t have to see them. Deployment descriptors are better created and maintained using the tools bundled with your J2EE environment. Powerful tools are one of the things a J2EE product customer should look for when selecting a platfor
