[jira] [Created] (SLING-3649) add a scripting engine for Thymeleaf templates
Oliver Lietz created SLING-3649: --- Summary: add a scripting engine for Thymeleaf templates Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018856#comment-14018856 ] Oliver Lietz commented on SLING-3649: - initial version of Apache Sling Scripting Thymeleaf added in r1600678 add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3008) Render resource type (and super type) if resource can't be adapted to a map in JSON
[
https://issues.apache.org/jira/browse/SLING-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019800#comment-14019800
]
Oliver Lietz commented on SLING-3008:
-
Does it mean we can simply remove the code block? (works for me)
{noformat}
if ( resource.getResourceType() != null ) {
obj.put(sling:resourceType, resource.getResourceType());
}
if ( resource.getResourceSuperType() != null ) {
obj.put(sling:resourceSuperType,
resource.getResourceSuperType());
}
{noformat}
Or is there anything else to do?
Render resource type (and super type) if resource can't be adapted to a map
in JSON
---
Key: SLING-3008
URL: https://issues.apache.org/jira/browse/SLING-3008
Project: Sling
Issue Type: Bug
Components: Servlets
Affects Versions: Servlets Get 2.1.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Servlets Get 2.1.6
If the resource can't be adapted to a (value) map, at least resource type and
resource super type (if not null) should be rendered in the json output
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-1505) add ability to produce multiple karaf features descriptors
[ https://issues.apache.org/jira/browse/SLING-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019826#comment-14019826 ] Oliver Lietz commented on SLING-1505: - [~justinedelson], our manually compiled [feature.xml|http://svn.apache.org/viewvc/sling/trunk/contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml?view=markup] targets Karaf 3 which will also be used by upcoming ServiceMix 6. Do we still need separate feature descriptors or can we close this issue and track emerging issues separately? add ability to produce multiple karaf features descriptors -- Key: SLING-1505 URL: https://issues.apache.org/jira/browse/SLING-1505 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Priority: Minor from the discussion in SLING-1499, it seems that we're going to need to provide a separate feature descriptor for servicemix. Ideally, this would be done in the same xml file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-1505) add ability to produce multiple karaf features descriptors
[ https://issues.apache.org/jira/browse/SLING-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-1505: --- Assignee: Oliver Lietz add ability to produce multiple karaf features descriptors -- Key: SLING-1505 URL: https://issues.apache.org/jira/browse/SLING-1505 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Oliver Lietz Priority: Minor from the discussion in SLING-1499, it seems that we're going to need to provide a separate feature descriptor for servicemix. Ideally, this would be done in the same xml file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026543#comment-14026543 ] Oliver Lietz commented on SLING-3649: - made Thymeleaf scripting configurable and extensible in r1601661 * out of the box support for legacy HTML5 through embedded NekoHTML * runtime configurable TemplateModeHandlers for XML, VALIDXML, XHTML, VALIDXHTML, HTML5 and LEGACYHTML5 * MessageResolver backed by ResourceBundleProvider from org.apache.sling.i18n * uses UTF-8 charset for reading templates (not configurable) add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3711) version range for packages in javax.jcr is unnecessarily narrowed
Oliver Lietz created SLING-3711:
---
Summary: version range for packages in javax.jcr is unnecessarily
narrowed
Key: SLING-3711
URL: https://issues.apache.org/jira/browse/SLING-3711
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting JavaScript 2.0.14
Reporter: Oliver Lietz
Assignee: Oliver Lietz
from {{MANIFEST.MF}}:
{{Import-Package: javax.jcr;version=1.0}} (_2.0.12_)
{{Import-Package: javax.jcr;version=[1.0,2)}} (_2.0.14_)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3711) version range for packages in javax.jcr is unnecessarily narrowed
[
https://issues.apache.org/jira/browse/SLING-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-3711.
-
Resolution: Fixed
r1606657
version range for packages in javax.jcr is unnecessarily narrowed
-
Key: SLING-3711
URL: https://issues.apache.org/jira/browse/SLING-3711
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting JavaScript 2.0.14
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Scripting JavaScript 2.0.16
from {{MANIFEST.MF}}:
{{Import-Package: javax.jcr;version=1.0}} (_2.0.12_)
{{Import-Package: javax.jcr;version=[1.0,2)}} (_2.0.14_)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3711) version range for packages in javax.jcr is unnecessarily narrowed
[
https://issues.apache.org/jira/browse/SLING-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-3711:
Fix Version/s: Scripting JavaScript 2.0.16
version range for packages in javax.jcr is unnecessarily narrowed
-
Key: SLING-3711
URL: https://issues.apache.org/jira/browse/SLING-3711
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting JavaScript 2.0.14
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Scripting JavaScript 2.0.16
from {{MANIFEST.MF}}:
{{Import-Package: javax.jcr;version=1.0}} (_2.0.12_)
{{Import-Package: javax.jcr;version=[1.0,2)}} (_2.0.14_)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3732) add an authentication module using Login with XING
Oliver Lietz created SLING-3732: --- Summary: add an authentication module using Login with XING Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz * use the cookie-based “[Login with XING|https://dev.xing.com/plugins/login_with]” for authentication * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3731) add an authentication module using XING API with OAuth
Oliver Lietz created SLING-3731: --- Summary: add an authentication module using XING API with OAuth Key: SLING-3731 URL: https://issues.apache.org/jira/browse/SLING-3731 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz * use the [XING API|https://dev.xing.com/docs] with OAuth 1.0 for [authentication|https://dev.xing.com/docs/authentication] * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3732) add an authentication module using Login with XING
[ https://issues.apache.org/jira/browse/SLING-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052534#comment-14052534 ] Oliver Lietz commented on SLING-3732: - initial version of Apache Sling Authentication XING Login added in r1607877 add an authentication module using Login with XING Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz * use the cookie-based “[Login with XING|https://dev.xing.com/plugins/login_with]” for authentication * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3731) add an authentication module using XING API with OAuth
[ https://issues.apache.org/jira/browse/SLING-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052533#comment-14052533 ] Oliver Lietz commented on SLING-3731: - initial version of Apache Sling Authentication XING OAuth added in r1607877 add an authentication module using XING API with OAuth -- Key: SLING-3731 URL: https://issues.apache.org/jira/browse/SLING-3731 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz * use the [XING API|https://dev.xing.com/docs] with OAuth 1.0 for [authentication|https://dev.xing.com/docs/authentication] * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3738) ChangeUserPasswordServlet propagates wrong path on password modification
Oliver Lietz created SLING-3738:
---
Summary: ChangeUserPasswordServlet propagates wrong path on
password modification
Key: SLING-3738
URL: https://issues.apache.org/jira/browse/SLING-3738
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Jackrabbit User Manager 2.2.0
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: JCR Jackrabbit User Manager 2.2.2
path starts with
{{AuthorizableResourceProvider.SYSTEM_USER_MANAGER_GROUP_PREFIX}} instead of
{{AuthorizableResourceProvider.SYSTEM_USER_MANAGER_USER_PREFIX}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3738) ChangeUserPasswordServlet propagates wrong path on password modification
[
https://issues.apache.org/jira/browse/SLING-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-3738.
-
Resolution: Fixed
r1607991
ChangeUserPasswordServlet propagates wrong path on password modification
Key: SLING-3738
URL: https://issues.apache.org/jira/browse/SLING-3738
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Jackrabbit User Manager 2.2.0
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: JCR Jackrabbit User Manager 2.2.2
path starts with
{{AuthorizableResourceProvider.SYSTEM_USER_MANAGER_GROUP_PREFIX}} instead of
{{AuthorizableResourceProvider.SYSTEM_USER_MANAGER_USER_PREFIX}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3732) add an authentication module using Login with XING
[ https://issues.apache.org/jira/browse/SLING-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3732: Fix Version/s: Authentication XING Login 0.0.2 add an authentication module using Login with XING Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Authentication XING Login 0.0.2 * use the cookie-based “[Login with XING|https://dev.xing.com/plugins/login_with]” for authentication * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3731) add an authentication module using XING API with OAuth
[ https://issues.apache.org/jira/browse/SLING-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3731: Fix Version/s: Authentication XING OAuth 0.0.2 add an authentication module using XING API with OAuth -- Key: SLING-3731 URL: https://issues.apache.org/jira/browse/SLING-3731 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Authentication XING OAuth 0.0.2 * use the [XING API|https://dev.xing.com/docs] with OAuth 1.0 for [authentication|https://dev.xing.com/docs/authentication] * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3649: Fix Version/s: Scripting Thymeleaf 0.0.2 add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.2 * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026543#comment-14026543 ] Oliver Lietz edited comment on SLING-3649 at 7/6/14 2:57 PM: - made Thymeleaf scripting configurable and extensible in r1601661, r1602107, r1602108, r1602110 * out of the box support for legacy HTML5 through embedded NekoHTML * runtime configurable TemplateModeHandlers for XML, VALIDXML, XHTML, VALIDXHTML, HTML5 and LEGACYHTML5 * ResourceResolver backed by Sling's ResourceResolver * MessageResolver backed by ResourceBundleProvider from org.apache.sling.i18n * make charset for reading templates configurable was (Author: olli): made Thymeleaf scripting configurable and extensible in r1601661 * out of the box support for legacy HTML5 through embedded NekoHTML * runtime configurable TemplateModeHandlers for XML, VALIDXML, XHTML, VALIDXHTML, HTML5 and LEGACYHTML5 * MessageResolver backed by ResourceBundleProvider from org.apache.sling.i18n * uses UTF-8 charset for reading templates (not configurable) add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.2 * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3649. - Resolution: Implemented r1605306 add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.2 * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3732) add an authentication module using Login with XING
[ https://issues.apache.org/jira/browse/SLING-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3732. - Resolution: Implemented r1607877 add an authentication module using Login with XING Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Authentication XING Login 0.0.2 * use the cookie-based “[Login with XING|https://dev.xing.com/plugins/login_with]” for authentication * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-1505) add ability to produce multiple karaf features descriptors
[ https://issues.apache.org/jira/browse/SLING-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-1505. - Resolution: Not a Problem add ability to produce multiple karaf features descriptors -- Key: SLING-1505 URL: https://issues.apache.org/jira/browse/SLING-1505 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Oliver Lietz Priority: Minor from the discussion in SLING-1499, it seems that we're going to need to provide a separate feature descriptor for servicemix. Ideally, this would be done in the same xml file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-1505) add ability to produce multiple karaf features descriptors
[
https://issues.apache.org/jira/browse/SLING-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056029#comment-14056029
]
Oliver Lietz commented on SLING-1505:
-
{noformat}
beat:~ olli$ ssh -p 8101 smx@localhost
The authenticity of host '[localhost]:8101 ([127.0.0.1]:8101)' can't be
established.
DSA key fingerprint is 90:05:42:d4:4d:2a:27:14:40:85:80:45:7b:c2:2c:0b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[localhost]:8101' (DSA) to the list of known hosts.
Authenticated with partial success.
Authenticated with partial success.
Password authentication
Password:
_ __ __ _
/ ___| ___ _ _(_) ___ ___| \/ (_)_ __
\___ \ / _ \ '__\ \ / / |/ __/ _ \ |\/| | \ \/ /
___) | __/ | \ V /| | (_| __/ | | | |
|/ \___|_|\_/ |_|\___\___|_| |_|_/_/\_\
Apache ServiceMix (6.0.0-SNAPSHOT)
Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or 'osgi:shutdown' to shutdown ServiceMix.
smx@rootfeature:repo-add
mvn:org.apache.sling/org.apache.sling.launchpad.karaf-features/0.1.1-SNAPSHOT/xml/features
Adding feature url
mvn:org.apache.sling/org.apache.sling.launchpad.karaf-features/0.1.1-SNAPSHOT/xml/features
smx@rootfeature:install sling-launchpad-jackrabbit
Refreshing bundles org.ops4j.pax.web.pax-web-jsp (154),
org.apache.felix.eventadmin (148), org.apache.felix.bundlerepository (50),
org.ops4j.pax.web.pax-web-jetty (81)
smx@rootfeature:install sling-launchpad-content
smx@root
{noformat}
add ability to produce multiple karaf features descriptors
--
Key: SLING-1505
URL: https://issues.apache.org/jira/browse/SLING-1505
Project: Sling
Issue Type: Improvement
Components: Maven Plugins and Archetypes
Reporter: Justin Edelson
Assignee: Oliver Lietz
Priority: Minor
from the discussion in SLING-1499, it seems that we're going to need to
provide a separate feature descriptor for servicemix.
Ideally, this would be done in the same xml file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-2132) Curl commands in Discover with sling in 15 minutes are slightly wrong
[ https://issues.apache.org/jira/browse/SLING-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-2132. - Resolution: Cannot Reproduce Curl commands in Discover with sling in 15 minutes are slightly wrong --- Key: SLING-2132 URL: https://issues.apache.org/jira/browse/SLING-2132 Project: Sling Issue Type: Bug Components: Site Environment: * Intel Core2 Q8300 @2,5GHz * Windows 7 Home Premium (64 bit) with all the latest updates for 11/7/2011 * jdk1.6.0_24 * org.apache.sling.launchpad-6-standalone.jar Reporter: Phil Assignee: Oliver Lietz Comment: I marked this as a major because this is the first thing any potential user tries when they download the project Steps to reproduce: * Install the launchpad jar in a blank directory * Executecurl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some title http://localhost:8080/content/mynode * Observe the response: html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 404 NOT_FOUND/title /head bodyh2HTTP ERROR 404/h2 pProblem accessing /content/mynode. Reason: preNOT_FOUND/pre/phr /ismallPowered by Jetty:///small/ibr/ According to the Discover with sling in 15 minutes this should have created some content. I had to replace it with: curl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some title http://localhost:8080/mynode One very interesting thing about this was that when I had been using Sling for some time, the curl command worked. I had to re-install a virgin version (by running the launchpad jar in a clean directory) to recreate the defect. I tried to recreate the defect in the version I was using, and even deleted the 'content' node, but that made no difference: in the version I had used for a while the curl command worked, and in the virgin version it didn't -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-2132) Curl commands in Discover with sling in 15 minutes are slightly wrong
[
https://issues.apache.org/jira/browse/SLING-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056032#comment-14056032
]
Oliver Lietz commented on SLING-2132:
-
Cannot reproduce with 6 and 7-SNAPSHOT. If the cause is a missing intermediate
node ({{content}}), create it with {{curl -X MKCOL -u admin:admin
http://localhost:8080/content}}.
Curl commands in Discover with sling in 15 minutes are slightly wrong
---
Key: SLING-2132
URL: https://issues.apache.org/jira/browse/SLING-2132
Project: Sling
Issue Type: Bug
Components: Site
Environment: * Intel Core2 Q8300 @2,5GHz
* Windows 7 Home Premium (64 bit) with all the latest updates for 11/7/2011
* jdk1.6.0_24
* org.apache.sling.launchpad-6-standalone.jar
Reporter: Phil
Assignee: Oliver Lietz
Comment: I marked this as a major because this is the first thing any
potential user tries when they download the project
Steps to reproduce:
* Install the launchpad jar in a blank directory
* Executecurl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some
title http://localhost:8080/content/mynode
* Observe the response:
html
head
meta http-equiv=Content-Type content=text/html;
charset=ISO-8859-1/
titleError 404 NOT_FOUND/title
/head
bodyh2HTTP ERROR 404/h2
pProblem accessing /content/mynode. Reason:
preNOT_FOUND/pre/phr /ismallPowered by
Jetty:///small/ibr/
According to the Discover with sling in 15 minutes this should have created
some content. I had to replace it with:
curl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some
title http://localhost:8080/mynode
One very interesting thing about this was that when I had been using Sling
for some time, the curl command worked. I had to re-install a virgin version
(by running the launchpad jar in a clean directory) to recreate the defect. I
tried to recreate the defect in the version I was using, and even deleted the
'content' node, but that made no difference: in the version I had used for a
while the curl command worked, and in the virgin version it didn't
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3017) improve Karaf integration tests
[ https://issues.apache.org/jira/browse/SLING-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3017: Fix Version/s: Launchpad Karaf Integration Tests 0.1.2 improve Karaf integration tests --- Key: SLING-3017 URL: https://issues.apache.org/jira/browse/SLING-3017 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Integration Tests 0.1.2 Attachments: SLING-3017.patch - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 3.4.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3027) improve Launchpad Karaf features
[ https://issues.apache.org/jira/browse/SLING-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3027: Fix Version/s: Launchpad Karaf Features 0.1.2 improve Launchpad Karaf features Key: SLING-3027 URL: https://issues.apache.org/jira/browse/SLING-3027 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Features 0.1.2 - break down sling-karaf feature into more fine-grained features for better reusability - add descriptions and versions - add more features - update integration tests - update Pax Exam to 3.4.0 - update Karaf to 3.0.0 - update Maven Failsafe Plugin to 2.16 - add workaround for KARAF-1972 - update README - cleanup -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3518) add a multipurpose filter based on Tuckey's UrlRewriteFilter
[ https://issues.apache.org/jira/browse/SLING-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3518: Fix Version/s: URL Rewriter 0.0.2 add a multipurpose filter based on Tuckey's UrlRewriteFilter Key: SLING-3518 URL: https://issues.apache.org/jira/browse/SLING-3518 Project: Sling Issue Type: Task Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: URL Rewriter 0.0.2 http://www.tuckey.org/urlrewrite/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (SLING-3732) add an authentication module using Login with XING
[ https://issues.apache.org/jira/browse/SLING-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3732. --- add an authentication module using Login with XING Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Authentication XING Login 0.0.2 * use the cookie-based “[Login with XING|https://dev.xing.com/plugins/login_with]” for authentication * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (SLING-3731) add an authentication module using XING API with OAuth
[ https://issues.apache.org/jira/browse/SLING-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3731. --- add an authentication module using XING API with OAuth -- Key: SLING-3731 URL: https://issues.apache.org/jira/browse/SLING-3731 Project: Sling Issue Type: New Feature Components: Authentication Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Authentication XING OAuth 0.0.2 * use the [XING API|https://dev.xing.com/docs] with OAuth 1.0 for [authentication|https://dev.xing.com/docs/authentication] * allow creating and updating JCR users based on supplied user data from XING -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (SLING-3649) add a scripting engine for Thymeleaf templates
[ https://issues.apache.org/jira/browse/SLING-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3649. --- add a scripting engine for Thymeleaf templates -- Key: SLING-3649 URL: https://issues.apache.org/jira/browse/SLING-3649 Project: Sling Issue Type: Task Components: Scripting Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.2 * http://www.thymeleaf.org * https://github.com/thymeleaf/thymeleaf -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3017) improve Karaf integration tests
[ https://issues.apache.org/jira/browse/SLING-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3017: Description: - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 4.0.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features was: - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 3.4.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features improve Karaf integration tests --- Key: SLING-3017 URL: https://issues.apache.org/jira/browse/SLING-3017 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Integration Tests 0.1.2 Attachments: SLING-3017.patch - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 4.0.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3815) Add support for X-Content-Type-Options: nosniff
[
https://issues.apache.org/jira/browse/SLING-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084940#comment-14084940
]
Oliver Lietz commented on SLING-3815:
-
[~bdelacretaz] [~asanso] We already have such a filter, though work in
progress: {{contrib/extensions/urlrewriter}} (SLING-3518)
Add support for X-Content-Type-Options: nosniff
Key: SLING-3815
URL: https://issues.apache.org/jira/browse/SLING-3815
Project: Sling
Issue Type: Improvement
Components: Engine
Reporter: Antonio Sanso
Priority: Minor
It would be nice if Sling will have customizable support for
X-Content-Type-Options: nosniff .
This is really useful to defend against some common attack e.g. XSS, Rosetta
Flash etc.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3821) run launchpad integration tests against Sling on Karaf
Oliver Lietz created SLING-3821: --- Summary: run launchpad integration tests against Sling on Karaf Key: SLING-3821 URL: https://issues.apache.org/jira/browse/SLING-3821 Project: Sling Issue Type: Test Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3821) run launchpad integration tests against Sling on Karaf
[
https://issues.apache.org/jira/browse/SLING-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085100#comment-14085100
]
Oliver Lietz commented on SLING-3821:
-
initial version of
{{org.apache.sling.launchpad.karaf-launchpad-integration-tests}} added in
r1615728, all failing tests excluded for now
run launchpad integration tests against Sling on Karaf
--
Key: SLING-3821
URL: https://issues.apache.org/jira/browse/SLING-3821
Project: Sling
Issue Type: Test
Components: Launchpad
Reporter: Oliver Lietz
Assignee: Oliver Lietz
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3017) improve Karaf integration tests
[ https://issues.apache.org/jira/browse/SLING-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1410#comment-1410 ] Oliver Lietz commented on SLING-3017: - [~rombert] Instead of downgrading Pax Exam from 4.x to 3.5 (r1616150) I prefer dropping support for Java 1.6. Pax Exam 4.x targets Java 8 and keeping up with Pax Exam helps finding issues with Pax Exam itself. Can you disable the build with 1.6 for Karaf Launchpad? improve Karaf integration tests --- Key: SLING-3017 URL: https://issues.apache.org/jira/browse/SLING-3017 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Integration Tests 0.1.2 Attachments: SLING-3017.patch - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 4.0.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3017) improve Karaf integration tests
[ https://issues.apache.org/jira/browse/SLING-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102829#comment-14102829 ] Oliver Lietz commented on SLING-3017: - source and target is still 1.6, we just run integration tests on JDK 1.7 and newer (r1618976, see also SM-2359) improve Karaf integration tests --- Key: SLING-3017 URL: https://issues.apache.org/jira/browse/SLING-3017 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Integration Tests 0.1.2 Attachments: SLING-3017.patch - separate testing support and test into own packages and jars - use Maven Failsafe Plugin for tests - update Pax Exam to 4.0.0 - enable test (remove Ignore annotation) - increase timeouts to 30 ms - test features -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3908) embed OGNL to avoid class loading issues
Oliver Lietz created SLING-3908: --- Summary: embed OGNL to avoid class loading issues Key: SLING-3908 URL: https://issues.apache.org/jira/browse/SLING-3908 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3908) embed OGNL to avoid class loading issues
[ https://issues.apache.org/jira/browse/SLING-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3908. - Resolution: Fixed r1622315 embed OGNL to avoid class loading issues Key: SLING-3908 URL: https://issues.apache.org/jira/browse/SLING-3908 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
Oliver Lietz created SLING-3912: --- Summary: add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: Task Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124885#comment-14124885 ] Oliver Lietz commented on SLING-3912: - r1623006 (initial version) add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: Task Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14130563#comment-14130563 ] Oliver Lietz commented on SLING-3912: - r1624367 add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: Task Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3912: Issue Type: New Feature (was: Task) add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: New Feature Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reopened SLING-3912: - add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: New Feature Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3912. - Resolution: Implemented add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: New Feature Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3577) slim down bundle
[ https://issues.apache.org/jira/browse/SLING-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3577. - Resolution: Fixed slim down bundle Key: SLING-3577 URL: https://issues.apache.org/jira/browse/SLING-3577 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit Server 2.1.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR Jackrabbit Server 2.2.0 slim down bundle by not embedding dependencies twice (as lib and inlined) and make use of concurrent and commons-pool bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3576) extend package exports and align versions
[ https://issues.apache.org/jira/browse/SLING-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3576. - Resolution: Fixed extend package exports and align versions - Key: SLING-3576 URL: https://issues.apache.org/jira/browse/SLING-3576 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit Server 2.1.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR Jackrabbit Server 2.2.0 export all packages of embedded jackrabbit-core and lucene-core and align versions of org.apache.sling.jcr.jackrabbit.server.security and org.apache.sling.jcr.jackrabbit.server.security.accessmanager -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3932) Logout as admin does not work
[ https://issues.apache.org/jira/browse/SLING-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14133247#comment-14133247 ] Oliver Lietz commented on SLING-3932: - works with http://svn.apache.org/repos/asf/sling/trunk/samples/fling/ and current bundles from Karaf Launchpad (if that helps) Logout as admin does not work - Key: SLING-3932 URL: https://issues.apache.org/jira/browse/SLING-3932 Project: Sling Issue Type: Bug Components: Launchpad Reporter: Carsten Ziegeler Priority: Blocker Fix For: Launchpad Builder 7 In the sample content, nothing happens when clicking logout as admin, the user is still logged in Not sure in which module the actual problem is. Logging out as a different user seems to work though -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3821) run launchpad integration tests against Sling on Karaf
[
https://issues.apache.org/jira/browse/SLING-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14134034#comment-14134034
]
Oliver Lietz commented on SLING-3821:
-
[~bdelacretaz] Feels like the integration tests are tightly coupled to the
standalone Launchpad (of course from my Karaf Launchpad point of view) e.g.
setting the {{jar.executor.server.port}} in r1625076 and also the tests which
fail with status code {{401}}. But I'm getting closer:
||Tests||Errors||Failures||Skipped||Success Rate||
|534|4|42|1|91.199%|
run launchpad integration tests against Sling on Karaf
--
Key: SLING-3821
URL: https://issues.apache.org/jira/browse/SLING-3821
Project: Sling
Issue Type: Test
Components: Launchpad
Reporter: Oliver Lietz
Assignee: Oliver Lietz
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-3941) NPE in org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory
Oliver Lietz created SLING-3941:
---
Summary: NPE in
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory
Key: SLING-3941
URL: https://issues.apache.org/jira/browse/SLING-3941
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.3.8
Reporter: Oliver Lietz
Priority: Minor
{noformat}
2014-09-16 20:52:04,855 | ERROR | FelixStartLevel | resource
| 154 - org.apache.sling.jcr.resource - 2.3.8 |
[org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory(37)]
The deactivate method has thrown an exception
java.lang.NullPointerException
at
org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.closed(CommonResourceResolverFactoryImpl.java:129)
at
org.apache.sling.resourceresolver.impl.ResourceResolverImpl.close(ResourceResolverImpl.java:145)
at
org.apache.sling.jcr.resource.internal.ObservationListenerSupport.dispose(ObservationListenerSupport.java:74)
at
org.apache.sling.jcr.resource.internal.JcrResourceListener.close(JcrResourceListener.java:122)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory.deactivate(JcrResourceProviderFactory.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)[:1.7.0_60]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_60]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_60]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_60]
at
org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:624)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:508)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:149)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.manager.SingleComponentManager.disposeImplementationObject(SingleComponentManager.java:355)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.manager.SingleComponentManager.deleteComponent(SingleComponentManager.java:170)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.manager.SingleComponentManager.ungetService(SingleComponentManager.java:929)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.scr.impl.manager.SingleComponentManager.ungetService(SingleComponentManager.java:915)[64:org.apache.felix.scr:1.8.2]
at
org.apache.felix.framework.ServiceRegistrationImpl.ungetFactoryUnchecked(ServiceRegistrationImpl.java:349)
at
org.apache.felix.framework.ServiceRegistrationImpl.ungetService(ServiceRegistrationImpl.java:258)
at
org.apache.felix.framework.ServiceRegistry.ungetService(ServiceRegistry.java:399)
at
org.apache.felix.framework.Felix.ungetService(Felix.java:3580)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.BundleContextImpl.ungetService(BundleContextImpl.java:486)
at
org.apache.felix.scr.impl.manager.DependencyManager$AbstractCustomizer.ungetService(DependencyManager.java:240)
at
org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.removedService(DependencyManager.java:390)
at
org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.removedService(DependencyManager.java:304)
at
org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1506)
at
org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1401)
at
org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.untrack(ServiceTracker.java:1261)
at
org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1440)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4419)[org.apache.felix.framework-4.2.1.jar:]
at
org.apache.felix.framework.Felix.access$000(Felix.java:74)[org.apache.felix.framework-4.2.1.jar:]
[jira] [Created] (SLING-3942) restore JSON rendering (without resource type and resource super type)
Oliver Lietz created SLING-3942: --- Summary: restore JSON rendering (without resource type and resource super type) Key: SLING-3942 URL: https://issues.apache.org/jira/browse/SLING-3942 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons JSON 2.0.8 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Commons JSON 2.0.10 see SLING-3008 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3942) restore JSON rendering (without resource type and resource super type)
[ https://issues.apache.org/jira/browse/SLING-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3942. - Resolution: Fixed r1625366 restore JSON rendering (without resource type and resource super type) -- Key: SLING-3942 URL: https://issues.apache.org/jira/browse/SLING-3942 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons JSON 2.0.8 Reporter: Oliver Lietz Assignee: Oliver Lietz Labels: JSON Fix For: Commons JSON 2.0.10 see SLING-3008 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-3944: --- Assignee: Oliver Lietz org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.6, Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3944: Fix Version/s: Scripting Java 2.0.12 org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.6, Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-3944.
-
Resolution: Fixed
{{javax.inject}} removed from bundle in r1625513, use e.g.
{{org.apache.geronimo.specs/geronimo-atinject_1.0_spec/1.0}} with Scripting Java
org.apache.sling.scripting.java bundle exports javax.inject package in wrong
version
Key: SLING-3944
URL: https://issues.apache.org/jira/browse/SLING-3944
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Java 2.0.6, Scripting Java 2.0.10
Reporter: Markus Haack
Assignee: Oliver Lietz
Priority: Critical
Fix For: Scripting Java 2.0.12
The org.apache.sling.scripting.java bundle exports the package javax.inject
in the version of the bundle, which is wrong and should be fixed.
This can lead to bundle version problems for other bundles which depend on
javax.inject in version [1.0,2) - the correct version (like Jersey Web
Services libraries).
Either export javax.inject with version 0.0.0 or even better with the correct
version 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137123#comment-14137123
]
Oliver Lietz commented on SLING-3944:
-
Jackrabbit 2.6 also depends on {{javax.inject}}, so why not use a proper bundle
which can be shared?
org.apache.sling.scripting.java bundle exports javax.inject package in wrong
version
Key: SLING-3944
URL: https://issues.apache.org/jira/browse/SLING-3944
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Java 2.0.10
Reporter: Markus Haack
Assignee: Oliver Lietz
Priority: Critical
Fix For: Scripting Java 2.0.12
The org.apache.sling.scripting.java bundle exports the package javax.inject
in the version of the bundle, which is wrong and should be fixed.
This can lead to bundle version problems for other bundles which depend on
javax.inject in version [1.0,2) - the correct version (like Jersey Web
Services libraries).
Either export javax.inject with version 0.0.0 or even better with the correct
version 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137178#comment-14137178
]
Oliver Lietz commented on SLING-3944:
-
I will revert, although I disagree. We have some bundles which depend on
{{javax.inject}} and I can't see any more deployment complexity by adding
_this_ really common bundle. We have also other bundles which depend on Apache
{{commons-*}} and do not embed those (not that common bundles), but share.
org.apache.sling.scripting.java bundle exports javax.inject package in wrong
version
Key: SLING-3944
URL: https://issues.apache.org/jira/browse/SLING-3944
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Java 2.0.10
Reporter: Markus Haack
Assignee: Oliver Lietz
Priority: Critical
Fix For: Scripting Java 2.0.12
The org.apache.sling.scripting.java bundle exports the package javax.inject
in the version of the bundle, which is wrong and should be fixed.
This can lead to bundle version problems for other bundles which depend on
javax.inject in version [1.0,2) - the correct version (like Jersey Web
Services libraries).
Either export javax.inject with version 0.0.0 or even better with the correct
version 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SLING-3908) embed OGNL to avoid class loading issues
[ https://issues.apache.org/jira/browse/SLING-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3908. --- embed OGNL to avoid class loading issues Key: SLING-3908 URL: https://issues.apache.org/jira/browse/SLING-3908 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SLING-3912) add a sample to show usage with Sling Models and Sling Query
[ https://issues.apache.org/jira/browse/SLING-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3912. --- add a sample to show usage with Sling Models and Sling Query Key: SLING-3912 URL: https://issues.apache.org/jira/browse/SLING-3912 Project: Sling Issue Type: New Feature Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137557#comment-14137557
]
Oliver Lietz commented on SLING-3944:
-
[~justinedelson], [~cziegeler] reverted in r1625589, version added in r1625675
like it does {{org.apache.sling.models.api}}
org.apache.sling.scripting.java bundle exports javax.inject package in wrong
version
Key: SLING-3944
URL: https://issues.apache.org/jira/browse/SLING-3944
Project: Sling
Issue Type: Bug
Components: Scripting
Affects Versions: Scripting Java 2.0.10
Reporter: Markus Haack
Assignee: Oliver Lietz
Priority: Critical
Fix For: Scripting Java 2.0.12
The org.apache.sling.scripting.java bundle exports the package javax.inject
in the version of the bundle, which is wrong and should be fixed.
This can lead to bundle version problems for other bundles which depend on
javax.inject in version [1.0,2) - the correct version (like Jersey Web
Services libraries).
Either export javax.inject with version 0.0.0 or even better with the correct
version 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3821) run launchpad integration tests against Sling on Karaf
[ https://issues.apache.org/jira/browse/SLING-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14143262#comment-14143262 ] Oliver Lietz commented on SLING-3821: - with latest releases we're up to 97.753%: ||Tests||Errors||Failures||Skipped||Success Rate|| |534|1|10|1|97.753%| run launchpad integration tests against Sling on Karaf -- Key: SLING-3821 URL: https://issues.apache.org/jira/browse/SLING-3821 Project: Sling Issue Type: Test Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3575) upgrade Jackrabbit to 2.6.5
[ https://issues.apache.org/jira/browse/SLING-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147861#comment-14147861 ] Oliver Lietz commented on SLING-3575: - We still need to fix the test (SLING-897) for Oak and Jackrabbit 2.6.5. I had a short chat with [~mduerig], but I need to investigate further what fails here. upgrade Jackrabbit to 2.6.5 --- Key: SLING-3575 URL: https://issues.apache.org/jira/browse/SLING-3575 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit Server 2.1.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR Jackrabbit Server 2.2.0 upgrade the embedded jackrabbit-core to 2.6.5 and lucene-core to 3.6.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147863#comment-14147863 ] Oliver Lietz commented on SLING-3944: - Yes. I can do a new release tomorrow. org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3944. - Resolution: Fixed r1625675 org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-3944. --- org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
Oliver Lietz created SLING-3985: --- Summary: update dependency Sling Commons Threads to 3.2.0 Key: SLING-3985 URL: https://issues.apache.org/jira/browse/SLING-3985 Project: Sling Issue Type: Improvement Affects Versions: Event 3.3.14 Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Fix For: Event 3.3.16 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
[ https://issues.apache.org/jira/browse/SLING-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3985: Component/s: Extensions update dependency Sling Commons Threads to 3.2.0 Key: SLING-3985 URL: https://issues.apache.org/jira/browse/SLING-3985 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Event 3.3.14 Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Fix For: Event 3.3.16 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
[ https://issues.apache.org/jira/browse/SLING-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3985: Attachment: SLING-3985.patch update dependency Sling Commons Threads to 3.2.0 Key: SLING-3985 URL: https://issues.apache.org/jira/browse/SLING-3985 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Event 3.3.14 Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Fix For: Event 3.3.16 Attachments: SLING-3985.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-3987) move from Subversion to Git
Oliver Lietz created SLING-3987: --- Summary: move from Subversion to Git Key: SLING-3987 URL: https://issues.apache.org/jira/browse/SLING-3987 Project: Sling Issue Type: Task Components: Best practices Reporter: Oliver Lietz track work for moving to Git https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4058) ResourceResolverProxyTest fails on Oak, 10 second delay in observation
[ https://issues.apache.org/jira/browse/SLING-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181278#comment-14181278 ] Oliver Lietz commented on SLING-4058: - failing test related to observers/events ResourceResolverProxyTest fails on Oak, 10 second delay in observation -- Key: SLING-4058 URL: https://issues.apache.org/jira/browse/SLING-4058 Project: Sling Issue Type: Bug Components: Oak Environment: macosx 10.9.5, java version 1.7.0_45, oak 1.0.7 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz As seen at https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.6 and on my box, tests fail with bq. Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 1 msec, and as a result the test takes age to run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4093) run performance tests to compare with JSP and Sightly
Oliver Lietz created SLING-4093:
---
Summary: run performance tests to compare with JSP and Sightly
Key: SLING-4093
URL: https://issues.apache.org/jira/browse/SLING-4093
Project: Sling
Issue Type: Test
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Scripting Thymeleaf 0.0.6
find out how Thymeleaf performs
[~klcodanr]:
{quote}
1. Performance:
I found JSP to be roughly 10x faster in contrived tests than Sightly. I've
uploaded a package which can be run on an AEM6 instance showing the
performance difference between the JSP and Sightly text components here:
https://www.danklco.com/assets/Sightly%20Performance%20Test.zip
{quote}
http://mail-archives.apache.org/mod_mbox/sling-dev/201410.mbox/%3cCAHbpyFZ0_f6V7jMTzj=zv0f3wvyjs2oyv6cowx3uucwn2n7...@mail.gmail.com%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
[
https://issues.apache.org/jira/browse/SLING-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181332#comment-14181332
]
Oliver Lietz commented on SLING-3985:
-
We would catch up with the interface
{{org.apache.sling.commons.threads.ThreadPool}} and use the same version for
tests and in launchpad.
update dependency Sling Commons Threads to 3.2.0
Key: SLING-3985
URL: https://issues.apache.org/jira/browse/SLING-3985
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Event 3.3.14
Reporter: Oliver Lietz
Assignee: Carsten Ziegeler
Priority: Minor
Fix For: Event 3.4.2
Attachments: SLING-3985.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
[
https://issues.apache.org/jira/browse/SLING-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181747#comment-14181747
]
Oliver Lietz commented on SLING-3985:
-
Looking again closer at it, we already use 3.2.0 in tests and I realized that
{{EventingThreadPool}} is only used internally when trying to create a
bootstrap integration test for Karaf Launchpad a while back (which didn't
work). The uncommon pattern of publishing a concrete class as service and the
usage of {{EventingThreadPool}} in {{AbstractJobQueue}} (1, 2) still look
strange to me. What is the purpose and what is the benefit of not updating?
1.
{noformat}
if ( config.getOwnThreadPoolSize() 0 ) {
this.threadPool = new
EventingThreadPool(services.threadPoolManager, config.getOwnThreadPoolSize());
} else {
this.threadPool = Environment.THREAD_POOL;
}
{noformat}
2.
{noformat}
if ( this.configuration.getOwnThreadPoolSize() 0 ) {
((EventingThreadPool)this.threadPool).release();
}
{noformat}
update dependency Sling Commons Threads to 3.2.0
Key: SLING-3985
URL: https://issues.apache.org/jira/browse/SLING-3985
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Event 3.3.14
Reporter: Oliver Lietz
Assignee: Carsten Ziegeler
Priority: Minor
Fix For: Event 3.4.2
Attachments: SLING-3985.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4093) run performance tests to compare with JSP and Sightly
[
https://issues.apache.org/jira/browse/SLING-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184218#comment-14184218
]
Oliver Lietz commented on SLING-4093:
-
The fix version is Thymeleaf as the package from [~klcodanr] already contains
code for JSP and Sightly and I have to do the Thymeleaf part.
I'm aware of room for performance (and feature) improvements in Scripting
Thymeleaf so this is a good starting point.
As the code at https://github.com/adaptto-conf/2014-sling-rookie-session seems
to work on pure Sling (so no AEM required) I prefer even that for comparison.
[~sseif...@pro-vision.de], can you import your code from GitHub into Sling's
repo or do you prefer pull requests for Thymeleaf at GitHub? [~bdelacretaz]
should know best where it fits in our testing projects.
run performance tests to compare with JSP and Sightly
-
Key: SLING-4093
URL: https://issues.apache.org/jira/browse/SLING-4093
Project: Sling
Issue Type: Test
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Scripting Thymeleaf 0.0.6
find out how Thymeleaf performs
[~klcodanr]:
{quote}
1. Performance:
I found JSP to be roughly 10x faster in contrived tests than Sightly. I've
uploaded a package which can be run on an AEM6 instance showing the
performance difference between the JSP and Sightly text components here:
https://www.danklco.com/assets/Sightly%20Performance%20Test.zip
{quote}
http://mail-archives.apache.org/mod_mbox/sling-dev/201410.mbox/%3cCAHbpyFZ0_f6V7jMTzj=zv0f3wvyjs2oyv6cowx3uucwn2n7...@mail.gmail.com%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3985) update dependency Sling Commons Threads to 3.2.0
[ https://issues.apache.org/jira/browse/SLING-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184220#comment-14184220 ] Oliver Lietz commented on SLING-3985: - Thanks, Carsten. Resolving to _Won't fix_ and keeping status quo? update dependency Sling Commons Threads to 3.2.0 Key: SLING-3985 URL: https://issues.apache.org/jira/browse/SLING-3985 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Event 3.3.14 Reporter: Oliver Lietz Assignee: Carsten Ziegeler Priority: Minor Fix For: Event 3.4.2 Attachments: SLING-3985.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3027) improve Launchpad Karaf features
[ https://issues.apache.org/jira/browse/SLING-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3027: Description: - break down sling-karaf feature into more fine-grained features for better reusability - add descriptions and versions - add more features - update integration tests - update Pax Exam to 4.4.0 - update Karaf to 3.0.2 - update Maven Failsafe Plugin to 2.17 - add workaround for KARAF-1972 - update README - cleanup was: - break down sling-karaf feature into more fine-grained features for better reusability - add descriptions and versions - add more features - update integration tests - update Pax Exam to 3.4.0 - update Karaf to 3.0.0 - update Maven Failsafe Plugin to 2.16 - add workaround for KARAF-1972 - update README - cleanup improve Launchpad Karaf features Key: SLING-3027 URL: https://issues.apache.org/jira/browse/SLING-3027 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Priority: Minor Fix For: Launchpad Karaf Features 0.1.2 - break down sling-karaf feature into more fine-grained features for better reusability - add descriptions and versions - add more features - update integration tests - update Pax Exam to 4.4.0 - update Karaf to 3.0.2 - update Maven Failsafe Plugin to 2.17 - add workaround for KARAF-1972 - update README - cleanup -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4223) make Content Loader extensible to support new import formats
Oliver Lietz created SLING-4223:
---
Summary: make Content Loader extensible to support new import
formats
Key: SLING-4223
URL: https://issues.apache.org/jira/browse/SLING-4223
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Oliver Lietz
The current Content Loader supports a basic set of import formats which are
identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
{{.zip}}.
There is a [user
request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%25bruce.e...@nextissuemedia.com%3e]
to support custom formats like Adobe Folio and [some ideas how to
implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3ca2ab572f-fa83-4ae2-806e-49cce87b9...@adobe.com%3e]:
* we create a new org.apache.sling.contentloader.reader package to be exported
at version 1.0
* move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType) to
that new package
* convert the BaseImportLoader into a standalone ContentReader service holder
used by the DefaultContentImporter and ContentLoaderService components.
* For the ContentReader service interface we define service registration
properties for the service to expose the file name extension (and maybe content
type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4223) make Content Loader extensible to support new import formats
[
https://issues.apache.org/jira/browse/SLING-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-4223:
Fix Version/s: JCR ContentLoader 2.2.0
make Content Loader extensible to support new import formats
Key: SLING-4223
URL: https://issues.apache.org/jira/browse/SLING-4223
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Oliver Lietz
Fix For: JCR ContentLoader 2.2.0
The current Content Loader supports a basic set of import formats which are
identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
{{.zip}}.
There is a [user
request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%25bruce.e...@nextissuemedia.com%3e]
to support custom formats like Adobe Folio and [some ideas how to
implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3ca2ab572f-fa83-4ae2-806e-49cce87b9...@adobe.com%3e]:
* we create a new org.apache.sling.contentloader.reader package to be
exported at version 1.0
* move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType)
to that new package
* convert the BaseImportLoader into a standalone ContentReader service holder
used by the DefaultContentImporter and ContentLoaderService components.
* For the ContentReader service interface we define service registration
properties for the service to expose the file name extension (and maybe
content type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3533: Fix Version/s: JCR ContentLoader 2.2.0 improve error handling and logging in content loader Key: SLING-3533 URL: https://issues.apache.org/jira/browse/SLING-3533 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR ContentLoader 2.1.6 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR ContentLoader 2.2.0 handle errors more appropriate and use proper log levels -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3535) reduce duplicated code in content loader
[
https://issues.apache.org/jira/browse/SLING-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-3535:
Fix Version/s: JCR ContentLoader 2.2.0
reduce duplicated code in content loader
Key: SLING-3535
URL: https://issues.apache.org/jira/browse/SLING-3535
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR ContentLoader 2.1.6
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: JCR ContentLoader 2.2.0
e.g. {{DefaultContentImporter}} and {{Loader}} can share more code in
{{BaseImportLoader}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-3534) separate node name and content type in content loader
[ https://issues.apache.org/jira/browse/SLING-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3534: Fix Version/s: JCR ContentLoader 2.2.0 separate node name and content type in content loader - Key: SLING-3534 URL: https://issues.apache.org/jira/browse/SLING-3534 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR ContentLoader 2.1.6 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR ContentLoader 2.2.0 extend API (node name and content type are currently taken from file name) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3619: Fix Version/s: JCR ContentLoader 2.2.0 Content Loader should handle input errors gracefully Key: SLING-3619 URL: https://issues.apache.org/jira/browse/SLING-3619 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR ContentLoader 2.1.8 Reporter: Yogesh Upadhyay Assignee: Oliver Lietz Priority: Minor Fix For: JCR ContentLoader 2.2.0 After upgrading to latest sling jar file, content loader stopped working to load content using Sling-Initial-Content. Getting following message in log 29.05.2014 23:20:21.504 *INFO* [Background Install /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] org.apache.sling.jcr.contentloader.internal.DefaultContentCreator createFile: Cannot find content type for body.jsp, using application/octet-stream -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3829) Add support for Content-Disposition attachment
[ https://issues.apache.org/jira/browse/SLING-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14239177#comment-14239177 ] Oliver Lietz commented on SLING-3829: - Should also be possible with [UrlRewriteFilter|http://urlrewritefilter.googlecode.com/svn/trunk/src/doc/manual/4.0/index.html] (SLING-3518), no? Add support for Content-Disposition attachment --- Key: SLING-3829 URL: https://issues.apache.org/jira/browse/SLING-3829 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Antonio Sanso Assignee: Antonio Sanso Priority: Minor In some situation will be useful (and safer) to force Content-Disposition attachment for some Content-Type (configurable ) under some specific (and sensitive) path (configurable) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4276) update Thymeleaf to 2.1.4
[
https://issues.apache.org/jira/browse/SLING-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-4276.
-
Resolution: Done
r1649199
update Thymeleaf to 2.1.4
-
Key: SLING-4276
URL: https://issues.apache.org/jira/browse/SLING-4276
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Scripting Thymeleaf 0.0.6
* update Thymeleaf
* update dependencies (unbescape)
* adjust {{AbstractHtmlTemplateParser}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4093) run performance tests to compare with JSP and Sightly
[
https://issues.apache.org/jira/browse/SLING-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304832#comment-14304832
]
Oliver Lietz commented on SLING-4093:
-
[~vladb], how does this relate to Scripting Thymeleaf?
run performance tests to compare with JSP and Sightly
-
Key: SLING-4093
URL: https://issues.apache.org/jira/browse/SLING-4093
Project: Sling
Issue Type: Test
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Scripting Thymeleaf 0.0.6
Attachments:
SLING-4093_-_Performance_tests_to_compare_JSP_and_Sightly.patch
find out how Thymeleaf performs
[~klcodanr]:
{quote}
1. Performance:
I found JSP to be roughly 10x faster in contrived tests than Sightly. I've
uploaded a package which can be run on an AEM6 instance showing the
performance difference between the JSP and Sightly text components here:
https://www.danklco.com/assets/Sightly%20Performance%20Test.zip
{quote}
http://mail-archives.apache.org/mod_mbox/sling-dev/201410.mbox/%3cCAHbpyFZ0_f6V7jMTzj=zv0f3wvyjs2oyv6cowx3uucwn2n7...@mail.gmail.com%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4330) provide a configuration parameter for paths patterns Sightly should handle
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311343#comment-14311343
]
Oliver Lietz commented on SLING-4330:
-
Thanks, [~radu.cotescu]. I've looked into {{SlingScriptAdapterFactory}} and we
should handle it there whichever option we choose (changing issue title
accordingly).
As discussed on
[dev@|http://mail-archives.apache.org/mod_mbox/sling-dev/201501.mbox/%3cCAFkwx-fMUkG8qakdxN=e0etwexqsor01tvtjnqwx+r9icyh...@mail.gmail.com%3e|dev@]
we have two practical options to implement selection of script engines in
{{SlingScriptAdapterFactory}} other than by extension:
*based on resource settings:*
* can (/needs to) be configured by script/template authors per (ancestor) node
(_more freedom for authors_) {noformat}sling:script = [
„html=thymeleaf“,
„js=nashorn“
]{noformat}
* needs to read configuration from repository (_traverse resource hierarchy,
difficult to cache_)
*based on paths patterns in script engine:*
* needs to be configured by admin (_more restrictive_)
* can result in conflicting patterns
* no need to traverse resource hierarchy to find configuration
provide a configuration parameter for paths patterns Sightly should handle
--
Key: SLING-4330
URL: https://issues.apache.org/jira/browse/SLING-4330
Project: Sling
Issue Type: New Feature
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.0
Reporter: Oliver Lietz
Running multiple script engines for same script (template) extension should
be possible.
Scripting Thymeleaf already provides that parameter, see
{{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4330) selection of script engines (in SlingScriptAdapterFactory) other than by extension
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-4330:
Summary: selection of script engines (in SlingScriptAdapterFactory) other
than by extension (was: provide a configuration parameter for paths patterns
Sightly should handle)
selection of script engines (in SlingScriptAdapterFactory) other than by
extension
--
Key: SLING-4330
URL: https://issues.apache.org/jira/browse/SLING-4330
Project: Sling
Issue Type: New Feature
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.0
Reporter: Oliver Lietz
Running multiple script engines for same script (template) extension should
be possible.
Scripting Thymeleaf already provides that parameter, see
{{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4396) make template mode handlers configuration driven
Oliver Lietz created SLING-4396: --- Summary: make template mode handlers configuration driven Key: SLING-4396 URL: https://issues.apache.org/jira/browse/SLING-4396 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.4 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.6 bind life cycle of components to required configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4396) make template mode handlers configuration driven
[ https://issues.apache.org/jira/browse/SLING-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-4396. - Resolution: Implemented r1658198 make template mode handlers configuration driven Key: SLING-4396 URL: https://issues.apache.org/jira/browse/SLING-4396 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Thymeleaf 0.0.4 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Scripting Thymeleaf 0.0.6 bind life cycle of components to required configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4330) selection of script engines (in SlingScriptAdapterFactory) other than by extension
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-4330:
Affects Version/s: (was: Scripting Sightly Engine 1.0.0)
Scripting Core 2.0.28
selection of script engines (in SlingScriptAdapterFactory) other than by
extension
--
Key: SLING-4330
URL: https://issues.apache.org/jira/browse/SLING-4330
Project: Sling
Issue Type: New Feature
Components: Scripting
Affects Versions: Scripting Core 2.0.28
Reporter: Oliver Lietz
Running multiple script engines for same script (template) extension should
be possible.
Scripting Thymeleaf already provides that parameter, see
{{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4330) provide a configuration parameter for paths patterns Sightly should handle
[
https://issues.apache.org/jira/browse/SLING-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14282371#comment-14282371
]
Oliver Lietz commented on SLING-4330:
-
bq. Do I understand it correctly, that you propose to limit a ScriptEngine to
only handle scripts found at a certain location ?
Yes. I'm bringing an application to AEM 6 where different teams from different
companies work on the HTML templating in a round-trip manner. I had to disable
Sightly on AEM 6 as it always kicks in for scripts/templates with extension
{{.html}} and fails. This seems not to be a problem right now as Classic UI is
used for authoring and administration and JSPs besides Thymeleaf for
templating, but could (_will_) be a problem in the future of course. Ideally I
can configure Sightly to only handle scripts e.g. in {{/libs/foundation}} and
{{/apps/client/app2}}.
provide a configuration parameter for paths patterns Sightly should handle
--
Key: SLING-4330
URL: https://issues.apache.org/jira/browse/SLING-4330
Project: Sling
Issue Type: New Feature
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.0
Reporter: Oliver Lietz
Running multiple script engines for same script (template) extension should
be possible.
Scripting Thymeleaf already provides that parameter, see
{{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4298) make BufferedServletOutputStream and CaptureResponseWrapper available to other scripting implementations
[
https://issues.apache.org/jira/browse/SLING-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279928#comment-14279928
]
Oliver Lietz commented on SLING-4298:
-
Got it. Please review r1652353, [~fmeschbe].
make BufferedServletOutputStream and CaptureResponseWrapper available to
other scripting implementations
Key: SLING-4298
URL: https://issues.apache.org/jira/browse/SLING-4298
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Scripting Core 2.0.30, Scripting JSP-Taglib 2.2.6
move private (inner) classes {{BufferedServletOutputStream}} and
{{CaptureResponseWrapper}}
({{org.apache.sling.scripting.jsp.taglib.IncludeTagHandler}}) from _Scripting
JSP Taglib_ to _Scripting Core_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-3829) Add support for Content-Disposition attachment
[
https://issues.apache.org/jira/browse/SLING-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278292#comment-14278292
]
Oliver Lietz commented on SLING-3829:
-
{{mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.urlrewritefilter/4.0.4_1}}
Add support for Content-Disposition attachment
---
Key: SLING-3829
URL: https://issues.apache.org/jira/browse/SLING-3829
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Antonio Sanso
Assignee: Antonio Sanso
Priority: Minor
In some situation will be useful (and safer) to force Content-Disposition
attachment for some Content-Type (configurable ) under some specific (and
sensitive) path (configurable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4147) Remove extensions from package name org.apache.sling.extensions.datasource.internal
[
https://issues.apache.org/jira/browse/SLING-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278459#comment-14278459
]
Oliver Lietz commented on SLING-4147:
-
* {{artifactId}} should be changed from
{{org.apache.sling.extensions.datasource}} to {{org.apache.sling.datasource}}
accordingly
* configuration of {{jacoco-maven-plugin}} needs to be updated
* empty directory
{{src/main/java/org/apache/sling/extensions/datasource/internal}} should be
removed (Git used?)
* test classes should also be moved from
{{src/test/java/org/apache/sling/extensions/datasource}} to
{{src/test/java/org/apache/sling/datasource}}
Remove extensions from package name
org.apache.sling.extensions.datasource.internal
---
Key: SLING-4147
URL: https://issues.apache.org/jira/browse/SLING-4147
Project: Sling
Issue Type: Task
Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Priority: Minor
Fix For: DataSource Provider 1.0.0
DataSource provider bundle currently has {{extensions}} in package name and
configuration pid. As {{extensions}} is mostly related to module location in
Sling svn it would be better to drop it from package name and component pid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-2623) Simplifying usage of JAAS based authentication with Repository in OSGi
[ https://issues.apache.org/jira/browse/SLING-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281845#comment-14281845 ] Oliver Lietz commented on SLING-2623: - [~asanso], [~chetanm]: What else needs to be done here? I would like to pick up SLING-2759. Please see also [Should we remove openid from Sling's launchpad?|https://www.mail-archive.com/dev@sling.apache.org/msg35931.html] Simplifying usage of JAAS based authentication with Repository in OSGi -- Key: SLING-2623 URL: https://issues.apache.org/jira/browse/SLING-2623 Project: Sling Issue Type: New Feature Components: JCR Reporter: Chetan Mehrotra Assignee: Antonio Sanso Attachments: SLING-2623-patch.txt, SLING-2623-svn-compat.diff, SLING-2623.patch, org.apache.sling.jcr.jackrabbit.base-0.0.1-SNAPSHOT-src.tar.gz Currently Sling uses LoginModulePlugin to provide pluggable authentication support. I have been working on a poc to enable similar pluggable support based on JAAS. Complete details are provided at [1]. This work consisted of two parts 1. Simplify usage of JAAS in OSGi env - This is currently being discussed/implemented as a new bundle in Apache Felix. Refer to FELIX-3705 [2] 2. Modify Sling to make use of new JAAS support - This is implemented in Sling fork at [3]. Details about changes required in Sling are provide below This issue is created to capture the overall details. If required separate issues can be created to implement specific parts. All changes can be seen at [3]. Kindly provide your feedback/comments on the proposed approach :) Feature Details === A - New org.apache.sling.jcr.jackrabbit.base bundle A new jar/bundle is added which provide some common classes which simplify Jackrabbit integration in OSGi env. Currently it provides two features * DelegatingLoginModule - This LoginModule acts as a bridge between OSGi and JR layer. It is based on Approach B explained in [1] * PrincipalProviderTracker - It is used to provide an OSGi based PrincipalProviderRegistry which follows the whiteboard pattern to collect PrincipalProviders B - Changes in Jackrabbit Server bundle The Jackrabbit server bundle has been modified to make use of the new features * Repository config is modified to ** Use the DelegatingLoginModule ** Use the OsgiAwareSecurityManager which uses the OSGi based PrincipalProviderRegistry * SlingDefaultLoginModule - A new module is exposed as part of this bundle's API. Any other bundle which earlier implemented the LoginModulePlugin can extend this login module and integrate with Sling Repository authentication * pom.xml - It has been modified to expose the supported LoginModules and certain security related packages C - Changes in Form authentication bundle The Form authentication bundle has been modified to regsiter a LoginModuleFactory. This uses the new approach to provide LoginModules as explained at [2],[4] Changes in Sling section of [1] provides more details on the changes done [1] https://github.com/chetanmeh/c/wiki/Jaas-in-OSGi-with-Jackrabbit-and-Sling [2] https://issues.apache.org/jira/browse/FELIX-3705 [3] https://github.com/chetanmeh/sling/compare/jaas-osgi-adv [4] https://github.com/chetanmeh/c/wiki/JAAS-in-OSGi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-2759) Provide an OpenId Connect Authentication Handler
[ https://issues.apache.org/jira/browse/SLING-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281844#comment-14281844 ] Oliver Lietz commented on SLING-2759: - [~asanso] There is still no release from [Apache Oltu|https://oltu.apache.org] for [OpenID Connect|http://openid.net/connect/] 1.0. Do we need to use a different [library|http://openid.net/developers/libraries/]? Provide an OpenId Connect Authentication Handler Key: SLING-2759 URL: https://issues.apache.org/jira/browse/SLING-2759 Project: Sling Issue Type: Wish Components: Authentication Reporter: Antonio Sanso Assignee: Antonio Sanso It would be nice to provide an OpenId Connect [0] Authentication Handler. Ideally this would leverage Apache Oltu OpenId Connect support [1] and pluggable login module [2] [0] http://openid.net/connect/ [1] https://issues.apache.org/jira/browse/AMBER-24 [2] https://issues.apache.org/jira/browse/SLING-2623 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4298) make BufferedServletOutputStream and CaptureResponseWrapper available to other scripting implementations
[
https://issues.apache.org/jira/browse/SLING-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281859#comment-14281859
]
Oliver Lietz commented on SLING-4298:
-
Same is done by
{{org.apache.sling.scripting.sightly.impl.engine.extension.PrintWriterResponseWrapper}}
in Sightly. We should share one implementation. WDYT, [~radu.cotescu]?
make BufferedServletOutputStream and CaptureResponseWrapper available to
other scripting implementations
Key: SLING-4298
URL: https://issues.apache.org/jira/browse/SLING-4298
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Scripting Core 2.0.30, Scripting JSP-Taglib 2.2.6
move private (inner) classes {{BufferedServletOutputStream}} and
{{CaptureResponseWrapper}}
({{org.apache.sling.scripting.jsp.taglib.IncludeTagHandler}}) from _Scripting
JSP Taglib_ to _Scripting Core_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4330) provide a configuration parameter for paths patterns Sightly should handle
Oliver Lietz created SLING-4330:
---
Summary: provide a configuration parameter for paths patterns
Sightly should handle
Key: SLING-4330
URL: https://issues.apache.org/jira/browse/SLING-4330
Project: Sling
Issue Type: New Feature
Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.0
Reporter: Oliver Lietz
Running multiple script engines for same script (template) extension should be
possible.
Scripting Thymeleaf already provides that parameter, see
{{org.apache.sling.scripting.thymeleaf.SlingTemplateModeHandler#getPatternSpec():org.thymeleaf.PatternSpec}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4411) provide Oak features
Oliver Lietz created SLING-4411:
---
Summary: provide Oak features
Key: SLING-4411
URL: https://issues.apache.org/jira/browse/SLING-4411
Project: Sling
Issue Type: New Feature
Components: Launchpad
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Fix For: Launchpad Karaf Features 0.2.0
provide features for Oak as we have now for Jackrabbit:
* {{oak-sling}}
* {{sling-jcr-oak}}
* {{sling-launchpad-oak}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SLING-1505) add ability to produce multiple karaf features descriptors
[ https://issues.apache.org/jira/browse/SLING-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-1505. --- add ability to produce multiple karaf features descriptors -- Key: SLING-1505 URL: https://issues.apache.org/jira/browse/SLING-1505 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Oliver Lietz Priority: Minor from the discussion in SLING-1499, it seems that we're going to need to provide a separate feature descriptor for servicemix. Ideally, this would be done in the same xml file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
