Apparent Problems with Release 2.3 JavaScript Debugger

MikeBeaumont

When reviewing/evaluating Release 2.3 RC0 Javascript Debugger, we find that it works fine until any line that uses the 'new Packages' command with a non JRE class.
So
initialContext = new Packages.javax.naming.InitialContext()
works fine, but
myBean = new Packages.org.examplebean.MyBean()
does not and it throws an
'org.mozilla.javascript.EcmaError: TypeError: [JavaPackage org.examplebean.MyBean] is not a function, its is NativeJavaPackage.
This is the case despite putting the user class (in this case 'MyBean') in the ReportViewer's classes directory.
We know that our code is ok, because the report runs fine in the 'Preview' mode outside of the debugger.
Where do the user classes, libraries have to go to be visible to the Javascript debugger?
Thanks in advance.