No error message was thrown, no .jar file was added to Repository or Repository settings, nothing happened. See juggler.jar in Attachments.
[IAN] The bug is in that the JAR requires some other JAR to be in the classpath.
I.e. we need to implement better notification of errors during beans installation
[IAN] Juggler.class includes this import:
and there is no class MethodTracer included in juggler.jar or in standard JDK
This report is a bit old. The behaviour is slightly different now - at least
some excpetions like ClassNotFoundException or NoClassDefFoundError or
InstantiationException are thrown...
So I've implemented two types of checking:
- during bean installation, the bean class is tested if it can be loaded,
- when bean is added to the form, it is tested if it can be instantiated.
In both cases right exceptions are caugth and user is given a message.
Morover, class loading error is detected during creating palette items and
component palette doesn't freeze up.
Is it enough?
verified in [nb31](34),[pilsen](010116)
BUG also appears in version : FFJ20
better step to reproduce :
- install new bean ( from attachment .jar file)
- select all beans (2)
- add to component palette
if you select palette category, you can see Error window,
and if you add bean from palette to your form you can see Error window again.
Created attachment 473 [details]
Jar file with bad beans
Resolved for 3.3.x or earlier, no new info since then -> closing.