Why do you have both the .config file and the sling:OsgiConfig nodes
for the same service pid?
I edited the config once using felix console. I think it created the
.config file while the sling:OsgiConfig node was already created by me
earlier.
On Mon, Feb 2, 2015 at 7:03 PM, Bertrand Delacretaz
The class org.apache.sling.installer.provider.jcr.impl.JcrInstaller is
by default configured to only take folders into account that are
called install. In CQ/AEM folders may be called install or
config.
Regards
Julian
On Mon, Feb 2, 2015 at 1:54 PM, Bertrand Delacretaz
bdelacre...@apache.org
Hi Bertrand
My config appears in status-configurations and is also available in the
component's 'activate' method whenever they change. So this part is working
fine. I observed that within my sling instance, there is a config folder
which had the 'service-pid.config' file created for this
please also take not of this recent discussion on the sling-dev mailing list
http://apache-sling.73963.n3.nabble.com/RT-Sling-Resource-Providers-for-NoSQL-databases-MongoDB-Couchbase-tt4046669.html
an example for an existing NoSQL resource provider that solves these problems is
Hi,
On Mon, Feb 2, 2015 at 2:25 PM, connuser1 connuser1 connus...@gmail.com wrote:
...I think whenever a install/service-pid.config node gets
created in the repo, the changes done to the sling:OsgiConfig node stop
taking effect
Yes, if you have two ways of specifying the config of a
Another observation. After editing my service's config atleast once using
the felix console, things start working perfectly, That is, now all changes
that I make in the config node, get applied on the service. Editing the
config once using felix console does some (binding...?) magic which I am
not
Hi,
On Mon, Feb 2, 2015 at 1:48 PM, connuser1 connuser1 connus...@gmail.com wrote:
...Editing the
config once using felix console does some (binding...?) magic which I am
not sure of
If you are able to edit your config from the Felix console it means
that it was indeed created...
If you
On Mon, Feb 2, 2015 at 2:39 PM, connuser1 connuser1 connus...@gmail.com wrote:
On Mon, Feb 2, 2015 at 7:03 PM, Bertrand Delacretaz bdelacre...@apache.org
wrote:
Why do you have both the .config file and the sling:OsgiConfig nodes
for the same service pid?
I edited the config once using felix
Hi
I am trying to configure a service by creating a node with jcr:primaryType
as sling:OsgiConfig in the /app/my-project/config directory. I am
following the steps as detailed in [1]. But I am unable to see the
configuration getting applied. Could someone please guide, what could I be
missing?
While I am still trying to figure out other differences, here are a few
observations:
One difference that I found was that the config file was placed in
'install' folder for sling-test while I was keeping it in 'config' folder
as per the docs. So I changed it to 'install' folder. Otherwise the
Thanks Bertrand. I'll compare with it.
On Mon, Feb 2, 2015 at 4:57 PM, Bertrand Delacretaz bdelacre...@apache.org
wrote:
Hi,
On Mon, Feb 2, 2015 at 11:40 AM, connuser1 connuser1
connus...@gmail.com wrote:
...I am trying to configure a service by creating a node with
jcr:primaryType
as
I've created an EventHandler service similar to the dropbox example [1]
Is this example still current for the sling trunk build?
I have the same boilerplate initialization for the Component as the dropbox
example:
@Component(immediate=true)
@Service(value=EventHandler.class)
Another oddity I noticed is that if I try to examine my components from
the sling web console components tab, selecting any of them gives a 404
rather than any actual information. This implies there is something broken
in the structure of the bundle an possibly not related to the actual log
errors
13 matches
Mail list logo
