A DESCRIPTION OF THE REQUEST :
Right now if you try encoding java.io.File() you get a very cryptic exception message:

java.lang.RuntimeException: failed to evaluate: <unbound>=Class.new()

This is fine if you know exactly what you are encoding. If however, you are encoding some object which in turn contains another object and so on and somewhere down the line a File or some other non-Bean class is being encoded, you will get the same message and there is absolutely no way to find out what the heck the message means.

It is likely easy to fix (since you are doing the encoding and have access to the source-code) and it is almost impossible to to work with the current implementation.

JUSTIFICATION :
Trying to figure out why encoding fails currently involves a lot of guess work, trial and error until the problem is isolated. This can takes *days* depending upon how complex your encoding operation is.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
If class A cannot be encoded because class B cannot be encoded because class File cannot be encoded, so I expect to get an exception message like this:

RuntimeException: Cannot encode class A
...
caused by: RuntimeException: Cannot encode class B
...
caused by: RuntimeException: Cannot encode class File
ACTUAL -
RuntimeException: Cannot encode class A
...
caused by: RuntimeException: Cannot encode class A
...
java.lang.RuntimeException: failed to evaluate: <unbound>=Class.new()
###@###.### 10/15/04 02:55 GMT