No content type for .pom files denoted in file "archiva-mime-types.txt" - 
workaround included
---------------------------------------------------------------------------------------------

                 Key: MRM-755
                 URL: http://jira.codehaus.org/browse/MRM-755
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.0.1
         Environment: Websphere 6.1.0.15 / IBM J9 VM / Windows XP
            Reporter: Stefan Prange


On Websphere 6,1, *.pom files can't be downloaded from Archiva via respository 
requests.
For instance, the URL 
  
http://localhost:9081/archiva/repository/internal/commons-lang/commons-lang/2.1/commons-lang-2.1.pom
leads to an exception like this:

[30.03.08 14:55:15:671 CEST] 00000032 WebApp        E   [Servlet 
Error]-[RepositoryServlet]: java.lang.NullPointerException
        at 
com.ibm.ws.webcontainer.srt.SRTServletResponse.setContentType(SRTServletResponse.java:1076)
        at 
it.could.webdav.DAVTransaction.setContentType(DAVTransaction.java:193)
        at 
org.codehaus.plexus.webdav.simple.ReplacementGetMethod.process(ReplacementGetMethod.java:157)
        at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79)
        at 
org.codehaus.plexus.webdav.simple.SimpleDavServerComponent.process(SimpleDavServerComponent.java:154)
        ...

The most likely cause seems to be that there is no mimetype for *.pom files 
listed in Archiva's resource file "archiva-mime-types.txt".

I added this mimetype by changing line 69 of "archiva-mime-types.txt" from
  application/xml                          xml xsl
to
  application/xml                          xml xsl pom

This way, .pom file are treated as xml files.

After that change the exception mentioned above did'nt occur anymore.

HTH, Stefan


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to