karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KARAF-2053) HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
Date Tue, 11 Dec 2012 09:53:22 GMT

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

Freeman Fang edited comment on KARAF-2053 at 12/11/12 9:51 AM:
---------------------------------------------------------------

Hi JB,

As we already configure org.ops4j.pax.web PID in http feature like 
<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>
have another org.ops4j.pax.web.cfg in etc folder  will  prevent to propagate properties for
the ConfigAdmin service from features config tag, this will cause jetty.xml can't be loaded
as org.ops4j.pax.web.config.file, so if we put a org.ops4j.pax.web.cfg in etc folder, we at
least should keep all configurations from the http feature config tag as well.

that said, also have 
{code}
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
in etc/org.ops4j.pax.web.cfg
{code}

Thanks
Freeman
                
      was (Author: ffang):
    Hi JB,

As we already configure org.ops4j.pax.web PID in http feature like 
<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>
have another org.ops4j.pax.web.cfg in etc folder  will  prevent to propagate properties for
the ConfigAdmin service from features config tag, this will cause jetty.xml can't be loaded
as org.ops4j.pax.web.config.file, so if we put a org.ops4j.pax.web.cfg in etc folder, we at
least should keep all configurations from the http feature config tag as well.

that said, also have 
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
in etc/org.ops4j.pax.web.cfg

Thanks
Freeman
                  
> HTTP feature should install a default etc/org.ops4j.pax.web.cfg file
> --------------------------------------------------------------------
>
>                 Key: KARAF-2053
>                 URL: https://issues.apache.org/jira/browse/KARAF-2053
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-webcontainer
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.10, 2.3.1, 3.0.0
>
>
> Now, when an user installs the http feature, it could be helpful to install a default
etc/org.ops4j.pax.web.cfg file, containing something like:
> org.osgi.service.http.port=8181
> #org.osgi.service.http.port.secure=9101
> #org.osgi.service.http.secure.enabled=true
> #org.ops4j.pax.web.ssl.keystore=./etc/keystores/keystore.jks
> #org.ops4j.pax.web.ssl.password=password
> #org.ops4j.pax.web.ssl.keypassword=password
> #org.ops4j.pax.web.clientAuthWanted=true
> #org.ops4j.pax.web.clientAuthRequired=false

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message