Although the previous two answers are basically correct, I don't think they really contain the response to Peru's initial question. I hope that the "elders" of this list will clarify things a bit for him. :-) I considered that I'd better avoid responding myself to this, as one that sometime ago was asking (myself and others) why should using the <logic:equals> or <logic:iterate> be better than using the equivalent java code - which was also faster for me to do than learning the new tags.... Still... In this specific case, maybe the answer is not writing a whole new custom tag at all. It wouldn't be very efficient anyway, especially if the "parsing" mentioned is done in one or two particular places only. It might show that maybe a model layer does not exist for the application, and maybe the data is directly retrieved from a (probably legacy) database. (Forgive me if I'm wrong.) At least that parsing could be done in the Action that prepares the view, and the data stored in a form that is easier to display. Even if you will still chose to use a custom tag for that, attaching it to the struts standard "logic" taglib wouldn't be a good choice ( if that was what you meant by a tag used as
<logic:substring ...>) Radu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
