Anything like that, which you can create a small, repeatable test case for, should be sent to WT to look at. I'm not saying that it IS a bug and/or that it WILL be fixed, but they should know.
Personally, I've used custom tags as quick means to return data (either from a standardized db lookup or a particular data manipulation I want done - like shorthand inline callmethod), I've never used them within other tags, and I suspect that the 'thought' process within Witango might not be ideal here. I would be interested in seeing what you are doing, if you'd care to CC me on your email. I can also do some testing here, and I would be interested to see if there's a behavioral difference between 5.0 and 5.5. Robert -----Original Message----- From: John McGowan [mailto:[EMAIL PROTECTED] Sent: Thursday, June 23, 2005 10:55 AM To: [email protected] Subject: Witango-Talk: Custom Tags in expressions So... Are there known issues with using Custom Tags in expressions. (ie, "If" Actions, expr="" attributes etc...) because It's not something we've ever really done before, and now that I'm testing out a couple of new custom tags that i will be doing that sort of thing with i'm seeing some very strange behaviour. Like "LEN(<@mycustomtag>)" where <@mycustomtag> returns an empty string, LEN is returning "56" obviously wronge, If I assign the output of the custom tag to a var and do a len on the var it returns 0 like it should... Just wanted to know if these issues were know about by anybody else or if they are new and I should submit bug reports. /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
