anchor.diff:  . Congratulations! You have created a dynamic module that is easy to maintain alongside your application.
   
   
  -== Creating an advanced dynamic module
  +== Creating an advanced dynamic module (EAR)
   
   So we have seen how to create a dynamic module comprised of just a single JAR. But it is also possible to create a dynamic module comprised of multiple JARs, as well as one that depends on other modules. This can be useful if we have several JARs we want to expose to our application as a unit (create a module), that also will change often alongside our application (choose a dynamic module over static).
   
  
positive.code: 
  NOTE: We can choose any name for the module, slot, or directory within `modules`. By convention, we name the module similarly to the package or Maven coordinates. The slot name we use here is the version, since a main module for joda-time already exists (with the same name).
  
  == Creating a dynamic module
  
  Static modules are good for creating common libraries that can be shared among multiple deployments--especially when those common libraries do not change often. But what if we have common libraries we want to make available but update almost as often as our application? Creating a dynamic module may be the right choice, since we can update it just like any other deployed artifact.
  
  
negative.code: = JBoss Modules with EAP by Example
  :toc: left
  :toclevels: 4
  :numbered:
  