Wow! Thanks for the quick response -- go GMT! This is a third-party jar so "fixing" it is not a long-term option. The beans.xml contains weld exclusions in their own namespace. Can't the OpenWebBeans provider simply ignore them? If the CDI spec doesn't provide for that, or for a provider-neutral include/exclude mechanism, it pretty much excludes third-party jars from an application, does it not?
The beans.xml file is: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:weld="http://jboss.org/schema/weld/beans"; xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/beans_1_0.xsd http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd";> <weld:scan> <weld:include name="**"/> <weld:exclude name="liquibase.integration.ant.**"> <weld:if-class-available name="!org.apache.tools.ant.Task"/> </weld:exclude> <weld:exclude name="liquibase.integration.servlet.**"> <weld:if-class-available name="!javax.servlet.ServletContext"/> </weld:exclude> <weld:exclude name="liquibase.integration.spring.**"> <weld:if-class-available name="!org.springframework.beans.factory.InitializingBean"/> </weld:exclude> </weld:scan> </beans> Ignoring unknown namespaces would be a useful feature. djh -- View this message in context: http://openejb.979440.n4.nabble.com/liquibase-Cannot-unmarshall-the-beans-xml-tp4664595p4664605.html Sent from the OpenEJB User mailing list archive at Nabble.com.
