I'll looking for feedback and would like to start some discussion on an idea that might be a nice Shale add-on. What do you think about the second approach in this ticket?
http://issues.apache.org/bugzilla/show_bug.cgi?id=37932 What do think about making this more of a generic feature so that any render could be decorated by family or component type. Make this configurable through a XML config file. Besides being able to fix the immediate validation bug, we could use the generic capabilities to add Ajax enabled features without having to lock into a specific implementation or get into the business of component building. General ajax enabled field level validation might be a interesting feature that could be added. The decorator renderer could add the view id and the client id of a component in a remote javascript validation request that could fire a method on a managed bean (new remoting). The view could be restored using the view id with the state manager and the component found in the tree using the client id both passed in the ajax call. Invoke the validation and intercept the messages into a response. Seems like it might work? It might be an easy way to convert a component rendering to XHTML by using the Clay parser to tokenize and re rendered in XML without having to understand the specifics of the component and renderer. You might want to wrapper panels in an html div to inject some slick CSS sex without having to know anything about the component. Any thoughts? Gary
