Re: [VOTE] Initial Release of Apache Sling Resource Filter version 1.0.0

[Ioan Eugen Stan]

+1 non binding.

Eugen Stan 
Netdava International

  Mesaj original  
De la: dk...@apache.org
Trimis: 4 septembrie 2018 19:17
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: Re: [VOTE] Initial Release of Apache Sling Resource Filter version 
1.0.0

+1

On Tue, Sep 4, 2018 at 12:14 PM Jason E Bailey  wrote:

> Hi,
>
> Welcome to a very special 12th attempt at releasing a bundle vote.
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12343798
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1955/
>
> You can use this UNIX script to download the release and verify the
> signatures:
>
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
>
> Usage:
> sh check_staged_release.sh 1955 /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.
>
> - Jason
>
> - Jason
>

Re: Markdown resource provider

[Ioan Eugen Stan]

Hi,

Nice work Robert.

@Jason: I do believe there is value in yaml frontmatter. A lot of existing 
tools support markdown + frontmatter and people using them are familiar with 
that. Adding something Sling specific is going to make interoerability harder. 
It is going to be non portable as well. 

I'm in favor of using front matter. It will help port markdown apps to sling 
and promote interoperability between such apps.

Regards,

Eugen Stan 
Netdava International

  Mesaj original  
De la: jason.bai...@24601.org
Trimis: 28 iulie 2018 20:28
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: Re: Markdown resource provider

I believe there's a difference between what the two end goals are. There is a 
the rendering of a Markdown resource into HTML and then there is using a 
Markdown file to generate a resource.

A couple of thoughts on this. 
# For a Markdown Resource providing attributes, I don't see a reason to use 
YAML for this. Markdown support integrated HTML and HTML supports custom tags.  
You could  create some thing along the lines of  this wouldn't be displayed when viewing a 
rendered version of the file but be accessible when parsing.

#  We have a module for taking different file types and creating a Resource 
Object out of them, that's the ContentParser. If the goal was to import the md 
file into an existing resource we'd use the ContentLoader. If we wanted the 
ability to read and write the file then I see a ResourceProvider and since we 
have a FSResourceProvider I still think it makes sense to allow that to be 
expandable. 



--
Jason

On Fri, Jul 27, 2018, at 10:31 AM, Carsten Ziegeler wrote:
>  
> 
> 
> > Daniel Klco wrote
> >> My first thought after reading the last paragraph was - Wouldn't it be
> >> cool if the FsResourceProvider was extensible so that specific files could
> >> be rendered in a specific manner, then you could add a MarkDown Handler and
> >> it would make it easier for other people to add custom handlers or to
> >> extend existing one for specific requirements.
> >>
> > 
> > Agreed! This mechanism could be useful for XML or JSON files as well.
> > Imagine if one could register an XSLT handler and just have Sling serve the
> > rendered HTML for a dump of XML files.
> > 
> 
> That's why I mentioned the resource decorator approach - it allows you
> to do this, and then you're even independent of the resource provider
> serving the resource.
> The decorator approach might not be the most obvious one, but I think it
> does the trick and doesn't require us to add another overlapping concept.
> 
> Regards
> Carsten
> -- 
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

Re: [VOTE] Release Apache Sling App CMS version 0.9.0 and Apache Sling File Optimization 0.9.0

[Ioan Eugen Stan]

+1 (non binding)

Eugen Stan 
Netdava International

  Mesaj original  
De la: jason.bai...@sas.com
Trimis: 27 iulie 2018 17:59
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: RE: [VOTE] Release Apache Sling App CMS version 0.9.0 and Apache Sling 
File Optimization 0.9.0

+1 (non binding)

-Original Message-
From: Daniel Klco [mailto:dk...@apache.org] 
Sent: Thursday, July 26, 2018 10:11 PM
To: dev@sling.apache.org
Subject: [VOTE] Release Apache Sling App CMS version 0.9.0 and Apache Sling 
File Optimization 0.9.0

EXTERNAL

This release is for a reference application built with Apache Sling as 
discussed here:
https://apache.markmail.org/thread/rqaj2vaex5upsf7g

As well as a library for Sling to compress & optimize files stored in the Sling 
repository.

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

You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1925 /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.

Re: Sling Karaf PR's and aggregated repo suggestion

[Ioan Eugen Stan]

Hi,

I just realised why the git repo approach does not work for me and maybe
other developers.

I'm using Intellij Idea and, in contrast with Eclipse, Intellij cannot
open multiple projects into the same window.

I'm not sure how other developers go around this but it makes working on
multiple project a bit of a pain, at least for me.

I have to open a lot of windows and manage them independently. This kind
of breaks my flow. Having an aggregator project that allows me to see
all related projects together will easy this task.

Regards,

[1]
https://intellij-support.jetbrains.com/hc/en-us/community/posts/206326369-How-to-have-multiple-projects-in-same-window-


On 15.06.2018 12:35, Ioan Eugen Stan wrote:
> Hello Oliver,
>
> On 15.06.2018 10:51, Oliver Lietz wrote:
>> On Thursday 14 June 2018 12:30:48 Ioan Eugen Stan wrote:
>>> Hello,
>> Hi,
>>
>>> I've made some PR's for Sling Karaf related projects and I would like to
>>> ask for review/merge. Developing on top of Sling Started project is not
>>> the best experience and since I've learned more about Sling internals I
>>> decided to improve Karaf.
>>>
>>> I would like to share my way of handling karaf related packages for easy
>>> development - it might be useful for other situations.
>>>
>>> The problem that it solves for me is:
>>>
>>> - Sling has a lot of repositories that keep each component in it's own
>>> repo. This is great for modularity and having a different version +
>>> history for that module however I have found it is not the best thing
>>> when you need to iterate fast and have it easy to build related packages.
>>>
>>> My solution is to rely on git submodules and create an aggregator
>>> repository/project that adds and manages the related projects.
>>>
>>> For something like Sling Karaf projects, it fits very nicely. I believe
>>> it might be good for other situations in Sling eco-system.
>>>
>>> I have pushed this setup here [1].
>> our current solution is Google's repo. You can set up your own set of 
>> modules 
>> easily. For Sling Karaf see https://github.com/oliverlietz/sling-karaf-repo
> Thank you for the feedback. I will check git-repo as it seems to be
> another solution to the problem of managing multiple git repositories.
>
> We kind of have the same problem internally but so far we managed with
> sub-modules.
>
>>> Also the PR's are available here [2] [3] and [4] .
>>>
>>> I've seen that there is another PR that needs some TLC by Christian
>>> Schneider. I would like to help out with Karaf maintenance - it seems it
>>> could use some help. I would love to be able to do that as part of Sling
>>> project.
>> Your PRs are rather large and touch different scopes. Please be more focused 
>> and start a discussion on dev first or add issues to JIRA whenever an issue 
>> is 
>> not just a typo or javadoc fix.
> Yes, they where kind of done in a hurry and more to fix my itch. I also
> saw that there is currently no release of sling karaf so I hoped that
> the requirements can be more relaxed until an intial version is pushed.
>
> I will come back over the next weeks with more refined PR's. Regarding
> the configfile issue - I've noticed that files referenced with `config`
> are not packaged with karaf custom distribution - and not available
> offline - so I have changed to configfile. After reading about the
> issues in [1] I think a better (slower) approach is to adress this with
> Karaf and file a bug/issue there.
>
>
> Thanks,
>
> [1]
> https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=15948530#comment-15948530
>> Thanks,
>> O.
>>
>>> Thanks,
>>>
>>> Eugen
>>>
>>>
>>> [1] https://github.com/netdava/sling-org-apache-sling-karaf
>>>
>>> [2] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/2
>>>
>>> [3]
>>> https://github.com/apache/sling-org-apache-sling-karaf-distribution/pull/1
>>>
>>> [4] https://github.com/apache/sling-org-apache-sling-karaf-configs/pull/1
>>>
>>> [5] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/1
>




signature.asc
Description: OpenPGP digital signature

[jira] [Commented] (SLING-7437) Support Jackrabbit 2.16 in org.apache.sling.jcr.registration

[Ioan Eugen Stan (JIRA)]

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

Ioan Eugen Stan commented on SLING-7437:


Hi,

I'm using the latest sling-karaf projects with jackrabbit 2.16.2 and I see the 
following components in my web console:
{noformat}
Bundle  org.apache.sling.jcr.registration (143)
Implementation Class
org.apache.sling.jcr.registration.impl.RmiRegistrationSupport
Default State   enabled
Activation  immediate
Configuration Policyrequire
Services
PID org.apache.sling.jcr.jackrabbit.server.RmiRegistrationSupport
Reference Log   Service Name: org.osgi.service.log.LogService
Cardinality: 0..1
Policy: dynamic
Policy Option: reluctant
Reference RepositoryService Name: javax.jcr.Repository
Cardinality: 0..n
Policy: dynamic
Policy Option: reluctant
Properties  service.description = RMI based Repository Registration
service.vendor = The Apache Software Foundation{noformat}
and
{noformat}
Bundle  org.apache.sling.jcr.registration (143)
Implementation Class
org.apache.sling.jcr.registration.impl.JndiRegistrationSupport
Default State   enabled
Activation  immediate
Configuration Policyrequire
Services
PID org.apache.sling.jcr.jackrabbit.server.JndiRegistrationSupport
Reference Log   Service Name: org.osgi.service.log.LogService
Cardinality: 0..1
Policy: dynamic
Policy Option: reluctant
Reference RepositoryService Name: javax.jcr.Repository
Cardinality: 0..n
Policy: dynamic
Policy Option: reluctant
Properties  service.description = JNDI Repository Registration
service.vendor = The Apache Software Foundation{noformat}
I guess the services are up and things work so maybe this can be closed as well.

 

 
 
...

> Support Jackrabbit 2.16 in org.apache.sling.jcr.registration
> 
>
> Key: SLING-7437
> URL: https://issues.apache.org/jira/browse/SLING-7437
> Project: Sling
>  Issue Type: Sub-task
>  Components: JCR
>Affects Versions: JCR Registration 1.0.4
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> JCR Registration is not compatible to Oak 1.8. We need to migrate it.
> I will provide a PR.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Sling Karaf PR's and aggregated repo suggestion

[Ioan Eugen Stan]

Hello Oliver,

On 15.06.2018 10:51, Oliver Lietz wrote:
> On Thursday 14 June 2018 12:30:48 Ioan Eugen Stan wrote:
>> Hello,
> Hi,
>
>> I've made some PR's for Sling Karaf related projects and I would like to
>> ask for review/merge. Developing on top of Sling Started project is not
>> the best experience and since I've learned more about Sling internals I
>> decided to improve Karaf.
>>
>> I would like to share my way of handling karaf related packages for easy
>> development - it might be useful for other situations.
>>
>> The problem that it solves for me is:
>>
>> - Sling has a lot of repositories that keep each component in it's own
>> repo. This is great for modularity and having a different version +
>> history for that module however I have found it is not the best thing
>> when you need to iterate fast and have it easy to build related packages.
>>
>> My solution is to rely on git submodules and create an aggregator
>> repository/project that adds and manages the related projects.
>>
>> For something like Sling Karaf projects, it fits very nicely. I believe
>> it might be good for other situations in Sling eco-system.
>>
>> I have pushed this setup here [1].
> our current solution is Google's repo. You can set up your own set of modules 
> easily. For Sling Karaf see https://github.com/oliverlietz/sling-karaf-repo

Thank you for the feedback. I will check git-repo as it seems to be
another solution to the problem of managing multiple git repositories.

We kind of have the same problem internally but so far we managed with
sub-modules.

>> Also the PR's are available here [2] [3] and [4] .
>>
>> I've seen that there is another PR that needs some TLC by Christian
>> Schneider. I would like to help out with Karaf maintenance - it seems it
>> could use some help. I would love to be able to do that as part of Sling
>> project.
> Your PRs are rather large and touch different scopes. Please be more focused 
> and start a discussion on dev first or add issues to JIRA whenever an issue 
> is 
> not just a typo or javadoc fix.
Yes, they where kind of done in a hurry and more to fix my itch. I also
saw that there is currently no release of sling karaf so I hoped that
the requirements can be more relaxed until an intial version is pushed.

I will come back over the next weeks with more refined PR's. Regarding
the configfile issue - I've noticed that files referenced with `config`
are not packaged with karaf custom distribution - and not available
offline - so I have changed to configfile. After reading about the
issues in [1] I think a better (slower) approach is to adress this with
Karaf and file a bug/issue there.


Thanks,

[1]
https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=15948530#comment-15948530
>
> Thanks,
> O.
>
>> Thanks,
>>
>> Eugen
>>
>>
>> [1] https://github.com/netdava/sling-org-apache-sling-karaf
>>
>> [2] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/2
>>
>> [3]
>> https://github.com/apache/sling-org-apache-sling-karaf-distribution/pull/1
>>
>> [4] https://github.com/apache/sling-org-apache-sling-karaf-configs/pull/1
>>
>> [5] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/1




signature.asc
Description: OpenPGP digital signature

Re: Sling Karaf PR's and aggregated repo suggestion

[Ioan Eugen Stan]

Hi,

On 14.06.2018 13:14, Robert Munteanu wrote:
> Hi Eugen,
>
> On Thu, 2018-06-14 at 12:30 +0300, Ioan Eugen Stan wrote:
>> My solution is to rely on git submodules and create an aggregator
>> repository/project that adds and manages the related projects.
>
> Have you seen
>
>   https://github.com/apache/sling-aggregator
Yes I saw it. It gives me the full sea of sling modules. It's a bit
easier for me to work on just Karaf with my approach. Once I get
accustomed more with Sling I can try to work with the other tools as well.

Any news regarding the PR's :)?

> ?
>
> Robert




signature.asc
Description: OpenPGP digital signature

Sling Karaf PR's and aggregated repo suggestion

[Ioan Eugen Stan]

Hello,

I've made some PR's for Sling Karaf related projects and I would like to
ask for review/merge. Developing on top of Sling Started project is not
the best experience and since I've learned more about Sling internals I
decided to improve Karaf.

I would like to share my way of handling karaf related packages for easy
development - it might be useful for other situations.

The problem that it solves for me is:

- Sling has a lot of repositories that keep each component in it's own
repo. This is great for modularity and having a different version +
history for that module however I have found it is not the best thing
when you need to iterate fast and have it easy to build related packages.

My solution is to rely on git submodules and create an aggregator
repository/project that adds and manages the related projects.

For something like Sling Karaf projects, it fits very nicely. I believe
it might be good for other situations in Sling eco-system.

I have pushed this setup here [1].

Also the PR's are available here [2] [3] and [4] .

I've seen that there is another PR that needs some TLC by Christian
Schneider. I would like to help out with Karaf maintenance - it seems it
could use some help. I would love to be able to do that as part of Sling
project.


Thanks,

Eugen


[1] https://github.com/netdava/sling-org-apache-sling-karaf

[2] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/2

[3]
https://github.com/apache/sling-org-apache-sling-karaf-distribution/pull/1

[4] https://github.com/apache/sling-org-apache-sling-karaf-configs/pull/1

[5] https://github.com/apache/sling-org-apache-sling-karaf-features/pull/1




signature.asc
Description: OpenPGP digital signature

Re: possible bug when loading content with many files from bundle

[Ioan Eugen Stan]

Hello Bertrand,

I've added https://issues.apache.org/jira/browse/SLING-7726 to track
this. Maybe I will have some time and fix it as well.


Regards,

Eugen


On 04.06.2018 13:20, Bertrand Delacretaz wrote:
> Hi,
>
> On Sat, May 26, 2018 at 12:20 PM, Ioan Eugen Stan  wrote:
>> ...I have created a branch to reproduce the bug [1]...
> Best is to track this in jira so it doesn't fall through the cracks.
> Let us know if you lack jira access rights.
>
> -Bertrand




signature.asc
Description: OpenPGP digital signature

[jira] [Created] (SLING-7726) Sling content loader fails to load big -1mb+ /many files

[Ioan Eugen Stan (JIRA)]

Ioan Eugen Stan created SLING-7726:
--

 Summary: Sling content loader fails to load big -1mb+ /many files
 Key: SLING-7726
 URL: https://issues.apache.org/jira/browse/SLING-7726
 Project: Sling
  Issue Type: Bug
Reporter: Ioan Eugen Stan


I've been playing around with sling, migrating our setup and content and
 I think I have discovered a bug when loading content into sling.

I'm using a sling-starter project and sling-started-content. I've
 updated started-contnet to include some frontend dependencies downloaded
 with npm.

The content jar size is 9mb and contains an extra ~ 3300 files and 330
 folders.

When I start sling-starter I get 403 page with the bellow error.

I believe there is a time-out loading the content or the content takes
 more than 1-5 minutes to load so that is why things break.

At a minimum, I do belive the logging can be improved to know if the
 content is loading or not or maybe I just need to switch to debug.

I have created a branch to reproduce the bug [1]. Use the following steps:

—

git clone
 [https://github.com/netdava/sling-org-apache-sling-starter-content.git]

cd sling-org-apache-sling-starter-content && git co 
 content-loading-bug-improvement

mvn clean install

Once the content is built, go to a sling-starter project and in
 sling.txt update version like this
 "org.apache.sling/org.apache.sling.starter.content/1.0.1-loadbug"

Forbidden (403)

The requested URL / resulted in an error in
 org.apache.sling.servlets.get.DefaultGetServlet.
 Request Progress:

0 TIMER_START

{Request Processing}

6 COMMENT timer_end format is

{,}


 20 LOG Method=GET, PathInfo=null
 39 TIMER_START

{handleSecurity}

2731 TIMER_END

{2688,handleSecurity}

authenticator
 org.apache.sling.auth.core.impl.SlingAuthenticator@54b78198 returns true
 6147 TIMER_START

{ResourceResolution}

7266 TIMER_END

{1108,ResourceResolution}

URI=/ resolves to
 Resource=JcrNodeResource, type=sling:OrderedFolder, superType=null,
 path=/content
 7297 LOG Resource Path Info: SlingRequestPathInfo: path='/content',
 selectorString='null', extension='null', suffix='/'
 7299 TIMER_START

{ServletResolution}

7318 TIMER_START

{resolveServlet(/content)}

7468 TIMER_END

{146,resolveServlet(/content)}

Using servlet
 org.apache.sling.servlets.get.DefaultGetServlet
 7481 TIMER_END

{180,ServletResolution}

URI=/ handled by
 Servlet=org.apache.sling.servlets.get.DefaultGetServlet
 7510 LOG Applying Requestfilters
 7522 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
 7534 LOG Calling filter:
 org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
 7541 LOG Applying Componentfilters
 7582 TIMER_START

{org.apache.sling.servlets.get.DefaultGetServlet#0}

7601 LOG Using
 org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to
 render for extension=null
 7687 LOG Applying Error filters
 7699 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
 7713 TIMER_START

{handleError:status=403}

8362 TIMER_END

{646,handleError:status=403}

Using handler
 org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
 8916 TIMER_END

{8914,Request Processing}

Dumping
 SlingRequestProgressTracker Entries

[1]
 
[https://github.com/netdava/sling-org-apache-sling-starter-content/tree/content-loading-bug-improvement]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [Dev][GSoC] Using a cache to store a string value

[Ioan Eugen Stan]

Hi,

I think you should store it in memory. Use a hashmap or something. 

Make it work and then optimize. The check should be very fast so don't worry 
about it. 

In case you do need to store it, use jcr. 

Always delay optimisations. Caching is an optimization.


Eugen Stan 
Netdava International

  Mesaj original  
De la: hasinidila...@gmail.com
Trimis: 6 iunie 2018 21:08
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: [Dev][GSoC] Using a cache to store a string value

Hi all,

I am implementing OpenID Connect protocol for Sling. First, Sling is
sending an authorization request to Google( OpenID Connect Provider - OP).
This request contains an attribute call state. State is a string object.

If the authorization is successful Google will send a response with an
authorization code. This response contains the same attribute state. This
state value and the request's state value must be same. Then only we can
validate the response.

To implement the this, I need to store the first state value somewhere. The
authorization code is valid for like 5 minutes. So the state value is only
needed to be stored for like 5 minutes. Therefore I thought to use a simple
cache for this purpose.

I would like to get your opinions for this.

Thank You.
-- 
*Hasini Witharana*
Undergraduate | Department of Computer Science and Engineering
University of Moratuwa
Linkedin 

Re: [Dev] Sling Bundle Installation

[Ioan Eugen Stan]

Hi,

I would also add that you can check bundle status in webconsole: 
http://localhost:8080/system/console/bundles .

There you can inspect visually if there are any issues with your bundle
inside your deployment.

They appear in red: missing packages, etc.

Of course the same for services, if the bundle is activated:
http://localhost:8080/system/console/services .

Regards,


On 30.05.2018 16:25, Robert Munteanu wrote:
>
> On Wed, 2018-05-30 at 18:16 +0530, Hasini Witharana wrote:
>> Hi Robert,
>>
>> Thank you for the help. I followed your steps and, now the endpoint
>> is
>> working.
> That's great to hear! Looking forward to the updated PR :-)
>
> Thanks,
>
> Robert




signature.asc
Description: OpenPGP digital signature

Re: moving streams from whiteboard

[Ioan Eugen Stan]

Hi Jason,

Nice to see new language features being used. I think they should be
added to the core of Sling. I don't know what is the baseline Java
version required by Sling but the older JVM's are getting fewer and
fewer. Oracle has helped with that by changing the policy regarding
public bug-fixes.

On that note, I would love to see a JCR API update but I imagine this
will be much more difficult to do.

Regards,

Eugen

[1] http://www.oracle.com/technetwork/java/javase/eol-135779.html

On 29.05.2018 18:47, Jason E Bailey wrote:
> First, I realize that Streams isn't the best package name. It's based on the 
> fact that the functionality is all around supporting java 8 streams.
>
> It has three distinct areas of functionality that can intermingle
>
> 1. ResourceStream - Takes a resource and provides a stream of it's 
> descendants.  Additionally provides the ability to set a range, limit, and 
> accepts a Predicate to filter resources as well as a Predicate to select 
> which branches to traverse on.
>
> 2. ResourceFilter - Provides a scripting feature to create a 
> Predicate that can be used to filter resources in any stream 
> regardless of how the stream is created
>
> 3.  A series of classes that allows you to build a Predicate  using 
> a fluent java based API.
>
> These three can exist separately from each other.
>
> @PMC folk, what do I need to get these set up as it's own repo?
>
> - Jason




signature.asc
Description: OpenPGP digital signature

Re: [DISCUSSION] Sling CMS Repo(s)

[Ioan Eugen Stan]

Hello Daniel,

On 26.05.2018 18:12, Daniel Klco wrote:
> Eugen,
>
> Thanks for the interest! Mind if i ask you a couple follow up questions?
I'm always open for discussions :).
>
>
>- Are you looking to brand the CMS application or the website /
>application which gets produced by the CMS?
My immediate focus is the website for end users. Looking at the other
popular CMS's out there (Wordpress, Django), they can customize the
admin theme but I haven't seen it done a lot in practice. I think a very
big percentage of people don't care that much/can afford. It would be
great to be able to provide a unified experience between the two.
Wordpress themes are very popular and I think they have hit the sweet
spot in terms of flexibility and how easy it is to do it.

https://codex.wordpress.org/Theme_Development

>- If you are looking to brand the CMS is this more of a put an icon at
>the top and change colors or would you want to completely change the look
>and feel?
As I mentioned above I think being able to put an icon and supply some
custom CSS is fine. For example I try to push for CSS frameworks because
of the benefits in maintenance, developer and component availability. So
I would like to be able to use something like bootstrap 4 or some other
popular framework to style website applications.
Personally I would like to customize the current CSS for the CMS as
well. I'll see if I can convince a friend to help out. What would be the
steps in that case?
>- The custom components, are these customizations to the CMS or to the
>websites?
When I talk about custom components I'm thinking more in terms of custom
content types that a developer can code (or a plugin can create) and
then Author/Editor can create and choose where to display them inside
the website.

In wordpress this functionality is called "custom post types" and there
are a lot of plugins like
https://wordpress.org/plugins/custom-post-type-ui/ that can allow people
to manage them.  In JCR I think this could be thought of as custom node
types but from my knowledge managing the life cycle of node types is not
that straight forward in JCR - I'm thinking of migrations in a running
system - adding/removing properties, changing structure. In SQL you have
tools like flyway for that https://flywaydb.org/
>
> BTW, if you want to see what's possible with the current version, I'm using
> it to power my personal website:
>
> https://www.danklco.com
Thanks. It looks great. I have seen some articles there that I think
will help me when I get started with the CMS :).
> Here's the code for that:
>
> https://github.com/klcodanr/danklco.com-site/tree/sling-cms
Sweet !!
> What I especially like is the "list" concept. Basically, you can pretty
> easily create a list of items and style it by extending this component:
>
> https://github.com/apache/sling-whiteboard/tree/master/
> cms/reference/src/main/resources/jcr_root/apps/reference/components/general/
> list
>
> For example, to create my tag pages:
>
> https://www.danklco.com/tags.html/etc/taxonomy/adobe/adobe-
> experience-manager
>
> I created a taglist component which just overrides the item output to style
> the tag items the way I wanted:
> https://github.com/klcodanr/danklco.com-site/tree/sling-
> cms/src/main/resources/jcr_root/apps/danklco-com/components/lists/taglist
>
> And then created a page with that taglist component on it.
That sounds awesome. In truth I need more time to understand and to
appreciate the full value of that. I'm still unfamiliar with a lot of
practices and concepts around JCR and Sling.

I do have a question: Why JSP? Could those be done using the other
scripting/templating languages ? I'm asking more out of curiosity - I
have no JSP experience and I don't plan to learn to write very soon :).

Thank you for the time to answer and for working on Sling CMS and making
it available to us. 
> -Dan
>
> On Sat, May 26, 2018 at 6:26 AM, Ioan Eugen Stan <ieu...@netdava.com> wrote:
>
>> Hello Daniel,
>>
>> Awesome news. I think it's a good start. Once I get to the point where
>> we can use the CMS and will need to customize it I can provide more
>> feedback.
>>
>> Some of my initial concerns will be around:
>>
>> a. provide custom CSS/theme - based on bootstrap 4 most likely. This is
>> branding, uniform look and feel mostly
>>
>> b. provide custom components - later in the project developemnt, once we
>> are familiar with the sling-cms
>>
>> I'm not very familiar with sling-cms internals to know if this is doable
>> right now but I have a feeling (b) is doable.
>>
>>
>> Excited for cms,
>>
>> Eugen
>>
>>
>> On 25.05.2018 17:46, Daniel Klco wrote:
>>> Hey All,
>>

Re: [DISCUSSION] Sling CMS Repo(s)

[Ioan Eugen Stan]

Hello Daniel,

Awesome news. I think it's a good start. Once I get to the point where
we can use the CMS and will need to customize it I can provide more
feedback.

Some of my initial concerns will be around:

a. provide custom CSS/theme - based on bootstrap 4 most likely. This is
branding, uniform look and feel mostly

b. provide custom components - later in the project developemnt, once we
are familiar with the sling-cms

I'm not very familiar with sling-cms internals to know if this is doable
right now but I have a feeling (b) is doable.


Excited for cms,

Eugen


On 25.05.2018 17:46, Daniel Klco wrote:
> Hey All,
>
> I've wrapped up all of the things I wanted to fix before releasing the
> first version of the Sling CMS Sample app.
>
> I'm thinking of creating two repositories:
>
>- sling-org-apache-sling-cms <- the core CMS code
>- sling-org-apache-sling-cms-reference <- the reference application /
>components so this can be versioned separately from the underlying
>application
>
> Does this sound good? Should the names contain sample?
>
> Regards,
> Dan
>




signature.asc
Description: OpenPGP digital signature

possible bug when loading content with many files from bundle

[Ioan Eugen Stan]

Hello,

I've been playing around with sling, migrating our setup and content and
I think I have discovered a bug when loading content into sling.

I'm using a sling-starter project and sling-started-content. I've
updated started-contnet to include some frontend dependencies downloaded
with npm.

The content jar size is 9mb and  contains an extra ~ 3300 files and 330
folders.

When I start sling-starter I get 403 page with the bellow error.

I believe there is a time-out loading the content or the content takes
more than 1-5 minutes to load so that is why things break.

At a minimum, I do belive the logging can be improved to know if the
content is loading or not or maybe I just need to switch to debug.

I have created a branch to reproduce the bug [1]. Use the following steps:

---

git clone
https://github.com/netdava/sling-org-apache-sling-starter-content.git

cd  sling-org-apache-sling-starter-content && git co 
content-loading-bug-improvement

mvn clean install



Once the content is built, go to a sling-starter project and in
sling.txt update version like this
"org.apache.sling/org.apache.sling.starter.content/1.0.1-loadbug"

-

Forbidden (403)

The requested URL / resulted in an error in
org.apache.sling.servlets.get.DefaultGetServlet.
Request Progress:

  0 TIMER_START{Request Processing}
  6 COMMENT timer_end format is {,} 
 20 LOG Method=GET, PathInfo=null
 39 TIMER_START{handleSecurity}
   2731 TIMER_END{2688,handleSecurity} authenticator
org.apache.sling.auth.core.impl.SlingAuthenticator@54b78198 returns true
   6147 TIMER_START{ResourceResolution}
   7266 TIMER_END{1108,ResourceResolution} URI=/ resolves to
Resource=JcrNodeResource, type=sling:OrderedFolder, superType=null,
path=/content
   7297 LOG Resource Path Info: SlingRequestPathInfo: path='/content',
selectorString='null', extension='null', suffix='/'
   7299 TIMER_START{ServletResolution}
   7318 TIMER_START{resolveServlet(/content)}
   7468 TIMER_END{146,resolveServlet(/content)} Using servlet
org.apache.sling.servlets.get.DefaultGetServlet
   7481 TIMER_END{180,ServletResolution} URI=/ handled by
Servlet=org.apache.sling.servlets.get.DefaultGetServlet
   7510 LOG Applying Requestfilters
   7522 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   7534 LOG Calling filter:
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
   7541 LOG Applying Componentfilters
   7582 TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
   7601 LOG Using
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to
render for extension=null
   7687 LOG Applying Error filters
   7699 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   7713 TIMER_START{handleError:status=403}
   8362 TIMER_END{646,handleError:status=403} Using handler
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
   8916 TIMER_END{8914,Request Processing} Dumping
SlingRequestProgressTracker Entries


[1]
https://github.com/netdava/sling-org-apache-sling-starter-content/tree/content-loading-bug-improvement


Regards,

Eugen




signature.asc
Description: OpenPGP digital signature

Re: Sling Hackathon Sept. 13th, 2018 in Berlin

[Ioan Eugen Stan]

Hello,

I also think I will be there. So please put me with 0.5 for now :D.

Excited to meet all of you in September.

/Eugen

On 21.05.2018 11:22, Robert Munteanu wrote:
> On Fri, 2018-05-18 at 13:07 +, Stefan Seifert wrote:
>> if you are interested and want to participate: please send me a
>> private mail or a reply on this list!
> Will be there, +1.
>
> Robert




signature.asc
Description: OpenPGP digital signature

Re: [proposal][scripting console] http API for terminal usage

[Ioan Eugen Stan]

Hi, 

Sounds interesting. Are you talking like building a CLI that can be used for 
scripts and maybe more management operations?

Could you please describe in more details how you see this working? I think it 
would be more easy for people to understand your use case. 

Thanks,

Eugen Stan 
Netdava International

  Mesaj original  
De la: peltier.nico...@gmail.com
Trimis: 14 mai 2018 13:05
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: [proposal][scripting console] http API for terminal usage

Hey,

thought about using terminal rather than felix html page for scripting
(when scripting take one line like for pipes, htis might be useful).

Thoughts?

Nicolas

Re: [proposal][osgi][scripting] redesigned scripts deployment and resolution

[Ioan Eugen Stan]

Thank you for your explanations Karl.

I think having both is a great thing. For once, you can explore using
the traditional, versioneless way. Once you solve the problem fast and
dirty you can move to the more elegant way of vearsioning  the scripts.
So your solution could be an upgrade path for traditional scripts. I
think it is important if developers are informed about their choices here.

Regards,


On 26.04.2018 16:29, Karl Pauls wrote:
> On Thu, Apr 26, 2018 at 12:11 PM, Ioan Eugen Stan <ieu...@netdava.com> wrote:
>> Hello Radu,
>>
>> I've read the project description and I like the direction in which you
>> are going. I believe being able to add constraints to code will make
>> things more clear.
>>
>> I do wish to ask something: I like the idea described in Sling in 15 min
>> [1]. I believe it's a very powerful way of developing pages and working
>> only on layout. Is this something that is going to go away?
> I doubt it :-)
>
>> Will I be forced to push scripts only via a bundle?
> No, for now this is a pure add-on that will not impact anything but
> allow you to push scripts via bundles as well (in which case you get
> the ability to version your scripts and have them have dependencies).
>
>> If that is so, I
>> might suggest a solution where we can add Require/Provide to a JCR node
>> of a special type and that might be deployed as a bundle. I imagine that
>> such a node will mostly nly Require and not Provide a lot of things
>> since it's goal would be to render Pages.
>>
>> I hope I understood correctly the issue and I'm not barking up the wrong
>> tree :).
> I think the point here is that while the current way of having scripts
> in the repository is great for some things, it has drawbacks in some
> other areas (mostly when it comes to deployment and maintainability).
> This is an attempt to marry the two by still allowing you the former
> and providing an optional solution for the latter while maintaining
> full interoperability.
>
> regards,
>
> Karl
>
>> Regards,
>>
>> [1]
>> https://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html
>>
>>
>> On 26.04.2018 12:34, Radu Cotescu wrote:
>>> Hello Sling devs,
>>>
>>> Karl and I have been working for the past weeks on a new scripting 
>>> prototype that we've now pushed to the Whiteboard [1]. The module is an 
>>> add-on that allows developers to deploy scripts through bundles, with the 
>>> following core features:
>>> standalone module that doesn't require any changes in Sling's current APIs
>>> bundles that provide scripts are wired to this add-on and then the add-on 
>>> registers servlets on behalf of the scripting bundles (one servlet / script)
>>> resource types can now be versioned (they're expressed as OSGi capabilities)
>>> resource types can have explicit dependencies to other resource types, and 
>>> everything is controlled by the wiring provided by the OSGi framework
>>> For the full details please check the documentation provided at [1]. We're 
>>> very interested in your opinions about this module, since we’d like to 
>>> integrate it into the next Sling Starter release.
>>>
>>> Thanks,
>>> Radu and Karl
>>>
>>> [1] - 
>>> https://github.com/apache/sling-whiteboard/tree/master/scripting-resolver 
>>> <https://github.com/apache/sling-whiteboard/tree/master/scripting-resolver>
>>
>
>




signature.asc
Description: OpenPGP digital signature

Re: [proposal][osgi][scripting] redesigned scripts deployment and resolution

[Ioan Eugen Stan]

Hello Radu,

I've read the project description and I like the direction in which you
are going. I believe being able to add constraints to code will make
things more clear.

I do wish to ask something: I like the idea described in Sling in 15 min
[1]. I believe it's a very powerful way of developing pages and working
only on layout. Is this something that is going to go away?

Will I be forced to push scripts only via a bundle? If that is so, I
might suggest a solution where we can add Require/Provide to a JCR node
of a special type and that might be deployed as a bundle. I imagine that
such a node will mostly nly Require and not Provide a lot of things
since it's goal would be to render Pages.

I hope I understood correctly the issue and I'm not barking up the wrong
tree :).

Regards,

[1]
https://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html


On 26.04.2018 12:34, Radu Cotescu wrote:
> Hello Sling devs,
>
> Karl and I have been working for the past weeks on a new scripting prototype 
> that we've now pushed to the Whiteboard [1]. The module is an add-on that 
> allows developers to deploy scripts through bundles, with the following core 
> features:
> standalone module that doesn't require any changes in Sling's current APIs
> bundles that provide scripts are wired to this add-on and then the add-on 
> registers servlets on behalf of the scripting bundles (one servlet / script)
> resource types can now be versioned (they're expressed as OSGi capabilities)
> resource types can have explicit dependencies to other resource types, and 
> everything is controlled by the wiring provided by the OSGi framework
> For the full details please check the documentation provided at [1]. We're 
> very interested in your opinions about this module, since we’d like to 
> integrate it into the next Sling Starter release.
>
> Thanks,
> Radu and Karl
>
> [1] - 
> https://github.com/apache/sling-whiteboard/tree/master/scripting-resolver 
> 




signature.asc
Description: OpenPGP digital signature

Re: [GSOC2018] Project Idea : Provide an OpenID Connect Authentication Handler

[Ioan Eugen Stan]

Hello Hasini, Robert,

I'm also going to work in this field - working to integrate Keycloak
OpenId Connect with Sling. I should start on it next month.

I will share more feedback as I am through the process and hope to
collaborate.

Good luck with you project.

@Hasini: I can help with regard to the Oauth / Oidc protocols and
architecture so if you ever find yourself struggling, reach out and I'll
find some time.

/Eugen


On 24.04.2018 12:06, Robert Munteanu wrote:
> Hi Hasini,
>
> On Tue, 2018-04-24 at 00:51 +0530, Hasini Witharana wrote:
>> Hi Robert,
>>
>> I have been selected to the $subject GSoC project. I am really
>> looking
>> forward to work with you.
> Congratulations, this is great news!
>
>> The below [1] is the proposal for the project. There are two
>> approaches for
>> the OIDC implementation.
>>
>>
>>1. Use Apache Oltu OAuth2.0 implementation as a dependency and
>> build
>>OIDC platform on top of it.
>>2. Build OAuth2.0 and OIDC implementations from the scratch
>>
>>
>> Since the time is limited, I think first approach is more
>> suitable.  I
>> would really like to have some advises from you for the initial
>> starting of
>> the project and community bounding.  Thank you very much for giving
>> me this
>> opportunity.
> Absolutely, I agree that option 1 is the way to go. We are not in the
> business of developing and maintaining OAuth implementations :-)
>
> I would suggest that first you get yourself familiar with Sling,
> following the documentation at [2]. For your specific scenario I guess
> that:
>
> 1. Running Sling
> 2. Deploying a new OSGi bundle in Sling
> 3. Updating the initial content from Sling
>
> would be the way to go and would cover 99% of the work that you need to
> do in Sling.
>
> Then it would be good to address the original comments on your proposal
> that I posted at [3] and adjust the plan accordingly.
>
> Other than that, please use dev@sling.apache.org for any queries that
> you might have - it's our main communication channel and all the right
> people are here.
>
> Welcome!
>
> Robert
>
>>
>> [1] -  https://docs.google.com/document/d/1ki_mv_
>> ngtMFsP2cqZkVfZfAYLAYle6M5Srs0WsgHXEs/edit?usp=sharing
>>
> [2]: https://sling.apache.org/documentation/getting-started.html
> [3]: 
> https://lists.apache.org/thread.html/34ed2da7489b285fe3b2e4da6dbe8219c94a7f5353d156fba4538824@%3Cdev.sling.apache.org%3E




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Release Apache Sling JCR Oak Server 1.2.0

[Ioan Eugen Stan]

+1

On 06.03.2018 09:20, Carsten Ziegeler wrote:
> +1
>
>
> Oliver Lietz wrote
>> Hi,
>>
>> we solved 6 issues in this release:
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12342843
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1880/
>>
>> You can use this UNIX script to download the release and verify the 
>> signatures:
>> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
>>
>> Usage:
>> sh check_staged_release.sh 1880 /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.
>>
>> NOTE: Integration tests require Testing PaxExam 2.0.0 (under vote).
>>
>> Regards,
>> O.
>>




signature.asc
Description: OpenPGP digital signature

Re: [DISCUSSION] Make Sling shiny - Basic CMS

[Ioan Eugen Stan]

Hi,

> Yep, indeed. Currently I'm working on building out some reference
> components like search, lists, column controls, text editors, etc.
That would be awesome. We would like to use such components in our setup
and we might help with some development and maintenance along the way.
That would take some time dough.

IMO we should be able to make the artifacts available as part of a
release process.
Is this part of the apache project or a you private project. I'm asking
because I would like to do some work in that direction (release as often
as possible).
>> - is there any relationship between sling-cms and Composum? It seems to
>> me like both projects are heading in a similar direction and a
>> colaboration might be beneficial. Composum provides Composum assests,
>> Composum Pages, etc. That functionality could be reused.
>>
> Not at the moment, I did add in Compsum for the package and node explorer
> capabilities, but I didn't realize Compsum Pages and Assets were so far
> along.
>
Have you had time to check them out? Can Sling CMS use those compnents?
Will they be used instead of internal/custom ones?




signature.asc
Description: OpenPGP digital signature

Re: repoinit just with oak

[Ioan Eugen Stan]

Hello Bertrand,

Thank you for the reply. I'm still working on the details of the
infrastructure.

We will have an instance of Sling and that would help us to run the
Repo-init instructions.

However, the contribution will still be helpful to ease JCR only
integration testing outside OSGI and we have such a use case.

I'll see if I can find some time to work on this and I will definitely
contribute to the changes upstream. Thank you for suggesting that.


Regards,


On 21.02.2018 18:24, Bertrand Delacretaz wrote:
> Hi,
>
> On Wed, Feb 21, 2018 at 2:47 PM, Ioan Eugen Stan <ieu...@netdava.com> wrote:
>> ...I saw that I need to implement
>> |SlingRepositoryInitializer that brings in Sling API, which I shouldn't
>> need
> I think you can bypass that requirement. If you look at the
> RepositoryInitializer.processRepository method [1] the gist is parsing
> the statements and using JcrRepoInitOpsProcessor to process the
> result.
>
> However, as running outside of Sling hasn't been a requirement so far,
> I suppose there might be non-essential dependencies that get in the
> way of doing that, but depending on your environment they might not
> matter, maybe you just won't be able to use certain non-essential
> classes.
>
> The alternative is to extract the pure JCR parts out of the jcr
> repoinit bundle, if you need that I think that would be a useful
> contribution.
>
> You're right that technically the JCR parts of this belong to the Oak
> level, but as it's the Sling community which needed that the modules
> have been created here for convenience.
>
> -Bertrand
>
> [1] 
> https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/master/src/main/java/org/apache/sling/jcr/repoinit/impl/RepositoryInitializer.java




signature.asc
Description: OpenPGP digital signature

Re: Support for Oak 1.8 (SLING-7446)

[Ioan Eugen Stan]

+1, but I'm a new user and don't have older sling code to maintain :D.


On 27.02.2018 13:11, Oliver Lietz wrote:
> hi,
>
> is everyone fine with upgrading to Oak 1.8 and dropping support (in HEAD) for 
> older versions of Oak and Jackrabbit in some modules?
>
> https://issues.apache.org/jira/browse/SLING-7446
>
> Thanks,
> O.
>




signature.asc
Description: OpenPGP digital signature

Re: repoinit just with oak

[Ioan Eugen Stan]

I've sent this by mistake to sling-dev instead of sling-users.

Sorry. I will re-post on Sling users, please ignore the message.


On 21.02.2018 15:47, Ioan Eugen Stan wrote:
> Hello,
>
> I've been looking for a way to initialize an Oak repository and I came
> across repoinit module [1].
>
> However, I'm using Oak outside of OSGI and I don't need all of Sling.
>
> Is that a use case that can be handled easily? If yes, I'll investigate
> and put up some documentation.
>
> Looking at the documentation, it seems to me that in theory it should be
> possible, however I saw that I need to implement
> |SlingRepositoryInitializer that brings in Sling API, which I shouldn't
> need.|
>
> To me repoinit language is similar to how SQL migrations are done and
> IMO that is a responsibility of the content store, not the web app
> especially since the store can be used by more then one micro service.
>
> |The application that uses Oak repo is not a web application and neither
> OSGI, and it will cost us to migrate so that is not an option.
> |
>
>
> Regards,
>
> Eugen
>
>
> [1]
> https://sling.apache.org/documentation/bundles/repository-initialization.html
>
>
>
>




signature.asc
Description: OpenPGP digital signature

repoinit just with oak

[Ioan Eugen Stan]

Hello,

I've been looking for a way to initialize an Oak repository and I came
across repoinit module [1].

However, I'm using Oak outside of OSGI and I don't need all of Sling.

Is that a use case that can be handled easily? If yes, I'll investigate
and put up some documentation.

Looking at the documentation, it seems to me that in theory it should be
possible, however I saw that I need to implement
|SlingRepositoryInitializer that brings in Sling API, which I shouldn't
need.|

To me repoinit language is similar to how SQL migrations are done and
IMO that is a responsibility of the content store, not the web app
especially since the store can be used by more then one micro service.

|The application that uses Oak repo is not a web application and neither
OSGI, and it will cost us to migrate so that is not an option.
|


Regards,

Eugen


[1]
https://sling.apache.org/documentation/bundles/repository-initialization.html






signature.asc
Description: OpenPGP digital signature

Re: [Sling Feature Model] Expanded requirements

[Ioan Eugen Stan]

Hi,

Thank you both for the clarification. I think it is a reasonable approach.

It's always best to validate specs with one or more implementations.

Then I propose that in the interest of greater adoption, maybe a name
change is in order.

Something that says: we install osgi packages and we are used by Sling
instead of having Sling in the name and inducing the idea of being Sling
specific or worst, Sling only.

Thank you,

On 21.02.2018 12:59, Carsten Ziegeler wrote:
> Hi,
>
> thanks! One major point of the feature model is to separate between the
> model and how it is used later on. All current existing approaches mix
> these two things in most cases.
>
> There is a lot of overlap with the Karaf feature model, but the idea is
> to get a common model that works for everyone and as David pointed out
> potentially creating an OSGi spec out of this. So the model should work
> for Karaf users, for people creating sub systems etc.
>
> In fact, the prototype we have in our whiteboard creates a Karaf kar
> file out of a feature which can then easily be used within Karaf. But
> that's just one way doing it
>
> Regards
>
> Carsten
>
>
> Ioan Eugen Stan wrote
>> Hi,
>>
>> I've looked on the specification and I've noticed that it also overlaps
>> with the Karaf Feature functionality.
>>
>> Is there any relation between the two? Is there collaboration between
>> the projects?
>>
>> As a user/consumer of technology I enjoy when technologies are
>> compatible and the tooling support is great.
>>
>> I believe collaboration in this area is beneficial. I would like to be
>> able to provision Sling features in Karaf and Karaf features in Sling
>> with ease.
>>
>> If you put the spec side by side they share a LOT of things, but there
>> are also some minor differences, like file format. Karaf uses XML which
>> has much better tooling support IMO, but this is a persistence format
>> and can be easily changed.
>>
>>
>> p.s. I like the spec, I imagine it took quite some time to write. Kudos !
>>
>> Regards,
>>
>> [1] https://karaf.apache.org/manual/latest/provisioning
>>
>>
>>
>> On 21.02.2018 09:10, Carsten Ziegeler wrote:
>>> Thanks David
>>>
>>> We're neither 100% clear on the requirements nor on the structure,
>>> meaning we don't know how many and what modules this will be. As we're
>>> following the one module per git repo rule, it's currently impossible to
>>> create the correct git repositories. And I guess it doesn't make sense
>>> to rename them or remove them every now and then.
>>>
>>> As the collaboration with the whiteboard is the same as with separate
>>> modules, I don't think there is anything wrong with having this in the
>>> whiteboard for now. Moving it out now creates more problems than it solves.
>>>
>>> Regards
>>>
>>> Carsten
>>>
>>>
>>> David Bosschaert wrote
>>>> Hi all,
>>>>
>>>> Over the recent past some additions have been made to the requirements of
>>>> the Sling Feature Model. The updated requirements can be found here:
>>>> https://github.com/apache/sling-whiteboard/blob/master/featuremodel/readme.md
>>>>
>>>> Any additional requirements, let us know!
>>>>
>>>> I'm hoping to start contributing to the implementation of some of these in
>>>> the near term and was wondering - is there a reason why the feature model
>>>> still in the sling-whiteboard? Or would it make sense to put it in its own
>>>> Sling git repo or repos?
>>>>
>>>> Best regards,
>>>>
>>>> David
>>>>
>>




signature.asc
Description: OpenPGP digital signature

Re: [Sling Feature Model] Expanded requirements

[Ioan Eugen Stan]

Hi,

I've looked on the specification and I've noticed that it also overlaps
with the Karaf Feature functionality.

Is there any relation between the two? Is there collaboration between
the projects?

As a user/consumer of technology I enjoy when technologies are
compatible and the tooling support is great.

I believe collaboration in this area is beneficial. I would like to be
able to provision Sling features in Karaf and Karaf features in Sling
with ease.

If you put the spec side by side they share a LOT of things, but there
are also some minor differences, like file format. Karaf uses XML which
has much better tooling support IMO, but this is a persistence format
and can be easily changed.


p.s. I like the spec, I imagine it took quite some time to write. Kudos !

Regards,

[1] https://karaf.apache.org/manual/latest/provisioning



On 21.02.2018 09:10, Carsten Ziegeler wrote:
> Thanks David
>
> We're neither 100% clear on the requirements nor on the structure,
> meaning we don't know how many and what modules this will be. As we're
> following the one module per git repo rule, it's currently impossible to
> create the correct git repositories. And I guess it doesn't make sense
> to rename them or remove them every now and then.
>
> As the collaboration with the whiteboard is the same as with separate
> modules, I don't think there is anything wrong with having this in the
> whiteboard for now. Moving it out now creates more problems than it solves.
>
> Regards
>
> Carsten
>
>
> David Bosschaert wrote
>> Hi all,
>>
>> Over the recent past some additions have been made to the requirements of
>> the Sling Feature Model. The updated requirements can be found here:
>> https://github.com/apache/sling-whiteboard/blob/master/featuremodel/readme.md
>>
>> Any additional requirements, let us know!
>>
>> I'm hoping to start contributing to the implementation of some of these in
>> the near term and was wondering - is there a reason why the feature model
>> still in the sling-whiteboard? Or would it make sense to put it in its own
>> Sling git repo or repos?
>>
>> Best regards,
>>
>> David
>>




signature.asc
Description: OpenPGP digital signature

Re: [DISCUSSION] Make Sling shiny - Basic CMS

[Ioan Eugen Stan]

Hi Daniel,

I've gone through the steps and I love it. I think a CMS can boost Sling
and the ecosystem a lot.

Congratulations on your results!

Some feedback:

- the process of creating a website should be streamlined to hide
details for the end user

- a base set of page templates like wordpress ones (Post and Page) would
be a great next step

- the configuration files could be moved to /etc/sling-cms/configs to
namespace things in case other apps need to access /etc

- is there any relationship between sling-cms and Composum? It seems to
me like both projects are heading in a similar direction and a
colaboration might be beneficial. Composum provides Composum assests,
Composum Pages, etc. That functionality could be reused.

Regards,


On 10.02.2018 02:52, Daniel Klco wrote:
> Thanks Jason! Obviously tested only with a Mac. I just pushed in an update
> to resolve the issue and updating the docker image to fix some UI issues.
>
> On Fri, Feb 9, 2018 at 11:51 AM, Jason E Bailey  wrote:
>
>> If you're not familiar with this. A colon is an illegal character in a
>> windows file name. When windows uses it as part of a file descriptor when
>> opening/creating a file it's to specify a side channel where extra data is
>> stored.
>>
>> So in the case of the jcr:content files git uses jcr:content as the file
>> descriptor and ends up creating a file called jcr that appears empty but
>> will still be the same size as the corresponding jcr:content.
>>
>> Eclipse is the actual creator of that error message as it rightly
>> recognized that this is most likely not what was intended. I'm assuming
>> that we can rename the files _jcr_content.json and still have them work.
>>
>> - Jason
>>
>> On Fri, Feb 9, 2018, at 8:47 AM, Jason E Bailey wrote:
>>> I'm pretty excited about this.  Did run into a slight problem. I use
>>> windows at work and your CMS commit actually breaks git for me. cms/ui/
>>> src/main/resources/jcr_root/etc/fileeditors/jcr:content.json is not
>>> considered a valid file.
>>>
>>> - Jason




signature.asc
Description: OpenPGP digital signature

Re: Sling docker image

[Ioan Eugen Stan]

Hello Robert,


I think taking back the name is a good idea. Maybe we could ask Docker
hub if we can somehow change the name.

I would like to support deploying Sling with Docker.


Regards,


On 31.01.2018 17:03, Robert Munteanu wrote:
> Hi,
>
> Related to the ongoing github.com/apache/sling landing page discussion,
> I'd like to discuss our docker setup.
>
> Currently we provide an apachelsling/sling [1] image, which is OK. I
> investigated setting up a build under the more official apache account,
> but unfortunately the automated docker builds picks up the image name
> from the repository, so we ended up with apache/sling-org-apache-sling-
> starter-docker, which is quite ugly.
>
> If we choose automated builds, getting back the 'sling' repository is
> something we should consider.
>
> Thanks,
>
> Robert
>
> [1]: https://hub.docker.com/r/apachesling/sling/
> [2]: https://hub.docker.com/r/apache/sling-org-apache-sling-starter-doc
> ker/




signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Appoint Robert Munteanu as new Apache Sling PMC Chair

[Ioan Eugen Stan]

+1


On 24.10.2017 23:33, Carsten Ziegeler wrote:
> Test mail - please ignore :)
>
> Carsten
>
>
> Carsten Ziegeler wrote
>> Hi,
>>
>> please cast your vote for Robert Munteanu as our new PMC chair
>>
>> Regards
>> Carsten
>>




signature.asc
Description: OpenPGP digital signature

Re: Contribute Slick?

[Ioan Eugen Stan]

Hi,

I second that. What sling needs most is a big community that can create
a marketplace like Wordpress has.

A place where you can publish plugins and modules that users can install
and that work out of the box.

Having a comunity and a marketplace is a big step forward for adoption
by non-developers.

Regards,


On 24.10.2017 01:53, Carsten Ziegeler wrote:
> I think it would be a great contribution and it's definitely welcome.
> Thanks for offering. I would assume that the contribution to Sling might
> get you even more feedback and contributors.
>
> What I personally would love to have, is splitting Slick up into some
> modules. For example, your front page to change the admin password could
> be of general interest for any Sling based installation. Same is for the
> UI to create users. This could be shared between different demos. I
> always planned to have something like this for the Slingshot sample, but
> never got to it.
>
> But this is just dreaming and not really required for the contribution
> itself.
>
> Regards
>
> Carsten
>
>
> Chris Millar wrote
>> At AdaptTo, I had a few conversations about contributing Slick [0] to
>> Apache Sling. Is this something the community is interested in? If so, I'd
>> like to start that process. Whether it be part of a contrib project or a
>> sample project.
>>
>> There would be things I would like to clean up before hand. Some
>> auto-generated try / catches, add unit tests, and get the Sling 9 version
>> thoroughly tested are just a few.
>>
>> If you have thoughts on this, please share them.
>>
>> Thanks!
>> Chris
>>
>> [0] https://github.com/auniverseaway/slick-2
>>




signature.asc
Description: OpenPGP digital signature

Re: [discuss] Launchpad user experience

[Ioan Eugen Stan]

Hi,

Great idea. How about Sling Starter/ Loader / Bootstrap ?


Regarding building a real app with Spring I would like to go through
that process (be a guinee pig). We would like to use the content
repository in a Saas like app using micro services.

The content would be written via one service via Oak API and edited by
the service desk via Composum, and read by other services also via Oak
API. 

My plan is to write a docker compose file that simulate the multiple
services. One of the service will have Sling + Composum installed.

I'm planning to use the RDBMS back-end for Oak because we have expertise
with PostgreSQL.

Some things that I would like to make test/know before going into
production:

- reading and writing from multiple services works ok - check delay,
caching, etc
- editing content via Composum works properly
- procedures on how to deploy content updates to production (FileVault
maybe)
- how to get content from production to staging to facilitate testing
- how to deploy and update our single page applications that consume our
API
- how to deploy/update translations for content

I know I have quite specific needs that might not fit into general
norms, but the needs are real and I am willing to document and share the
process and all the code samples. All I need in return is some guidance.


Regards,

On 03.10.2017 13:11, Carsten Ziegeler wrote:
> I think we can improve the user experience with our launchpad.
> Let's start with the simpler issue:
>
> Right now if you start the app and try "too soon" to open a page in your
> browser you might get a nasty message like some service is missing etc.
> That's not very helpful.
>
> I've written a simple bundle at [1] which displays the message "Apache
> Sling is starting up...". We could even enhance it with a little
> javascript to reload itself. I know we have the startup filter, but
> that's more a general purpose thing while this module is exactly there
> to improve the user experience. We could add whatever we need to improve
> that. I think we should release it and add it to launchpad to make this
> problem go away.
>
> Now the more interesting part is ... naming :)
>
> While the downloads page states "Sling Application" we always refer to
> it as "launchpad". Even the downloaded artifact has "launchpad" in it.
> Now "launchpad" has no meaning to someone new to Sling and further more
> its a technical term describing how we launch Sling. So I think we
> should not use this for our Sling downloads.
>
> "Sling Application" is far better but might not be the best description
> either. I thought about "Sling Demo Application" but that's not quiet
> right either. It's definitely not a distribution as we don't intend that
> people use this in production.
>
> So I think we should come up with a good (short) name for this thing and
> then use it throughout our documentation and in the artifact id. And
> forget about using the term launchpad. (As soon as we move to the new
> feature model we don't use launchpad technology anymore anyway).
>
> We should also improve our docs on building a real application with
> Sling. But that's a different topic and I plan to work on this in
> November to improve the docs around that.
>
> WDYT?
>
> Regards
> Carsten
>
> [1]
> https://svn.apache.org/repos/asf/sling/whiteboard/cziegeler/demo.startup/




signature.asc
Description: OpenPGP digital signature

[jira] [Commented] (SLING-6201) Deploy Sling 9 docker image to Docker Hub

[Ioan Eugen Stan (JIRA)]

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

Ioan Eugen Stan commented on SLING-6201:


The Java image has been deprecated on docker hub. I imagine because Oracle JRE 
cannot be distributed without Oracle approval. 

Please use openjdk image instead: https://hub.docker.com/_/openjdk/
I recommend using "openjdk:jre-alpine" as it is much smaller (based on alpine 
linux) than the full one (based on ubuntu). 

Alpine Linux contains the kernel, busy-box, openjdk jre and sling app. 


> Deploy Sling 9 docker image to Docker Hub
> -
>
> Key: SLING-6201
> URL: https://issues.apache.org/jira/browse/SLING-6201
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Note - we should switch to the apache account instead of the apachesling one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: composum upload does not update jcr:lastModified for files and images

[Ioan Eugen Stan]

Hello Robert,


Thanks for the suggestions. I got a reply on Composum github issues[1]

It seems Composum does not update related properties by default. If I
change jcr:data via upload, only jcr:data is updated.

In the reply, it says it is fixed in Composum 1.8, just released. I did
not check it.


Regards,

[1] https://github.com/ist-dresden/composum/issues/84


On 08.06.2017 11:48, Robert Munteanu wrote:
> Hi Eugen,
>
> On Thu, 2017-06-01 at 16:41 +0300, Ioan Eugen Stan wrote:
>> Hello,
>>
>> I have posted this issue on the composum issue tracker [0], but not
>> sure
>> where is the right place so I'm posting it here as well.
>>
>> I'm using the latest sling-launchpad
>> org.apache.sling.launchpad-9-20170531.170627-12089.jar with composum
>> browser.
>>
>> I use the browser to create a |nt:file| image |content/hello.png|. I
>> can
>> preview the image.
>> After that I upload a new image by double clicking on the jcr:data
>> and
>> using the upload dialog there.
>>
>> Using the preview button on |jcr:content| node, I can see the new
>> image.
>> Using preview on the |hello.png| file shows the old version.
>>
>> Also, viewing the image on the public link displayes the old image as
>> well [1]
>>
>> One workaround is to manually change the |jcr:lastModified| property
>> of
>> the 'jcr:content' node.
>> That way, the image is updated.
>>
>>
>> The same thing happens with file updates as well. Editing a file via
>> the
>> composum web interface does not change the contents in the public
>> link,
>> unless you update the jcr:lastModified proeprty.
> From your description this sounds like a composum issue. Out of
> curiosity, do file uploads performed without composum exhibit the same
> issue?
>
> Thanks,
>
> Robert
>
>>
>> [0] https://github.com/ist-dresden/composum/issues/84
>>
>> [1] http://localhost:8080/content/hello.png
>>




signature.asc
Description: OpenPGP digital signature

Re: Please welcome Nicolas Peltier, Sling committer

[Ioan Eugen Stan]

Congratulations Nicolas!


On 08.06.2017 10:53, Robert Munteanu wrote:
> Hi Sling community,
>
> Based on his ongoing and valuable contributions to the project,
> centered around the Sling Pipes module, the Sling PMC has elected
> Nicolas Peltier as a Sling committer, and he has accepted the
> invitation.
>
> Please join me in welcoming him!
>
> Nicolas - if you want to honor the old tradition of new committers
> briefly introducing themselves to the list, feel free. And maybe take
> the time to verify your SVN permissions to update http://sling.apache.o
> rg/project-information/project-team.html :-)
>
> Best,
>
> Robert




signature.asc
Description: OpenPGP digital signature

Re: Sling Node Type Web Console Plugin

[Ioan Eugen Stan]

Sounds great Andreas. Bertrand's advice seems good too.


On 08.06.2017 11:26, Bertrand Delacretaz wrote:
> Hi Andy,
>
> On Thu, Jun 8, 2017 at 12:46 AM, Andreas Schaefer Sr.  
> wrote:
>> ...Would you guys be interested in a Web Console Plugin that shows the 
>> installed Node Types with their hierarchy
>> in a way similar the “good-old CRX Explorer” from AEM?...
> I think that would be useful, unless we already have something that I missed.
>
> Implementing it as a resource provider might make sense? And mount it
> by default under /system/nodetypes.
>
> -Bertrand




signature.asc
Description: OpenPGP digital signature

composum upload does not update jcr:lastModified for files and images

[Ioan Eugen Stan]

Hello,

I have posted this issue on the composum issue tracker [0], but not sure
where is the right place so I'm posting it here as well.

I'm using the latest sling-launchpad
org.apache.sling.launchpad-9-20170531.170627-12089.jar with composum
browser.

I use the browser to create a |nt:file| image |content/hello.png|. I can
preview the image.
After that I upload a new image by double clicking on the jcr:data and
using the upload dialog there.

Using the preview button on |jcr:content| node, I can see the new image.
Using preview on the |hello.png| file shows the old version.

Also, viewing the image on the public link displayes the old image as
well [1]

One workaround is to manually change the |jcr:lastModified| property of
the 'jcr:content' node.
That way, the image is updated.


The same thing happens with file updates as well. Editing a file via the
composum web interface does not change the contents in the public link,
unless you update the jcr:lastModified proeprty.


[0] https://github.com/ist-dresden/composum/issues/84

[1] http://localhost:8080/content/hello.png



signature.asc
Description: OpenPGP digital signature

unable to edit resources in Webdav mount via Nautilus

[Ioan Eugen Stan]

Hello,

I'm using the latest sling-launchpad 9 snapshot version
org.apache.sling.launchpad-9-20170531.170627-12089.jar in a local
application. I mounted the JCR repository as a Webdav filesystem in
Nautilus.

I authenticated in Nautilus with dav://admin@localhost:8080/ and admin
password.

I can add resources and copy files into Sling/JCR repo and I can also
replace content, but I can't rename, edit files or move them around.

Is this a limitation/bug in Sling/JCR a configuration issue with Sling
JCR or shoul I check the webdav client (Nautilus)?


Thanks,





signature.asc
Description: OpenPGP digital signature

Re: sling 9 very large - reducing the size?

[Ioan Eugen Stan]

Hi Robert,


Thank you for the clarification and the link. All I have to do is figure
out if I need tika or not. It's still a huge bundle and maybe the tika
guys could do something to improve that, but it's another discussion.

It makes sens to be like this. I imagine some hints for using sling in
production would be welcomed and this should be there.

Have a great day,


On 22.05.2017 14:09, Robert Munteanu wrote:
> Hi Eugen,
>
> On Sat, 2017-05-20 at 21:24 +0300, Ioan Eugen Stan wrote:
>> Hello Sling ,
>>
>> I've noticed sling 9 is quite big. The latest snapshot jar is about
>> 107 MB.
>>
>> - ~40MB of this is occupied by install/10/tike-bundle-1.14.jar . Is
>> this
>> bundle always required?
> This (IIRC) is required for full-text search to function in Oak.
>
>
>> - removing install/0/org.apache.sling.samples.slingshot-0.8.0.jar can
>> shave another 5MB
> Yes, but it's explicitly in there because we want to include a demo of
> an application with the default download.
>
>
>> Reducing the sling-launchpad image size should make the platform
>> easier
>> to work with.
> For more context, we see the Sling Launchpad as a 'demo' platform which
> allows you to quickly get your feet wet and understand how Sling works.
>
> For production usage, I would expect most people would define their own
> launchpad, potentially from an existing Launchpad. There's also support
> for dynamically removing artifacts from an existing launchpad, see [1],
> but I'm not sure how many use it for that exact purpose.
>
> HTH,
>
> Robert
>
> [1]: http://sling.apache.org/documentation/development/slingstart.html#
> removing-and-changing-of-artifacts
>
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>>




signature.asc
Description: OpenPGP digital signature

feedback + missing karaf feature for sling with RDBDocumentStore?

[Ioan Eugen Stan]

Hello,

I'm evaluating Sling to use as a CMS in our project. Since I'm planning
to use Karaf as the foundation I decidede to test that out.

I've managed to build and install a running Sling instance with oak tar
backend and played a bit with Composum.

Things worked fine so far, great job. e are planning to deploy Sling
with the RDBDocumentStore since we don't have Mongo experience and I
would not like to complicate the deployment. We also have established
procedures on how to backup and maintain a PostgreSQL database.

However I have noticed that the Karaf features.xml file is missing a
feature to deploy Sling with RDBDocumentStore backend.

Is this a simple omission or are there other reasons why this is not
provided? I'll be able to help build a feature for this case and
contribute it to Sling if it's just an omission. I may need some
guidance and code feedback.

Some other things I have noticed is that the features are not documented
and you don't know which features to install, without having experience
with the project.

Thanks,






signature.asc
Description: OpenPGP digital signature

build fails - missing dependency - easy fix

[Ioan Eugen Stan]

Hello,

I've just built Sling locally and the build failed with a missing
dependency. It's an easy fix. See bellow the git diff. I've included the
SNAPSHOT version, but you could include the release of
org.apache.sling.validation.api.

p.s. Glad to hear Sling 9 is being released soon. I'm planning to use it
in a project (I enjoy composum feature). I have some questions that I
will post on the mailing list as I formulate them.


Great job,

Ioan Eugen Stan

-

diff --git a/bundles/extensions/validation/examples/pom.xml
b/bundles/extensions/validation/examples/pom.xml
index f52ce72ff9..5117080d75 100644
--- a/bundles/extensions/validation/examples/pom.xml
+++ b/bundles/extensions/validation/examples/pom.xml
@@ -68,7 +68,7 @@
 
 org.apache.sling
 org.apache.sling.validation.api
-1.0.0-SNAPSHOT
+1.0.1-SNAPSHOT
 provided
 
 




[ERROR] Failed to execute goal on project
org.apache.sling.validation.examples: Could not resolve dependencies for
project
org.apache.sling:org.apache.sling.validation.examples:bundle:1.0.0-SNAPSHOT:
Failure to find
org.apache.sling:org.apache.sling.validation.api:jar:1.0.0-SNAPSHOT in
https://repository.apache.org/snapshots was cached in the local
repository, resolution will not be reattempted until the update interval
of apache.snapshots has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command






signature.asc
Description: OpenPGP digital signature

sling 9 very large - reducing the size?

[Ioan Eugen Stan]

Hello Sling ,

I've noticed sling 9 is quite big. The latest snapshot jar is about 107 MB.

- ~40MB of this is occupied by install/10/tike-bundle-1.14.jar . Is this
bundle always required?

- removing install/0/org.apache.sling.samples.slingshot-0.8.0.jar can
shave another 5MB


Reducing the sling-launchpad image size should make the platform easier
to work with.


Regards,









signature.asc
Description: OpenPGP digital signature