works fine for me!
On 2014-12-22 17:12, Alexander Broekhuis wrote:
I've pushed a fix for this, can you please check if it is ok now?
2014-12-22 16:55 GMT+01:00 Alexander Broekhuis :
I've found the problem.
What happens: The LogService uses a ServiceFactory. Following the
spec, a
ServiceFac
When adding the logHelper I tried to prevent changing the API - that's
why I did it like this (and the RSA it is not the only bundle that uses
more than one logHelper). But looking at your explanation, I think
having one logHelper and therefore having an according API change is the
preferable
I've pushed a fix for this, can you please check if it is ok now?
2014-12-22 16:55 GMT+01:00 Alexander Broekhuis :
> I've found the problem.
>
> What happens: The LogService uses a ServiceFactory. Following the spec, a
> ServiceFactory will only create an actual service the first time a bundle
>
I've found the problem.
What happens: The LogService uses a ServiceFactory. Following the spec, a
ServiceFactory will only create an actual service the first time a bundle
calls "getService". This service is cached, and reused each time a bundle
does a getService on the factory.
So for the logger,
Hi Alexander,
I see the same, but only with the latest commit. So I assume some of
your (correct) changes in the last commit is triggering this now. I'll
check whether I can figure out what's going on here ...
Regards,
Bjoern
On 2014-12-22 15:01, Alexander Broekhuis wrote:
Hi,
I'm work
Hi,
I'm working on the current remote_proxy_factory to make it more generic, so
that it is easier to use.
During testing I ran into a crash when an endpoint is published for which
no proxy bundle is available. This crash is due to a call to the
logHelper_log function. I tried to trace the problem
