It looks like this could be a large change if we were to fix it. The org.apache.myfaces.trinidadbuild.plugin.faces.GenerateFacesConfigMojo
Executes an XSL (transform.xsl) that removes any component that doesn't match the typePrefix, I assumed this would only affect the components to generate, but apparently it also affects the faces-config-base.xml contents as well. This makes sense for trinidad, but I wonder if it would be helpful to support multiple type prefixes or event a more advanced matching than just a prefix for people using the plugin for their own project? -Andrew On 9/24/07, Andrew Robinson <[EMAIL PROTECTED]> wrote: > I haven't looked into the code yet, but it looks like 1.2.3-SNAPSHOT > of the maven-faces-plugin is truncating the faces-config-base > > I have the file "faces-impl/src/main/conf/META-INF/faces-config-base.xml" > > In this file I have: > > <?xml version="1.0"?> > <!DOCTYPE faces-config PUBLIC > "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" > "http://java.sun.com/dtd/web-facesconfig_1_1.dtd";> > > <faces-config xmlns="http://java.sun.com/xml/ns/javaee"; > > <application> > > <default-render-kit-id>org.apache.myfaces.trinidad.core</default-render-kit-id> > </application> > <lifecycle> > > <phase-listener>com.christws.faces.phase.ExpiredViewPhaseListener</phase-listener> > </lifecycle> > <component> > <component-type>javax.faces.ViewRoot</component-type> > > <component-class>com.christws.faces.component.view.UINavigableViewRoot</component-class> > </component> > </faces-config> > > > The phase listener is included (lifecycle element), but not the view > root. I have tried other component tags, and they are all dropped. Is > the XML include filtered to only certain elements? Should I file a > bug, or am I missing something? > > -Andrew >
