[
https://issues.apache.org/jira/browse/KARAF-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996306#comment-12996306
]
Achim Nierbeck edited comment on KARAF-465 at 2/18/11 9:25 AM:
---------------------------------------------------------------
Ok, taking this last proposal we end up with the following features:
This leads to the following "new" feature for http:
<feature name="http" version="${project.version}" resolver="(obr)">
<configfile
finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/${project.version}/xml/jettyconfig</configfile>
<config name="org.ops4j.pax.web">
org.osgi.service.http.port=8181
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
</config>
<feature version="[7.0,8.0)">jetty</feature>
<bundle>mvn:org.ops4j.pax.web/pax-web-api/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-spi/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-runtime/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-jetty/${pax.web.version}</bundle>
</feature>
The new http-whiteboard feature
<feature name="http-whiteboard" version="${project.version}"
resolver="(obr)">
<feature>http</feature>
<bundle>mvn:org.ops4j.pax.web/pax-web-jsp/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-extender-whiteboard/${pax.web.version}</bundle>
</feature>
The war features will end up like:
<feature name="war" version="${project.version}" resolver="(obr)">
<config name="org.ops4j.pax.url.war">
org.ops4j.pax.url.war.importPaxLoggingPackages=true
</config>
<feature>http-whiteboard</feature>
<bundle
start-level='30'>mvn:org.apache.karaf.shell/org.apache.karaf.shell.web/${project.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-extender-war/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-deployer/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.url/pax-url-war/${pax.url.version}</bundle>
</feature>
was (Author: achim_nierbeck):
Ok, taking this last proposal we end up with the following features:
This leads to the following "new" feature for http:
<feature name="http" version="${project.version}" resolver="(obr)">
<configfile
finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/${project.version}/xml/jettyconfig</configfile>
<config name="org.ops4j.pax.web">
org.osgi.service.http.port=8181
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
</config>
<feature version="[7.0,8.0)">jetty</feature>
<bundle>mvn:org.ops4j.pax.web/pax-web-api/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-spi/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-runtime/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-jetty/${pax.web.version}</bundle>
</feature>
<feature name="http-whiteboard" version="${project.version}"
resolver="(obr)">
<feature>http</feature>
<bundle>mvn:org.ops4j.pax.web/pax-web-jsp/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-extender-whiteboard/${pax.web.version}</bundle>
</feature>
The war features will end up like:
<feature name="war" version="${project.version}" resolver="(obr)">
<config name="org.ops4j.pax.url.war">
org.ops4j.pax.url.war.importPaxLoggingPackages=true
</config>
<feature>http-whiteboard</feature>
<bundle
start-level='30'>mvn:org.apache.karaf.shell/org.apache.karaf.shell.web/${project.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-extender-war/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.web/pax-web-deployer/${pax.web.version}</bundle>
<bundle>mvn:org.ops4j.pax.url/pax-url-war/${pax.url.version}</bundle>
</feature>
> Merge http with war feature
> ---------------------------
>
> Key: KARAF-465
> URL: https://issues.apache.org/jira/browse/KARAF-465
> Project: Karaf
> Issue Type: Improvement
> Reporter: Achim Nierbeck
> Fix For: 3.0.0
>
>
> Right now the war-extender, deployer and the white-board extender are
> separated from the http service together with the jetty bundles.
> For most users this separation is not needed because the main use-cases are
> around the war-extender of pax-web.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
