Tapestry Mixins & ClassTransformations

Tapestry‘s Class Transformation can save you a lot of time and can show you clearly why it is better than inheritance most of the time. This blog has many examples of it. I just finished a new one. Here is the scenario. I want a label to have a title attribute(simple tooltip) which is to be fetched from the message catalog of the corresponding component/page. This is not that difficult, just create a mixin. But what if you want all labels to have this feature, even the ones you have no control over like the labels in BeanEditors.

Lets go step by step. First the mixin

public class HelpText {

    private Environment environment;

    void setupEnvironment(MarkupWriter writer) {
        final ValidationDecorator delegate = environment.peek(ValidationDecorator.class);
                new HelpTextValidationDecorator(delegate,  environment));



This mixin just pushes our own ValidationDecorator implementation onto the Environment.

public class HelpTextValidationDecorator extends ValidationDecoratorWrapper {
    private static final Logger logger = 
    private ValidationDecorator delegate;

    private Environment environment;

    private PropertyEditContext propertyContext;

    public HelpTextValidationDecorator(ValidationDecorator delegate, Environment environment) {

        this.delegate = delegate;
        this.environment = environment;
    public void insideField(Field field){
        propertyContext = environment.peek(PropertyEditContext.class);

    public void insideLabel(Field field, Element labelElement) {
        delegate.insideLabel(field, labelElement);

        ComponentResources resources = ((Component)field).getComponentResources(); 
        String helpText = null;

        if(propertyContext != null){
            helpText = getHelpTextForBeanEditForm(resources);
        }else {
            helpText = getHelpText(resources);
        if(helpText != null){
            labelElement.attribute("title", helpText);
        ValidationDecorator currentDecorator = environment.peek(ValidationDecorator.class);
        if (currentDecorator == this) {

    private String getHelpText(ComponentResources resources){
        String propertyName = ((InternalComponentResources)
        Messages messages = resources.getContainerMessages();
        return getMessage(messages, propertyName, resources);
    private String getHelpTextForBeanEditForm(ComponentResources resources){
        Messages messages = propertyContext.getContainerMessages();
        String propertyName = propertyContext.getPropertyId();
        return getMessage(messages, propertyName, resources);        

    private String getMessage(Messages messages, String propertyName, 
            ComponentResources resources) {
        String key = propertyName + "-help";
        String helpText = null;
        if (messages.contains(key)) {
            helpText = messages.get(key);
         }else {
             logger.warn(String.format("key %s in properties file of page %s", key, 
        return helpText;

This decorator delegates most method calls to the original decorator. Method insideField() stores the PropertyEditContext into an instance variable which is later used by insideLabel(). insideLabel() method is called just after creating the opening tag of label. We add an attribute named title to the label tag. The content of the title are obtained from the message catalog. The key and message catalog are obtained from PropertyEditContext in case the label is within a beaneditor, otherwise these details are obtained from the container’s ComponentResources. Note we are using value parameter for obtaining the property name, so it will only work for form fields which have a value property for input. Finally we remove the decorator from the Environment.

Now that the mixin is in place, we need a way to add this mixin to every label. Here comes the magic, Class transformation. We implement ComponentClassTransformWorker.

public class HelpTextMixinWorker implements ComponentClassTransformWorker {

    public void transform(ClassTransformation transformation, MutableComponentModel model) {
        if (Label.class.getName().equals(transformation.getClassName())) {



For Tapestry 5.3+, the code is a bit different

public class HelpTextMixinWorker implements ComponentClassTransformWorker2 {
   public void transform(final PlasticClass plasticClass, 
        TransformationSupport support, MutableComponentModel model) {
        if (Label.class.getName().equals(plasticClass.getClassName())) {


Finally, remember to contribute this to the ComponentClassTransformWorker(ComponentClassTransformWorker2 in case of 5.3+) service.

    public static void
            provideWorkers(OrderedConfiguration<ComponentClassTransformWorker> workers) {
        workers.addInstance("HelpTextMixinWorker", HelpTextMixinWorker.class);

Tagged: , , ,

One thought on “Tapestry Mixins & ClassTransformations

  1. Lance September 1, 2011 at 6:59 PM Reply

    Can you please explain to me why you chose to pop() the ValidationDecorator from the environment in HelpTextValidationDecorator.insideLabel() instead of HelpText.afterRender()?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: