tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Froidevaux (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TOMEE-43) library-directory ignored
Date Fri, 04 Nov 2011 12:11:01 GMT

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

Werner Froidevaux resolved TOMEE-43.
------------------------------------

    Resolution: Fixed

Solved with apache-tomee-1.0.0-beta-2-20111029.082511-21-webprofile.
                
> library-directory ignored
> -------------------------
>
>                 Key: TOMEE-43
>                 URL: https://issues.apache.org/jira/browse/TOMEE-43
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 1.0.0-beta-2
>         Environment: Linux, Java6
>            Reporter: Werner Froidevaux
>
> library-directory is ignored with the latest snapshot apache-tomee-1.0.0-beta-2-20111024.180646-18-webprofile.tar.gz.

> This was not the case with the snapshot apache-tomee-1.0.0-beta-2-20111022.170518-16-webprofile.tar.gz.
> The library directory is configured in application.xml with the option <library-directory>APP-INF/lib</library-directory>.
> Probably the option is not ignored but something with the classloader management changed
in the latest snapshot so that servlet classes located in a JAR in the library-directory are
not found. A sample stack trace looks as follows:
> SEVERE: Class org.opencrx.application.webdav.WebDavServlet not found
> java.lang.ClassNotFoundException: org.opencrx.application.webdav.WebDavServlet
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:264)
>         at org.apache.myfaces.shared.util.ClassUtils.classForName(ClassUtils.java:191)
>         at org.apache.myfaces.shared.util.ClassUtils.simpleClassForName(ClassUtils.java:210)
>         at org.apache.myfaces.shared_impl.webapp.webxml.WebXml.getFacesServletMappings(WebXml.java:133)
>         at org.apache.myfaces.spi.impl.DefaultWebConfigProvider.getFacesServletMappings(DefaultWebConfigProvider.java:46)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:110)
>         at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111)
>         at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4723)
>         at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
>         at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message