You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sirona.apache.org by "Gaetan Pitteloud (JIRA)" <ji...@apache.org> on 2014/11/07 10:55:33 UTC

[jira] [Created] (SIRONA-40) Provide web-fragment.xml files

Gaetan Pitteloud created SIRONA-40:
--------------------------------------

             Summary: Provide web-fragment.xml files
                 Key: SIRONA-40
                 URL: https://issues.apache.org/jira/browse/SIRONA-40
             Project: Sirona
          Issue Type: Wish
    Affects Versions: 0.2-incubating
            Reporter: Gaetan Pitteloud


There are situations when a webapp's web.xml must be configured with <absolute-ordering>, in order to be more precise about which jar can (or cannot) provide a ServletContainerInitializer to configure the webapp. The presence or absence of the jar on the classpath is not sufficient, especially when jar dependencies are too wide.
However, when a webapp is configured with <absolute-ordering>, the servlet container only looks into the jars which contain a META-INF/web-fragment.xml for a matching name, in order to load the ServletContainerInitializer from the named jar.
Thus, only jars with a web-fragment.xml defining a name can be selectively included in a webapp that defines <absolute-ordering>.

Both sirona-web and sirona-reporting jars define a ServletContainerInitializer. However, if the webapp is configured with <absolute-ordering>, there is no way to include sirona features.

Sirona jars should contain a META-INF/web-fragment.xml, containing just the <name> tag, so that a webapp developer can choose whether to include them when using <absolute-ordering> in the final webapp's web.xml.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)