Xsd not found on classpath

[Cantor, Scott]

On 6/27/13 12:24 PM, "Byte Flinger" <byteflinger at gmail.com> wrote:

>Well my eclipse has got m2e plugin installed and it is pointing to a real
>maven installation rather than the built-in but I am not sure what you
>meant by that comment? Does either one require something specific upon
>build? The wiki makes mention of some eclipse command-line flags however
>if I understand that correctly it is just to get the imported idp xsd
>that contains the definition of LoginHandlerType (something which I am
>not having an issue with so skipped it).

I'm saying that Eclipse doing anything has no relationship to a working
IdP or maven build, and to say more, you'd have to have gone through the
process of developing with this stuff. All I know is that it means nothing
that Eclipse works. It often works while maven fails.

>As for the lib folder, I placed the jar inside it in shibboleth and ran
>the install script to update the war and I think I checked that it was
>inside the lib folder but I will make the check again.

That's fine, my point is that you have to do the full IdP install/build to
end up with anything testable that I would trust.

>Besides all that, would such an error be thrown if anything was
>missconfigured in the customisation, as in, regardless of what it's in
>the java/spring files it should still find the xsd, correct?

Not my area of expertise, but if it's looking for that schema filename, I
assume the rest is irrelevant to the error. Issues with Spring would
manifest in other ways.

Could be there's a duplicate jar perhaps, or you have an unpacked war in
the way, or something like that.

-- Scott