felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Daniel <david.daniel.1...@gmail.com>
Subject Re: Immediate not active but satisfied
Date Fri, 21 Jul 2017 14:24:59 GMT
Yes.  I will put a try catch around my activate.  I didnt even think about
that.  Thank you.

On Fri, Jul 21, 2017 at 10:23 AM, Carsten Ziegeler <cziegeler@apache.org>
wrote:

> Hi,
>
> could it be that you have an activate method and it throws an exception?
>
> Regards
> Carsten
>
> David Daniel wrote
> > I was under the impression that if a component is marked as
> immediate=true
> > then it would start and run as a singleton once it was satisfied.  This
> is
> > apparently not the case.  Is there a way to say once I have been
> satisfied
> > then start and stay active until shutdown.
> >
> > @Component(service = {UndertowServer.class},
> >         immediate=true)
> > public class UndertowServer {
> > ...
> >
> >
> >  [  69]   com.orbis.aardvark.web.services.UndertowServer  enabled
> >     [  28] [satisfied   ]
> >
> >
> > Thank you for any help,
> >   David Daniel
> >
>
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message