[VOTE RESULT] Release Testing ResourceResolver Mock 0.1.0
The vote passed with 5 binding +1 votes from Mike Müller, Ian Boston, Bertrand Delacretaz, Felix Meschberger, and Carsten Ziegeler Thanks for voting Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Closed] (SLING-2826) Add new testing module for easy resource resolver mocking
[ https://issues.apache.org/jira/browse/SLING-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-2826. --- Add new testing module for easy resource resolver mocking - Key: SLING-2826 URL: https://issues.apache.org/jira/browse/SLING-2826 Project: Sling Issue Type: New Feature Components: Testing Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Testing ResourceResolver Mock 0.1.0 Mocking a resource resolver / factory is a quiet complicated task, however for creating integration tests its often required. This module provides a simple ResourceResolver / Factory mock which is an in-memory implementation of the resource resolver -- 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] [Updated] (SLING-2836) Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods cause Sling Referrer Filter Tab clones
[
https://issues.apache.org/jira/browse/SLING-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Tripodi updated SLING-2836:
--
Attachment: SLING-2836.patch
The proposed patch fixes the reported issue
Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods
cause Sling Referrer Filter Tab clones
-
Key: SLING-2836
URL: https://issues.apache.org/jira/browse/SLING-2836
Project: Sling
Issue Type: Bug
Components: Console
Affects Versions: Security 1.0.2
Reporter: Simone Tripodi
Fix For: Security 1.0.4
Attachments: SLING-2836.patch
As per subject, {{ReferrerFilter#activate()}} and
{{ReferrerFilter#deactivate()}} methods are not annotated with {{@Activate}}
and {{@Deactivate}} annotations, that causes the _Sling Referrer Filter_ tab
in the _Configuration Status_ is cloned.
I'd assume that it is because the {{ReferrerFilter}} is never deactivated so
multiple {{ReferrerFilter}} instances exist.
Patch is following!
--
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] [Assigned] (SLING-2836) Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods cause Sling Referrer Filter Tab clones
[
https://issues.apache.org/jira/browse/SLING-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-2836:
---
Assignee: Carsten Ziegeler
Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods
cause Sling Referrer Filter Tab clones
-
Key: SLING-2836
URL: https://issues.apache.org/jira/browse/SLING-2836
Project: Sling
Issue Type: Bug
Components: Console
Affects Versions: Security 1.0.2
Reporter: Simone Tripodi
Assignee: Carsten Ziegeler
Fix For: Security 1.0.4
Attachments: SLING-2836.patch
As per subject, {{ReferrerFilter#activate()}} and
{{ReferrerFilter#deactivate()}} methods are not annotated with {{@Activate}}
and {{@Deactivate}} annotations, that causes the _Sling Referrer Filter_ tab
in the _Configuration Status_ is cloned.
I'd assume that it is because the {{ReferrerFilter}} is never deactivated so
multiple {{ReferrerFilter}} instances exist.
Patch is following!
--
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-2836) Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods cause Sling Referrer Filter Tab clones
[
https://issues.apache.org/jira/browse/SLING-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2836.
-
Resolution: Fixed
Thanks for your patch. I've applied it.
While the @Activate annotation is not really necessary as that method is using
the default method name + signature, @Deactive is required. However, for
claritiy I added both annotations
Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods
cause Sling Referrer Filter Tab clones
-
Key: SLING-2836
URL: https://issues.apache.org/jira/browse/SLING-2836
Project: Sling
Issue Type: Bug
Components: Console
Affects Versions: Security 1.0.2
Reporter: Simone Tripodi
Assignee: Carsten Ziegeler
Fix For: Security 1.0.4
Attachments: SLING-2836.patch
As per subject, {{ReferrerFilter#activate()}} and
{{ReferrerFilter#deactivate()}} methods are not annotated with {{@Activate}}
and {{@Deactivate}} annotations, that causes the _Sling Referrer Filter_ tab
in the _Configuration Status_ is cloned.
I'd assume that it is because the {{ReferrerFilter}} is never deactivated so
multiple {{ReferrerFilter}} instances exist.
Patch is following!
--
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
[VOTE] Release Apache Sling Security 1.0.4
Hi, this vote is about a fix in the security module (SLING-2836) So please vote for the release of: Apache Sling Security 1.0.4 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-124https://repository.apache.org/content/repositories/orgapachesling-237/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 124 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release Apache Sling Security 1.0.4
+1 Carsten 2013/4/22 Carsten Ziegeler cziege...@apache.org Hi, this vote is about a fix in the security module (SLING-2836) So please vote for the release of: Apache Sling Security 1.0.4 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-124https://repository.apache.org/content/repositories/orgapachesling-237/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 124 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
[jira] [Assigned] (SLING-2807) remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel
[ https://issues.apache.org/jira/browse/SLING-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-2807: --- Assignee: Carsten Ziegeler remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel --- Key: SLING-2807 URL: https://issues.apache.org/jira/browse/SLING-2807 Project: Sling Issue Type: Sub-task Components: Launchpad Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Attachments: SLING-2807.patch all three are broken (outdated and incomplete) -- 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-2807) remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel
[ https://issues.apache.org/jira/browse/SLING-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2807. - Resolution: Fixed Fix Version/s: Launchpad Builder 7 Thanks for your patch, Oliver. It really seems to make sense to remove this stuff which is not maintained at all. remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel --- Key: SLING-2807 URL: https://issues.apache.org/jira/browse/SLING-2807 Project: Sling Issue Type: Sub-task Components: Launchpad Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Fix For: Launchpad Builder 7 Attachments: SLING-2807.patch all three are broken (outdated and incomplete) -- 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] [Assigned] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-2789: --- Assignee: Carsten Ziegeler deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- 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-2789) deploying Sling 7-SNAPSHOT on Karaf fails
[ https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637857#comment-13637857 ] Carsten Ziegeler commented on SLING-2789: - Many thanks for taking this up and working on integration with Karaf. I've applied your provided patch, however :) I disabled the build of these modules for now. I've some questions (really just curious): - Why are you using the version 0.1.0.BUILD-SNAPSHOT ? - There are currently snapshot dependencies to Karaf tooling. What are the release plans for that? Thanks deploying Sling 7-SNAPSHOT on Karaf fails - Key: SLING-2789 URL: https://issues.apache.org/jira/browse/SLING-2789 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Environment: Karaf 3.0.0.* Reporter: Oliver Lietz Assignee: Carsten Ziegeler Attachments: SLING-2789.patch, sling-launchpad-karaf.tar.gz $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start $ ssh -p 8101 karaf@localhost karaf@root() feature:install http karaf@root() feature:install webconsole karaf@root() feature:repo-add mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features karaf@root() feature:install sling no errors on startup but JCR is nearly empty to prevent errors: - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to features.xml - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from features.xml - remove management from featuresBoot in org.apache.karaf.features.cfg or remove org.apache.aries.* from features.xml setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true does not help -- 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] [Assigned] (SLING-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-2827: --- Assignee: Carsten Ziegeler discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637870#comment-13637870 ] Carsten Ziegeler commented on SLING-2827: - Thanks for your contribution, Stefan - I've applied your first version (md5 d8891e5401114b2a629d3ff01044a1d6). However I wasn't able to apply the patches. Could you please create a new patch based on the version from svn? discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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-2822) Extensible Sling system health checking tool
[ https://issues.apache.org/jira/browse/SLING-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637871#comment-13637871 ] Bertrand Delacretaz commented on SLING-2822: I wouldn't completely remove the JUnit stuff, rather move it to a separate bundle under testing/junit where it belongs, and maybe not include it by default once we eventually add HC to the Sling launchpad. The optional imports are a good sign that this needs to be a separate bundle. Here's my current open issues list, revised to include this: -The servlet output is not JSON -Implement access restrictions as described above -A Web console plugin might be useful to execute rules found under a specified path -Provide a simple HTML report of rules execution (in the Web console maybe?) -Tags on rules? Can be useful to execute only subsets of them -Need to clarify the naming conventions as per Felix's comment above -Implement a demo rule that checks scripts for suboptimal/deprecated code and outputs improvement suggestions (helps make sure rule output is appropriate for such use cases) -Add a core rule that checks OSGi configuration parameters -Move the JUnit stuff to its own bundle under testing/junit Extensible Sling system health checking tool Key: SLING-2822 URL: https://issues.apache.org/jira/browse/SLING-2822 Project: Sling Issue Type: Improvement Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Attachments: nodes.json, nodes.json, setup.bash I have created a prototype at https://github.com/bdelacretaz/muppet-prototype that we might want to move to our contrib folder. Muppet (it's like a Puppet, but different (*)) allows you to check the health of a system by defining rules that (out of the box) verify things like the presence of specific OSGi bundles, JMX MBeans values, JUnit tests execution (including scriptable ones thanks to the Sling testing tools), correct disabling of default Sling credentials, etc. New rule types can be defined by adding RuleBuilder OSGi services, there are several examples in this initial code. I'll add a how-to for this initial version here. Known issues are: -The output does not indicate the value that causes a rule to fail -The servlet output is not JSON yet -Tags on rules would be nice to be able to run just the performance or security rules for example -A rule for checking OSGi configuration parameters would be useful. (*) credits to Joerg Hoh for that one, as well as inspiration in https://github.com/joerghoh/cq5-healthcheck -- 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-2822) Extensible Sling system health checking tool
[ https://issues.apache.org/jira/browse/SLING-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637873#comment-13637873 ] Felix Meschberger commented on SLING-2822: -- I wouldn't completely remove the JUnit stuff, rather move it to a separate bundle under testing/junit where it belongs Sounds like a good plan to me. Extensible Sling system health checking tool Key: SLING-2822 URL: https://issues.apache.org/jira/browse/SLING-2822 Project: Sling Issue Type: Improvement Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Attachments: nodes.json, nodes.json, setup.bash I have created a prototype at https://github.com/bdelacretaz/muppet-prototype that we might want to move to our contrib folder. Muppet (it's like a Puppet, but different (*)) allows you to check the health of a system by defining rules that (out of the box) verify things like the presence of specific OSGi bundles, JMX MBeans values, JUnit tests execution (including scriptable ones thanks to the Sling testing tools), correct disabling of default Sling credentials, etc. New rule types can be defined by adding RuleBuilder OSGi services, there are several examples in this initial code. I'll add a how-to for this initial version here. Known issues are: -The output does not indicate the value that causes a rule to fail -The servlet output is not JSON yet -Tags on rules would be nice to be able to run just the performance or security rules for example -A rule for checking OSGi configuration parameters would be useful. (*) credits to Joerg Hoh for that one, as well as inspiration in https://github.com/joerghoh/cq5-healthcheck -- 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: [VOTE] Release Apache Sling Security 1.0.4
+1 Regards Felix -- Felix Meschberger | Principal Scientist | Adobe On 22.04.13 10:13, Carsten Ziegeler cziege...@apache.org wrote: Hi, this vote is about a fix in the security module (SLING-2836) So please vote for the release of: Apache Sling Security 1.0.4 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-124http s://repository.apache.org/content/repositories/orgapachesling-237/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 124 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards -- Carsten Ziegeler cziege...@apache.org
RE: [VOTE] Release Apache Sling Security 1.0.4
+1 best regards mike -Original Message- From: Carsten Ziegeler [mailto:cziege...@apache.org] Sent: Monday, April 22, 2013 10:14 AM To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling Security 1.0.4 Hi, this vote is about a fix in the security module (SLING-2836) So please vote for the release of: Apache Sling Security 1.0.4 Staging repository: https://repository.apache.org/content/repositories/orgapachesling- 124https://repository.apache.org/content/repositories/orgapachesling-237/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 124 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2710) Define TenantManager API
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637881#comment-13637881
]
Carsten Ziegeler commented on SLING-2710:
-
I had a brief look at the current state and I think there is something wrong
wrt TenantProvider/TenantManager. While the API of TenantProvider suggests that
there is more than a single provider, the implementation uses exactly one,
which is also the manager implementation. So either we separate this, or remove
the tenant provider interface.
Right now, I would opt for removing TenantProvider, especially as this opens
some questions when creating a new tenant through the manager. Which provider
is used and why and wouldn't we need a way to create a tenant based on a
provider?
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove) through
the Web Console. In addition the TenantProvider service interface allows for
looking tenants up (read).
For administrative purposes it would be good to have a TenantManager service
interface which allows for these administrative tasks. Something like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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-2710) Define TenantManager API
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637888#comment-13637888
]
Felix Meschberger commented on SLING-2710:
--
I think the confusing stems from the names ...
TenantProvider is used by client applications to read tenants and tenant
information.
TenantManager is used by management agents to actually manage tenants such as
creating, removing, or updating them.
There is only a single TenantProvider and only a single TenantManager in the
framework.
The idea is properly separate read-only access and management access into
separate APIs since the read-only case will be the major use case while the
update use case should be reserved to management applications, such as for
example some Tenant management UI.
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove) through
the Web Console. In addition the TenantProvider service interface allows for
looking tenants up (read).
For administrative purposes it would be good to have a TenantManager service
interface which allows for these administrative tasks. Something like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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] [Updated] (SLING-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-2827: --- Attachment: discovery.impl.svn.patch [~cziegeler] Sure, sorry bout that, that might stem from the fact that it was created in git..:S Attached the svn-based diff based on r1470424 including the latest rename of DiscoveryAware to TopologyEventListener discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.svn.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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-2710) Define TenantManager API
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637892#comment-13637892
]
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right? I think the
javadocs need some clarifications in this case. And maybe a different name than
TenantProvider - I might be biased but it sounds similar to ResourceProvider
where we have a potential set of providers and not just a single one.
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove) through
the Web Console. In addition the TenantProvider service interface allows for
looking tenants up (read).
For administrative purposes it would be good to have a TenantManager service
interface which allows for these administrative tasks. Something like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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: [jira] [Commented] (SLING-2710) Define TenantManager API
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of for a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant applying to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased but it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks. Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637932#comment-13637932 ] Carsten Ziegeler commented on SLING-2827: - Thanks for the updated patch, Stefan - it's applied now. discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.svn.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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: [jira] [Commented] (SLING-2710) Define TenantManager API
Thanks Felix - for the naming while I see minor problems with
TenantProvider I don't have a stronge urge to change the name and in lack
of a good alternative we can keep it.
The separation between the reading and the administrative use case makes
sense to me.
So what about declaring this done and do a release?
Carsten
2013/4/22 Felix Meschberger fmesc...@adobe.com
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of for a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant applying to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased but it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks. Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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
--
Carsten Ziegeler
cziege...@apache.org
Re: [jira] [Commented] (SLING-2710) Define TenantManager API
Ah just noticed the second part:
* For now this provider interface provides access to a tenant applying to
a
* particular request as well as to all tenants known to this provider.
There is nothing about a request in this interface, so I think this should
be changed?
Carsten
2013/4/22 Carsten Ziegeler cziege...@apache.org
Thanks Felix - for the naming while I see minor problems with
TenantProvider I don't have a stronge urge to change the name and in lack
of a good alternative we can keep it.
The separation between the reading and the administrative use case makes
sense to me.
So what about declaring this done and do a release?
Carsten
2013/4/22 Felix Meschberger fmesc...@adobe.com
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of for a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant applying to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased but it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks. Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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
--
Carsten Ziegeler
cziege...@apache.org
--
Carsten Ziegeler
cziege...@apache.org
Re: [jira] [Commented] (SLING-2710) Define TenantManager API
On 22.04.13 13:24, Carsten Ziegeler cziege...@apache.org wrote:
Ah just noticed the second part:
* For now this provider interface provides access to a tenant applying
to
a
* particular request as well as to all tenants known to this provider.
There is nothing about a request in this interface, so I think this should
be changed?
Yes ;-)
Regards
Felix
Carsten
2013/4/22 Carsten Ziegeler cziege...@apache.org
Thanks Felix - for the naming while I see minor problems with
TenantProvider I don't have a stronge urge to change the name and in
lack
of a good alternative we can keep it.
The separation between the reading and the administrative use case makes
sense to me.
So what about declaring this done and do a release?
Carsten
2013/4/22 Felix Meschberger fmesc...@adobe.com
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of
for a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant
applying to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased
but it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think
the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL:
https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks.
Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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
--
Carsten Ziegeler
cziege...@apache.org
--
Carsten Ziegeler
cziege...@apache.org
Re: [jira] [Commented] (SLING-2710) Define TenantManager API
On 22.04.13 13:22, Carsten Ziegeler cziege...@apache.org wrote:
Thanks Felix - for the naming while I see minor problems with
TenantProvider I don't have a stronge urge to change the name and in lack
of a good alternative we can keep it.
The separation between the reading and the administrative use case makes
sense to me.
So what about declaring this done and do a release?
+1 ;-)
Regards
Felix
Carsten
2013/4/22 Felix Meschberger fmesc...@adobe.com
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of for
a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant applying
to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased but
it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think
the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks.
Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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
--
Carsten Ziegeler
cziege...@apache.org
[jira] [Resolved] (SLING-2710) Define TenantManager API
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2710.
-
Resolution: Fixed
As discussed on the mailing list, we can consider this done
Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove) through
the Web Console. In addition the TenantProvider service interface allows for
looking tenants up (read).
For administrative purposes it would be good to have a TenantManager service
interface which allows for these administrative tasks. Something like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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: [jira] [Commented] (SLING-2710) Define TenantManager API
Great, i've just closed the issue :)
Let's give people a couple of days for further comments and then I'll cut a
release.
2013/4/22 Felix Meschberger fmesc...@adobe.com
On 22.04.13 13:22, Carsten Ziegeler cziege...@apache.org wrote:
Thanks Felix - for the naming while I see minor problems with
TenantProvider I don't have a stronge urge to change the name and in lack
of a good alternative we can keep it.
The separation between the reading and the administrative use case makes
sense to me.
So what about declaring this done and do a release?
+1 ;-)
Regards
Felix
Carsten
2013/4/22 Felix Meschberger fmesc...@adobe.com
Hi
Maybe we should have this discussion on the list ?
On 22.04.13 12:13, Carsten Ziegeler (JIRA) j...@apache.org wrote:
Carsten Ziegeler commented on SLING-2710:
-
So we expect only a single provider to be available, right?
Yes.
I think the javadocs need some clarifications in this case.
Currently it states:
/**
* The codeTenantProvider/code defines the service interface of for
a
sevice
* which may be asked for {@link Tenant tenant instances}.
* p
* For now this provider interface provides access to a tenant applying
to
a
* particular request as well as to all tenants known to this provider.
*/
@ProviderType
And maybe a different name than TenantProvider - I might be biased but
it
sounds similar to ResourceProvider where we have a potential set of
providers and not just a single one.
I don't have too strong of an opinion regarding the name. But I think
the
distinction between the general (and broder) use of reading tenants as
opposed to the specialized management of tenants warrants having two
separate APIs.
In any case, there is, of course, also an AdapterFactory for tenants in
the implementation.
Regards
Felix
Define TenantManager API
Key: SLING-2710
URL:
https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Tenant 1.0
Attachments: SLING-2710-2.patch, SLING-2710.patch
Tenants currently can only be administered (create, update, remove)
through the Web Console. In addition the TenantProvider service
interface allows for looking tenants up (read).
For administrative purposes it would be good to have a TenantManager
service interface which allows for these administrative tasks.
Something
like:
public interface TenantManager extends TenantProvider {
Tenant create(String tenantId, MapString, Object properties);
void setProperty(Tenant tenant, String name, Object value);
void remove(Tenant tenant);
}
--
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
--
Carsten Ziegeler
cziege...@apache.org
--
Carsten Ziegeler
cziege...@apache.org
[jira] [Commented] (SLING-2835) Addition of OSGi-aware javax.activation bundle
[ https://issues.apache.org/jira/browse/SLING-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637993#comment-13637993 ] Felix Meschberger commented on SLING-2835: -- Thanks for the patch. I have a comment on formatting: We generally use Sun's original Java formatting guidelines. Particularly we format all blocks as regular brace-encapsulated blocks even if the block has a single-statement only. May I ask you to fix ? Thanks. Addition of OSGi-aware javax.activation bundle -- Key: SLING-2835 URL: https://issues.apache.org/jira/browse/SLING-2835 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Robert Munteanu Attachments: org.apache.sling.javax.activation.zip Currently Sling exposes the javax.activation package using a system framework extension. This works well for some use cases. However, it does not work well with the official javax.mail bundle. The javax.mail bundle is now OSGi-aware, but the classloading problems between javax.mail and javax.activation persist. javax.activation tries to read a /META-INF/mailcap file from the javamail jar and loads DataContentHandler classes from the javamail jar. To prevent this problem from occuring I have created a javax.activation bundle which provides a custom CommandMap implementation. This implementation uses the foreign bundle's classloader ( e.g. javax.mail classloader ) to load classes. This solves the classloading conflict between javax.mail and javax.activation. I will attach a zip archive of the maven project to the bundle as a contribution. The file is named org.apache.sling.javax.activation.zip and has the sha1sum cd4ad4279b5673a070d919a118d9aca571656f91 , md5sum 68487bdca46ba47bce9947087bd659ea . -- 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] [Updated] (SLING-2835) Addition of OSGi-aware javax.activation bundle
[ https://issues.apache.org/jira/browse/SLING-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2835: --- Attachment: org.apache.sling.javax.activation.zip Addition of OSGi-aware javax.activation bundle -- Key: SLING-2835 URL: https://issues.apache.org/jira/browse/SLING-2835 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Robert Munteanu Attachments: org.apache.sling.javax.activation.zip, org.apache.sling.javax.activation.zip Currently Sling exposes the javax.activation package using a system framework extension. This works well for some use cases. However, it does not work well with the official javax.mail bundle. The javax.mail bundle is now OSGi-aware, but the classloading problems between javax.mail and javax.activation persist. javax.activation tries to read a /META-INF/mailcap file from the javamail jar and loads DataContentHandler classes from the javamail jar. To prevent this problem from occuring I have created a javax.activation bundle which provides a custom CommandMap implementation. This implementation uses the foreign bundle's classloader ( e.g. javax.mail classloader ) to load classes. This solves the classloading conflict between javax.mail and javax.activation. I will attach a zip archive of the maven project to the bundle as a contribution. The file is named org.apache.sling.javax.activation.zip and has the sha1sum cd4ad4279b5673a070d919a118d9aca571656f91 , md5sum 68487bdca46ba47bce9947087bd659ea . -- 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-2835) Addition of OSGi-aware javax.activation bundle
[ https://issues.apache.org/jira/browse/SLING-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638013#comment-13638013 ] Robert Munteanu commented on SLING-2835: I've reformatted the code to use braces for single-line statements. The new checksums are 36d15b31af430d0769c54eb03c33ccf0a0b527ce ( SHA1 ) and 9c4c797b8bc520dd248344877be5ea66 (MD5). Addition of OSGi-aware javax.activation bundle -- Key: SLING-2835 URL: https://issues.apache.org/jira/browse/SLING-2835 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Robert Munteanu Attachments: org.apache.sling.javax.activation.zip, org.apache.sling.javax.activation.zip Currently Sling exposes the javax.activation package using a system framework extension. This works well for some use cases. However, it does not work well with the official javax.mail bundle. The javax.mail bundle is now OSGi-aware, but the classloading problems between javax.mail and javax.activation persist. javax.activation tries to read a /META-INF/mailcap file from the javamail jar and loads DataContentHandler classes from the javamail jar. To prevent this problem from occuring I have created a javax.activation bundle which provides a custom CommandMap implementation. This implementation uses the foreign bundle's classloader ( e.g. javax.mail classloader ) to load classes. This solves the classloading conflict between javax.mail and javax.activation. I will attach a zip archive of the maven project to the bundle as a contribution. The file is named org.apache.sling.javax.activation.zip and has the sha1sum cd4ad4279b5673a070d919a118d9aca571656f91 , md5sum 68487bdca46ba47bce9947087bd659ea . -- 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] [Updated] (SLING-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-2827: --- Attachment: discovery.impl.activate_and_changing.patch [~cziegeler] another patch based on the current trunk of discovery/impl: it contains a fix for properly sending TOPOLOGY_INIT as the first event for newly bound TopologyEventListeners - plus makes sure a TOPOLOGY_CHANGING is sent before TOPOLOGY_CHANGED. discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.activate_and_changing.patch, discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.svn.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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-2827) discovery.impl: a resource based implementation of the discovery.api
[ https://issues.apache.org/jira/browse/SLING-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638048#comment-13638048 ] Carsten Ziegeler commented on SLING-2827: - Thanks for another patch, Stefan - it's applied now discovery.impl: a resource based implementation of the discovery.api Key: SLING-2827 URL: https://issues.apache.org/jira/browse/SLING-2827 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Stefan Egli Assignee: Carsten Ziegeler Attachments: discovery.impl.activate_and_changing.patch, discovery.impl.bootstrap.patch, discovery.impl.loops.timeouts.webconsole.patch, discovery.impl.svn.patch, discovery.impl.tar.gz This ticket is about contributing a resource based implementation of the discovery api (see [0]) named discovery.impl to Sling. The implementation is attached as a .tar.gz - its md5 hash is d8891e5401114b2a629d3ff01044a1d6 Short description of the discovery.impl: The discovery.impl is an out-of-the-box implementation of the discovery.api using standard features of Sling. The discovery.api provides a view of a topology consisting of a number of individual sling-instances. The instances are loosely coupled, except for being part of the topology they do not implicitly or necessarily share anything else. For those instances though that form a cluster - ie when connected to the same repository - the api has an abstraction called ClusterView. The discovery.impl uses two mechanisms for discovering other instances: * it stores information about the local instance at a unique location in the repository. Thus allowing other instances that access the same repository to see and recognize each other. * it connects to 'remote' instances via a plain HTTP POST, announcing the instances that it can see, and getting back the instances of the counterpart All of the above is done regularly using a heart-beat - thus allowing to get a view of the currently live instances. The discovery.api additionally supports leader-election within a cluster: it ensures that one and only one instance is elected leader and stays leader until it disappears/shuts down/dies. The discovery.impl uses repository-based voting between the instances of a cluster to establish a common 'cluster view'. Based on an established view, the discovery.impl is then able to deterministically elect one of the instances of the view as the leader (namely the one with the lowest 'id'). Also, to support the PropertyProvider concept of the discovery.api, the properties of each instance are propagated to the other instances using the heartbeat as piggyback (either via the repository or via HTTP POSTs for remote instances). To get an idea of the discovery.impl build and add and start the two bundles (org.apache.sling.discovery.api and org.apache.sling.discovery.impl) to your sling installation and open the browser to the provided, simplistic 'topology webconsole' at http://localhost:4502/system/console/topology Please let me know if anything needs further explanation, details. Looking forward to having this included in Sling! Cheers, Stefan -- [0] http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/discovery/api -- 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] [Updated] (SLING-2798) Apache Cassandra backend for Sling: GSoC2013 Project
[ https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dishara Wijewardana updated SLING-2798: --- Attachment: Sling Cassandra backend Architecture.jpg Apache Cassandra backend for Sling: GSoC2013 Project Key: SLING-2798 URL: https://issues.apache.org/jira/browse/SLING-2798 Project: Sling Issue Type: Bug Components: Samples Reporter: Ian Boston Labels: cassandra, gsoc, gsoc2013, java, osgi, sling Attachments: Sling Cassandra backend Architecture.jpg This is a proposal for GSoC2013: create an Resource Provider that allows resources stored in Apache Cassandra to be exposed as Sling Resources. Resources[1] are the basic building blocks of Sling. ResourceProviders[2] allow data sources to be added to the core ResourceProvider within Sling allowing those data sources to provide Resources at pre-determined locations in the resource tree. To put it in more familiar terms, implementing and adding a Resource provider is like mounting or mapping a network drive. A more recent addition to the facilities available in Sling include updatable ResourceProviders. Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear scalability to web scale. It is used by many of the best known names on the internet. Initially this will provide read only resource access, but if there is time in the project will allow read write access to a cassandra cluster. Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra will be valuable. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://sling.apache.org/site/resources.html 2 http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html 3 http://cassandra.apache.org/ -- 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: Apache Cassandra backend for Sling: GSoC2013 Project
Hi Ian, Here [1] I have attached the high level architecture diagram of the cassandra back end implementation for Sling to the JIRA. Please let me know if there is any concerns so that I can use this diagram to the proposal. [1] - https://issues.apache.org/jira/secure/attachment/12579842/Sling%20Cassandra%20backend%20Architecture.jpg On Sat, Apr 13, 2013 at 4:29 PM, Ian Boston i...@tfd.co.uk wrote: Hi, The breakdown looks good, but I think you should aim to keep the implementation in Cassandra simple to start with and not underestimate how much time it may take to implement both read/write and access control on read/write. No need to change the plan or be too specific at this stage. Best Regards Ian On 12 April 2013 23:24, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi Ian, I am in the process of writing the proposal. So as you mentioned earlier it is better to split this in to 4 sub tasks and 2 before midterm and 2 after mid term. So in summary I would like to add the subtasks that I feel. Please add anything I am missing or anything required to have. Main tasks overview: 1. Implementing a CassandraResourceProvider to READ from Cassandra. Implementation Details [1] 2. Test with one node Cassandra cluster end to end with the implementation of #1. 3. Enhance CassandraResourceProvider to READ with access control (with latest security related APIs). 4. Enhance CassandraResourceProvider(or may be a new interface for writing i.e CassandraPopulator) to WRITE and WRITE with access control. Here as I feel, #1 and #2 completion will more weight and relatively more time consuming than #3 and #4 (I am not aware of the complexity of incoperating the access control to READ/WRITE). Appreciate your valuable feedback on this, whether this task breakdown is appropriate or not suits to the GSoC time line or anything more to add/remove and etc ? [1] : Implementation Details: - Write a CassanrdaResourceProviderUtil which is basically a cassendra client which will facilitate all cassandra related operations required by other modules (CassandraResourceProvider and CassandraResourceResolver). - Implementation of CassandraResourceProvider - Implementation of CassandraResourceResolver - Implementation of CassandraResource On Sun, Apr 7, 2013 at 3:27 PM, Ian Boston i...@tfd.co.uk wrote: On 7 April 2013 14:07, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Sun, Apr 7, 2013 at 3:00 AM, Ian Boston i...@tfd.co.uk wrote: That sounds good. If you havent already it will be important to become familiar with OSGi and Sling itself. Please dont do too much work before getting being accepted. I cant guarantee that you will be accepted since there are lots of Apache projects, lots of submissions and a limited number of places given to Apache. Yes I agree with you. There are loads of projects from Apache each year. But if the proposal is solid where it's apparently attainable within the timeline and if community willing to mentor the project with high priority, I think there is a very good chance of getting accepted. But still can't guarantee it 100%. I got what you meant ;-). Good, we understand each other, and your analysis is correct. Just incase it hasn't been obvious, I am very willing to mentor this project, as are other members of the community for other projects. Ian Thanks for the feedback. Have a great weekend. Ian On 7 April 2013 02:12, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi Ian Than you for the quick response. I have started localhost Cassendra and written some codes through hector API to create columns and etc. And works fine. I am still doing some more test codings to get familiar more with Cassendra these days so that I can reuse those codes and write an appropriate CassendraResourceProviderUtil class .Meanwhile I will prepare the project proposal. Please let me know if you want something more/else to be done before hand that would be useful to this project. On Sat, Apr 6, 2013 at 12:45 PM, Ian Boston i...@tfd.co.uk wrote: Hi Hector looks good. Sling wont ship a Cassandra instance, for this project it will uses a Cassandra instance setup separately Last time I spun up Cassandra it for dev purposes it was just as easy as installing MySQL or PostgreSQL, so I think that fine. +1. If using Hector, I think it would be good to do everything in CQL and keep it all very simple and transparent. Remember the aim of the project is to prove that the ResourceProvider API can support Cassandra as a
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling JCR Resource Resolver #1628
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.jcr.resource/1628/changes
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1628
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1628/changes Changes: [cziegeler] SLING-2830 : Discontinue per job configurations for queue processing [cziegeler] Handle retry delay [cziegeler] Update svn:ignore [cziegeler] SLING-2829 : Add API for starting a job and service interface for executing a job [cziegeler] SLING-2829 : Add API for starting a job and service interface for executing a job [cziegeler] SLING-2832 : Use resource API SLING-2831 : Use new discovery API SLING-2830 : Discontinue per job configurations for queue processing SLING-2829 : Add API for starting a job and service interface for executing a job -- [INFO] [INFO] [INFO] Building Apache Sling Event Support 3.1.5-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/maven-metadata.xml (1010 B at 3.7 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/org.apache.sling.discovery.api-0.1.0-20130419.165701-5.pom Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/org.apache.sling.discovery.api-0.1.0-20130419.165701-5.pom (4 KB at 27.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-container-native/2.5.0/pax-exam-container-native-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-container-native/2.5.0/pax-exam-container-native-2.5.0.pom (3 KB at 55.3 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/2.5.0/exam-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/2.5.0/exam-2.5.0.pom (14 KB at 291.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam-reactor/2.5.0/exam-reactor-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam-reactor/2.5.0/exam-reactor-2.5.0.pom (5 KB at 42.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam/2.5.0/pax-exam-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam/2.5.0/pax-exam-2.5.0.pom (3 KB at 66.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-spi/2.5.0/pax-exam-spi-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-spi/2.5.0/pax-exam-spi-2.5.0.pom (3 KB at 48.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-junit4/2.5.0/pax-exam-junit4-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-junit4/2.5.0/pax-exam-junit4-2.5.0.pom (2 KB at 125.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-link-mvn/2.5.0/pax-exam-link-mvn-2.5.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-link-mvn/2.5.0/pax-exam-link-mvn-2.5.0.pom (804 B at 26.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.testing.resourceresolver-mock/0.1.0/org.apache.sling.testing.resourceresolver-mock-0.1.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.testing.resourceresolver-mock/0.1.0/org.apache.sling.testing.resourceresolver-mock-0.1.0.pom (3 KB at 11.0 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/org.apache.sling.discovery.api-0.1.0-20130419.165701-5.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.discovery.api/0.1.0-SNAPSHOT/org.apache.sling.discovery.api-0.1.0-20130419.165701-5.jar (28 KB at 170.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-container-native/2.5.0/pax-exam-container-native-2.5.0.jar Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam/2.5.0/pax-exam-2.5.0.jar Downloading: http://repo.maven.apache.org/maven2/org/ops4j/base/ops4j-base-store/1.3.0/ops4j-base-store-1.3.0.jar Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/swissbox/pax-swissbox-lifecycle/1.5.1/pax-swissbox-lifecycle-1.5.1.jar Downloading: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam-spi/2.5.0/pax-exam-spi-2.5.0.jar Downloaded: http://repo.maven.apache.org/maven2/org/ops4j/pax/exam/pax-exam/2.5.0/pax-exam-2.5.0.jar (76 KB at 3412.5 KB/sec) Downloading:
Re: Apache Cassandra backend for Sling: GSoC2013 Project
Hi Dishara, The diagram looks good and summarises how resource providers are integrated into the resources resolver. Obviously there is a little more detail in reality, but its a good overview. Ian On Tuesday, April 23, 2013, Dishara Wijewardana wrote: Hi Ian, Here [1] I have attached the high level architecture diagram of the cassandra back end implementation for Sling to the JIRA. Please let me know if there is any concerns so that I can use this diagram to the proposal. [1] - https://issues.apache.org/jira/secure/attachment/12579842/Sling%20Cassandra%20backend%20Architecture.jpg On Sat, Apr 13, 2013 at 4:29 PM, Ian Boston i...@tfd.co.uk wrote: Hi, The breakdown looks good, but I think you should aim to keep the implementation in Cassandra simple to start with and not underestimate how much time it may take to implement both read/write and access control on read/write. No need to change the plan or be too specific at this stage. Best Regards Ian On 12 April 2013 23:24, Dishara Wijewardana ddwijeward...@gmail.com wrote: Hi Ian, I am in the process of writing the proposal. So as you mentioned earlier it is better to split this in to 4 sub tasks and 2 before midterm and 2 after mid term. So in summary I would like to add the subtasks that I feel. Please add anything I am missing or anything required to have. Main tasks overview: 1. Implementing a CassandraResourceProvider to READ from Cassandra. Implementation Details [1] 2. Test with one node Cassandra cluster end to end with the implementation of #1. 3. Enhance CassandraResourceProvider to READ with access control (with latest security related APIs). 4. Enhance CassandraResourceProvider(or may be a new interface for writing i.e CassandraPopulator) to WRITE and WRITE with access control. Here as I feel, #1 and #2 completion will more weight and relatively more time consuming than #3 and #4 (I am not aware of the complexity of incoperating the access control to READ/WRITE). Appreciate your valuable feedback on this, whether this task breakdown is appropriate or not suits to the GSoC time line or anything more to add/remove and etc ? [1] : Implementation Details: - Write a CassanrdaResourceProviderUtil which is basically a cassendra client which will facilitate all cassandra related operations required by other modules (CassandraResourceProvider and CassandraResourceResolver). - Implementation of CassandraResourceProvider - Implementation of CassandraResourceResolver - Implementation of CassandraResource On Sun, Apr 7, 2013 at 3:27 PM, Ian Boston i...@tfd.co.uk wrote: On 7 April 2013 14:07, Dishara Wijewardana ddwijeward...@gmail.com wrote: On Sun, Apr 7, 2013 at 3:00 AM, Ian Boston i...@tfd.co.uk wrote: That sounds good. If you havent already it will be important to become familiar with OSGi and Sling itself. Please dont do too much work before getting being accepted. I cant guarantee that you will be accepted since there are lots of Apache projects, lots of submissions and a limited number of places given to Apache. Yes I agree with you. There are loads of projects from Apache each year. But if the proposal is solid where it's apparently attainable within the timeline and if community willing to mentor the project with high priority, I think there is a very good chance of getting accepted. But still can't guarantee it 100%. I got what you meant ;-). Good, we understand each other, and your analysis is correct. Just incase it hasn't been obvious, I am very willing to mentor this project, as are other members of the community for other projects. Ian -- Thanks /Dishara
Build failed in Jenkins: sling-contrib-1.6 #990
See https://builds.apache.org/job/sling-contrib-1.6/990/changes Changes: [cziegeler] Minor code clean up and move property descriptions/labels into separate metatype.properties [cziegeler] Add discovery impl to reactor [cziegeler] SLING-2827 : discovery.impl: a resource based implementation of the discovery.api . Apply another patch from Stefan Egli (activate and changing patch) [cziegeler] Clean up dependencies in pom [cziegeler] Minor javadoc updates [cziegeler] Implementation is mostly resource based [cziegeler] Minor javadoc updates [cziegeler] SLING-2827 : discovery.impl: a resource based implementation of the discovery.api . Apply patch from Stefan Egli [cziegeler] SLING-2827 : discovery.impl: a resource based implementation of the discovery.api . Committed initial contribution from Stefan Egli (md5: d8891e5401114b2a629d3ff01044a1d6) [cziegeler] SLING-2789 : deploying Sling 7-SNAPSHOT on Karaf fails . Apply patch from Oliver Lietz [cziegeler] SLING-2807 : remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel. Apply patch from Oliver Lietz [cziegeler] SLING-2807 : remove create-karaf-descriptor from org.apache.sling.launchpad, contrib/servicemix-feature and contrib/launchpad/smx-kernel. Apply patch from Oliver Lietz [cziegeler] Rename DiscoveryAware to TopologyEventListener [cziegeler] Use released versions after release. [cziegeler] [maven-release-plugin] prepare for next development iteration [cziegeler] [maven-release-plugin] prepare release org.apache.sling.security-1.0.4 [cziegeler] SLING-2836 : Missing @(De)Activate annotations in ReferrerFilter#(de)activate() methods cause Sling Referrer Filter Tab clones -- [...truncated 3047 lines...] [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/jackrabbit/jackrabbit-api/2.4.2/jackrabbit-api-2.4.2.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/launchpad/testing/target/launchpad-bundles/resources/bundles/15/jackrabbit-api-2.4.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/derby/derby/10.5.3.0_1/derby-10.5.3.0_1.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/launchpad/testing/target/launchpad-bundles/resources/bundles/15/derby-10.5.3.0_1.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/tika/tika-core/1.0/tika-core-1.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/launchpad/testing/target/launchpad-bundles/resources/bundles/15/tika-core-1.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/tika/tika-bundle/1.0/tika-bundle-1.0.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/launchpad/testing/target/launchpad-bundles/resources/bundles/15/tika-bundle-1.0.jar Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.1-SNAPSHOT/maven-metadata.xml (2 KB at 2.8 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.1-SNAPSHOT/org.apache.sling.jcr.jackrabbit.server-2.1.1-20121112.103400-864.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.1-SNAPSHOT/org.apache.sling.jcr.jackrabbit.server-2.1.1-20121112.103400-864.jar (4290 KB at 1003.5 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.1-SNAPSHOT/org.apache.sling.jcr.jackrabbit.server-2.1.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/launchpad/testing/target/launchpad-bundles/resources/bundles/15/org.apache.sling.jcr.jackrabbit.server-2.1.1-SNAPSHOT.jar Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.usermanager/2.2.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.usermanager/2.2.1-SNAPSHOT/maven-metadata.xml (2 KB at 2.6 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.usermanager/2.2.1-SNAPSHOT/org.apache.sling.jcr.jackrabbit.usermanager-2.2.1-20121112.103410-371.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.jackrabbit.usermanager/2.2.1-SNAPSHOT/org.apache.sling.jcr.jackrabbit.usermanager-2.2.1-20121112.103410-371.jar (78 KB at 244.2 KB/sec) [INFO] Copying bundle from
[jira] [Created] (SLING-2837) Broken links on main project page
Remko Popma created SLING-2837: -- Summary: Broken links on main project page Key: SLING-2837 URL: https://issues.apache.org/jira/browse/SLING-2837 Project: Sling Issue Type: Bug Components: Site Reporter: Remko Popma Page http://sling.apache.org/ contains two broken links: both links in the Getting started section don't work. * Discover Sling in 15 minutes points to http://sling.apache.org/discover-sling-in-15-minutes.html should be http://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html * Getting started points to http://sling.apache.org/getting-started.html should be http://sling.apache.org/documentation/getting-started.html There may be other broken links, I did not check them all... Hope this is useful. -Remko -- 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
