CDK: naming conventions to avoid necessity write all the FQNs of classes in Renderer template and Component stub ---------------------------------------------------------------------------------------------------------------- Key: RF-12309 URL: https://issues.jboss.org/browse/RF-12309 Project: RichFaces Issue Type: Feature Request Security Level: Public(Everyone can see) Components: cdk Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč Fix For: 5.0.0.Alpha1 There are lot of bindings which needs to be manually hard-coded in order to make the component work: Look at sample of the calendar component: 1. [Renderer template|https://github.com/richfaces/components/blob/4.2.2.20120513-Fina...] 2. [Component interface|https://github.com/richfaces/components/blob/4.2.2.20120513-Fin...] ---- What could follow naming conventions? 1. *Renderer template* * {{<class>}} - use the package where the template resides in: {{calendar.template.xml}} -> {{CalendarRenderer}} * {{<superclass}} - use the {{<class> + Base}}: {{CalendarRenderer}} -> {{CalendarRendererBase}}, if not exists, use {{org.richfaces.renderkit.RendererBase}} 2. *component* {{org.richfaces.component.AbstractCalendar}} * component-type: {{org.richfaces.Calendar}} * component-family: {{org.richfaces.Calendar}} * generated class: {{org.richfaces.component.UICalendar}} * renderer: {{org.richfaces.CalendarRenderer}} * tag: {{@Tag(name = "calendar", handler = "org.richfaces.view.facelets.CalendarHandler")}} Some definitions what need to be configured per component library: e.g. prefix for component type/family/renderer, etc. Only classes which violates conventions would be necessary to configure specifically.