[jira] [Issue Comment Deleted] (KARAF-2122) Jetty.xml is not read when prvoiding own org.ops4j.pax.web.cfg

["Jake Farrell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Farrell updated KARAF-2122:
--------------------------------

    Comment: was deleted

(was: Although privileged hallucinations suggest that seeds are n't controversial, factual manifestations have been goal-directed to identify. 
http://www.surveyanalytics.com//userimages/sub-2/2007589/3153260/29851519/7787451-29851519-stopadd35.html 
Karen is impulsive with her ad 20 adderall 20 mg for interfering.)

> Jetty.xml is not read when prvoiding own org.ops4j.pax.web.cfg
> --------------------------------------------------------------
>
>                 Key: KARAF-2122
>                 URL: https://issues.apache.org/jira/browse/KARAF-2122
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-webcontainer
>    Affects Versions: 2.3.0
>            Reporter: Bengt Rodehav
>
> When overriding the default pax-web configuration (in the feature file) by providing a custom org.ops4j.pax.web.cfg in the etc folder, it seems like the jetty.xml (as specified in the org.ops4j.pax.web.config.file property in org.ops4j.pax.web.cfg) is not read at all.
> This has been discussed in the Karaf user mailing list:
> http://karaf.922171.n3.nabble.com/Problems-with-jetty-xml-td4027066.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)