Hi If beans.xml has specific tags it will not be read.
If it fails once "fixed" it is surely it needs this particular config so you need the same/equivalent for openejb (for instance using inclusion config with scan.xml) Le 12 août 2013 02:48, "djheisterberg" <[email protected]> a écrit : > Is anyone using liquibase 3 with OpenEJB? I wasn't really intending to but > discovered that liquibase is CDI-ready (maybe even CDI-demanding!) and > found > that simply having it in the classpath resulted in an exception when > starting the container: > > org.apache.openejb.OpenEJBException: Cannot unmarshall the beans.xml > at > > org.apache.openejb.config.ReadDescriptors.readBeans(ReadDescriptors.java:552) > at > > org.apache.openejb.config.ReadDescriptors.readBeans(ReadDescriptors.java:442) > at > org.apache.openejb.config.ReadDescriptors.deploy(ReadDescriptors.java:75) > ... and much more ... > > The liquibase beans.xml has only some weld-specific excludes. > > I tried removing beans.xml from the liquibase jar. The container came up, > but it looks like CDI annotations were still being processed as it failed > with unresolved injection points for some liquibase classes. > > I do have a small maven project that reproduces this. > > djh > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/liquibase-Cannot-unmarshall-the-beans-xml-tp4664595.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
