Hi,
yes, this is afaik the only backwards incompatible change, but it
needs to be there. RIFE 1.5 implements a custom version of
CharSequence that does supports dynamic strings. This is needed to
fill in the values of stateful components that are executed later in
the request processing.
If you're using the values directly into a template (which you should
to do), then "template.setValue(CharSequence)" should just work.
Otherwise, append a toString() to it.
Best regards,
Geert
On 09 May 2006, at 15:40, Narendra Jain wrote:
Hello
Just relating to backward compatibility
getExitQueryUrl("exitname") is giving error "Type mismatch: cannot
convert from CharSequence to String"
So I need to add typecasting everywhere.
Regards
--
Geert Bevin Uwyn bvba GTalk: [EMAIL PROTECTED]
"Use what you need" Avenue de Scailmont 34 Skype: gbevin
http://www.uwyn.com 7170 Manage, Belgium AIM: geertbevin
gbevin at uwyn dot com Tel: +32 64 84 80 03 Mobile: +32 477 302 599
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
