and then i found Apache Wicket!

So what you do is write a component that extends from the framework supplied Link class -

class DobLink extends Link{

DobLink(String id,List dobs){
super(id, new Model(dobs));
}

@Override
public boolean isVisible(){
List dobs = model.getModelObject();
return !dobs.isEmpty();
}

@Override
public void onClick(){
setResonsePage(new DobPage());
}

}

In the HTML template – (wicket works with plain HTML templates)

Other Date(s) of Birth

and on the server-side page class –

add(new DobLink(“dob”, dobList ));

Now the link visibility will toggle based on the dobList size.
I would strongly recommend Wicket for all tag lib haters.

There is a grails-wicket plugin apparently. Need to take a look!

I created one, (clearly for us in the states) for a state drop down list that also allows a passed in default choice for state if one had been selected previously and is in session or otherwise.

Our project doesn’t have a States table to pull from and it was getting to be a pain typing it again and again. We then tried including the list but it was difficult to pull off if someone was using different names for the already selected state, etc. A custom tag was the answer! Went from all those lines of code down to one line in the GSP.

Missed you at GUM, BTW.

static namespace = “data”

let’s you prefix your taglib with ‘data:’ rather than ‘g:’

<data:moreData …

Once you have a bunch of tag lib classes, it makes it a little easier to know which *TagLib.groovy class to look in to find the implementation.