On Thu, Nov 26, 2009 at 23:08, Vidar Ramdal <[email protected]> wrote:
>> Yes, using the jcrinstall bundle and creating a sling:OsgiConfig node
>> (which you can easily define as initial content). The node must reside
>> in a "config" folder [...]
>
> You mean "install", right?

No, but I think the name is not important, the nodetype
sling:OsgiConfig is the marker here. (@Bertrand: could you clarify?)

> I'm struggling to get this to work. When I manually create a
> LogManager.factory.config configuration (through the web console), the
> configuration appears on the "Configurations" drop down list. Also, a
> .config file is created in the
> sling/config/o/a/s/c/log/LogManager/factory/config directory, called
> dc2c6dfb-47c4-40c8-bf55-1651bb557504.config.
> The configuration also works: The custom logging I've set up is working.
>
> Now, to avoid having to set this up manually each time I deploy my
> application, I thought I could just put that file in my bundle, and
> loading it as initial content under
> /apps/mybundle/install/dc2c6dfb-47c4-40c8-bf55-1651bb557504.config

No, as mentioned above, it should have the service pid, which in this
case is "org.apache.sling.config.log.LogManager.factory.config". If
you look at the Felix web console you'll find it as PID at the bottom
for copy&paste. The uuid you used is only an implementation detail of
how Felix persists the configuration on the filesystem. Try

/apps/mybundle/config/org.apache.sling.config.log.LogManager.factory
(using the sling:OsgiConfig nodetype)

Regards,
Alex

-- 
Alexander Klimetschek
[email protected]

Reply via email to