Skip to content
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.

Devlog

Jump to bottom
Philipp Haussleiter edited this page Nov 25, 2015 · 1 revision

Devlog

20100304
Refactored the remoting code, streamlining esp. exception handling. The protocol changed, so this is not compatible with earlier versions.

20100113 phl

  • Added new Command to set/get istrumentedMethods:
    bbistrumentedMethods | get | set | – gets/sets the istrumentedMethods property of the BundleBee grid node.
  • Updated maven profiles:
    -P release – Builds the assembly file with all example modules.
    -P examples – Builds the BundleBee project with all example modules.

20100108
Created and fixed #28 (r175): I got an IllegalAccessException for yet unknown reasons

20091020
Fixed #17: avoid weaving static methods

20091019 joergp
Weaver: removed org.eclipse.* from privatePackage, shrinking the jar from 2MB to 1MB

20091012 joergp
Added sample application ‘Examples/Fractal’ that computes and displays mandelbrot sets in a distributed way. Can be started from the console using bbfractalui.

20091011 phl
Started with working on issue #21. There is a maven plugin, to build and sign a webstart application.
To use this build cycle there was first the need to fix the current maven build #22.
The next big task will be a starter application that will start the BB Framework within a Java Webstart application. I plan to solve also issue #13 with this approach.

20091002 joergp
Fixed several classloading issues: #18, #19, #20

  • javassist failed at runtime when custom type have been used as parameters. $sig cannot be resolved
  • after fixing that: a servicefilter could not be correctly determined, bc. the $sig class had a different classloader from ‘this’
  • after fixing that: the custom type could not be resolved on the remote side, bc. the CL of the servlet bundle cannot access the custom bundle (thats how OSGi is intended to work)
  • after fixing that: the remote site could not handle primitive parameter types when calling the service by reflection

20090930 joergp
Integrated project EchoCLI into TestBundle, for they are very closely coupled and EchoCLI consist of nearly nothing.

20090930 joergp
Redesigned weaved code in project Weaver. It has been factored so that only 3 lines of code remain to be weaved in.
It is threadsafe now.
Established proper exception handling for exceptions that occured in the remote site:

  • If a runtime exception occured, it is just rethrown.
  • If one of the the declared exceptions of the method occured (taking inheritance into account), it is rethrown.
  • Otherwise a BundleBee runtime exception is thrown.

20090928 joergp
Created an ANT based build system (#8). See Build with Ant. Cleaned up dependencies a bit.
Also added a complete set of NetBeans projects.

20090925 joergp
Fixed #7. Service methods may now return primitve types.
Added a test command for the CLI calling example services from TestBundle.

20090923 joergp
Fixed #5. The javassist ClassPool needs to resolve custom types when compiling the weaved-in code. Therefore, the ClassPool needs to access the classpath of the bundle which is currently loaded. Luckily, that classloader is provided by the framework and can be used to augment the ClassPool.

20090915 joergp
Fixed #6. Pass the classloader of the invoked bundle object down to the remote service invocation so that classes of the returned objects are derived from the same context as calling bundle object.
It happened to be that classes ‘Call’ and ‘ServiceCallAspect’ had a different classloader which then was used for class loading in the incoming ObjectInputStream, leading to a ClassNotFoundException. The exact reason why the classloaders are different has not yet been investigated.

20090915 joergp
Updated javassist from 3.7 to 3.11.0.GA.

20090908 joergp
Implemented #12. See Security.

Clone this wiki locally