Hi Pieter,
The short answer is "no", but you should take a look at remote services.
The way Pelix/iPOPO works (registries, direct calls, ...) is not directly compatible with the way multiprocessing works (fork, pipes, queues, ...).
However, if you use services to give access to the core features of your bundles, you might have two ways to run your code in different processes:
1/ Using remote services [1]: you start as many Frameworks as necessary and let them detect their peers and consume their services;
2/ By having a single Framework, but each bundle start a new work process. Some proxies can be registered as services to send orders to and retrieves results from the underlying process.
In both cases, the services are consumed the same way: only the underlying binding changes.
Using remote services [1] is easier to implement (everything is already included), but costs I/O time.
Having services to hide the multiprocess aspect gives more control and maybe costs less I/O time, but it needs to be developped from scratch.
Kind regards,
Thomas