Details

    • Type: Wish Wish
    • Status: Closed
    • Priority: Major Major
    • Resolution: Auto Closed
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: overlay
    • Labels:
      None

      Description

      I'm looking for a way to use the war overlay feature and have the web.xml merged with the content of both the parent war and the child war.

      For example, we have two wars A and B, and B is depending on A using the overlay feature. Now, I'd like all filters, servlets etc that are configured in A to be available in the resulting war, as well as all filters, servlets etc from B. If the id attributes clash, then the objects from B should be used.

      Any ideas how this could be accomplished?

      1. merge-web.xml.xslt
        2 kB
        Michiel Meeuwissen

        Activity

        Hide
        Stephane Nicoll added a comment -

        We have that in mind. I can't provide any schedule though.

        The idea would be to integrate the merge functionnality from the Cargo project. FYI we are currently refactoring the overlay mechansim.

        Show
        Stephane Nicoll added a comment - We have that in mind. I can't provide any schedule though. The idea would be to integrate the merge functionnality from the Cargo project. FYI we are currently refactoring the overlay mechansim.
        Hide
        Anders Romin added a comment -

        That's ok for me. Thanks for a fast reply!
        I'm also looking forward to the refactored overlay implementation...

        Show
        Anders Romin added a comment - That's ok for me. Thanks for a fast reply! I'm also looking forward to the refactored overlay implementation...
        Hide
        Richard C. L. Li added a comment -

        I am in need of this feature, any progress? I can help to implement this feature if you permitted, this should be easy though.

        Show
        Richard C. L. Li added a comment - I am in need of this feature, any progress? I can help to implement this feature if you permitted, this should be easy though.
        Hide
        Stephane Nicoll added a comment -

        Howdy,

        You can certainly help if you think it's easy

        I guess we should rely on the cargo api and provide the bridge to this system + tests + documentation. I've investigated the solution provided with cargo and found it very complete but also a bit complex to use.

        Show
        Stephane Nicoll added a comment - Howdy, You can certainly help if you think it's easy I guess we should rely on the cargo api and provide the bridge to this system + tests + documentation. I've investigated the solution provided with cargo and found it very complete but also a bit complex to use.
        Hide
        Gabriele Columbro added a comment -
        Show
        Gabriele Columbro added a comment - An Xpatch kind of thing is not applicable? http://cocoon.apache.org/2.2/maven-plugins/maven-plugin/1.0/1360_1_1.html
        Hide
        Michiel Meeuwissen added a comment -

        In an ant-build I used to simply merge 2 web.xml's using an XSLT. This may not be flexible enough in every situation, but at least it would be simple to implement.

        Show
        Michiel Meeuwissen added a comment - In an ant-build I used to simply merge 2 web.xml's using an XSLT. This may not be flexible enough in every situation, but at least it would be simple to implement.
        Hide
        Stephane Nicoll added a comment -

        The cactus project has a merge web.xml feature that we might consider integrating here in one way or the other.

        Show
        Stephane Nicoll added a comment - The cactus project has a merge web.xml feature that we might consider integrating here in one way or the other.
        Hide
        Knut Vidar Siem added a comment -

        From the Cactus project page:

        2011/08/05 - Jakarta Cactus has been retired.

        I would like to see this issue resolved as well. Meanwhile, alternatives include:

        This thread from StackOverflow.com could also be of interest: Maven: Customize web.xml of web-app project

        Show
        Knut Vidar Siem added a comment - From the Cactus project page : 2011/08/05 - Jakarta Cactus has been retired. I would like to see this issue resolved as well. Meanwhile, alternatives include: Cargo Maven2 Plugin - Merging WAR files XML Maven Plugin - XSL Transformation This thread from StackOverflow.com could also be of interest: Maven: Customize web.xml of web-app project
        Hide
        Michael Osipov added a comment - - edited

        Cocoon's Maven Plugin is, unfortunately, unusable. I was wondering why neither of my .xweb files from my project were applied. I checked the source: https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/cocoon-maven-plugin/cocoon-maven-plugin-1.0.0-M2/src/main/java/org/apache/cocoon/maven/deployer/AbstractDeployMojo.java and the only call to the method xpatch passes new File[0], so nothing is applied. Only xweb files for dependencies are applied.
        See https://issues.apache.org/jira/browse/COCOON-2084

        Show
        Michael Osipov added a comment - - edited Cocoon's Maven Plugin is, unfortunately, unusable. I was wondering why neither of my .xweb files from my project were applied. I checked the source: https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/cocoon-maven-plugin/cocoon-maven-plugin-1.0.0-M2/src/main/java/org/apache/cocoon/maven/deployer/AbstractDeployMojo.java and the only call to the method xpatch passes new File [0] , so nothing is applied. Only xweb files for dependencies are applied. See https://issues.apache.org/jira/browse/COCOON-2084
        Hide
        Michael Osipov added a comment -

        This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

        Show
        Michael Osipov added a comment - This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

          People

          • Assignee:
            Unassigned
            Reporter:
            Anders Romin
          • Votes:
            16 Vote for this issue
            Watchers:
            15 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development