[jira] [Resolved] (SLING-5439) HttpEntity in SimpleHttpTransport should be consumed / discarded

[Tommaso Teofili (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili resolved SLING-5439.

Resolution: Fixed

fixed in r1725303

> HttpEntity in SimpleHttpTransport should be consumed / discarded
> 
>
> Key: SLING-5439
> URL: https://issues.apache.org/jira/browse/SLING-5439
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: Content Distribution Core 0.1.14
>
>
> {{SimpleHttpDistributionTransport#deliverPackage}} returns Http {{Content}} 
> but doesn't use it. While it seems it's not possible to just let it go (as 
> that would leak as an unconsumed resource) such content should be discarded.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: [VOTE] Release Apache Sling Models Impl 1.2.6

[Stefan Seifert]

+1

[VOTE] Release Apache Sling Models Impl 1.2.6

[Stefan Seifert]

Hi,

We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12334324

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1408/

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 1408 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.


stefan

[jira] [Resolved] (SLING-5437) The NoSQL providers should throw LoginException if the connection to the NoSQL database can't be established

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-5437.
---
Resolution: Fixed

Completed: At revision: 1725576  

added check for couchbase as well and some more refactoring about automatic 
index creation to ensure it takes only place after successful connection check.

> The NoSQL providers should throw LoginException if the connection to the 
> NoSQL database can't be established
> 
>
> Key: SLING-5437
> URL: https://issues.apache.org/jira/browse/SLING-5437
> Project: Sling
>  Issue Type: New Feature
>  Components: NoSQL
>Affects Versions: NoSQL Generic Resource Provider 1.0.0, NoSQL Couchbase 
> Resource Provider 1.0.0, NoSQL MongoDB Resource Provider 1.0.0
>Reporter: Robert Munteanu
>Assignee: Stefan Seifert
> Fix For: NoSQL Generic Resource Provider 1.1.0, NoSQL Couchbase 
> Resource Provider 1.1.0, NoSQL MongoDB Resource Provider 1.1.0
>
> Attachments: 
> 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch
>
>
> While trying to find a proper test for SLING-5217, I noticed that the NoSQL 
> providers don't check the connection when the ResourceProvider is 
> instantiated. Therefore the ResourceProvider is always considered valid and 
> when access is attempted exceptions are thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5437) The NoSQL providers should throw LoginException if the connection to the NoSQL database can't be established

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert updated SLING-5437:
--
Fix Version/s: (was: NoSQL Couchbase Client 1.0.2)
   NoSQL Couchbase Resource Provider 1.1.0

> The NoSQL providers should throw LoginException if the connection to the 
> NoSQL database can't be established
> 
>
> Key: SLING-5437
> URL: https://issues.apache.org/jira/browse/SLING-5437
> Project: Sling
>  Issue Type: New Feature
>  Components: NoSQL
>Affects Versions: NoSQL Generic Resource Provider 1.0.0, NoSQL Couchbase 
> Resource Provider 1.0.0, NoSQL MongoDB Resource Provider 1.0.0
>Reporter: Robert Munteanu
>Assignee: Stefan Seifert
> Fix For: NoSQL Generic Resource Provider 1.1.0, NoSQL Couchbase 
> Resource Provider 1.1.0, NoSQL MongoDB Resource Provider 1.1.0
>
> Attachments: 
> 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch
>
>
> While trying to find a proper test for SLING-5217, I noticed that the NoSQL 
> providers don't check the connection when the ResourceProvider is 
> instantiated. Therefore the ResourceProvider is always considered valid and 
> when access is attempted exceptions are thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Worthwhile to create a Sling CMS?

[Sandro Boehme]

Hi Ruben,

Am 19.01.16 um 18:19 schrieb Ruben Reusser:

for what it's worth, it would be really nice to have an inline editing
experience, maybe like

https://slate.adobe.com/welcome/

Yes, I agree.
It should be possible for frontend components that are shown on the live 
page to have dependencies to other packages like inline editors. I did 
some test with the JSPM API [1] and it looks like it is feasible to 
download and install the dependencies and its transitive dependencies on 
the fly.


To use that in the page editor for editing content more changes are 
needed but I think it should not be too hard and I agree that it would 
be a nice thing to have.


Best,

Sandro

[1] - https://github.com/jspm/jspm-cli/blob/master/docs/api.md

Re: Worthwhile to create a Sling CMS?

[Bertrand Delacretaz]

Hi Sandro,

On Tue, Jan 19, 2016 at 2:25 PM, Sandro Boehme  wrote:
> ...It would help me a big deal if some of you could tell me if they would use
> this kind of CMS or if the know people who would use it as that validates
> (or invalidates) my effort!..

I don't need to host a CMS myself these days, so wouldn't use that,
but I think a Sling-based CMS would be a great showcase of what Sling
can do.

-Bertrand

Re: Worthwhile to create a Sling CMS?

[Bertrand Delacretaz]

Hi Sandro,

On Tue, Jan 19, 2016 at 2:46 PM, Sandro Boehme  wrote:
> ...Would you use it and maybe develop
> components for it if it would be available immediately as a service in the
> web (e.g. like Wix)?...

I don't think so, but my personal needs in terms of CMS are extremely
limited these days. When my friends look for websites/CMS I usually
steer them to wordpress.com to be able to get out of the way as soon
as possible. And I use that as well for my own blog, for historical
reasons and with no need for something better at the moment.

So my use cases are atypical, I'm not a good customer for such a
thing. But as I said, very interested in having concrete examples of
how to use Sling.

-Bertrand

Re: Worthwhile to create a Sling CMS?

[Sandro Boehme]

Am 19.01.16 um 14:35 schrieb Bertrand Delacretaz:

Hi Sandro,

On Tue, Jan 19, 2016 at 2:25 PM, Sandro Boehme  wrote:

...It would help me a big deal if some of you could tell me if they would use
this kind of CMS or if the know people who would use it as that validates
(or invalidates) my effort!..


I don't need to host a CMS myself these days, so wouldn't use that,
but I think a Sling-based CMS would be a great showcase of what Sling
can do.

-Bertrand



Thanks for your feedback Bertrand! Would you use it and maybe develop 
components for it if it would be available immediately as a service in 
the web (e.g. like Wix)? What CMS would you personally use instead? Or 
what other superior offering is there in your opinion?


Best,

Sandro

Worthwhile to create a Sling CMS?

[Sandro Boehme]

Hello,

I personally think there is a market and demand for a small Sling CMS 
that is a website builder which assembles frontend components from an 
open marketplace.


It would help me a big deal if some of you could tell me if they would 
use this kind of CMS or if the know people who would use it as that 
validates (or invalidates) my effort!


It should be as simple and straightforward as a typical website builder 
for composing a page from the frontend components. At the same time the 
barrier to develop these components should be as low as possible and 
developers should be able to sell components to allow a thriving 
marketplace for users to choose components from.


When researching to see if there is something comparable I didn't found 
anything. The closest were Wix, LightCMS, Hippo (marketplace planned), 
Liferay and Nuxeo. But they all have an enterprise edition which raises 
the barrier for many users and developers to use the CMS and makes the 
distribution of the CMS harder. If you know something else that matches 
my goals better I would really like to know it!


For me it seems obvious to go that route but I'm certainly biased :-). 
This is why your opinion is very important to me!


If you would like to know more about this initiative you will find more 
(technical) information at the introduction page of the survey here: 
https://de.surveymonkey.com/r/WL7S2PJ
Of course if you don't have the time you don't need to fill the 
questionnaire and you can just read the first page.


Any feedback is much appreciated!

Thanks,

Sandro

[jira] [Resolved] (SLING-5440) DistributionAgentJobConsumer should only fetch the entry

[Tommaso Teofili (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili resolved SLING-5440.

Resolution: Fixed

fixed in r1725533

> DistributionAgentJobConsumer should only fetch the entry
> 
>
> Key: SLING-5440
> URL: https://issues.apache.org/jira/browse/SLING-5440
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
>Priority: Trivial
> Fix For: Content Distribution Core 0.1.14
>
>
> {{DistributionAgentJobConsumer}} fetches both {{DistributionQueueEntry}} and 
> the name of the queue to process from the Sling {{Job}} while only getting 
> the first one is enough as it contains information about the 
> {{DistributionQueueItemStatus}} which also contains the queue name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Worthwhile to create a Sling CMS?

[Ondrej Florian]

Hi Sandro,

Having yet another CMS for 'normal' people like Wix may not be worthwhile.
HOWEVER, going into verticals may be much more interesting.

I personally think the Sling could be great data integration platform.
- imagine modeling SAP or SF data as resources...
- being able to 'mix' those resources into a web pages or reports
- build forms / workflows 

...this also takes you very close to document/knowledge management :-)


Ondrej


On 19/01/2016 14:46, "Sandro Boehme"  wrote:

>Am 19.01.16 um 14:35 schrieb Bertrand Delacretaz:
>> Hi Sandro,
>>
>> On Tue, Jan 19, 2016 at 2:25 PM, Sandro Boehme  wrote:
>>> ...It would help me a big deal if some of you could tell me if they would 
>>> use
>>> this kind of CMS or if the know people who would use it as that validates
>>> (or invalidates) my effort!..
>>
>> I don't need to host a CMS myself these days, so wouldn't use that,
>> but I think a Sling-based CMS would be a great showcase of what Sling
>> can do.
>>
>> -Bertrand
>>
>
>Thanks for your feedback Bertrand! Would you use it and maybe develop 
>components for it if it would be available immediately as a service in 
>the web (e.g. like Wix)? What CMS would you personally use instead? Or 
>what other superior offering is there in your opinion?
>
>Best,
>
>Sandro

Re: Worthwhile to create a Sling CMS?

[Peter Hunsberger]

We use a sorta open source CMS called dotCMS.  Rather obscure, but meets
many of our needs, among which is scaling to support 400 authors and
somewhere over 900 web sites.  As we scale to more users we'd like to start
to decompose that into distributed components:

- authoring
- indexing (Elastic Seach in our case)
- publishing
- caching (Redis in our case)
- content distribution
- workflow management
- authorization, authentication

Basically, having each function run in Docker containers that can be
instantiated as needed.  Our needs are likely way different than what
you're aiming at, but to the extent you can meet them you may end up with a
pretty flexible solution?

On Tuesday, January 19, 2016, Sandro Boehme  wrote:

> Hello,
>
> I personally think there is a market and demand for a small Sling CMS that
> is a website builder which assembles frontend components from an open
> marketplace.
>
> It would help me a big deal if some of you could tell me if they would use
> this kind of CMS or if the know people who would use it as that validates
> (or invalidates) my effort!
>
> It should be as simple and straightforward as a typical website builder
> for composing a page from the frontend components. At the same time the
> barrier to develop these components should be as low as possible and
> developers should be able to sell components to allow a thriving
> marketplace for users to choose components from.
>
> When researching to see if there is something comparable I didn't found
> anything. The closest were Wix, LightCMS, Hippo (marketplace planned),
> Liferay and Nuxeo. But they all have an enterprise edition which raises the
> barrier for many users and developers to use the CMS and makes the
> distribution of the CMS harder. If you know something else that matches my
> goals better I would really like to know it!
>
> For me it seems obvious to go that route but I'm certainly biased :-).
> This is why your opinion is very important to me!
>
> If you would like to know more about this initiative you will find more
> (technical) information at the introduction page of the survey here:
> https://de.surveymonkey.com/r/WL7S2PJ
> Of course if you don't have the time you don't need to fill the
> questionnaire and you can just read the first page.
>
> Any feedback is much appreciated!
>
> Thanks,
>
> Sandro
>


-- 
Peter Hunsberger

[jira] [Created] (SLING-5440) DistributionAgentJobConsumer should only fetch the entry

[Tommaso Teofili (JIRA)]

Tommaso Teofili created SLING-5440:
--

 Summary: DistributionAgentJobConsumer should only fetch the entry
 Key: SLING-5440
 URL: https://issues.apache.org/jira/browse/SLING-5440
 Project: Sling
  Issue Type: Improvement
  Components: Distribution
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
Priority: Trivial
 Fix For: Content Distribution Core 0.1.14


{{DistributionAgentJobConsumer}} fetches both {{DistributionQueueEntry}} and 
the name of the queue to process from the Sling {{Job}} while only getting the 
first one is enough as it contains information about the 
{{DistributionQueueItemStatus}} which also contains the queue name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Worthwhile to create a Sling CMS?

[Sandro Boehme]

Hi Bertrand,

Am 19.01.16 um 15:16 schrieb Bertrand Delacretaz:

... but my personal needs in terms of CMS are extremely
limited these days. When my friends look for websites/CMS I usually
steer them to wordpress.com to be able to get out of the way as soon

:-D yeah I understand.


as possible. And I use that as well for my own blog, for historical
reasons and with no need for something better at the moment.
I agree and used Wordpress for the web shop of my wife (wingsuit.de) as 
well.
And then there are were cases where I would like to have small changes 
or update things. But with Wordpress being developed in PHP it doesn't 
really motivate me to do that let alone having fun doing it. Also for 
experimental blogs or business ideas I would love to have a very helpful 
CMS written in Java so I can have a more individual result.




So my use cases are atypical, I'm not a good customer for such a
thing. But as I said, very interested in having concrete examples of
how to use Sling.
Yeah, if it turns out, that the Sitebuilder has not enough value for 
users or developers to use, I'm happy to provide it as a showcase.


Thanks a lot for your feedback!

Sandro



-Bertrand

Re: Worthwhile to create a Sling CMS?

[Bertrand Delacretaz]

On Tue, Jan 19, 2016 at 4:20 PM, Peter Hunsberger
 wrote:
> ...Basically, having each function run in Docker containers that can be
> instantiated as needed.  Our needs are likely way different than what
> you're aiming at, but to the extent you can meet them you may end up with a
> pretty flexible solution?...

One of my way-too-far-on-this-todo-list-ideas is to try and run
multiple specialized Sling instances along the lines that you mention,
collaborating via a (JMS or other) message bus. With the provisioning
model and a crankstart-style launcher it's easy to create specialized
Sling instances, and async servlets should allow for sharing the load
via a message bus. Ok, there's a bit of "in theory" in all that ;-)

I won't have much time to work on this in the near future but if you
guys are game for that I'd be happy to collaborate on the design and
testing of such a thing.

-Bertrand

[jira] [Commented] (SLING-5078) Missing indexes on MongoDBResourceProvider

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106904#comment-15106904
 ] 

Stefan Seifert commented on SLING-5078:
---

Completed: At revision: 1725553  

some further fixes that prevented the integration tests from succeeding

> Missing indexes on MongoDBResourceProvider
> --
>
> Key: SLING-5078
> URL: https://issues.apache.org/jira/browse/SLING-5078
> Project: Sling
>  Issue Type: Improvement
>  Components: NoSQL
>Affects Versions: NoSQL MongoDB Resource Provider 1.0.0
>Reporter: Norberto Leite
>Assignee: Stefan Seifert
> Fix For: NoSQL MongoDB Resource Provider 1.0.2
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> MongoDB supports secondary indexes but those are missing from the existing 
> implementation. 
> Not only for performance but also for uniqueness guarantee we should have the 
> following indexes: 
> *_path* - unique 
> *_parent* - unique 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Worthwhile to create a Sling CMS?

[Sandro Boehme]

Am 19.01.16 um 16:20 schrieb Peter Hunsberger:

We use a sorta open source CMS called dotCMS.  Rather obscure, but meets
many of our needs, among which is scaling to support 400 authors and
somewhere over 900 web sites.  As we scale to more users we'd like to start
to decompose that into distributed components:

- authoring
- indexing (Elastic Seach in our case)
- publishing
- caching (Redis in our case)
- content distribution
- workflow management
- authorization, authentication

Basically, having each function run in Docker containers that can be
instantiated as needed.  Our needs are likely way different than what
you're aiming at, but to the extent you can meet them you may end up with a
pretty flexible solution?
Yes, I'm not aiming at distributed components and more for small to 
medium websites. There is no separated authoring and publishing instance 
for example. But I can imagine that this can be done using Slings 
discovery API later on.


Best,

Sandro

[jira] [Assigned] (SLING-5437) The NoSQL providers should throw LoginException if the connection to the NoSQL database can't be established

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert reassigned SLING-5437:
-

Assignee: Stefan Seifert  (was: Robert Munteanu)

yes, this makes sense. we'll have to update the package version. we then should 
update the bundle version of the generic bundle as well, at least to 1.1 or to 
2.0.

i will commit your patch and add support for couchbase as well.

> The NoSQL providers should throw LoginException if the connection to the 
> NoSQL database can't be established
> 
>
> Key: SLING-5437
> URL: https://issues.apache.org/jira/browse/SLING-5437
> Project: Sling
>  Issue Type: New Feature
>  Components: NoSQL
>Affects Versions: NoSQL Generic Resource Provider 1.0.0, NoSQL Couchbase 
> Resource Provider 1.0.0, NoSQL MongoDB Resource Provider 1.0.0
>Reporter: Robert Munteanu
>Assignee: Stefan Seifert
> Fix For: NoSQL Generic Resource Provider 1.0.2, NoSQL Couchbase 
> Client 1.0.2, NoSQL MongoDB Resource Provider 1.0.2
>
> Attachments: 
> 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch
>
>
> While trying to find a proper test for SLING-5217, I noticed that the NoSQL 
> providers don't check the connection when the ResourceProvider is 
> instantiated. Therefore the ResourceProvider is always considered valid and 
> when access is attempted exceptions are thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Worthwhile to create a Sling CMS?

[Peter Hunsberger]

That sounds like the way we'd want to head.  We're not likely to try and
help build this on Sling unless our current CMS proves unable to do it.
That could take many months to determine but is one of the things we're
looking at this year.

On Tuesday, January 19, 2016, Bertrand Delacretaz 
wrote:

> On Tue, Jan 19, 2016 at 4:20 PM, Peter Hunsberger
> > wrote:
> > ...Basically, having each function run in Docker containers that can be
> > instantiated as needed.  Our needs are likely way different than what
> > you're aiming at, but to the extent you can meet them you may end up
> with a
> > pretty flexible solution?...
>
> One of my way-too-far-on-this-todo-list-ideas is to try and run
> multiple specialized Sling instances along the lines that you mention,
> collaborating via a (JMS or other) message bus. With the provisioning
> model and a crankstart-style launcher it's easy to create specialized
> Sling instances, and async servlets should allow for sharing the load
> via a message bus. Ok, there's a bit of "in theory" in all that ;-)
>
> I won't have much time to work on this in the near future but if you
> guys are game for that I'd be happy to collaborate on the design and
> testing of such a thing.
>
> -Bertrand
>


-- 
Peter Hunsberger

Re: Worthwhile to create a Sling CMS?

[Ruben Reusser]

for what it's worth, it would be really nice to have an inline editing 
experience, maybe like


https://slate.adobe.com/welcome/

Ruben

On 1/19/2016 5:25 AM, Sandro Boehme wrote:

Hello,

I personally think there is a market and demand for a small Sling CMS 
that is a website builder which assembles frontend components from an 
open marketplace.


It would help me a big deal if some of you could tell me if they would 
use this kind of CMS or if the know people who would use it as that 
validates (or invalidates) my effort!


It should be as simple and straightforward as a typical website 
builder for composing a page from the frontend components. At the same 
time the barrier to develop these components should be as low as 
possible and developers should be able to sell components to allow a 
thriving marketplace for users to choose components from.


When researching to see if there is something comparable I didn't 
found anything. The closest were Wix, LightCMS, Hippo (marketplace 
planned), Liferay and Nuxeo. But they all have an enterprise edition 
which raises the barrier for many users and developers to use the CMS 
and makes the distribution of the CMS harder. If you know something 
else that matches my goals better I would really like to know it!


For me it seems obvious to go that route but I'm certainly biased :-). 
This is why your opinion is very important to me!


If you would like to know more about this initiative you will find 
more (technical) information at the introduction page of the survey 
here: https://de.surveymonkey.com/r/WL7S2PJ
Of course if you don't have the time you don't need to fill the 
questionnaire and you can just read the first page.


Any feedback is much appreciated!

Thanks,

Sandro