MDA 0.7 Question
Krug, Jeff
Jeff.Krug at gtri.gatech.edu
Tue Apr 17 19:19:33 BST 2012
Maybe I should have been more specific. I was just updating the third example on the webpage to work with some of my metadata, and I get the below error regarding the parser pool classes. All three examples reference the same class name for this, so my first instinct of a typo in the config file seemed to be ruled out. When I compared the library directory from this extraction to my 0.6.1 release, the missing opensaml jar caught my eye. Maybe this is a simple configuration issue and the name of the bean is wrong in all three config files, but it seemed like the mostly likely issue was I was missing a jar file that the developers typically have in their development environment.
ERROR - Unable to initialize Spring context
org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.opensaml.util.xml.BasicParserPool] for bean with name 'parserPool' defined in URL [file:/home/jk90/src/aggregator-cli-0.7.0/configExample3.xml]; nested exception is java.lang.ClassNotFoundException: org.opensaml.util.xml.BasicParserPool
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1262) ~[spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:576) ~[spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1331) ~[spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:897) ~[spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:566) ~[spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) ~[spring-context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) ~[spring-context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:140) ~[spring-context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:84) ~[spring-context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at net.shibboleth.metadata.cli.SimpleCommandLine.main(SimpleCommandLine.java:83) ~[aggregator-cli-0.7.0.jar:na]
Caused by: java.lang.ClassNotFoundException: org.opensaml.util.xml.BasicParserPool
Thanks.
________________________________________
From: dev-bounces at shibboleth.net [dev-bounces at shibboleth.net] on behalf of Chad La Joie [lajoie at shibboleth.net]
Sent: Tuesday, April 17, 2012 1:52 PM
To: Shib Dev
Subject: Re: MDA 0.7 Question
MDA has never really relied on OpenSAML, it just used the util module.
All of those classes were extracted and moved to java-support and so
there is no reason to rely on the OpenSAML util module anymore.
On 4/17/12 1:36 PM, Krug, Jeff wrote:
> The 0.7 release of the MDA did not come with an opensaml in the
> zipfile. Is there a specific snapshot of opensaml I should use with
> it? I have a 3.0 version from when I was doing some testing with the
> 0.6.1 MDA, but I did not want to just blindly copy that over, since some
> of the posts here have implied lots of activity in the opensaml 3.0 tree.
>
>
>
> Thanks,
> Jeff
>
>
>
>
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
More information about the dev
mailing list