TomEE 1.x is Java EE 6 so not JSF 2.2 compliant (Java EE 7). This is the reason.
If you need JSF 2.2, you need to switch to Apache TomEE 2.x We will soon release a first milestone. JLouis -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, Feb 26, 2015 at 3:39 PM, DonatasCiuksys <[email protected]> wrote: > I was hapilly using MyFaces 2.2.x with TomEE 1.7 Plus until I tried to use > FlowScope. As soon as faces-config.xml started containing: > > <navigation-case> > ... > <to-flow-document-id /> > </navigation-case> > > TomEE crashed during start-up with: > > Caused by: javax.xml.bind.UnmarshalException: Unexpected element > {http://xmlns.jcp.org/xml/ns/javaee}to-flow-document-id, expected > [{http://java.sun.com/xml/ns/javaee}description, > {http://java.sun.com/xml/ns/javaee}display-name, > {http://java.sun.com/xml/ns/javaee}icon, > {http://java.sun.com/xml/ns/javaee}from-action, > {http://java.sun.com/xml/ns/javaee}from-outcome, > {http://java.sun.com/xml/ns/javaee}if, > {http://java.sun.com/xml/ns/javaee}to-view-id, > {http://java.sun.com/xml/ns/javaee}redirect] > at > > org.metatype.sxc.jaxb.RuntimeContext.validationError(RuntimeContext.java:390) > > So, new JSF 2.2 features are a no-no with TomEE 1.7? Or is it just a matter > of faces-config schema upgrade? > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/TomEE-1-7-JSF-2-2-Flows-UnmarshalException-tp4673897.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
