>From: "Baker,Jonathan" <[EMAIL PROTECTED]> > > Are there any known compatibility issues between shale (or any of its > parts such as clay) and ADF Faces? Shale is an application-level > filter, and it looks like ADF faces is also an application-level filter. > I thought the clay view handler may also present issues. > > I just thought I would ask for any know issues before I got started to > try not to waste time trying to make something work that can't. >
I'm not aware of any but I have not made the time to try putting them together yet. Clay's view handler looks for viewId's ending in a *.html or *.xml suffix. These are the default suffixes. The view handler is only activated for view id's ending with these suffixes. Otherwise, it just delegates to the original view handler. I have not heard of anyone building a base clay configuration file for the ADF components yet. This is similar to creating a TLD. Month's ago a tomahawk clay configuration file was contributed. At the time, we thought that myfaces should package this in with the tomahawk bundling. I'd rather see us (Shale) package these in with clay rather than trying to suggest that component libraries should feel obligated to bundle them in with their archives. I'd like to see more example applications of using clay with various component libraries at the minimum. If you are able to put these together, please try to contribute it back so at a minimum we have a simple example. > Thanks > > JB Gary > >
