karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-686) ship jetty.xml in kit etc folder and refer it for the http feature
Date Fri, 24 Jun 2011 06:54:47 GMT

    [ https://issues.apache.org/jira/browse/KARAF-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054266#comment-13054266
] 

Jean-Baptiste Onofré commented on KARAF-686:
--------------------------------------------

AFAIR, Achim added a jetty.xml in a contrib folder shipped in the Karaf distribution.

I don't think it's a good idea to embed jetty.xml by default in the Karaf distribution and
http feature is an optional one.

It's clear that we really need to think about a profile mechanism supporting this kind of
situation :)

> ship jetty.xml in kit etc folder and refer it for the http feature
> ------------------------------------------------------------------
>
>                 Key: KARAF-686
>                 URL: https://issues.apache.org/jira/browse/KARAF-686
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> currently http feature has configuration like
> <feature name="http" version="2.2.1" resolver="(obr)">
>         <configfile finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/2.2.2-SNAPSHOT/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>
> This means each time we install http feature it will download jettyconfig.xml remotely
and override the local etc/jetty.xml, so any configuration we saved in local etc/jetty.xml
will lose. 
> We should ship jetty.xml in kit etc folder and always refer it for the http feature,
which is easier for customer to configure the jetty.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message