Sakai has startup warnings on Tomcat 8.0.39+

On it didn't look like anyone knew why castor was in shared.

The problem of the missing JARs like:

is caused by castor-1.0.jar which has a META-INF/MANIFEST.MF of:

Adding a context.xml to the META-INF of every project fixes it. I feel like there's probably only a select group of projects that needs this, but I don't see any negative effects adding it everywhere. (Which is essentially what changing in in context.xml does)

So the webdav is an unrelated discussion here and I don't know how that got involved.

Sakai does startup in 8.0.39 but it starts up with ugly warnings at the start. So far there's 2 fixes I've found.

1) In conf/catalina.properties append xerces-J_1.4.0.jar,jdbc-se2.0.jar,jndi_1.2.1.jar,jta1.0.1.jar,cglib-full-2.0.2.jar,commons-logging.jar to the end of tomcat.util.scan.StandardJarScanFilter.jarsToSkip
2) Modify context.xml add

FYI: If you have <JarScanFilter> still you should remove it as this causes errors.

But it would still seems like good practice if the StandardJarScanner checked if a file existed before looking it up. We can file a bug for them.

Polling some of my colleagues for WebDAV use cases, I've heard about a few different uses of WebDAV that the drag-and-drop in Resources doesn't address, such as connecting via WebDAV to quickly rearrange or organize files and folders (that is more efficient than using the web interface); uploading a bunch of files with structure that didn't work well when extracting from an uploaded zipped file; and using the WebDAV connection as a mounted network drive to pull down files.

I think we need to redesign the Resources tool (as was proposed at Open Apereo 2016) to address these issues and use cases before we can remove WebDAV.

There might be a limited number of people at each institution that are using WebDAV, but those people probably have very specific or important use cases that require them to use WebDAV to accomplish the task.