private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
Configuring Multiple WebApp Source Directory
 |
available since jetty-6.1.12.rc2 and jetty-7.0.0pre3 |
It can be configured by passing Resource[], String[], or String (csv) in the constructor.
The primary resource(first in the list) is the main resource.
WEB-INF/lib and WEB-INF/classes are merged.
This basically means your dependent classes on webappA will be available in the classpath for webappB.
This feature enables webapp overlays.
Configuration in context.xml
Configuration in jetty-maven-plugin
|
When maven fails to dependency-inject overloaded resources, use: Note that for the other webapp sources, you can add them to the plugin's extra scan targets for dynamic reload. |
Example
Scenario:
Configuration:
<resources>webappY/src/main/webapp, webappX/src/main/webapp</resources>
Output:
Overlays
|
available since jetty-6.1.12.rc3 and jetty-7.0.0pre4 |
When using mvn jetty:run, you don't need to configure anything.
Just add a dependency like:
If configured manually, it would look like:
The order of the overlays depends on how you arrange the war dependencies in your pom.xml (top to bottom)