Here's an explanation for what's going on there. I can see how this might
be confusing to a new user.

The Configuration page in the Web Console displays a combination of the
currently defined Configuration objects *and* available Metatypes. Now what
might be a bit confusing is that when you have a @Component and @Properties
annotations, you don't actually generate a Configuration object (in the
Configuration Admin sense). Instead, what you are really defining is the
default properties for the component. For a component without a
Configuration, it will *only* be displayed on the Configurations tab if
there is metatype available for this. For a component with a Configuration
but without metatype, it will be displayed, but with a message in the popup
about how the metatype was automatically generated (or something like that).

The interplay between Declarative Services, Configuration Admin, and
Metatype take a bit getting used to. This might come across as a RTFM
comment, but in all seriousness, I highly recommend that anyone using this
platform read these three specifications to really understand what's going
on under the hood.

HTH,
Justin




On Tue, Sep 29, 2015 at 5:17 AM Roll, Kevin <[email protected]> wrote:

> That was it! Everything showed right up. Unfortunately I did not see that
> documented on any of the various pages I looked at. Thanks!
>
> -----Original Message-----
> From: Justin Edelson [mailto:[email protected]]
> Sent: Monday, September 28, 2015 7:56 PM
> To: [email protected]
> Subject: Re: Configuration Admin Service
>
> On your @Component annotation is metatype set to true?
> On Mon, Sep 28, 2015 at 7:39 PM Roll, Kevin <[email protected]> wrote:
>
> > Apologies for a simple question. I'm trying to write my first
> > ManagedService... I have an existing service that now implements this
> > interface and has the @Component and @Service annotations and some
> > @Property annotations as well. I see the appropriate XML in the file
> under
> > OSGI-INF. I have a BundleActivator that registers the managed service (as
> > shown here:
> >
> http://felix.apache.org/documentation/subprojects/apache-felix-config-admin.html
> ).
> > The problem is, no matter what I've tried, my bundle does not show up on
> > the Configuration page in Sling. Is there another step that I've missed?
> > Thanks!
> >
> >
>

Reply via email to