Bug #20

cannot use primitive types as parameters for remote calls

Added by Jörg Plewe over 2 years ago. Updated about 2 years ago.

Status:Closed Start:10/02/2009
Priority:Urgent Due date:
Assigned to:Jörg Plewe % Done:

100%
Category:Weaving
Target version:0.5.2

Description

Parameter classes are resolved from their names in ManagerImpl#loadClass(). For primitives, this does not work by e.g. classLoader.loadClass("int").

Caused by: java.lang.ClassNotFoundException: int
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:481)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
        at org.bundlebee.manager.impl.ManagerImpl.loadClasses(ManagerImpl.java:242)

History

Updated by Jörg Plewe over 2 years ago

  • Target version changed from 0.5.3 to 0.5.2

Updated by Jörg Plewe over 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Fixed with r2780.

Just try to resolve primitive names ('int', 'float',...) against their types (Integer.TYPE, Float.TYPE,...) first.

Updated by Philipp Haußleiter about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF