Java EE (Java Enterprise Edition) General Discussion

I have the Core Java Server Faces book, and in reading the "Component" chapter, there is an example of creating a Component which acts like Tab pane, that simply links to different pages.

Is this a practical application ?
I have implemented something similar on a site (using struts), but simply used raw HTML and CSS, put it into an include, and, viola. Done.
The total code is about 10 lines, and the actual code needed to do the include is about 3 lines... looking much like the custom tag shown in the book.

Here are the only reasons I think this is actually practical... and please give me some other reasons, as I tooootally want to know some reasons why you'd code near 1000 lines (UI Component, the tag, a renderer...etc):
1) the Renderer. you could code your app so it's available to be rendered on a cell phone, etc.
2) cutting out the hardcoded html... but don't see this as that big of an issue.

Let me know what you think. I'm trying to decide whether to refactor my tabs into a component... but, I'm thinking it's not worth it.

Any help would be appreciated !
Thanks !!