Right, I have this: https://github.com/jieryn/web-fragment-example But it works, much to my surprise and sadness.
Would it be useful if the mergeWeb would print out the web-fragment.xml it is processing if there is an error? I think this will be more useful as more people take increasing advantage of Servlet 3.x modular features. On Tue, Oct 8, 2013 at 10:53 AM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi > > it doesn't reproduce creating a project with a dependency of the same kind > (jar) with a web-fragment? > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/10/8 jieryn <jie...@gmail.com> > >> I'm using Apache TomEE 1.6.0-SNAPSHOT from October 8th. I have seen >> these errors for a while now, but am not able to reproduce it in a >> sample project. I have a lot of WEB-INF/lib/blah.jar files which >> contain META-INF/web-fragment.xml files which configure the system >> modularly. At start up, I see the following: >> >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, >> local:"error-page"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, local:"filter"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, local:"listener"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, >> local:"mime-mapping"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, >> local:"security-constraint"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, >> local:"session-config"). >> javax.xml.bind.UnmarshalException: unexpected element >> (uri:"http://www.openejb.org/System/Configuration";, >> local:"welcome-file-list"). >> >> Expected elements are >> <{http://java.sun.com/xml/ns/javaee}session-config>,<{ >> http://java.sun.com/xml/ns/javaee}servlet-mapping>,<{ >> http://java.sun.com/xml/ns/javaee}pre-destroy>,<{ >> http://java.sun.com/xml/ns/javaee}mime-mapping>,<{ >> http://java.sun.com/xml/ns/javaee}message-destination>,<{ >> http://java.sun.com/xml/ns/javaee}persistence-unit-ref>,<{ >> http://java.sun.com/xml/ns/javaee}login-config>,<{ >> http://java.sun.com/xml/ns/javaee}error-page>,<{ >> http://java.sun.com/xml/ns/javaee}persistence-context-ref>,<{ >> http://java.sun.com/xml/ns/javaee}icon>,<{ >> http://java.sun.com/xml/ns/javaee}servlet>,<{ >> http://java.sun.com/xml/ns/javaee}env-entry>,<{http://java.sun.comf>,<{ >> http://java.sun.com/xml/ns/javaee}ejb-ref>,<{ >> http://java.sun.com/xml/ns/javaee}security-constraint>,<{ >> http://java.sun.com/xml/ns/javaee}ejb-local-ref> >> >> Each instance has that Expected elements long line after it, however I >> truncated it for this email. >> >> Any ideas? >>
