Just wondering what people think about not including <listener> <listener-class>org.apache.shale.view.faces.LifecycleListener</listener-class> </listener>
in the taglib.tld of myfaces-core. I believe correct me if I am wrong that this is the only shale class that uses servlet 2.4. If shale users wish to use these capabilites then they can add the listener to their web.xml. If they are running in a servlet 2.3 environment (like I am with WebSphere Portal 5.1) then it is possible for the application to load and the get most of the benefits of shale. Of course the other option is to put the listener and the tld into another jar which I guess may or may not be more inconvenient than the approach above to users of 2.4. I think it's worth it to support losing a little convenience for more compatibility, but only for a reasonable time. I think eventually we will upgrade to WebSphere Portal 6 which supports servlet 2.4 but for now we are actually forced to use shale-core-1.1.2 combined with shale-clay-1.0.3. It works but it is not the optimal setup.
