Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
2016-05-16 18:35 GMT+03:00 Hilbert, Colin : > > > > On 5/16/16, 10:49 AM, "Violeta Georgieva" wrote: > > >2016-05-16 17:45 GMT+03:00 Hilbert, Colin : > >> > >> Hello, > >> > >> On 5/5/16, 3:55 PM, "Violeta Georgieva" wrote: > >> > >> >Hi, > >> > > >> > > >> >2016-05-05 20:51 GMT+03:00 Hilbert, Colin : > >> >> > >> >> Hi, > >> >> > >> >> On 5/5/16, 1:48 PM, "Hilbert, Colin" > >wrote: > >> >> > >> >> >Hello, > >> >> > > >> >> >Thank you for checking up on this. In the meantime, is there a > >> >>different > >> >> >way you recommend I add these to the class path other than moving > >>the > >> >> >jars? > >> >> > > >> >> >Colin > >> >> > > >> >> > > >> >> >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: > >> >> > > >> >> >>Hi, > >> >> >> > >> >> >> > >> >> >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin > >> >>: > >> >> >>> > >> >> >>> Tomcat version 7.0.69 > >> >> >>> Also happens on 7.0.68 and 7.0.67 > >> >> >>> > >> >> >>> I don¹t get this error on 7.0.65 > >> >> >>> > >> >> >>> I have deployed an idp.war on tomcat > >> >> >>> The idp.war has a service.xml file that looks like this at the > >> >> >>>beginning: > >> >> >>> > >> >> >>> > >> >> >>> >> >> >>> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" > >> >> >>> > >> >> > >> > >xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority > >" > >> >> >>> > >> >>xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" > >> >> >>> > >> >>xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" > >> >> >>> > >xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" > >> >> >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" > >> >> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >> >> >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services > >> >> >>classpath:/schema/shibboleth-2.0-services.xsd > >> >> >>> urn:mace:shibboleth:2.0:afp > >> >> >>classpath:/schema/shibboleth-2.0-afp.xsd > >> >> >>> > >> >> >>>urn:mace:shibboleth:2.0:attribute:authority > >> >> >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd > >> >> >>> urn:mace:shibboleth:2.0:resolver > >> >> >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd > >> >> >>> > >> >> >>>urn:mace:shibboleth:2.0:idp:profile-handler > >> >> >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd > >> >> >>> > >>urn:mace:shibboleth:2.0:relying-party > >> >> >>classpath:/schema/shibboleth-2.0-relying-party.xsd > >> >> >>> urn:mace:shibboleth:2.0:resource > >> >> >>classpath:/schema/shibboleth-2.0-resource.xsd²> > >> >> >>> > >> >> >>> The stack complains that it cannot find the first schemaLocation > >> >listed > >> >> >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ > >> >>there > >> >> >>are > >> >> >>jars there, one of which is shibboleth-common-1.2.1.jar > >> >> >>> > >> >> >>> Which has the path /schema/ containing all those listed > >> >schemaLocations > >> >> >>from the service.xml > >> >> >>> > >> >> >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ > >> >>and > >> >> >>>the > >> >> >>exception goes away but I haven¹t had to do this prior to .67 > >> >> >>> > >> >> >>> Can anyone shed some light on this? > >> >> >> > >> >> >> > >> >> >>I think that this is related to the following feature [1]. > >> >> >>I'll check that. > >> >> >> > >> >> >>Regards, > >> >> >>Violeta > >> >> >> > >> >> >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 > >> >> > > >> >> > > >> >> > >>>- > >> >> >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> >> >For additional commands, e-mail: users-h...@tomcat.apache.org > >> >> > > >> >> > >> >> Sorry for the top post. I didn’t understand what I was doing. > >> > > >> >Please follow the discussion [1] on the dev list. > >> > > >> >Regards, > >> >Violeta > >> > > >> >[1] http://marc.info/?t=14617548634&r=1&w=2 > >> > > >> >> Colin. > >> >> > >> > >> Is there a bugzilla ticket that I can follow on this? > > > >No there isn't. > >You can open one and point to the mail thread. > > > >Regards, > >Violeta > > > >> Colin > >> > > How does one link the email thread in the ticket, would I just save this > outlook message and attach it as a file or do I provide that link for the > discussion you gave me previousy? Use this http://marc.info/?t=14617548634&r=1&w=2 Regards, Violeta > Colin >
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
On 5/16/16, 10:49 AM, "Violeta Georgieva" wrote: >2016-05-16 17:45 GMT+03:00 Hilbert, Colin : >> >> Hello, >> >> On 5/5/16, 3:55 PM, "Violeta Georgieva" wrote: >> >> >Hi, >> > >> > >> >2016-05-05 20:51 GMT+03:00 Hilbert, Colin : >> >> >> >> Hi, >> >> >> >> On 5/5/16, 1:48 PM, "Hilbert, Colin" >wrote: >> >> >> >> >Hello, >> >> > >> >> >Thank you for checking up on this. In the meantime, is there a >> >>different >> >> >way you recommend I add these to the class path other than moving >>the >> >> >jars? >> >> > >> >> >Colin >> >> > >> >> > >> >> >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: >> >> > >> >> >>Hi, >> >> >> >> >> >> >> >> >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin >> >>: >> >> >>> >> >> >>> Tomcat version 7.0.69 >> >> >>> Also happens on 7.0.68 and 7.0.67 >> >> >>> >> >> >>> I don¹t get this error on 7.0.65 >> >> >>> >> >> >>> I have deployed an idp.war on tomcat >> >> >>> The idp.war has a service.xml file that looks like this at the >> >> >>>beginning: >> >> >>> >> >> >>> >> >> >>> > >> >>> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" >> >> >>> >> >> >> >xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority >" >> >> >>> >> >>xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" >> >> >>> >> >>xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" >> >> >>> >xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" >> >> >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" >> >> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> >> >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services >> >> >>classpath:/schema/shibboleth-2.0-services.xsd >> >> >>> urn:mace:shibboleth:2.0:afp >> >> >>classpath:/schema/shibboleth-2.0-afp.xsd >> >> >>> >> >> >>>urn:mace:shibboleth:2.0:attribute:authority >> >> >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd >> >> >>> urn:mace:shibboleth:2.0:resolver >> >> >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd >> >> >>> >> >> >>>urn:mace:shibboleth:2.0:idp:profile-handler >> >> >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd >> >> >>> >>urn:mace:shibboleth:2.0:relying-party >> >> >>classpath:/schema/shibboleth-2.0-relying-party.xsd >> >> >>> urn:mace:shibboleth:2.0:resource >> >> >>classpath:/schema/shibboleth-2.0-resource.xsd²> >> >> >>> >> >> >>> The stack complains that it cannot find the first schemaLocation >> >listed >> >> >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ >> >>there >> >> >>are >> >> >>jars there, one of which is shibboleth-common-1.2.1.jar >> >> >>> >> >> >>> Which has the path /schema/ containing all those listed >> >schemaLocations >> >> >>from the service.xml >> >> >>> >> >> >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ >> >>and >> >> >>>the >> >> >>exception goes away but I haven¹t had to do this prior to .67 >> >> >>> >> >> >>> Can anyone shed some light on this? >> >> >> >> >> >> >> >> >>I think that this is related to the following feature [1]. >> >> >>I'll check that. >> >> >> >> >> >>Regards, >> >> >>Violeta >> >> >> >> >> >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 >> >> > >> >> > >> >> >>>- >> >> >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> >> >For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > >> >> >> >> Sorry for the top post. I didn’t understand what I was doing. >> > >> >Please follow the discussion [1] on the dev list. >> > >> >Regards, >> >Violeta >> > >> >[1] http://marc.info/?t=14617548634&r=1&w=2 >> > >> >> Colin. >> >> >> >> Is there a bugzilla ticket that I can follow on this? > >No there isn't. >You can open one and point to the mail thread. > >Regards, >Violeta > >> Colin >> How does one link the email thread in the ticket, would I just save this outlook message and attach it as a file or do I provide that link for the discussion you gave me previousy? Colin
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
2016-05-16 17:45 GMT+03:00 Hilbert, Colin : > > Hello, > > On 5/5/16, 3:55 PM, "Violeta Georgieva" wrote: > > >Hi, > > > > > >2016-05-05 20:51 GMT+03:00 Hilbert, Colin : > >> > >> Hi, > >> > >> On 5/5/16, 1:48 PM, "Hilbert, Colin" wrote: > >> > >> >Hello, > >> > > >> >Thank you for checking up on this. In the meantime, is there a > >>different > >> >way you recommend I add these to the class path other than moving the > >> >jars? > >> > > >> >Colin > >> > > >> > > >> >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: > >> > > >> >>Hi, > >> >> > >> >> > >> >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin > >>: > >> >>> > >> >>> Tomcat version 7.0.69 > >> >>> Also happens on 7.0.68 and 7.0.67 > >> >>> > >> >>> I don¹t get this error on 7.0.65 > >> >>> > >> >>> I have deployed an idp.war on tomcat > >> >>> The idp.war has a service.xml file that looks like this at the > >> >>>beginning: > >> >>> > >> >>> > >> >>> >> >>> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" > >> >>> > >> > xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" > >> >>> > >>xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" > >> >>> > >>xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" > >> >>> xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" > >> >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" > >> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >> >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services > >> >>classpath:/schema/shibboleth-2.0-services.xsd > >> >>> urn:mace:shibboleth:2.0:afp > >> >>classpath:/schema/shibboleth-2.0-afp.xsd > >> >>> > >> >>>urn:mace:shibboleth:2.0:attribute:authority > >> >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd > >> >>> urn:mace:shibboleth:2.0:resolver > >> >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd > >> >>> > >> >>>urn:mace:shibboleth:2.0:idp:profile-handler > >> >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd > >> >>> urn:mace:shibboleth:2.0:relying-party > >> >>classpath:/schema/shibboleth-2.0-relying-party.xsd > >> >>> urn:mace:shibboleth:2.0:resource > >> >>classpath:/schema/shibboleth-2.0-resource.xsd²> > >> >>> > >> >>> The stack complains that it cannot find the first schemaLocation > >listed > >> >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ > >>there > >> >>are > >> >>jars there, one of which is shibboleth-common-1.2.1.jar > >> >>> > >> >>> Which has the path /schema/ containing all those listed > >schemaLocations > >> >>from the service.xml > >> >>> > >> >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ > >>and > >> >>>the > >> >>exception goes away but I haven¹t had to do this prior to .67 > >> >>> > >> >>> Can anyone shed some light on this? > >> >> > >> >> > >> >>I think that this is related to the following feature [1]. > >> >>I'll check that. > >> >> > >> >>Regards, > >> >>Violeta > >> >> > >> >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 > >> > > >> > > >> >- > >> >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> >For additional commands, e-mail: users-h...@tomcat.apache.org > >> > > >> > >> Sorry for the top post. I didn’t understand what I was doing. > > > >Please follow the discussion [1] on the dev list. > > > >Regards, > >Violeta > > > >[1] http://marc.info/?t=14617548634&r=1&w=2 > > > >> Colin. > >> > > Is there a bugzilla ticket that I can follow on this? No there isn't. You can open one and point to the mail thread. Regards, Violeta > Colin >
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Hello, On 5/5/16, 3:55 PM, "Violeta Georgieva" wrote: >Hi, > > >2016-05-05 20:51 GMT+03:00 Hilbert, Colin : >> >> Hi, >> >> On 5/5/16, 1:48 PM, "Hilbert, Colin" wrote: >> >> >Hello, >> > >> >Thank you for checking up on this. In the meantime, is there a >>different >> >way you recommend I add these to the class path other than moving the >> >jars? >> > >> >Colin >> > >> > >> >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: >> > >> >>Hi, >> >> >> >> >> >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin >>: >> >>> >> >>> Tomcat version 7.0.69 >> >>> Also happens on 7.0.68 and 7.0.67 >> >>> >> >>> I don¹t get this error on 7.0.65 >> >>> >> >>> I have deployed an idp.war on tomcat >> >>> The idp.war has a service.xml file that looks like this at the >> >>>beginning: >> >>> >> >>> >> >>> > >>> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" >> >>> >> xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" >> >>> >>xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" >> >>> >>xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" >> >>> xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" >> >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" >> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services >> >>classpath:/schema/shibboleth-2.0-services.xsd >> >>> urn:mace:shibboleth:2.0:afp >> >>classpath:/schema/shibboleth-2.0-afp.xsd >> >>> >> >>>urn:mace:shibboleth:2.0:attribute:authority >> >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd >> >>> urn:mace:shibboleth:2.0:resolver >> >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd >> >>> >> >>>urn:mace:shibboleth:2.0:idp:profile-handler >> >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd >> >>> urn:mace:shibboleth:2.0:relying-party >> >>classpath:/schema/shibboleth-2.0-relying-party.xsd >> >>> urn:mace:shibboleth:2.0:resource >> >>classpath:/schema/shibboleth-2.0-resource.xsd²> >> >>> >> >>> The stack complains that it cannot find the first schemaLocation >listed >> >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ >>there >> >>are >> >>jars there, one of which is shibboleth-common-1.2.1.jar >> >>> >> >>> Which has the path /schema/ containing all those listed >schemaLocations >> >>from the service.xml >> >>> >> >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ >>and >> >>>the >> >>exception goes away but I haven¹t had to do this prior to .67 >> >>> >> >>> Can anyone shed some light on this? >> >> >> >> >> >>I think that this is related to the following feature [1]. >> >>I'll check that. >> >> >> >>Regards, >> >>Violeta >> >> >> >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 >> > >> > >> >- >> >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> >For additional commands, e-mail: users-h...@tomcat.apache.org >> > >> >> Sorry for the top post. I didn’t understand what I was doing. > >Please follow the discussion [1] on the dev list. > >Regards, >Violeta > >[1] http://marc.info/?t=14617548634&r=1&w=2 > >> Colin. >> Is there a bugzilla ticket that I can follow on this? Colin
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Hi, 2016-05-05 20:51 GMT+03:00 Hilbert, Colin : > > Hi, > > On 5/5/16, 1:48 PM, "Hilbert, Colin" wrote: > > >Hello, > > > >Thank you for checking up on this. In the meantime, is there a different > >way you recommend I add these to the class path other than moving the > >jars? > > > >Colin > > > > > >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: > > > >>Hi, > >> > >> > >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin : > >>> > >>> Tomcat version 7.0.69 > >>> Also happens on 7.0.68 and 7.0.67 > >>> > >>> I don¹t get this error on 7.0.65 > >>> > >>> I have deployed an idp.war on tomcat > >>> The idp.war has a service.xml file that looks like this at the > >>>beginning: > >>> > >>> > >>> >>> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" > >>> > >>xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" > >>> xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" > >>> xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" > >>> xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" > >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" > >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services > >>classpath:/schema/shibboleth-2.0-services.xsd > >>> urn:mace:shibboleth:2.0:afp > >>classpath:/schema/shibboleth-2.0-afp.xsd > >>> > >>>urn:mace:shibboleth:2.0:attribute:authority > >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd > >>> urn:mace:shibboleth:2.0:resolver > >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd > >>> > >>>urn:mace:shibboleth:2.0:idp:profile-handler > >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd > >>> urn:mace:shibboleth:2.0:relying-party > >>classpath:/schema/shibboleth-2.0-relying-party.xsd > >>> urn:mace:shibboleth:2.0:resource > >>classpath:/schema/shibboleth-2.0-resource.xsd²> > >>> > >>> The stack complains that it cannot find the first schemaLocation listed > >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ there > >>are > >>jars there, one of which is shibboleth-common-1.2.1.jar > >>> > >>> Which has the path /schema/ containing all those listed schemaLocations > >>from the service.xml > >>> > >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ and > >>>the > >>exception goes away but I haven¹t had to do this prior to .67 > >>> > >>> Can anyone shed some light on this? > >> > >> > >>I think that this is related to the following feature [1]. > >>I'll check that. > >> > >>Regards, > >>Violeta > >> > >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 > > > > > >- > >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >For additional commands, e-mail: users-h...@tomcat.apache.org > > > > Sorry for the top post. I didn’t understand what I was doing. Please follow the discussion [1] on the dev list. Regards, Violeta [1] http://marc.info/?t=14617548634&r=1&w=2 > Colin. >
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Hi, On 5/5/16, 1:48 PM, "Hilbert, Colin" wrote: >Hello, > >Thank you for checking up on this. In the meantime, is there a different >way you recommend I add these to the class path other than moving the >jars? > >Colin > > >On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: > >>Hi, >> >> >>2016-04-26 22:49 GMT+03:00 Hilbert, Colin : >>> >>> Tomcat version 7.0.69 >>> Also happens on 7.0.68 and 7.0.67 >>> >>> I don¹t get this error on 7.0.65 >>> >>> I have deployed an idp.war on tomcat >>> The idp.war has a service.xml file that looks like this at the >>>beginning: >>> >>> >>> >> xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" >>> >>xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" >>> xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" >>> xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" >>> xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" >>> xmlns:resource="urn:mace:shibboleth:2.0:resource" >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xsi:schemaLocation="urn:mace:shibboleth:2.0:services >>classpath:/schema/shibboleth-2.0-services.xsd >>> urn:mace:shibboleth:2.0:afp >>classpath:/schema/shibboleth-2.0-afp.xsd >>> >>>urn:mace:shibboleth:2.0:attribute:authority >>classpath:/schema/shibboleth-2.0-attribute-authority.xsd >>> urn:mace:shibboleth:2.0:resolver >>classpath:/schema/shibboleth-2.0-attribute-resolver.xsd >>> >>>urn:mace:shibboleth:2.0:idp:profile-handler >>classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd >>> urn:mace:shibboleth:2.0:relying-party >>classpath:/schema/shibboleth-2.0-relying-party.xsd >>> urn:mace:shibboleth:2.0:resource >>classpath:/schema/shibboleth-2.0-resource.xsd²> >>> >>> The stack complains that it cannot find the first schemaLocation listed >>but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ there >>are >>jars there, one of which is shibboleth-common-1.2.1.jar >>> >>> Which has the path /schema/ containing all those listed schemaLocations >>from the service.xml >>> >>> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ and >>>the >>exception goes away but I haven¹t had to do this prior to .67 >>> >>> Can anyone shed some light on this? >> >> >>I think that this is related to the following feature [1]. >>I'll check that. >> >>Regards, >>Violeta >> >>[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 > > >- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org > Sorry for the top post. I didn’t understand what I was doing. Colin.
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Hello, Thank you for checking up on this. In the meantime, is there a different way you recommend I add these to the class path other than moving the jars? Colin On 4/27/16, 4:06 AM, "Violeta Georgieva" wrote: >Hi, > > >2016-04-26 22:49 GMT+03:00 Hilbert, Colin : >> >> Tomcat version 7.0.69 >> Also happens on 7.0.68 and 7.0.67 >> >> I don¹t get this error on 7.0.65 >> >> I have deployed an idp.war on tomcat >> The idp.war has a service.xml file that looks like this at the >>beginning: >> >> >> > xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" >> >xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" >> xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" >> xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" >> xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" >> xmlns:resource="urn:mace:shibboleth:2.0:resource" >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="urn:mace:shibboleth:2.0:services >classpath:/schema/shibboleth-2.0-services.xsd >> urn:mace:shibboleth:2.0:afp >classpath:/schema/shibboleth-2.0-afp.xsd >> >>urn:mace:shibboleth:2.0:attribute:authority >classpath:/schema/shibboleth-2.0-attribute-authority.xsd >> urn:mace:shibboleth:2.0:resolver >classpath:/schema/shibboleth-2.0-attribute-resolver.xsd >> >>urn:mace:shibboleth:2.0:idp:profile-handler >classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd >> urn:mace:shibboleth:2.0:relying-party >classpath:/schema/shibboleth-2.0-relying-party.xsd >> urn:mace:shibboleth:2.0:resource >classpath:/schema/shibboleth-2.0-resource.xsd²> >> >> The stack complains that it cannot find the first schemaLocation listed >but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ there >are >jars there, one of which is shibboleth-common-1.2.1.jar >> >> Which has the path /schema/ containing all those listed schemaLocations >from the service.xml >> >> I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ and >>the >exception goes away but I haven¹t had to do this prior to .67 >> >> Can anyone shed some light on this? > > >I think that this is related to the following feature [1]. >I'll check that. > >Regards, >Violeta > >[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Hi, 2016-04-26 22:49 GMT+03:00 Hilbert, Colin : > > Tomcat version 7.0.69 > Also happens on 7.0.68 and 7.0.67 > > I don’t get this error on 7.0.65 > > I have deployed an idp.war on tomcat > The idp.war has a service.xml file that looks like this at the beginning: > > >xmlns:attribute-afp="urn:mace:shibboleth:2.0:afp" > xmlns:attribute-authority="urn:mace:shibboleth:2.0:attribute:authority" > xmlns:attribute-resolver="urn:mace:shibboleth:2.0:resolver" > xmlns:profile="urn:mace:shibboleth:2.0:idp:profile-handler" > xmlns:relyingParty="urn:mace:shibboleth:2.0:relying-party" > xmlns:resource="urn:mace:shibboleth:2.0:resource" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="urn:mace:shibboleth:2.0:services classpath:/schema/shibboleth-2.0-services.xsd > urn:mace:shibboleth:2.0:afp classpath:/schema/shibboleth-2.0-afp.xsd > urn:mace:shibboleth:2.0:attribute:authority classpath:/schema/shibboleth-2.0-attribute-authority.xsd > urn:mace:shibboleth:2.0:resolver classpath:/schema/shibboleth-2.0-attribute-resolver.xsd > urn:mace:shibboleth:2.0:idp:profile-handler classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd > urn:mace:shibboleth:2.0:relying-party classpath:/schema/shibboleth-2.0-relying-party.xsd > urn:mace:shibboleth:2.0:resource classpath:/schema/shibboleth-2.0-resource.xsd”> > > The stack complains that it cannot find the first schemaLocation listed but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ there are jars there, one of which is shibboleth-common-1.2.1.jar > > Which has the path /schema/ containing all those listed schemaLocations from the service.xml > > I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ and the exception goes away but I haven’t had to do this prior to .67 > > Can anyone shed some light on this? I think that this is related to the following feature [1]. I'll check that. Regards, Violeta [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56777
Failed to read schema document 'classpath:/schema/shibboleth-2.0-services.xsd'
Tomcat version 7.0.69 Also happens on 7.0.68 and 7.0.67 I don’t get this error on 7.0.65 I have deployed an idp.war on tomcat The idp.war has a service.xml file that looks like this at the beginning: http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="urn:mace:shibboleth:2.0:services classpath:/schema/shibboleth-2.0-services.xsd urn:mace:shibboleth:2.0:afp classpath:/schema/shibboleth-2.0-afp.xsd urn:mace:shibboleth:2.0:attribute:authority classpath:/schema/shibboleth-2.0-attribute-authority.xsd urn:mace:shibboleth:2.0:resolver classpath:/schema/shibboleth-2.0-attribute-resolver.xsd urn:mace:shibboleth:2.0:idp:profile-handler classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd urn:mace:shibboleth:2.0:relying-party classpath:/schema/shibboleth-2.0-relying-party.xsd urn:mace:shibboleth:2.0:resource classpath:/schema/shibboleth-2.0-resource.xsd”> The stack complains that it cannot find the first schemaLocation listed but if I go to the deployed idp folder in tomcat idp/WEB-INF/lib/ there are jars there, one of which is shibboleth-common-1.2.1.jar Which has the path /schema/ containing all those listed schemaLocations from the service.xml I can move all the jars from idp/WE-INF/lib/ to tomcat7.0.69/lib/ and the exception goes away but I haven’t had to do this prior to .67 Can anyone shed some light on this?
