Hi again David
ManagedProperties uses the Configuration Admin ManagedService and MetaType
service for everything it does. It really is just spice on top, so except
for making the configuration widely available, i don't see how i could
really go against the divisions of resposibility you describe.
Sorry for double posting, but it seems, that my first email was not working? At
least in mail-archive the thread is not accessible for some reason
(https://www.mail-archive.com/users@felix.apache.org/msg18161.html)
Starting some days ago, the GoGo shell is gone crazy and prints something like
I've tested the factory configuration and I am afraid that my problem is not
being solved with this approach.
I think I might have to explain the problem in more detail, that you'll get a
better understanding.
I am implementing a REST service using the HTTP Whiteboard mechanism. This
interface
On Fri, Jul 13, 2018 at 4:37 AM, Philipp Höfler <
philipp.hoef...@pernexas.com> wrote:
> I've tested the factory configuration and I am afraid that my problem is
> not being solved with this approach.
>
> I think I might have to explain the problem in more detail, that you'll
> get a better
The Felix team is pleased to announce the release of Felix Log Service
version 1.2.0 & Log Service Framework Extension 1.0.0
The Felix Log Service implements OSGi Log Service specification at
version 1.4 (R7).
The Felix Log Service Framework Extension is a framework extension
that bootstraps the
Hi,
I'm following the current development of OSGi support in Vaadin 10/11
and found this issue:
https://github.com/vaadin/flow/issues/4376
Vaadin seems to make use of a ServletContainerInitializer for its Routes
and it seems not to work with jetty and felix.
Is there support for
Hi,
there is no support for ServletContainerInitializer in the OSGi
whiteboard specification and therefore no support in the Apache Felix
implementation.
Major reason of this is the dynamic nature of OSGi, bundles can come and
go and when a bundle arrives the servlet context might already be
On Fri, Jul 13, 2018 at 11:17 AM, Carsten Ziegeler
wrote:
> Hi,
>
> there is no support for ServletContainerInitializer in the OSGi
> whiteboard specification and therefore no support in the Apache Felix
> implementation.
>
> Major reason of this is the dynamic nature of OSGi, bundles can come
I've been doing some work to enable the HTTP/2 support in jetty for usage
within the Felix Http Jetty 4.x bundle for an apache sling based project.
I'm not sure about the history of the felix.http.jetty bundle, but can I
ask why it was decided to make copies of the jetty classes inside the felix
Hi Martin,
If I understand what you are saying, it doesn’t seem very osgi friendly to me.
To me the “osgi way” would be to have the config admin service work from normal
property files, databases, or what have you, and have ManagedProperties only
work from configuration from config admin.
Hi Philipp,
Can you tell me which versions of the gogo bundles you are using? and whether
you are using org.apache.felix.gogo.jline or org.apache.felix.gogo.shell?
Also, how do you invoke the framework? e.g. from command line? from IDE? (which
one?)
The output looks very like gogo has a
Hallo Derek,
thanks for your reply.
As I am quite unfamiliar with all the osgi stuff, I am not sure if I can
completely answer all of your questions.
My application is basically based on the OSGi enRoute REST service sample [1].
In the debug.bndrun file the following Gogo lines are available. I
12 matches
Mail list logo