public class WARManifestProcessor extends Object
Constants.WEB_BUNDLE_SCHEME,
our registered handler gets a chance to look at the stream and process the
MANIFEST.MF. It adds necessary OSGi metadata as specified in section #5.2.1.2
of RFC #66. It uses the following information during computation:
- WAR manifest entries, i.e., developer supplied data
- Properties supplied via URL query parameters
- Other information present in the WAR, e.g., existence of any jar in
WEB-INF/lib causes that jar to be added as Bundle-ClassPath.
For exact details, refer to the spec.| Constructor and Description |
|---|
WARManifestProcessor() |
| Modifier and Type | Method and Description |
|---|---|
static Manifest |
processManifest(URL url,
String query)
Reads content of the given URL, uses it to come up with a new Manifest.
|
static Map<String,String> |
readQueryParams(String query) |
public static Manifest processManifest(URL url, String query) throws IOException
url - URL which is used to read the original Manifest and other dataquery - extra parameters passed by deployerIOException - if IO related error occursCopyright © 2017–2019 Eclipse Foundation. All rights reserved.