I gave up on using a .tag file to do this and wrote my own Tag class. In the process I think I may have learned something that relates to this problem: No matter the expression language to be applied to the attributes of a tag, they are all set as Strings. In doTag() (or a related method with body tags) those String expressions may be evaluated and somehow non-strings retrieved. Maybe this means that maybe the right way to pass objects in to .tag files is to pass a string that would evaluate to the object, and somehow inside the .tag file to force an extra (nested?) ognl evaluation? (All that said, why does the attribute declaration allow a type specification if they're always Strings? -- Does that mean this is a red herring?)
Hope that helps someone else solve this problem at some point. If you do, please respond to me/this thread letting me know the real solution. On a related note--I've found no way to prevent a trailing newline in a .tag file, and therefore in the output of the evaluated tag. The Tag Class also solved that problem. -Dale Newfield [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Struts2-WebWork-and-tagdir-style-tags--tf2681755.html#a7500798 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
