[jira] [Created] (SLING-2999) JMX Resource Provider
Carsten Ziegeler created SLING-2999: --- Summary: JMX Resource Provider Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Adding a usage service property to BindingsValuesProvider ?
Hi
Am 06.08.2013 um 20:26 schrieb Justin Edelson:
Hi Carsten,
I can't speak for exactly what Bertrand is thinking, but when I was
thinking about it, the scope/usage was an orthogonal concern to which
engine is selected.
Whereas today you do:
ScriptEngineManager.getEngineByExtension(ecma)
You could do
ScriptEngineManager.getEngineByExtension(ecma, [healthcheck,
workflow])
(of course, we can't actually do that as ScriptEngineManager is a JDK
class; we'd have to create an extension)
Alternatively, this could be done after SlingScript object is created:
SlingScript script = resource.adaptTo(SlingScript.class);
script.setUsage([healthcheck]);
I don't think the SlingScript is the place to set the scope/usage on: The
script is provided with the bindings and executes code. In other words: The
Script does not manage its context or scope or usage itself. [Yes the code
currently does but this is an implementation detail and the actual BVPs are
provided by the SlingScriptAdapterFactory -- so in fact the
SlingScriptAdapterFactory currently does it]
Additionally, in SLING-2993 I proposed SlingScript to be @ConsumerType, so
extending this interface would require a major version update of the package
version.
Other options would be to set the scope on the ScriptEngineManager:
ScriptEngineManager sem = // service Reference
if (sem instanceof SlingScopeSupport) {
((SlingScopeSupport) sem).setScope(...);
}
ScriptEngine se = sem.getEngine
Sling's ScriptEngineManager could then for example create proxy ScriptEngine
objects which would make sure the BVPs are called for script execution.
Regards
Felix
When creating the SlingBindings for the script to execute, the following
BindingsValuesProviders would be consulted (in order):
* the generic BVPs (which apply to all scripting languages)
* the BVPs tagged with the value of the script engine factory's
compatible.javax.script.name property
* the BVPs tagged with the script engine factory's name
* the BVPs tagged with the scope/usage property
Or something like that...
The significant advantage of doing this vs. hardcoding the usage-specific
bindings at the point of script engine access is that it doesn't allow for
downstream customization. Which is important IMHO in the case of
healthcheck - we want to enable custom hc rules which may benefit from a
custom BVP. This is also true in a workflow engine.
Justin
On Tue, Aug 6, 2013 at 1:41 PM, Carsten Ziegeler cziege...@apache.orgwrote:
Ok, just to make it clear, as long as there is no support in all script
engines, I'm -1
Carsten
2013/8/6 Justin Edelson jus...@justinedelson.com
Hi Bertrand,
FWIW, I was thinking about something very similar (although I was
thinking
of calling it 'scope', not 'usage'), but never got around to implementing
it.
+1 for me.
Justin
On Tue, Aug 6, 2013 at 10:58 AM, Bertrand Delacretaz
bdelacre...@apache.org
wrote:
Hi,
I'd like to use BindingsValuesProvider services in my health check
module, to provide bindings like jmx for scripted health checks,
which should be ignored for general Sling scripting (or not - some
providers might apply to both general scripting and health checks).
I'm thinking of adding an optional usage service property to
BindingsValuesProvider services, does anyone see a problem with that?
The Sling script engine would then consider only
BindingsValuesProvider which have no usage property (for backwards
compatibility) or which have usage=scripting.
And my health checks would consider only BindingsValuesProvider which
have usage=healthcheck.
-Bertrand
--
Carsten Ziegeler
cziege...@apache.org
Re: Adding a usage service property to BindingsValuesProvider ?
Hi Am 07.08.2013 um 07:46 schrieb Carsten Ziegeler: I'm not totally against this, but just adhoc adding this property without a complete concept seems wrong to me. Defining the technical selection process (e.g. as you describe it) is one part, but the other equally important part, how to select from a script dev point of view. How can I write a JSP and tag this as a healtcheck script? And how does this work for other scripting languages? I think this is not the question here. A script is a script is a script. It has to cope with the bindings it gets and if there would be missing bindings, it would have to cope. The interesting thing would be a request processing script expecting e.g. the default request binding while this will not be provided by HealthCheck context. Such a request processing script would of course just fail with an NPE sooner or later. A Healthcheck script could fail more gracefully by just checking for required bindings. Can we find a generic way that works in all / most scripting languages? Do we really have different existing use cases apart from hc or is this just a it would be nice? I would not bite my teeth into the scripts or some particular language. This is a dead end IMHO. A script, at the end of the day, executes some action and might or might not expect some bindings (global variables in some languages). The script would have to cope with them missing or of the wrong type or such... But there is not currently a way that a script could declare I am an HC script or I am a Request Processing script. Not even a taglib can do that -- at the end of the day a TagLib is syntactic sugar for functionality, which must also be usable otherwise. Regards Felix As said, for JSPs we have taglibs which would solve the problem and doesn't require a BVP, I think for javascript is something equivalent. Of course as a provider of such support you have to provide different implementations (a taglib, a javascript lib etc.) - and maybe we should tackle it from this angle. Carsten 2013/8/6 Justin Edelson jus...@justinedelson.com Hi Carsten, I can't speak for exactly what Bertrand is thinking, but when I was thinking about it, the scope/usage was an orthogonal concern to which engine is selected. Whereas today you do: ScriptEngineManager.getEngineByExtension(ecma) You could do ScriptEngineManager.getEngineByExtension(ecma, [healthcheck, workflow]) (of course, we can't actually do that as ScriptEngineManager is a JDK class; we'd have to create an extension) Alternatively, this could be done after SlingScript object is created: SlingScript script = resource.adaptTo(SlingScript.class); script.setUsage([healthcheck]); When creating the SlingBindings for the script to execute, the following BindingsValuesProviders would be consulted (in order): * the generic BVPs (which apply to all scripting languages) * the BVPs tagged with the value of the script engine factory's compatible.javax.script.name property * the BVPs tagged with the script engine factory's name * the BVPs tagged with the scope/usage property Or something like that... The significant advantage of doing this vs. hardcoding the usage-specific bindings at the point of script engine access is that it doesn't allow for downstream customization. Which is important IMHO in the case of healthcheck - we want to enable custom hc rules which may benefit from a custom BVP. This is also true in a workflow engine. Justin On Tue, Aug 6, 2013 at 1:41 PM, Carsten Ziegeler cziege...@apache.org wrote: Ok, just to make it clear, as long as there is no support in all script engines, I'm -1 Carsten 2013/8/6 Justin Edelson jus...@justinedelson.com Hi Bertrand, FWIW, I was thinking about something very similar (although I was thinking of calling it 'scope', not 'usage'), but never got around to implementing it. +1 for me. Justin On Tue, Aug 6, 2013 at 10:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, I'd like to use BindingsValuesProvider services in my health check module, to provide bindings like jmx for scripted health checks, which should be ignored for general Sling scripting (or not - some providers might apply to both general scripting and health checks). I'm thinking of adding an optional usage service property to BindingsValuesProvider services, does anyone see a problem with that? The Sling script engine would then consider only BindingsValuesProvider which have no usage property (for backwards compatibility) or which have usage=scripting. And my health checks would consider only BindingsValuesProvider which have usage=healthcheck. -Bertrand -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731716#comment-13731716 ] Felix Meschberger commented on SLING-2999: -- I like this. But why introduce a new namespace mbean ? To prevent collisions with the ObjectName properties ? Could this be solved without a namespace ? JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Adding a usage service property to BindingsValuesProvider ?
On Wed, Aug 7, 2013 at 9:04 AM, Felix Meschberger fmesc...@adobe.com wrote:
...But there is not currently a way that a script could declare I am an HC
script or
I am a Request Processing script...
The missing piece here is that the HC scripts that I'm talking about
(and probably the workflow ones that Justin mentioned) are *not* your
usual Sling script, adapted from a Resource etc.
In the HC case the (mini-)script is just an expression that's part of
an OSGi config (see SLING-2987 for examples), as in:
expression = jmx.attribute('java.lang:type=ClassLoading',
'LoadedClassCount') 10
so the separation between request processing scripts and HC scripts is
obvious. They are executed in very different contexts, which warrant
different script bindings.
In the HC case, bindings need to be provided by OSGi services so as to
be extensible - we have an existing API to do that
(BindingValuesProviders), the proposal is simply to allow that API to
indicate more specifically what the bindings are meant to be used for.
Hardcoded bindings for HC are unnecessarily limitative, and inventing
a different bindings provider API just for HC feels very wrong, so I
have a hard time understanding the reluctance to this proposal.
-Bertrand
Re: Adding a usage service property to BindingsValuesProvider ?
Hi Bertrand
We don't really disagree at all ;-)
In fact having written my previous messages, I wonder, whether our default
values we provide to scripts (request, response, etc.) should not really be
provided by a BVP in the request (or such) scope/context/usage ;-)
Somehow I tend to get to the term context for this thing.
Regards
Felix
Am 07.08.2013 um 09:34 schrieb Bertrand Delacretaz:
On Wed, Aug 7, 2013 at 9:04 AM, Felix Meschberger fmesc...@adobe.com wrote:
...But there is not currently a way that a script could declare I am an HC
script or
I am a Request Processing script...
The missing piece here is that the HC scripts that I'm talking about
(and probably the workflow ones that Justin mentioned) are *not* your
usual Sling script, adapted from a Resource etc.
In the HC case the (mini-)script is just an expression that's part of
an OSGi config (see SLING-2987 for examples), as in:
expression = jmx.attribute('java.lang:type=ClassLoading',
'LoadedClassCount') 10
so the separation between request processing scripts and HC scripts is
obvious. They are executed in very different contexts, which warrant
different script bindings.
In the HC case, bindings need to be provided by OSGi services so as to
be extensible - we have an existing API to do that
(BindingValuesProviders), the proposal is simply to allow that API to
indicate more specifically what the bindings are meant to be used for.
Hardcoded bindings for HC are unnecessarily limitative, and inventing
a different bindings provider API just for HC feels very wrong, so I
have a hard time understanding the reluctance to this proposal.
-Bertrand
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
I assume you are talking of Sling 7 ? If so, I agree ;-) Regards Felix Am 07.08.2013 um 07:52 schrieb Carsten Ziegeler: I definitely agree that we should try to get Sling 6 out asap - and I think we're pretty close to that. Apart maybe from a release of one or two additional bundles, we need to release the discovery stuff (I plan to do this end of this week/early next week) and the new admin login stuff Felix is working on (hopefully this needs just a few weeks from now). Once these releases are through we can release Sling 6. So I think let's look at the snapshot dependencies in launchpad, see if these artifacts have some urgent open issues, fix them (if there are any) and then release the stuff. For the build server problems, I'm totally unhappy with the Jenkins installation (and this since years) - apart from spamming the mailing list, the value right now seems really very low. Though I have no idea how to change this... Regards Carsten 2013/8/7 Robert Munteanu romb...@apache.org Sorry to resurrect such an old thread, but I started this conversation 3 months ago and we aren't close to releasing Sling 7. IMO the build server flakiness contributes to this uncertainty, but so do a few or our tests, being unstable as well. What I'd like to propose now is to make a very minor, specific release of the Sling Launchpad: build it with org.apache.sling.launchpad.base 2.5.0 . This is a low-risk move - I've tested it myself and has the advantage of allowing first-time users to get on board with Java 7. Right now I fear that some of them walk away after an unsuccessful attempt of running Sling. Thoughts? Robert -- Carsten Ziegeler cziege...@apache.org
Re: Adding a usage service property to BindingsValuesProvider ?
On Wed, Aug 7, 2013 at 9:43 AM, Felix Meschberger fmesc...@adobe.com wrote: ...In fact having written my previous messages, I wonder, whether our default values we provide to scripts (request, response, etc.) should not really be provided by a BVP in the request (or such) scope/context/usage ;-) Yes, we could mark our own BVPs with context=request from now on, but the request processing script engines should also get any BVPs which do not have a context service property, for backwards compatibility. ...Somehow I tend to get to the term context for this thing. Ok, that was my first idea and Justin's as well, context sounds good - I'll rephrase my proposal accordingly, coming up... -Bertrand
Re: Adding a usage service property to BindingsValuesProvider ?
Here's my revised proposal based on this thread's discussions: 1. Add a context service property to our existing BindingValuesProvider (BVP) implementations, value=request. The context property can have multiple values. 2. Modify the scripting setup in DefaultSlingScript so that any BVP which has a context service property which doesn't include a request value is ignored. Maybe warn if a BVP with no context property is found, as we'd like people to add this property from now on. 3. Provide a service to collect relevant BVPs when setting up scripting, based on a set of context values. -Bertrand
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
On Wed, Aug 7, 2013 at 9:47 AM, Felix Meschberger fmesc...@adobe.com wrote: I assume you are talking of Sling 7 ? If so, I agree ;-) Me too. -Bertrand
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731747#comment-13731747 ] Bertrand Delacretaz commented on SLING-2999: Looks good to me, this will be useful to access health check MBeans as per SLING-2987 JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Adding a usage service property to BindingsValuesProvider ?
Hi Basically sounds good. Am 07.08.2013 um 09:55 schrieb Bertrand Delacretaz: Here's my revised proposal based on this thread's discussions: 1. Add a context service property to our existing BindingValuesProvider (BVP) implementations, value=request. The context property can have multiple values. This would be a service reference filter of (|(context=request)(!(context=*))) (I think) 2. Modify the scripting setup in DefaultSlingScript so that any BVP which has a context service property which doesn't include a request value is ignored. Maybe warn if a BVP with no context property is found, as we'd like people to add this property from now on. When using the service reference filter (or target on the @Reference annotation) we don't really care. Not sure, whether we should really warn ... In fact I would say, that BVPs without the property should just be used anywhere. The problem is that BVP is a @ConsumerType service interface in the Sling API. We must take extreme care to change it or its semantics. 3. Provide a service to collect relevant BVPs when setting up scripting, based on a set of context values. Since the selection is so easy with a service selection filter or target attribute on a @Reference annotation, such a service would be overkill ;-) Regards Felix -Bertrand
Re: Adding a usage service property to BindingsValuesProvider ?
On Wed, Aug 7, 2013 at 10:09 AM, Felix Meschberger fmesc...@adobe.com wrote: ...In fact I would say, that BVPs without the property should just be used anywhere that might work - I was going to say that [1] for example makes no sense in my health check context, but that provider is being careful to not add anything if the resource binding is not available so we're fine. ...3. Provide a service to collect relevant BVPs when setting up scripting, based on a set of context values. Since the selection is so easy with a service selection filter or target attribute on a @Reference annotation, such a service would be overkill ;-)... Ok, I'm not a fan of the LDAP-like filter syntax but it's workable, and except for the DefaultSlingScript which needs to take care of backwards compatibility the filters should be simple. -Bertrand
Re: Adding a usage service property to BindingsValuesProvider ?
2013/8/7 Felix Meschberger fmesc...@adobe.com A script, at the end of the day, executes some action and might or might not expect some bindings (global variables in some languages). The script would have to cope with them missing or of the wrong type or such... But there is not currently a way that a script could declare I am an HC script or I am a Request Processing script. Exactly, that's my point - and unless we have a mechanism for this, marking a BVP is useless. Not even a taglib can do that -- at the end of the day a TagLib is syntactic sugar for functionality, which must also be usable otherwise. Right - but it fits exactly the needs at least in JSP of what is discussed here. Instead of saying I'm a workflow script , the script uses the workflow taglib. Carsten Regards Felix As said, for JSPs we have taglibs which would solve the problem and doesn't require a BVP, I think for javascript is something equivalent. Of course as a provider of such support you have to provide different implementations (a taglib, a javascript lib etc.) - and maybe we should tackle it from this angle. Carsten 2013/8/6 Justin Edelson jus...@justinedelson.com Hi Carsten, I can't speak for exactly what Bertrand is thinking, but when I was thinking about it, the scope/usage was an orthogonal concern to which engine is selected. Whereas today you do: ScriptEngineManager.getEngineByExtension(ecma) You could do ScriptEngineManager.getEngineByExtension(ecma, [healthcheck, workflow]) (of course, we can't actually do that as ScriptEngineManager is a JDK class; we'd have to create an extension) Alternatively, this could be done after SlingScript object is created: SlingScript script = resource.adaptTo(SlingScript.class); script.setUsage([healthcheck]); When creating the SlingBindings for the script to execute, the following BindingsValuesProviders would be consulted (in order): * the generic BVPs (which apply to all scripting languages) * the BVPs tagged with the value of the script engine factory's compatible.javax.script.name property * the BVPs tagged with the script engine factory's name * the BVPs tagged with the scope/usage property Or something like that... The significant advantage of doing this vs. hardcoding the usage-specific bindings at the point of script engine access is that it doesn't allow for downstream customization. Which is important IMHO in the case of healthcheck - we want to enable custom hc rules which may benefit from a custom BVP. This is also true in a workflow engine. Justin On Tue, Aug 6, 2013 at 1:41 PM, Carsten Ziegeler cziege...@apache.org wrote: Ok, just to make it clear, as long as there is no support in all script engines, I'm -1 Carsten 2013/8/6 Justin Edelson jus...@justinedelson.com Hi Bertrand, FWIW, I was thinking about something very similar (although I was thinking of calling it 'scope', not 'usage'), but never got around to implementing it. +1 for me. Justin On Tue, Aug 6, 2013 at 10:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, I'd like to use BindingsValuesProvider services in my health check module, to provide bindings like jmx for scripted health checks, which should be ignored for general Sling scripting (or not - some providers might apply to both general scripting and health checks). I'm thinking of adding an optional usage service property to BindingsValuesProvider services, does anyone see a problem with that? The Sling script engine would then consider only BindingsValuesProvider which have no usage property (for backwards compatibility) or which have usage=scripting. And my health checks would consider only BindingsValuesProvider which have usage=healthcheck. -Bertrand -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
Re: Adding a usage service property to BindingsValuesProvider ?
Again, I'm still missing a suggestion on how to mark a script to run in a given context. Carsten 2013/8/7 Bertrand Delacretaz bdelacre...@apache.org On Wed, Aug 7, 2013 at 10:09 AM, Felix Meschberger fmesc...@adobe.com wrote: ...In fact I would say, that BVPs without the property should just be used anywhere that might work - I was going to say that [1] for example makes no sense in my health check context, but that provider is being careful to not add anything if the resource binding is not available so we're fine. ...3. Provide a service to collect relevant BVPs when setting up scripting, based on a set of context values. Since the selection is so easy with a service selection filter or target attribute on a @Reference annotation, such a service would be overkill ;-)... Ok, I'm not a fan of the LDAP-like filter syntax but it's workable, and except for the DefaultSlingScript which needs to take care of backwards compatibility the filters should be simple. -Bertrand -- Carsten Ziegeler cziege...@apache.org
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
On Wed, Aug 7, 2013 at 8:52 AM, Carsten Ziegeler cziege...@apache.org wrote: I definitely agree that we should try to get Sling 6 out asap - and I think we're pretty close to that. Apart maybe from a release of one or two additional bundles, we need to release the discovery stuff (I plan to do this end of this week/early next week) and the new admin login stuff Felix is working on (hopefully this needs just a few weeks from now). Once these releases are through we can release Sling 6. So I think let's look at the snapshot dependencies in launchpad, see if these artifacts have some urgent open issues, fix them (if there are any) and then release the stuff. Sounds good to me. I though we were still far from releasing, so Sling 7 makes me happier than Sling 6.1 . For the build server problems, I'm totally unhappy with the Jenkins installation (and this since years) - apart from spamming the mailing list, the value right now seems really very low. Though I have no idea how to change this... Perhaps we can use Travis for that. I know that Oak does that [1] and I've set up a proof-of-concept some time ago at [2] but didn't update it in quite some time. The advantage of Travis is that it always starts with a fresh VM for each build, so there's no problematic master-slave communication, which is the #1 problem with our current Jenkins setup. On the other hand, it doesn't do all the graphs that Jenkins does and does not publish binary artifacts. To set up a Travis build we need a .travis.yml file in the root of the repository, see [3] for what I used. I can take care of setting up the .travis.yml file to make sure that Sling builds on Travis. Then we need to find out how to authorize Travis to build apache/sling ; OAK did it so it's possible. Robert [1]: https://travis-ci.org/apache/jackrabbit-oak [2]: https://travis-ci.org/rombert/sling/ [3]: https://github.com/rombert/sling/blob/0fdfca2b3e1e5c473d5fa028aee71c6f1944a09e/.travis.yml Regards Carsten 2013/8/7 Robert Munteanu romb...@apache.org Sorry to resurrect such an old thread, but I started this conversation 3 months ago and we aren't close to releasing Sling 7. IMO the build server flakiness contributes to this uncertainty, but so do a few or our tests, being unstable as well. What I'd like to propose now is to make a very minor, specific release of the Sling Launchpad: build it with org.apache.sling.launchpad.base 2.5.0 . This is a low-risk move - I've tested it myself and has the advantage of allowing first-time users to get on board with Java 7. Right now I fear that some of them walk away after an unsuccessful attempt of running Sling. Thoughts? Robert -- Carsten Ziegeler cziege...@apache.org -- Sent from my (old) computer
[jira] [Commented] (SLING-2999) JMX Resource Provider
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731771#comment-13731771
]
Carsten Ziegeler commented on SLING-2999:
-
Yes, the namespace is there do avoid collision with potentially existing
properties. The properties are already contained in the object name, so we
could go without them, thus avoiding the use of a namespace. I don't have a
concrete use case for needing the object name properties as properties of the
mbean resource, but if we need them later on, we would need some separation.
The only alternative I see is to prefix the property names which is kind of a
namespace but not in the jcr sense, like property-{name}
JMX Resource Provider
-
Key: SLING-2999
URL: https://issues.apache.org/jira/browse/SLING-2999
Project: Sling
Issue Type: New Feature
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
For easier rendering of JMX mbeans within Sling, a special resource provider
should make the JMX information available at
*/system/sling/monitoring/mbeans* (Configurable)
/system/sling/monitoring/mbeans - resource type = sling:mbeans
+ resource sub tree with all mbeans
An MBean has an object name which has
* a domain
* properties where type and name are very common
The domain is converted into a sub path and the properties are converted to a
resource name. For example: _org.apache.sling:name=test,type=hello_ creates a
resource _org/apache/sling/name=test,type=hello_. The name can be obtained by
calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might
need escaping (for the values and the = character) in order to create valid
resource names.
Each MBean resource has at least:
||Property name ||Description|
|sling:resourceType|object name of the MBean|
|sling:resourceSuperType| sling:mbean|
|mbean:description|The description of the MBean (optional)|
|mbean:className|MBean class name|
|mbean:objectName|MBean object name|
|mbean properties|separate property for each property of the object name|
And a child resource named _mbean:attributes_ if the MBean has attributes.
For each attribute a child resource of _mbean:attributes_ is created where
the name of the resource is the name of the attribute and:
||Property name ||Description|
|sling:resourceType|Type of the attribute|
|sling:resourceSuperType| sling:mbeanattribute|
|mbean:description|The description of the attribute (optional)|
|mbean:value|String representation of the value or a string array for multi
values|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2997) ResourceAccessSecurityImpl uses @Override for interface methods, but does not declare compiler version as Java 6
[ https://issues.apache.org/jira/browse/SLING-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731801#comment-13731801 ] Felix Meschberger commented on SLING-2997: -- I agree. Java 5 is dead and new code should IMHO be free to required Java 6 -- if only for the @Override annotation which IMHO is a big plus in code stability by supporting the compiler with its static code analysis. ResourceAccessSecurityImpl uses @Override for interface methods, but does not declare compiler version as Java 6 Key: SLING-2997 URL: https://issues.apache.org/jira/browse/SLING-2997 Project: Sling Issue Type: Bug Components: ResourceResolver Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Resource Access Gate 1.0.0 The class org.apache.sling.resourceaccesssecurity.impl.ResourceAccessSecurityImpl uses @Override to indicate interface implementation. This, however, is only valid on Java 6 and above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Adding a usage service property to BindingsValuesProvider ?
On Wed, Aug 7, 2013 at 10:26 AM, Carsten Ziegeler cziege...@apache.org wrote: Again, I'm still missing a suggestion on how to mark a script to run in a given context... You don't. There are request processing scripts, the ones we have and always had - there's no change for those, except that with this change they won't get any BVPs which are marked for a context that is not request. Existing BVPs are not marked like that so no change. There's no way and no need to mark those scripts for a different context, they are request processing scripts. Then there are new health check (mini-)scripts which are different animals: they are provided in OSGi configs as shown earlier in this thread. Their context is hardcoded to healthcheck, there's no need to change that. Another way to look at this, and maybe I should have phrased my proposal like that, is that the goal is to setup different script engines: currently we're just using a request processing script engine, I need a healtcheck script engine with different bindings, and it makes sense to generalize the idea. -Bertrand
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote: ...I can take care of setting up the .travis.yml file to make sure that Sling builds on Travis. Then we need to find out how to authorize Travis to build apache/sling ; OAK did it so it's possible Sounds good to me! -Bertrand
Re: Adding a usage service property to BindingsValuesProvider ?
Hmm, this doesn't really convince me. So this means there is no way to set the context apart from creating/retrieving a script engine by hand (java code)? So scripts run with the usual Sling script resolution will always just use BVPs not marked for any context and BVPs marked for the context request. I still fail to see the usefulness - but as you all seem to go crazy about it, I wont block this Carsten 2013/8/7 Bertrand Delacretaz bdelacre...@apache.org On Wed, Aug 7, 2013 at 10:26 AM, Carsten Ziegeler cziege...@apache.org wrote: Again, I'm still missing a suggestion on how to mark a script to run in a given context... You don't. There are request processing scripts, the ones we have and always had - there's no change for those, except that with this change they won't get any BVPs which are marked for a context that is not request. Existing BVPs are not marked like that so no change. There's no way and no need to mark those scripts for a different context, they are request processing scripts. Then there are new health check (mini-)scripts which are different animals: they are provided in OSGi configs as shown earlier in this thread. Their context is hardcoded to healthcheck, there's no need to change that. Another way to look at this, and maybe I should have phrased my proposal like that, is that the goal is to setup different script engines: currently we're just using a request processing script engine, I need a healtcheck script engine with different bindings, and it makes sense to generalize the idea. -Bertrand -- Carsten Ziegeler cziege...@apache.org
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
Yepp, let's give it a try - we don't need to publish the artifacts, just getting a success/fail mail is enough Carsten 2013/8/7 Bertrand Delacretaz bdelacre...@apache.org On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote: ...I can take care of setting up the .travis.yml file to make sure that Sling builds on Travis. Then we need to find out how to authorize Travis to build apache/sling ; OAK did it so it's possible Sounds good to me! -Bertrand -- Carsten Ziegeler cziege...@apache.org
Re: Adding a usage service property to BindingsValuesProvider ?
On Wed, Aug 7, 2013 at 11:47 AM, Carsten Ziegeler cziege...@apache.org wrote: ...scripts run with the usual Sling script resolution will always just use BVPs not marked for any context and BVPs marked for the context request... That's exactly the idea - no change for existing request processing scripts, and the ability to use scripts in different contexts, without polluting the request scripting context with useless or potentially dangerous bound objects. I still fail to see the usefulness - but as you all seem to go crazy about it, I wont block this.. thanks! -Bertrand
[jira] [Commented] (SLING-920) Jenkins continuous integration setup
[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731864#comment-13731864 ] Robert Munteanu commented on SLING-920: --- Added .travis.yml file in http://svn.apache.org/viewvc?view=revisionrevision=1511240 and also filed INFRA-6643 to activate the Travis hook on Github. Jenkins continuous integration setup Key: SLING-920 URL: https://issues.apache.org/jira/browse/SLING-920 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Use this issue to record changes to the Hudson continuous environment setup at http://hudson.zones.apache.org/hudson/view/Sling/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )
On Wed, Aug 7, 2013 at 12:49 PM, Carsten Ziegeler cziege...@apache.org wrote: Yepp, let's give it a try - we don't need to publish the artifacts, just getting a success/fail mail is enough Added .travis.yml file in http://svn.apache.org/viewvc?view=revisionrevision=1511240 and also filed INFRA-6643 to activate the Travis hook on Github. After the INFRA issue is resolved I'll look into tweaking the build. Robert Carsten 2013/8/7 Bertrand Delacretaz bdelacre...@apache.org On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote: ...I can take care of setting up the .travis.yml file to make sure that Sling builds on Travis. Then we need to find out how to authorize Travis to build apache/sling ; OAK did it so it's possible Sounds good to me! -Bertrand -- Carsten Ziegeler cziege...@apache.org -- Sent from my (old) computer
[jira] [Resolved] (SLING-2972) Improve processing performance if job is processed locally
[ https://issues.apache.org/jira/browse/SLING-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2972. - Resolution: Fixed Direct processing of local events has been added in rev 1504035 Improve processing performance if job is processed locally -- Key: SLING-2972 URL: https://issues.apache.org/jira/browse/SLING-2972 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.2.0 Currently the job processing is completely observation based: even if a job is added locally and also processed locally, this is not immediately put into the queue. This creates an unnecessary delay between adding a job and processing it which can easily be avoided by directly putting the job into the queue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2971) BackgroundLoader thread dies for invalid paths
[ https://issues.apache.org/jira/browse/SLING-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2971. - Resolution: Fixed I think we can close this now - as the underlying problem is due to Oak BackgroundLoader thread dies for invalid paths -- Key: SLING-2971 URL: https://issues.apache.org/jira/browse/SLING-2971 Project: Sling Issue Type: Bug Components: Extensions Reporter: Chetan Mehrotra Assignee: Carsten Ziegeler Priority: Minor Fix For: Extensions Event 3.2.0 Attachments: SLING-2971.patch BackgroundLoader thread which is used by JobManager to load and process job asynchronously dies if any submitted job path is found to be invalid. --- 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in Thread Thread[Apache Sling Job Background Loader,5,main] java.lang.NullPointerException at org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219) at java.lang.Thread.run(Thread.java:662) --- It might not happen in actual scenario always but it would be better if the while loop does not end for such cases -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2950) Disabling the distribution flag takes only effect after bundle restart
[ https://issues.apache.org/jira/browse/SLING-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2950. - Resolution: Fixed This has been changed in rev 1501098 Disabling the distribution flag takes only effect after bundle restart -- Key: SLING-2950 URL: https://issues.apache.org/jira/browse/SLING-2950 Project: Sling Issue Type: Bug Components: Extensions Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.2.0 If the disable distribution flag is changed, it only has an effect after a restart of the bundle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2724) Error handling doesn't respect servlet spec
[ https://issues.apache.org/jira/browse/SLING-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2724. - Resolution: Fixed Error handling doesn't respect servlet spec --- Key: SLING-2724 URL: https://issues.apache.org/jira/browse/SLING-2724 Project: Sling Issue Type: Bug Components: Engine, Servlets Reporter: Antonio Sanso Assignee: Carsten Ziegeler Fix For: Servlets Resolver 2.2.6, Engine 2.2.10 If there is some servlet that is sending a 500 error (response.sendError(500)) and output something after e.g. All good (maybe this is the wrong part...) and a 500.jsp exists, Sling will shows both: - the error page 500.jsp - and the the extra output (e.g. All good) This seems to violate the spec: These methods [sendError, sendRedirect] will have the side effect of committing the response, if it has not already been committed, and terminating it. No further output to the client should be made by the servlet after these methods are called. If data is written to the response after these methods are called, the data is ignored. Integration test showing the issue in [0] Mailing list thread in [1] [0] https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolver/errorhandler/ErrorHandlingTest.java [1] sling.markmail.org/thread/k2t7p5mhi4hgelwb -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [GSoC2013] Unsatisfied dependencies.
On Tue, Aug 6, 2013 at 3:18 PM, Ian Boston i...@tfd.co.uk wrote: Hi, On 6 August 2013 10:24, Robert Munteanu rob...@lmn.ro wrote: On Tue, Aug 6, 2013 at 12:10 PM, Dishara Wijewardana ddwijeward...@gmail.com wrote: com.google.common.base -- Cannot be resolved com.google.common.collect -- Cannot be resolved These are coming from Guava and Guava is a proper OSGi bundle. @Robert, thank you for the pointer. @Dishara Will be better to just add Guava as a bundle rathe than embed it since it uses threads to reap weak references and do clean up. I manually Added Guva OSGI bundle. It worked as mentioned. Is that what you meant? And I am going through each missing ones and adding those to pom and checking. Still few more to go. Will update on that. Meantime I would want to know whether sling already has a Apache Thrift bundle in sling runtime ? If so how can I find the version of it. Because If I add package a different version I think it will again be confused at runtime because of the two versions of the same bundle. Also Embed-Transitive*true*/Embed-Transitive Never been able to get Embed-Transitive to work. I have always listed each artifact Id separately. Best Regards Ian Robert -- Sent from my (old) computer -- Thanks /Dishara
Re: [RT] Logging and Logback
Hi Carsten I started hacking around to this avail -- but I am nowhere near completion ... I committed my current (incomplete) work to https://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/logback Regards Felix Am 06.08.2013 um 13:30 schrieb Carsten Ziegeler: Hi, i've the need for a custom log append not logging into a file. This is something our current logging bundles do not support. By looking around using logback could be an answer and I also found [1] where moving to logback has already been discussed. So I'm wondering what/how to this. One solution would be to do this on our own as discussed in that thread, another solution would be to leverage other logging solutions like maybe pax logging and just providing a compatibility layer for our current configurations. WDYT? Regards Carsten [1] http://apache-sling.73963.n3.nabble.com/Trying-to-convert-Sling-Logging-gt-Logback-How-much-backwards-compatibility-do-we-need-td4020965.html -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2944) Replace administrative login by service-based login
[ https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731910#comment-13731910 ] Felix Meschberger commented on SLING-2944: -- Hmm, excellent point. The goal of the header is to allow for multiple bundles to cooperate on the same service -- the MTA for example where the sub services may be spread accross bundles. WDYT ? Replace administrative login by service-based login --- Key: SLING-2944 URL: https://issues.apache.org/jira/browse/SLING-2944 Project: Sling Issue Type: New Feature Components: API, JCR, ResourceResolver, Service User Mapper Affects Versions: JCR Resource 2.2.8, JCR Jackrabbit Server 2.1.0, JCR Base 2.1.2, JCR API 2.1.0, API 2.4.2, Resource Resolver 1.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Service User Mapper 1.0.0, Servlets Resolver 2.2.6, JCR Resource 2.3.0, JCR Jackrabbit Server 2.2.0, JCR Base 2.1.4, JCR API 2.2.0, File System Resource Provider 1.1.4, Extensions Bundleresource 2.1.4, API 2.5.0, Resource Resolver 1.1.0 Attachments: serviceusermapper.tgz, SLING-2944.patch From the start Sling tried to solve the problem of providing services access to the repository and resource tree without having to hard code and configure any passwords. This was done first with the SlingRepository.loginAdministrative and later with the ResourceResolverFactory.getAdministrativeResourceResolver methods. Over time this mechanism proved to be the hammer to hit all nails. Particularly these methods while truly useful have the disadvantage of providing full administrative privileges to services where just some specific kind of privilege would be enough. For example for the JSP compiler it would be enough to be able to read the JSP source scripts and write the Java classes out to the JSP compiler's target location. Other access is not required. Similarly to manage users user management privileges are enough and no access to /content is really required. To solve this problem a new API for Service Authentication has been proposed at https://cwiki.apache.org/confluence/display/SLING/Service+Authentication. The prototype of which is implemented in http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/deprecate_login_administrative. This issue is about merging the prototype code back into trunk and thus fully implementing the feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2944) Replace administrative login by service-based login
[ https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731925#comment-13731925 ] Carsten Ziegeler commented on SLING-2944: - Right - I think the point is to be able to configure this without a specific packaging (bundling) of services - so we rather want to configure this based on a service than on a bundle - as the service might move from one bundle to another. Unfortunately we only get support for the client bundle through a ServiceFactory. On the other hand we can't rely alone on a service identifier (comparable to the PID) as this would be open to the same attack as the additional header. So the only thing which is quiet safe to use is the bundle symbolic name as we have it right now. I think it's better to be a little bit safer with the burden of potentially more configuration if sub services spread across bundles. So I would remove the header Replace administrative login by service-based login --- Key: SLING-2944 URL: https://issues.apache.org/jira/browse/SLING-2944 Project: Sling Issue Type: New Feature Components: API, JCR, ResourceResolver, Service User Mapper Affects Versions: JCR Resource 2.2.8, JCR Jackrabbit Server 2.1.0, JCR Base 2.1.2, JCR API 2.1.0, API 2.4.2, Resource Resolver 1.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Service User Mapper 1.0.0, Servlets Resolver 2.2.6, JCR Resource 2.3.0, JCR Jackrabbit Server 2.2.0, JCR Base 2.1.4, JCR API 2.2.0, File System Resource Provider 1.1.4, Extensions Bundleresource 2.1.4, API 2.5.0, Resource Resolver 1.1.0 Attachments: serviceusermapper.tgz, SLING-2944.patch From the start Sling tried to solve the problem of providing services access to the repository and resource tree without having to hard code and configure any passwords. This was done first with the SlingRepository.loginAdministrative and later with the ResourceResolverFactory.getAdministrativeResourceResolver methods. Over time this mechanism proved to be the hammer to hit all nails. Particularly these methods while truly useful have the disadvantage of providing full administrative privileges to services where just some specific kind of privilege would be enough. For example for the JSP compiler it would be enough to be able to read the JSP source scripts and write the Java classes out to the JSP compiler's target location. Other access is not required. Similarly to manage users user management privileges are enough and no access to /content is really required. To solve this problem a new API for Service Authentication has been proposed at https://cwiki.apache.org/confluence/display/SLING/Service+Authentication. The prototype of which is implemented in http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/deprecate_login_administrative. This issue is about merging the prototype code back into trunk and thus fully implementing the feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2944) Replace administrative login by service-based login
[ https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731932#comment-13731932 ] Felix Meschberger commented on SLING-2944: -- Right using a service does not work: Not only is a service property unsafe, its also worthless: Its not allways a service desiring repository or resource tree access. It could also be a simple immediate component which happily sits in the background doing some cleanup (for example). But I am ok with removing the header stuff for now. Replace administrative login by service-based login --- Key: SLING-2944 URL: https://issues.apache.org/jira/browse/SLING-2944 Project: Sling Issue Type: New Feature Components: API, JCR, ResourceResolver, Service User Mapper Affects Versions: JCR Resource 2.2.8, JCR Jackrabbit Server 2.1.0, JCR Base 2.1.2, JCR API 2.1.0, API 2.4.2, Resource Resolver 1.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Service User Mapper 1.0.0, Servlets Resolver 2.2.6, JCR Resource 2.3.0, JCR Jackrabbit Server 2.2.0, JCR Base 2.1.4, JCR API 2.2.0, File System Resource Provider 1.1.4, Extensions Bundleresource 2.1.4, API 2.5.0, Resource Resolver 1.1.0 Attachments: serviceusermapper.tgz, SLING-2944.patch From the start Sling tried to solve the problem of providing services access to the repository and resource tree without having to hard code and configure any passwords. This was done first with the SlingRepository.loginAdministrative and later with the ResourceResolverFactory.getAdministrativeResourceResolver methods. Over time this mechanism proved to be the hammer to hit all nails. Particularly these methods while truly useful have the disadvantage of providing full administrative privileges to services where just some specific kind of privilege would be enough. For example for the JSP compiler it would be enough to be able to read the JSP source scripts and write the Java classes out to the JSP compiler's target location. Other access is not required. Similarly to manage users user management privileges are enough and no access to /content is really required. To solve this problem a new API for Service Authentication has been proposed at https://cwiki.apache.org/confluence/display/SLING/Service+Authentication. The prototype of which is implemented in http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/deprecate_login_administrative. This issue is about merging the prototype code back into trunk and thus fully implementing the feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Build failed in Jenkins: sling-trunk-1.7 #166
See https://builds.apache.org/job/sling-trunk-1.7/166/changes Changes: [cziegeler] Correct license header [rombert] SLING-920 - Jenkins continuous integration setup Added .travis.yml file for travis-ci integration. -- [...truncated 24472 lines...] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Adapter Annotations . SUCCESS [4.795s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin to create Jackrabbit OCM descriptors SUCCESS [5.367s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Compiling JSP Sources into Bundles SUCCESS [4.079s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Supporting Bundle Development SUCCESS [4.488s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [15.054s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [3.970s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.405s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [3.598s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [10.776s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [2.389s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [2.645s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.612s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [10.710s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [4.296s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [9.147s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.964s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [2.208s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [2.072s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.265s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [5.549s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [4.451s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [8.244s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [3.398s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [7.304s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [4.453s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [3.842s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [14.322s] Aug 07, 2013 1:18:51 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [3.863s] Aug
Re: [GSoC2013] Unsatisfied dependencies.
On 7 August 2013 12:49, Dishara Wijewardana ddwijeward...@gmail.com wrote: @Dishara Will be better to just add Guava as a bundle rathe than embed it since it uses threads to reap weak references and do clean up. I manually Added Guva OSGI bundle. It worked as mentioned. Is that what you meant? And I am going through each missing ones and adding those to pom and checking. Still few more to go. Will update on that. Meantime I would want to know whether sling already has a Apache Thrift bundle in sling runtime ? If so how can I find the version of it. Because If I add package a different version I think it will again be confused at runtime because of the two versions of the same bundle. One of the strengths of OSGi is you can add many versions of the same jar/bundle containing different versions of the same package. Thats why import and export have version numbers on the packages. AFAIK, there isnt a Thrift bundle. Ian
Build failed in Jenkins: sling-trunk-1.6 #1794
See https://builds.apache.org/job/sling-trunk-1.6/1794/changes Changes: [cziegeler] Add missing licence header [cziegeler] Correct license header [rombert] SLING-920 - Jenkins continuous integration setup Added .travis.yml file for travis-ci integration. -- [...truncated 23571 lines...] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [16.366s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [4.923s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.574s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [6.335s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [11.368s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [2.701s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [2.045s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.732s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [10.247s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [4.784s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [8.075s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.728s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [2.158s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [2.275s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.318s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [14.885s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [3.810s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [8.460s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [2.512s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [9.140s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [5.702s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [5.753s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [54.486s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [2.709s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Authentication Service ... SUCCESS [4.451s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OpenID Authentication SUCCESS [8.380s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Form Based Authentication Handler SUCCESS [6.425s] Aug 7, 2013 1:34:30 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Authentication Selector .. SUCCESS [3.346s] Aug 7, 2013 1:34:30 PM
Build failed in Jenkins: sling-trunk-1.7 #167
See https://builds.apache.org/job/sling-trunk-1.7/167/changes Changes: [cziegeler] Add missing licence header -- [...truncated 24508 lines...] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Adapter Annotations . SUCCESS [3.608s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin to create Jackrabbit OCM descriptors SUCCESS [4.049s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Compiling JSP Sources into Bundles SUCCESS [3.362s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Supporting Bundle Development SUCCESS [3.320s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [12.176s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [3.523s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.268s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [2.096s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [9.454s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [3.237s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [3.039s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.395s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [10.360s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [4.434s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [6.662s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.443s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [2.398s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [2.114s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.144s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [4.249s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [3.433s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [7.066s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [2.286s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [6.850s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [4.461s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [3.447s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [12.464s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [2.524s] Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling
Build failed in Jenkins: sling-trunk-1.6 #1795
See https://builds.apache.org/job/sling-trunk-1.6/1795/changes Changes: [stefanegli] SLING-2985 : tooling : show content of .content.xml in project explorer - WIP/Work in progress : adding prototype of content[-package][.content.xml] browsing. 'mounts' the syncDir as a new toplevel node to a sling-faceted project and allows browsing through folders/.content.xml-content. [stefanegli] SLING-2985 : tooling : show content of .content.xml in project explorer - add SLING_ICON to SharedImages -- [...truncated 30863 lines...] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [15.552s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [4.307s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.027s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [1.985s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [8.952s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [1.963s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [2.014s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.133s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [9.161s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [4.086s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [7.081s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.306s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [1.997s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [2.002s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.116s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [10.711s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [3.777s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [7.218s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [2.898s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [7.167s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [3.533s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [3.210s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [12.871s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [2.333s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Authentication Service ... SUCCESS [3.530s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OpenID Authentication SUCCESS [5.742s] Aug 7, 2013 5:33:07 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Form Based
Build failed in Jenkins: sling-trunk-1.7 #168
See https://builds.apache.org/job/sling-trunk-1.7/168/changes Changes: [stefanegli] SLING-2985 : tooling : show content of .content.xml in project explorer - WIP/Work in progress : adding prototype of content[-package][.content.xml] browsing. 'mounts' the syncDir as a new toplevel node to a sling-faceted project and allows browsing through folders/.content.xml-content. [stefanegli] SLING-2985 : tooling : show content of .content.xml in project explorer - add SLING_ICON to SharedImages -- [...truncated 24487 lines...] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Adapter Annotations . SUCCESS [4.584s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin to create Jackrabbit OCM descriptors SUCCESS [5.448s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Compiling JSP Sources into Bundles SUCCESS [5.151s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Supporting Bundle Development SUCCESS [5.183s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [14.621s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [3.925s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.557s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [2.237s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [9.453s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [2.221s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [2.537s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.349s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [10.191s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [5.167s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [7.334s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.357s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [3.279s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [2.845s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.591s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [7.410s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [4.064s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [8.981s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [3.818s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [9.822s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [7.719s] Aug 07, 2013 6:23:16 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [3.813s] Aug 07, 2013 6:23:16 PM
Sling SVN Dist Access
All, I am attempting to complete the release for Sling JSP TagLib 2.2.0, however it seems I don't have commit access to the repository for the Sling project's folder on dist.apache.org ( https://dist.apache.org/repos/dist/release/sling/). When I checked with the infrastructure team, they said that by default only PMC members have access to the releases directory. Can I be granted access to that directory? Or should I request the release be completed by a PMC member. Thanks, Dan
Build failed in Jenkins: sling-trunk-1.7 #169
See https://builds.apache.org/job/sling-trunk-1.7/169/changes Changes: [fmeschbe] SLING-2944 Prevent NPE if there is no authenticationInfo is null. -- [...truncated 23478 lines...] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Adapter Annotations . SUCCESS [4.738s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin to create Jackrabbit OCM descriptors SUCCESS [5.781s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Compiling JSP Sources into Bundles SUCCESS [6.394s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Maven Plugin for Supporting Bundle Development SUCCESS [4.985s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [17.287s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [4.352s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [2.528s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [3.574s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [15.799s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [2.805s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [2.901s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [2.931s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [11.174s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [7.372s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [10.160s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [2.334s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [2.865s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [3.481s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [2.777s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [10.200s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [5.923s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [9.810s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [3.511s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [12.257s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [7.256s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [5.310s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [38.119s] Aug 07, 2013 10:45:23 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [3.643s] Aug 07, 2013 10:45:23 PM
Build failed in Jenkins: sling-trunk-1.6 #1796
See https://builds.apache.org/job/sling-trunk-1.6/1796/changes Changes: [fmeschbe] SLING-2944 Prevent NPE if there is no authenticationInfo is null. -- [...truncated 26729 lines...] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Launchpad Maven Plugin ... SUCCESS [10.406s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Standalone Archetype .. SUCCESS [3.096s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Launchpad Webapp Archetype .. SUCCESS [1.460s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Initial Content Archetype ... SUCCESS [1.961s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Servlet Archetype ... SUCCESS [9.179s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Bundle Archetype SUCCESS [1.349s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling JCRInstall Bundle Archetype . SUCCESS [1.255s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Sling Taglib Archetype SUCCESS [1.408s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling API .. SUCCESS [7.369s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Service User Mapper .. SUCCESS [3.183s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource Resolver SUCCESS [5.003s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Java Transaction API SUCCESS [1.504s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: XML APIs SUCCESS [1.256s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: Activation API SUCCESS [1.228s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling System Bundle Extension: WS APIs . SUCCESS [1.269s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Dynamic Class Loader Support . SUCCESS [34.096s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSON Library . SUCCESS [2.504s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling SLF4J Implementation . SUCCESS [5.052s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OSGi LogService Implementation ... SUCCESS [1.468s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling MIME type mapping support SUCCESS [5.360s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Commons OSGi support . SUCCESS [2.484s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scheduler Support SUCCESS [2.201s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Testing Utilities SUCCESS [10.405s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Support ... SUCCESS [1.471s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Authentication Service ... SUCCESS [2.339s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling OpenID Authentication SUCCESS [4.549s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Form Based Authentication Handler SUCCESS [3.538s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Authentication Selector .. SUCCESS [1.636s] Aug 7, 2013 11:07:22 PM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache
Re: [GSoC2013] Unsatisfied dependencies.
On Wed, Aug 7, 2013 at 6:48 PM, Ian Boston i...@tfd.co.uk wrote: On 7 August 2013 12:49, Dishara Wijewardana ddwijeward...@gmail.com wrote: @Dishara Will be better to just add Guava as a bundle rathe than embed it since it uses threads to reap weak references and do clean up. I manually Added Guva OSGI bundle. It worked as mentioned. Is that what you meant? And I am going through each missing ones and adding those to pom and checking. Still few more to go. Will update on that. Meantime I would want to know whether sling already has a Apache Thrift bundle in sling runtime ? If so how can I find the version of it. Because If I add package a different version I think it will again be confused at runtime because of the two versions of the same bundle. One of the strengths of OSGi is you can add many versions of the same jar/bundle containing different versions of the same package. Thats why import and export have version numbers on the packages. AFAIK, there isnt a Thrift bundle. Hi Ian, I got all of them solved except one. Now only following is there and seems this is something else. I tried couple of dependencies and still same result. Any idea why ? com.sun.java_cup.internal -- Cannot be resolved and overwritten by Boot Delegation Here is what I additionally added to include the missing classes. Embed-Dependencyhector-core,jaxp-ri,FastInfoset,cassandra-thrift,commons-pool,libthrift,httpclient,httpcore/Embed-Dependency And those dependencies are dependency groupIdcom.sun.org.apache/groupId artifactIdjaxp-ri/artifactId version1.4/version /dependency dependency groupIdcom.sun.xml.fastinfoset/groupId artifactIdFastInfoset/artifactId version1.2.8/version /dependency dependency groupIdorg.apache.cassandra/groupId artifactIdcassandra-thrift/artifactId version1.1.0/version /dependency dependency groupIdcommons-pool/groupId artifactIdcommons-pool/artifactId version1.5.5/version /dependency dependency groupIdorg.apache.thrift/groupId artifactIdlibthrift/artifactId version0.9.0/version /dependency dependency groupIdorg.apache.httpcomponents/groupId artifactIdhttpclient/artifactId version4.2/version /dependency dependency groupIdorg.apache.httpcomponents/groupId artifactIdhttpcore/artifactId version4.2/version /dependency Ian -- Thanks /Dishara
Re: [Status Update] Apache Cassandra backend for Sling
On Mon, Aug 5, 2013 at 5:50 AM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Tue, Jul 23, 2013 at 5:32 PM, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Mon, Jul 22, 2013 at 1:56 PM, Ian Boston i...@tfd.co.uk wrote: Hi Dishara, The Unit test coverage sounds great. I will pull the code and review today. Have you tried loading the bundle into a running Sling instance ? Not yet. I will try that out and let you know in one of following ways Thanks. Once you have built it you can load in 2 ways: method A mvn clean install sling:install The sling:install will post the Jar into the OSGi container over HTTP and cause it to start. Hi Ian I started Sling launchpad and Cassandra Server as well. And uploaded the bundle through management console from http://localhost:8080/system/console. When I try to start the bundle it does nothing and no error logs in the back end as well. The I noticed following where me.prettyprint.* classes cannot loaded and hence my bundle cannot start. So ideally my bundle only contains it self only. Not included its dependencies. As I feel one option is get a me.prettyprint.* jar and install that bundle (I am not sure whether it also fails due to a similar reason). So what is the best approach to this ? Symbolic Name org.apache.sling.cassandra Version 0.0.1.SNAPSHOT Bundle Location inputstream:org.apache.sling.cassandra-0.0.1-SNAPSHOT.jar Last Modification Mon Aug 05 05:26:16 IST 2013 Description Provides a ResourceProvider implementation supporting Apache Cassandra based resources. Start Level 20 Exported Packages org.apache.sling.cassandra.resource.provider,version=0.0.1.SNAPSHOT org.apache.sling.cassandra.resource.provider.mapper,version=0.0.1.SNAPSHOT org.apache.sling.cassandra.resource.provider.util,version=0.0.1.SNAPSHOT Imported Packages com.sun.org.apache.xerces.internal.impl.dv.util -- Cannot be resolved and overwritten by Boot Delegation javax.servlet.http from org.apache.felix.http.jetty (1) me.prettyprint.cassandra.model,version=[1.0,2) -- Cannot be resolved me.prettyprint.cassandra.serializers,version=[1.0,2) -- Cannot be resolved me.prettyprint.hector.api,version=[1.0,2) -- Cannot be resolved me.prettyprint.hector.api.beans,version=[1.0,2) -- Cannot be resolved me.prettyprint.hector.api.ddl,version=[1.0,2) -- Cannot be resolved me.prettyprint.hector.api.factory,version=[1.0,2) -- Cannot be resolved me.prettyprint.hector.api.query,version=[1.0,2) -- Cannot be resolved org.apache.sling.api.resource,version=[2.3,3) from org.apache.sling.api (98) org.slf4j,version=[1.5,2) from slf4j.api (6) Manifest Headers Bnd-LastModified: 1375238009819 Build-Jdk: 1.6.0_26 Built-By: dishara Bundle-Description: Provides a ResourceProvider implementation supporting Apache Cassandra based resources. Bundle-ManifestVersion: 2 Bundle-Name: Apache Sling Cassandra Resource Provider Bundle-SymbolicName: org.apache.sling.cassandra Bundle-Version: 0.0.1.SNAPSHOT Created-By: Apache Maven Bundle Plugin Export-Package: org.apache.sling.cassandra.resource.provider.mapper; version=0.0.1.SNAPSHOT, org.apache.sling.cassandra.resource.provider; uses:=javax.servlet.http, me.prettyprint.hector.api, org.apache.sling.api.resource, org.apache.sling.cassandra.resource.provider.mapper; version=0.0.1.SNAPSHOT, org.apache.sling.cassandra.resource.provider.util; uses:=me.prettyprint.cassandra.model, me.prettyprint.cassandra.serializers, me.prettyprint.hector.api, me.prettyprint.hector.api.query, org.apache.sling.api.resource, org.apache.sling.cassandra.resource.provider; version=0.0.1.SNAPSHOT Import-Package: com.sun.org.apache.xerces.internal.impl.dv.util, javax.servlet.http, me.prettyprint.cassandra.model; version=[1.0, 2), me.prettyprint.cassandra.serializers; version=[1.0, 2), me.prettyprint.hector.api; version=[1.0, 2), me.prettyprint.hector.api.beans; version=[1.0, 2), me.prettyprint.hector.api.ddl; version=[1.0, 2), me.prettyprint.hector.api.factory; version=[1.0, 2), me.prettyprint.hector.api.query; version=[1.0, 2), org.apache.sling.api.resource; version=[2.3, 3), org.slf4j; version=[1.5, 2) Manifest-Version: 1.0 Tool: Bnd-2.1.0.20130426-122213 method B Goto http://localhost:8080/system/console select the bundle tab and install the bundle by uploading. If you monitor the logs you should see no errors, the bundle should register and you should be able to map cassandra read only to somewhere in the resource tree. Can you explain in a bit more detail how I should map a cassandra resources from sling browser http://localhost:8080/.explorer.html ? . I can add different JCR node types. How my cassandra node type get registered here. Does it load all resource providers from reflection when I implemented the provider interface. Hi Ian, Can you please provide me an explanation on above fact I raised which is related to this thread, thought you might have missed this.
