[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2741) "org.jboss.seam.spring.ContextLoader" cannot be resolved to a type

"org.jboss.seam.spring.ContextLoader" cannot be resolved to a type ------------------------------------------------------------------ Key: JBSEAM-2741 URL: http://jira.jboss.com/jira/browse/JBSEAM-2741 Project: Seam Issue Type: Bug Components: Spring Affects Versions: 2.0.1.GA Reporter: Kurt Vermeiren Assigned To: Dan Allen I'm trying to load the Spring application context via the component.xml I followed the instructions in the Seam Reference documentation, the component.xml looks like: <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:spring="http://jboss.com/products/seam/spring" xmlns:security="http://jboss.com/products/seam/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.0.xsd http://jboss.com/products/seam/persistence http://jboss.com/products/seam/persistence-2.0.xsd http://jboss.com/products/seam/drools http://jboss.com/products/seam/drools-2.0.xsd http://jboss.com/products/seam/bpm http://jboss.com/products/seam/bpm-2.0.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-2.0.xsd http://jboss.com/products/seam/mail http://jboss.com/products/seam/mail-2.0.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.0.xsd"> ... <spring:context-loader> <spring:config-locations> <value>WEB-INF/SpringContext.xml</value> </spring:config-locations> </spring:context-loader> However I keep getting an error saying that "org.jboss.seam.spring.ContextLoader" cannot be resolved to a type. I checked jboss-seam-ioc.jar (in the classpath), and I see that ContextLoader is not in org.jboss.seam.spring but in the org.jboss.seam.ioc.spring package. I think I can work around it by loading the spring context via web.xml, but I wonder if this is a bug?