You're right. I'm not sure what I was doing incorrectly, but it was likely the way I was quoting the variables or not quoting them in some cases.
Luckily it's alot easier than I was making it. I can use either of the __javaScript() or __BeanShell() functions to solve my problem. Thanks. On Wed, May 6, 2009 at 11:09 AM, sebb <[email protected]> wrote: > On 06/05/2009, Ed Young <[email protected]> wrote: > > Once again, as soon as I posted below, I seem to have solved my problem, > and > > again it's much simpler than I'd made it. > > > > I simply made a user variable something like this: > > > > CONTENT_LENGTH ${__BeanShell("v=0${RTSP_PORT}o=- ${SESSION_ID} 0 IN > IP4 > > ${HOSTNAME}s=t=0 0a=X-playlist-item: ${PROVIDER_ID} ${ASSET_ID}c=IN IP4 > > 0.0.0.0m=video 0 udp MP2T".length())} > > Same would work with __javaScript(). > > > The only issue is whether I need to include the CRLF > __javaScript('\r\n') in > > the content length calculation. I had to omit it from the above > > CONTENT_LENGTH because it seems BeanShell doesn't like having > __javaScript() > > functions passed into it. > > > > BeanShell does not see function calls or variable references as these > are resolved before the string is passed to it. > > But why not just use "\r\n" in the string? > > The only tricky part is where a variable contains double-quotes, in > which case "${VAR}" won't be a valid string. The solution is to use > vars.get("VAR") which is a string. > > > > > On Wed, Apr 29, 2009 at 7:13 PM, sebb <[email protected]> wrote: > > > > > > > On 29/04/2009, Ed Young <[email protected]> wrote: > > > > Is there a way to calculate the length of some string, including any > > > > embedded variables? > > > > > > Why do you need to do this? > > > > > > > It would have to first expand the variables and then do the > > > calculation... > > > > > > Just pass the string to a function that returns its length; variables > > > are resolved before the function is called. > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: > [email protected] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > -- > > > > - Ed > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- - Ed
