-
Notifications
You must be signed in to change notification settings - Fork 0
ReleaseNotes_0_5_3
Highlights of this release:
- new Tutorial HelloBundle
- Node-Registry will now find itself a free port
- property org.bundlebee.weaver.instrumentedmethods is now changeable from within the runtime
- issues resolved
We have a new Start Bundle. You can read about it, in our first BundleBee Tutorial:
Getting started with BundleBee
If you want to start two instance of BundleBee on the same system (e.g. to have a better use of a two core CPU),
there was the problem, that the service of each BB-Instance need to be mapped on different port.
You can configure the two port within the plugins/config.ini file. Started with this release, the distributed registry
is able to find itself a new, available port, if the port-number from the settings is already in use.
The in property org.bundlebee.weaver.instrumentedmethods you can set the Java-elements (Packages/Classes/Methodes)
being instrumented by the BB-Framework. You are now able to change the value of this property within your runtime.
You can either get the value: bbmethods get, set a new value bbmethods set org.bundlebee.weaver.instrumentedmethods=“…”
or load a property file from an url to change the value bbmethods load http://example.com/config/bb.properties.
- #22 Fix Maven Build