Apache Tomcat: META-INF directory ignored during creation of .war file

971 views Asked by At

I'm developing a web-application with Apache Tomcat. My web-app has a META-INF directory with the context.xml file in it. The problem is that when I try to create a .war file with the command "jar -cvf mywebapp.war ." , I get this warning (I'm translating as I can to English):

META-INF will be ignored
adding META-INF/context.xml(in = 142)(compression 17%)
META-INF/MANIFEST.MF will be ignored

Since when I start Tomcat I get some errors, I thought that maybe it was all due to this warning. Thank you.

EDIT:

<?xml version="1.0" encoding="UTF-8"?>
<web-app id="mywebapp" version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

    <display-name>My web app</display-name>
    <description>...</description>

    <welcome-file-list>
        <welcome-file>html/index.html</welcome-file>
    </welcome-file-list>

    <!-- Define the roles we want to use in the application -->
    <security-role> 
        <role-name>member</role-name> 
    </security-role>

    <security-constraint> 
        <!-- Define the resource -->
        <web-resource-collection> 
            <web-resource-name>Members Only</web-resource-name> 
            <url-pattern>html/members/*</url-pattern> 
        </web-resource-collection> 

        <!-- Only members can access this resource --> 
        <auth-constraint> 
            <role-name>member</role-name> 
        </auth-constraint>  

        <user-data-constraint>
            <!-- transport-guarantee can be CONFIDENTIAL, INTEGRAL, or NONE -->
            <transport-guarantee>NONE</transport-guarantee>
        </user-data-constraint>     
    </security-constraint> 

    <!-- Use BASIC security -->
    <login-config> 
        <auth-method>BASIC</auth-method> 
        <realm-name>Secure area</realm-name> 
    </login-config> 

</web-app>
1

There are 1 answers

0
David Levesque On BEST ANSWER

Try adding a slash at the beginning of the <url-pattern> for resource "Members Only" in the <security-constraint> section, e.g.:

<url-pattern>/html/members/*</url-pattern> 

instead of

<url-pattern>html/members/*</url-pattern>