I'm also a WebObjects guy, taglibs pretty much do the same thing as WOComponents, and I can't particularily think of any case where they can't. You can create tags that are as coupled or uncoupled to each other as you'd like.
> the big problem ive been having, coming from a WebObjects environment, is > that its not so easy to set up reusable components. for instance, one of > my components creates a table. another component builds on that and > creates a table of checkboxes. doing this in a taglib is impossible ( to > my knowledge ), so one has to do it ina JSP. icky. Not impossible at all -- one could do this with nested <logic:iterate> tags and an <html:checkbox>, so why couldn't one do it in a custom manner? > in one of the current projects im working on, we need to display search > results in a specific manner. however, there are at least 7 different > ways to generate search results, each of which has their own action ( > with some common search classes shared in between them all ). i wasnt > able to just say "ok, this component will display an item the way we > want it. as you're looping through, just use this one component." Is this a static or runtime determination of which render component to use? If it's dynamic, you'd have to write a visitor to pick the right renderer. If it's static, it's just a matter of nesting a renderer tag inside your table building tag. I'd need more concrete information to give you a code example of the idea.... Naturally the main thing annoying about writing custom taglibs is that the BodyContent stack model takes getting used to... but its complexity is due to the fact it gives you pretty much full control to do almost whatever you'd like with your tags. Cheers Stu Charlton Infusion Development http://www.infusiondev.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
