Shibboleth Developers

["Howard Gilbert" <>]

This tends to be localized to a block of code in the constructor or
...common.ShibResource which either loads a file as a Resource (from the
classpath) or as a URL.

Java has an option that C++ doesn't have. When you have a string like
"options/withfries.txt", in C++ this has to mean the withfries.txt file in
the options subdirectory of the current directory. In Java it can mean the
same thing (if it is treated as a File name), but it can also mean the
withfries.txt file from the options subdirectory of the first JAR file in
the classpath that has an options subdirectory containing a withfries.txt
file (if treated as a Resource name). The problem is that non-URL syntax in
the SP is ONLY filename and that non-URL syntax in the IdP (and therefore
the Java SP that shares this class) is ONLY Resource name.

Ideally there would a way to express all three options, but this is a matter
for the whole group to discuss.

> -----Original Message-----
> The Java code mostly loads XML files with the same parsing code, and that
> had issues with file paths at one point. I believe I corrected that to
> some
> degree a while back to fix a problem with metadatatool.
> 
> So, I would *think* the Java code could handle C:/usr/local/shibboleth-sp
> but don't know.