It then inserts the deployment descriptor files along with the corresponding application code and resources into the appropriate modules.
While it is theoretically possible to generate the required extended deployment descriptors manually, it is impractical to do so.
We do not specify this information in the example, though, because the deployment descriptor is packaged at development time.
EJB 3.0 supports partial XML deployment descriptors where you can define interceptor bindings that externalize matching an interceptor to a class.
These generated artifacts are deployment descriptors and helper classes.
You can see in Listing 3 that some elements in the deployment descriptor correspond to the JMS concepts of acknowledge mode, subscription durability, and message selector.
XML deployment descriptors can override annotations so you can externalize configurations and override Settings for different deployment environments.
You'll refer to this name in Part 2 when you write a deployment descriptor for your workflow.
We define this mapping in the deployment descriptor of the enterprise application.
