So what features are you trying to avoid? It sounds like you're talking about the view controller stuff but I can't be sure. I can't think of any problems Shale would cause for you if you used all of the add on stuff in faces-config.xml. For instance, if you don't want the ViewController functionality just don't have any backing beans implement ViewController.
Sean On 7/21/06, Butash, Bob <[EMAIL PROTECTED]> wrote:
I have a question regarding the packaging of the faces-config.xml file with the jar files. It has been our normal practice not to modify or alter the open source jar files that we include in our application code, this enables us to easily migrate to new releases of the code. However with Shale we have noticed the inclusion of the faces-config.xml file the configures the application with features that we do not want to leverage at this time. We find ourselves having to manually alter the packaged faces-config so it will not conflict with our configuration. I would think that it would be a better practice to provide examples and documentation as to how to configure an application to use shale but not to include a faces-config.xml in the standard jar files. My concern is more with the application and lifecylce elements. Wondering what others thoughts are on this matter. Thanks, Bob Butash
