Here are some of the errors:
Invalid method signature: tring;)Ljava/lang/Object; null
Invalid method signature: ava/lang/Object;)Ljava/lang/Object; null
Invalid method signature: /Object; null
Invalid method signature: ava/lang/String;)V null
Invalid method signature: ;)V null
Invalid method signature: (Ljava/lang/String;)Ljava/lang/StringBuffer; null
Invalid method signature: (Ljava/lang/String;[Ljava/lang/String;)Ljava/lang/Object; null
Invalid method signature: g;)Ljava/lang/Object; null
Invalid method signature: runtime/CFPage;[Ljava/lang/Object;)Ljava/lang/Object; null
Invalid method signature: ;)Ljava/lang/Object; null
Invalid method signature: /String;)Ljava/lang/Object; null
Thanks for reading this! I'm pretty desperate for a fix to this problem.
It doesn't seem to matter much what I'm passing into evaluate(). I use it to get at data in dynamically named queries, replace placeholders in text with labels, and run dynamically-generated CFScript. All of these events can trigger the error.
I'm aware that evaluate() is not always the best way to do things, but it is sometimes far more convenient than other methods, and in some cases is the only reasonable way to accomplish a task.
It seems to me that this is a bug in evaluate(). Anyone from Macromedia willing to take a look at this problem?
Invalid method signature: (Lcoldfusion/runtime/Variagle;
Is there anyone associated with Macromedia who can shed any light on this
because I think the number of people here who have expressed their problems of
this without any resolution is a worrying issue!?
Invalid method signature: ;[Ljava/lang/String;)Ljava/lang/Object; null <br>The error occurred on line 184.
Is anyone listening here?
I'm going to look at the evaluate() idea and see if that has anything to do
with it but. MM need to answer us on this one!
The bug we logged is 59825. It was a sync issue with the evaluate() call -
too technical to get into here. A public hotfix wasn't made available.
This fix made it into 7.0.1. You can call support to get the 6.1 hotfix or
you can just use the workaround.
The only problem is that support wants $499 in advance (which will be
refunded, due to the MM post above stating that it is a bug) and they cannot
seem to get my creditcard data into the system.
Is this hotfix available somewhere other than through the rather tedious
procedure of calling support?
We have tried installed the ColdFusion 6.1 updater, cleared class files and
unchecked "Save Class Files". However the Invalid Method Signature error stills
occurs every now and then.
Explaining that this is a bug in ColdFusion and not our code sounds like an
excuse that they won't (and shouldn't) accept.
I tried searching this site for the hot fix you mentioned with no success.
no hot fix for this issue.
Forcing our clients to upgrade to ColdFusion MX 7 because you guys have a bug
in your 6.1 product is, to say the lease, unfair. Please provide a direct link
to the hot fix for this problem.