[jira] [Resolved] (SLING-11997) Sling post servlet delete protected node like group report success but actual failed

2023-08-08 Thread Jun Zhang (Jira)


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

Jun Zhang resolved SLING-11997.
---
Resolution: Not A Problem

endu p an AEM issue instead of sling issue, sorry

> Sling post servlet delete protected node like group report success but actual 
> failed
> 
>
> Key: SLING-11997
> URL: https://issues.apache.org/jira/browse/SLING-11997
> Project: Sling
>  Issue Type: Bug
>  Components: Sling Security
>Reporter: Jun Zhang
>Priority: Minor
>
> Sling post servlet delete protected node report success but actual failed
>  
> curl -u user:pwd -F":operation=delete" 
> [http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL|http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]
>  
> it report success response below:
> {code:java}
> curl -u admin:admin -F"deleteAuthorizable=true" 
> http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
> 
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
>     
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
>     
>         
>             
>                 Status
>                 200
>             
>             
>                 Message
>                 OK
>             
>             
>                 Location
>                  alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" 
> border="0">/home/groups/C/CrKDhM1fP5xxs5YcN6rL src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>             
>             
>                 Parent Location
>                  id="ParentLocation">/home/groups/C
>             
>             
>                 Path
>                  id="Path">/home/groups/C/CrKDhM1fP5xxs5YcN6rL
>             
>             
>                 Referer
>                 
>             
>             
>                 ChangeLog
>                 pre/pre
>             
>         
>     
>     Go Back
>      alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" border="0">Modified Resource class="cq-LinkChecker cq-LinkChecker--suffix cq-LinkChecker--invalid" 
> src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>     Parent of Modified Resource
>     
>  {code}
>  but actually failed
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (SLING-11997) Sling post servlet delete protected node like group report success but actual failed

2023-08-08 Thread Jun Zhang (Jira)


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

Jun Zhang updated SLING-11997:
--
Description: 
Sling post servlet delete protected node report success but actual failed

 

curl -u user:pwd -F":operation=delete" 
[http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL|http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]

 

it report success response below:
{code:java}
curl -u admin:admin -F"deleteAuthorizable=true" 
http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL


    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL

    
    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
    
        
            
                Status
                200
            
            
                Message
                OK
            
            
                Location
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Parent Location
                /home/groups/C
            
            
                Path
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Referer
                
            
            
                ChangeLog
                pre/pre
            
        
    
    Go Back
    Modified Resource
    Parent of Modified Resource
    
 {code}
 but actually failed

 

 

  was:
Sling post servlet delete protected node report success but actual failed

 

curl -u user:pwd -F":operation=delete" 
[http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]

 

it report success response below:
{code:java}
curl -u admin:admin -F"deleteAuthorizable=true" 
http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL


    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL

    
    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
    
        
            
                Status
                200
            
            
                Message
                OK
            
            
                Location
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Parent Location
                /home/groups/C
            
            
                Path
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Referer
                
            
            
                ChangeLog
                pre/pre
            
        
    
    Go Back
    Modified Resource
    Parent of Modified Resource
    
 {code}
 but actually failed

 

 


> Sling post servlet delete protected node like group report success but actual 
> failed
> 
>
> Key: SLING-11997
> URL: https://issues.apache.org/jira/browse/SLING-11997
> Project: Sling
>  Issue Type: Bug
>  Components: Sling Security
>Reporter: Jun Zhang
>Priority: Minor
>
> Sling post servlet delete protected node report success but actual failed
>  
> curl -u user:pwd -F":operation=delete" 
> [http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL|http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]
>  
> it report success response below:
> {code:java}
> curl -u admin:admin -F"deleteAuthorizable=true" 
> http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
> 
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
>     
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
>     
>         
>             
>                 Status
>                 200
>             
>             
>                 Message
>                 OK
>             
>             
>                 Location
>                  alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" 
> border="0">/home/groups/C/CrKDhM1fP5xxs5YcN6rL src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>             
>             
>                 Parent Location
>                  id="ParentLocation">/home/groups/C
>             
>             
>                 Path
>                  id="Path">/home/groups/C/CrKDhM1fP5xxs5YcN6rL
>             
>             
>                 Referer
>                 
>             
>             
>                 ChangeLog
>                 pre/pre
>             
>         
>     
>     Go Back
>      alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" border="0">Modified Resource class="cq-LinkChecker cq-LinkChecker--suffix cq-LinkChecker--invalid" 
> src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>     Parent of Modified Resource
>     
>  {code}
>  but actually failed
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (SLING-11997) Sling post servlet delete protected node like group report success but actual failed

2023-08-08 Thread Jun Zhang (Jira)


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

Jun Zhang commented on SLING-11997:
---

FYI, proper parameter like -FdeleteAuthorizable=true works to delete that 
successfully

> Sling post servlet delete protected node like group report success but actual 
> failed
> 
>
> Key: SLING-11997
> URL: https://issues.apache.org/jira/browse/SLING-11997
> Project: Sling
>  Issue Type: Bug
>  Components: Sling Security
>Reporter: Jun Zhang
>Priority: Minor
>
> Sling post servlet delete protected node report success but actual failed
>  
> curl -u user:pwd -F":operation=delete" 
> [http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL|http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]
>  
> it report success response below:
> {code:java}
> curl -u admin:admin -F"deleteAuthorizable=true" 
> http://localhost:8080/home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
> 
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
> 
>     
>     Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
>     
>         
>             
>                 Status
>                 200
>             
>             
>                 Message
>                 OK
>             
>             
>                 Location
>                  alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" 
> border="0">/home/groups/C/CrKDhM1fP5xxs5YcN6rL src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>             
>             
>                 Parent Location
>                  id="ParentLocation">/home/groups/C
>             
>             
>                 Path
>                  id="Path">/home/groups/C/CrKDhM1fP5xxs5YcN6rL
>             
>             
>                 Referer
>                 
>             
>             
>                 ChangeLog
>                 pre/pre
>             
>         
>     
>     Go Back
>      alt="invalid link: /home/groups/C/CrKDhM1fP5xxs5YcN6rL" title="invalid link: 
> /home/groups/C/CrKDhM1fP5xxs5YcN6rL" border="0">Modified Resource class="cq-LinkChecker cq-LinkChecker--suffix cq-LinkChecker--invalid" 
> src="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0">
>     Parent of Modified Resource
>     
>  {code}
>  but actually failed
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (SLING-11997) Sling post servlet delete protected node like group report success but actual failed

2023-08-08 Thread Jun Zhang (Jira)
Jun Zhang created SLING-11997:
-

 Summary: Sling post servlet delete protected node like group 
report success but actual failed
 Key: SLING-11997
 URL: https://issues.apache.org/jira/browse/SLING-11997
 Project: Sling
  Issue Type: Bug
  Components: Sling Security
Reporter: Jun Zhang


Sling post servlet delete protected node report success but actual failed

 

curl -u user:pwd -F":operation=delete" 
[http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL]

 

it report success response below:
{code:java}
curl -u admin:admin -F"deleteAuthorizable=true" 
http://localhost:4502/home/groups/C/CrKDhM1fP5xxs5YcN6rL


    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL

    
    Content modified /home/groups/C/CrKDhM1fP5xxs5YcN6rL
    
        
            
                Status
                200
            
            
                Message
                OK
            
            
                Location
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Parent Location
                /home/groups/C
            
            
                Path
                /home/groups/C/CrKDhM1fP5xxs5YcN6rL
            
            
                Referer
                
            
            
                ChangeLog
                pre/pre
            
        
    
    Go Back
    Modified Resource
    Parent of Modified Resource
    
 {code}
 but actually failed

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #963 is FIXED

2023-08-08 Thread Apache Jenkins Server
Please see 
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/963/
 for details.

No further emails will be sent until the status of the build is changed.

[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #962 is BROKEN

2023-08-08 Thread Apache Jenkins Server
latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230808.090033-1.xml.gz
 (329 kB at 22 MB/s)
[INFO] Uploaded to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230808.090033-1-oak_tar_far.far
 (116 MB at 47 MB/s)
[INFO] Uploaded to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230808.090033-1-oak_mongo_far.far
 (115 MB at 46 MB/s)
[INFO] Downloading from snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml
[INFO] Uploading to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/maven-metadata.xml
 (7.5 kB at 7.5 MB/s)
[INFO] Uploading to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml
[INFO] Uploaded to snapshot-repo: 
file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml
 (297 B at 11 kB/s)
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time:  08:04 min
[INFO] Finished at: 2023-08-08T09:08:37Z
[INFO] 
[INFO] [jenkins-event-spy] Generated 
/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest@tmp/withMaven9a14847f/maven-spy-20230808-090032-73816873579779605240160.log
[Pipeline] }
[withMaven] artifactsPublisher - Archive artifact pom.xml under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT.pom
[withMaven] artifactsPublisher - Archive artifact 
target/org.apache.sling.starter-13-SNAPSHOT.jar under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT.jar
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-composum.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-composum.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-htl_repl.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-htl_repl.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-slingshot.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-slingshot.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-starter.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-starter.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-base.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-base.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-boot.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-boot.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-caconfig.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-caconfig.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-discovery.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-discovery.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-docker.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-docker.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-event.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-event.slingosgifeature
[withMaven] artifactsPublisher - Archive artifact 
target/slingfeature-tmp/feature-groovy.json under 
org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sl

[GitHub] [sling-org-apache-sling-starter] rombert merged pull request #207: chore(deps): update dependency org.apache.sling:org.apache.sling.servlets.resolver to v2.9.14

2023-08-08 Thread via GitHub


rombert merged PR #207:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/207


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [sling-org-apache-sling-starter] renovate-bot opened a new pull request, #207: chore(deps): update dependency org.apache.sling:org.apache.sling.servlets.resolver to v2.9.14

2023-08-08 Thread via GitHub


renovate-bot opened a new pull request, #207:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/207

   [![Mend 
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)
   
   This PR contains the following updates:
   
   | Package | Change | Age | Adoption | Passing | Confidence |
   |---|---|---|---|---|---|
   | 
[org.apache.sling:org.apache.sling.servlets.resolver](https://sling.apache.org) 
([source](https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-servlets-resolver.git))
 | `2.9.12` -> `2.9.14` | 
[![age](https://developer.mend.io/api/mc/badges/age/maven/org.apache.sling:org.apache.sling.servlets.resolver/2.9.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![adoption](https://developer.mend.io/api/mc/badges/adoption/maven/org.apache.sling:org.apache.sling.servlets.resolver/2.9.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![passing](https://developer.mend.io/api/mc/badges/compatibility/maven/org.apache.sling:org.apache.sling.servlets.resolver/2.9.12/2.9.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.apache.sling:org.apache.sling.servlets.resolver/2.9.12/2.9.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 |
   
   ---
   
   ### Configuration
   
    **Schedule**: Branch creation - At any time (no schedule defined), 
Automerge - At any time (no schedule defined).
   
    **Automerge**: Disabled by config. Please merge this manually once you are 
satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry 
checkbox.
   
    **Ignore**: Close this PR and you won't be reminded about this update 
again.
   
   ---
   
- [ ] If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR has been generated by [Mend 
Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository 
job log 
[here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter).
   

   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Closed] (SLING-11964) DefaultErrorHandler must not reset response

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11964.
-

> DefaultErrorHandler must not reset response
> ---
>
> Key: SLING-11964
> URL: https://issues.apache.org/jira/browse/SLING-11964
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.9.12
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
> The Sling Engine is ensuring that the response is already reset before the 
> ErrorHandler is invoked. As there might be error filters running between that 
> reset and the ErrorHandler, the ErrorHandler must not reset the response 
> again. Otherwise it would wipe out whatever the filters had already done to 
> the response



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (SLING-11896) Fix build failures on Windows plattform

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11896.
-

> Fix build failures on Windows plattform
> ---
>
> Key: SLING-11896
> URL: https://issues.apache.org/jira/browse/SLING-11896
> Project: Sling
>  Issue Type: Task
>Affects Versions: Servlets Resolver 2.9.10
>Reporter: Joerg Hoh
>Assignee: Joerg Hoh
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
>  
> See 
> [https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/34] 
> and
> [https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-apache-sling-servlets-resolver/detail/SLING-11895/1/pipeline/]
> Also re-enable the windows builds.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (SLING-11982) Avoid redundant repository access

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11982.
-

> Avoid redundant repository access
> -
>
> Key: SLING-11982
> URL: https://issues.apache.org/jira/browse/SLING-11982
> Project: Sling
>  Issue Type: Task
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.9.12
>Reporter: Joerg Hoh
>Assignee: Joerg Hoh
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
> Cache already read resources in the propertyMap of the ResourceResolvers. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (SLING-11908) Cache already resolved child resources of resource type resources

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11908.
-

> Cache already resolved child resources of resource type resources
> -
>
> Key: SLING-11908
> URL: https://issues.apache.org/jira/browse/SLING-11908
> Project: Sling
>  Issue Type: Task
>Reporter: Joerg Hoh
>Assignee: Joerg Hoh
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
> The NamedScriptResourceCollector and the ResourceCollector both need to 
> resolve the child resources of all resolved resourcetypes to determine which 
> script/servlet to execute.
> This is done over and over again; this overhead is unnecessary especially in 
> scenarios, where a lot selectors are bound to the default resourcetype, which 
> consistently need to get resolved, even if the default resourcetype is not 
> used in this resolution at all.
> This complete list of child resources should be cached (once resolved) and 
> re-used instead of refetching it again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (SLING-11558) [Performance] Remove resource -> path -> resource conversion

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11558.
-

> [Performance] Remove resource -> path -> resource conversion
> 
>
> Key: SLING-11558
> URL: https://issues.apache.org/jira/browse/SLING-11558
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.9.8
>Reporter: Joerg Hoh
>Assignee: Joerg Hoh
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently the 
> [ResourceCollector|https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/helper/ResourceCollector.java]
>  uses the 
> [LocationIterator|https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/helper/LocationIterator.java]
>  to build a list of possible locations where the script for a resource type 
> can be located.
> The interface is based on Strings (representing a repository path), although 
> both within the LocationIterator and in the ResourceCollector Resources are 
> used.
> * The mapping of a path to a string requires a repository access, thus 
> accessing the repo twice (checking in the LocationIterator if a resource 
> exists at a certain path, plus conversion of that path again into a resource 
> in the ResourceCollector) is redundant. Instead the LocationIterator should 
> just return resources instead of the paths to resources.
> * The LocationIterator implements the {{Iterator}} interface, although it is 
> only used in the ResourceCollector, which just iterates over all entries in a 
> single loop. The LocationIterator could just return a collection of Resources 
> (not implementing the Iterator interface), which makes the logic in this 
> class much cleaner.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Closed] (SLING-11911) Use proper resource resolving in Sling Servlet Resolver web console

2023-08-08 Thread Joerg Hoh (Jira)


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

Joerg Hoh closed SLING-11911.
-

> Use proper resource resolving in Sling Servlet Resolver web console
> ---
>
> Key: SLING-11911
> URL: https://issues.apache.org/jira/browse/SLING-11911
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.9.12
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
> For historical reason the servlet resolver web console didn't actually 
> resolve the resource to correctly decompose the URL but always used a 
> heuristics. With SlingUriBuilder providing the method 
> {{SlingUriBuilder.rebaseResourcePath()}} this now became much simpler and we 
> can easily do the resolving in the web console in the same way like it is 
> done in Sling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[RESULT] [VOTE] Release Apache Sling Servlets Resolver 2.9.14

2023-08-08 Thread Jörg Hoh
Hi,

The vote has passed with the following result :

+1 (binding): Jörg Hoh, Carsten Ziegeler, Eric Norman
+1 (non binding):

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Jörg


Am Do., 3. Aug. 2023 um 12:47 Uhr schrieb Jörg Hoh :

> Hi,
>
> We solved 6 issues in this 
> release:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353299=Text
>
> Staging 
> repository:https://repository.apache.org/content/repositories/orgapachesling-2777/
>
> You can use this UNIX script to download the release and verify the 
> signatures:https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
> Usage:
> sh check_staged_release.sh 2777 /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.
>
>
>
> --
> Cheers,
> Jörg Hoh,
>
> https://cqdump.joerghoh.de
> Twitter: @joerghoh
>


-- 
Cheers,
Jörg Hoh,

https://cqdump.joerghoh.de
Twitter: @joerghoh