Since we support of wrapping of WARs with webbundle: URL scheme, we should explore the option of using it to wrap plain vanilla WARs when such WARs are deployed using --type=osgi property. This will allow OSGi Web Container to be available to a wider audience.
OSGiArchiveHandler cannot not know about WAB - WAB support is provided
by osgi-web-container, so the dependency needs to be broken. I think if
you take properties like the following, you can avoid the decoupling:
Sahoo Said:
OSGiArchiveHandler cannot not know about WAB - WAB support is provided by osgi-web-container, so the dependency needs to be broken. I think if you take properties like the following, you can avoid the decoupling:
asadmin deploy --type osgi --properties uriScheme=wab queryParams="comma separated name=value pairs"
then you can just create a new URI inside OSGiArchiveHandler.expand(). You can then obtain an InputStream from the new URI and use the same.