[jira] [Updated] (SLING-2425) Incorrect and inconsistent escaping of property names used in JcrPropertyMap
[ https://issues.apache.org/jira/browse/SLING-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2425: Fix Version/s: JCR Resource 2.1.0 Incorrect and inconsistent escaping of property names used in JcrPropertyMap Key: SLING-2425 URL: https://issues.apache.org/jira/browse/SLING-2425 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Alexander Klimetschek Assignee: Carsten Ziegeler Fix For: JCR Resource 2.1.0 The JcrPropertyMap uses the (wrong) ISO9075 encoding for property names, and this also behaves differently between the read() and readFully() variants. 1) ISO9075 is needed for XML names, e.g. for mapping JCR names into Xpath queries. But the set of valid JCR names is much larger (for example - is valid, while it is not allowed in ISO9075 and becomes _x002d_). org.apache.jackrabbit.util.Text#escapeIllegalJcrChars() must be used instead to escape any string for use as JCR names. [0] 2) Inconsistency: a) read() will take the key and use ISO9075#encodePath(), before looking up the jcr property using the encoded variant b) readFully() will go through all jcr properties and cache them with the key using ISO9075#decode() Hence for all valid JCR names, which are not valid under ISO9075 (like 1_prop, -foo), these can be looked up using the cached variant b) (as decode() won't touch them), while they cannot be looked up using read() at all due to the forced arbitrary escaping. I think there should be no auto-magically escaping at all (also not in the accompanying JcrModifiablePropertyMap). Incorrect naming errors should simply be passed through, it is the job of the application to handle that. The framework should not run an arbitrary undocumented escaping, if it cannot enforce that anyway, since there are other ways to create properties with a different valid char set (using the JCR API). [0] http://wiki.apache.org/jackrabbit/EncodingAndEscaping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2076: Fix Version/s: (was: JCR Resource 2.1.0) I'm unscheduling this from 2.1.0 to not block the release. I think we a new jcr resource release is overdue :) Make MapEntries more dynamic Key: SLING-2076 URL: https://issues.apache.org/jira/browse/SLING-2076 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Vidar S. Ramdal Assignee: Vidar S. Ramdal In some scenarios it would be nice to be able to store mapping specs other places than under /etc/map (for instance scattered around the repository/resource tree, or in an external XML file). It would be better if the entire map specification was provided by a separate service. The current MapEntries would act as the default implementation. Mailing list discussion: http://markmail.org/thread/5ww634sqarxtudks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2448) org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference
[ https://issues.apache.org/jira/browse/SLING-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2448: --- Attachment: SLING-2448-remove-guava.txt org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference -- Key: SLING-2448 URL: https://issues.apache.org/jira/browse/SLING-2448 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Robert Munteanu Priority: Minor Attachments: SLING-2448-remove-guava.txt, SLING-2448.txt, eclipse-errors.png org.apache.sling.jcr.resource embeds parts of the guava bundle inconsistently. It embeds the Map class, but not the MapDifference interface, which is directly refered from the Maps class. This error is typically flagged in Eclipse with a very cryptic message: 'The project was not built since its build path is incomplete. Cannot find the class file for com.google.common.collect.MapDifference$ValueDifference. Fix the build path then try building this project'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2139) JCR Explorer fails to display data
[
https://issues.apache.org/jira/browse/SLING-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-2139:
---
Component/s: Extensions
Affects Version/s: Sling Explorer 1.0.2
Fix Version/s: Sling Explorer 1.0.4
JCR Explorer fails to display data
--
Key: SLING-2139
URL: https://issues.apache.org/jira/browse/SLING-2139
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Sling Explorer 1.0.2
Environment: IE 9.0.1 or Chrome 12.0.742.112
Window 7 64 bit
org.apache.sling.launchpad-6-standalone.jar
jdk1.6.0_24 (64 bit)
Reporter: Phil
Assignee: Bertrand Delacretaz
Fix For: Sling Explorer 1.0.4
Attachments: SLING-2139.diff, SlingJcrExplorer.png
1: Execute curl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some
title http://localhost:8080/content/mynode1
2: Use a browser and navigate to http://localhost:8080/content/mynode1.json
3: Observe the correct response {title:some
title,sling:resourceType:foo/bar,jcr:primaryType:nt:unstructured}
4: Use the jcrexplorer and navigate to /content/mynode1
5: Observe that the properties title and resourceType are not displayed (see
attached image)
In general sometimes I get data, and sometimes I don't. On occasion if I have
put a json map as the value of the string, I only get the first { displayed
and no other text.
The route I have described is very repeatable, and I have tried it with
multiple browsers, multiple times
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2443) Missing WWW-Authenticate header on OPTIONS request with trunk servlets.resolver bundle
[ https://issues.apache.org/jira/browse/SLING-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2443: --- Comment: was deleted (was: Fixed in revision 1308347) Missing WWW-Authenticate header on OPTIONS request with trunk servlets.resolver bundle -- Key: SLING-2443 URL: https://issues.apache.org/jira/browse/SLING-2443 Project: Sling Issue Type: Bug Components: Servlets Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Fix For: JCR Webdav 2.1.2 Running the launchpad/builder standalone jar from the trunk correctly returns an WWW-Authenticate header on an OPTIONS request with no credentials: $ curl -D - -X OPTIONS http://localhost:8080/ HTTP/1.1 401 Unauthorized WWW-Authenticate: Basic realm=Jackrabbit Webdav Server Content-Type: ... But if I replace the org.apache.sling.servlets.resolver 2.1.0 bundle that's in there with the latest snapshot (revision 1302994) that header is missing: it gets removed by the response.reset() call in DefaultErrorHandlerServlet.sendIntro(...), which makes it impossible to connect with WebDAV. That response.reset() call was not present in 2.1.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2443) Missing WWW-Authenticate header on OPTIONS request with trunk servlets.resolver bundle
[ https://issues.apache.org/jira/browse/SLING-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2443: --- Fix Version/s: JCR Webdav 2.1.2 Fixed in revision 1308347 Missing WWW-Authenticate header on OPTIONS request with trunk servlets.resolver bundle -- Key: SLING-2443 URL: https://issues.apache.org/jira/browse/SLING-2443 Project: Sling Issue Type: Bug Components: Servlets Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Fix For: JCR Webdav 2.1.2 Running the launchpad/builder standalone jar from the trunk correctly returns an WWW-Authenticate header on an OPTIONS request with no credentials: $ curl -D - -X OPTIONS http://localhost:8080/ HTTP/1.1 401 Unauthorized WWW-Authenticate: Basic realm=Jackrabbit Webdav Server Content-Type: ... But if I replace the org.apache.sling.servlets.resolver 2.1.0 bundle that's in there with the latest snapshot (revision 1302994) that header is missing: it gets removed by the response.reset() call in DefaultErrorHandlerServlet.sendIntro(...), which makes it impossible to connect with WebDAV. That response.reset() call was not present in 2.1.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2139) JCR Explorer fails to display data
[
https://issues.apache.org/jira/browse/SLING-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert A. Decker updated SLING-2139:
Attachment: SLING-2139.diff
Added a second replace to replace '/' with '_' just like it was already
replacing ':' with '_'.
JCR Explorer fails to display data
--
Key: SLING-2139
URL: https://issues.apache.org/jira/browse/SLING-2139
Project: Sling
Issue Type: Bug
Environment: IE 9.0.1 or Chrome 12.0.742.112
Window 7 64 bit
org.apache.sling.launchpad-6-standalone.jar
jdk1.6.0_24 (64 bit)
Reporter: Phil
Attachments: SLING-2139.diff, SlingJcrExplorer.png
1: Execute curl -u admin:admin -Fsling:resourceType=foo/bar -Ftitle=some
title http://localhost:8080/content/mynode1
2: Use a browser and navigate to http://localhost:8080/content/mynode1.json
3: Observe the correct response {title:some
title,sling:resourceType:foo/bar,jcr:primaryType:nt:unstructured}
4: Use the jcrexplorer and navigate to /content/mynode1
5: Observe that the properties title and resourceType are not displayed (see
attached image)
In general sometimes I get data, and sometimes I don't. On occasion if I have
put a json map as the value of the string, I only get the first { displayed
and no other text.
The route I have described is very repeatable, and I have tried it with
multiple browsers, multiple times
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2311) Sling Performance Testing tool
[ https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-2311: - Attachment: ResolveWithManyVanityPath.png attaching possible outcome of this performance framework Sling Performance Testing tool -- Key: SLING-2311 URL: https://issues.apache.org/jira/browse/SLING-2311 Project: Sling Issue Type: New Feature Components: Testing Reporter: Antonio Sanso Assignee: Carsten Ziegeler Priority: Minor Attachments: ResolveWithManyAliasTest.java, ResolveWithManyVanityPath.png, SLING-2311-patch.txt As described/discussed in [0] it would be nice to have a performance test tool in Sling . This can be useful in different situations (e.g. micro benchmarks of a feature and so on). Patch to follow [0] http://sling.markmail.org/message/bz44im7aqeae4r57 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2311) Sling Performance Testing tool
[ https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-2311: - Attachment: ResolveWithManyAliasTest.java Adding new test case covering the scenario discussed in [0] sling:alias support. It tests node having 1000 children and resource not found. Here the outcome of the test with sling:alias support enabled jcr.resource-2.0.11 51 57 76 263 546 and with sling:alias support disabled jcr.resource-2.0.110 0 0 1 48 [0] http://sling.markmail.org/message/mlbw237hchhcyv6s Sling Performance Testing tool -- Key: SLING-2311 URL: https://issues.apache.org/jira/browse/SLING-2311 Project: Sling Issue Type: New Feature Components: Testing Reporter: Antonio Sanso Assignee: Carsten Ziegeler Priority: Minor Attachments: ResolveWithManyAliasTest.java, SLING-2311-patch.txt As described/discussed in [0] it would be nice to have a performance test tool in Sling . This can be useful in different situations (e.g. micro benchmarks of a feature and so on). Patch to follow [0] http://sling.markmail.org/message/bz44im7aqeae4r57 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2450) JcrInstaller generates incorrect node name in /apps/system/config (or else the installer doesn't process the nodename properly)
[ https://issues.apache.org/jira/browse/SLING-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2450: Affects Version/s: Installer Core 3.3.4 Installer Configuration Factory 1.0.4 Fix Version/s: Installer Configuration Factory 1.0.6 JCR Installer 3.1.4 Installer Core 3.3.6 JcrInstaller generates incorrect node name in /apps/system/config (or else the installer doesn't process the nodename properly) --- Key: SLING-2450 URL: https://issues.apache.org/jira/browse/SLING-2450 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.3.4, JCR Installer 3.1.2, Installer Configuration Factory 1.0.4 Reporter: Tyson Norris Assignee: Carsten Ziegeler Fix For: Installer Core 3.3.6, JCR Installer 3.1.4, Installer Configuration Factory 1.0.6 when using ConfigurationAdmin or osgi web console to create a config for a ManagedServiceFactory, a nt:file node is created in /apps/system/config with a node name like: com.adobe.granite.auth.oauth.provider.com.adobe.granite.auth.oauth.provider.99bd39e3-4367-47b0-a5a2-b4e1a0f8a5b9.config The installer, however will not process the node (and create the managed service propertly) unless the node name is formatted like: com.adobe.granite.auth.oauth.provider-99bd39e3-4367-47b0-a5a2-b4e1a0f8a5b9.config Note that: - com.adobe.granite.auth.oauth.provider string only occurs once - there is a dash - after provider I'm not sure which problem it is, but it may be one of: - the JcrInstaller generates the wrong node name - OR the JcrInstaller does not process the node name properly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding
[
https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Peter updated SLING-2449:
-
Attachment:
SLING-2449_background_servlets__enable_tracking_of_user,_status-code,_content-type,_length.patch
Taken against revision 1231138
background servlets: enable tracking of user, status-code, content-type,
length and encoding
Key: SLING-2449
URL: https://issues.apache.org/jira/browse/SLING-2449
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Ben Peter
Labels: patch
Attachments:
SLING-2449_background_servlets__enable_tracking_of_user,_status-code,_content-type,_length.patch
Enable background jobs to store the user on whose behalf the request was
backgrounded
Enable background job to store the following data from the result of the
backgrounded request:
* HTTP Status
* Status Message
* Content-Type
* Content-Length
* Character-Encoding
Change {{JobStreamServlet}} to return the stored data appropriately
Change {{JobConsolePlugin}} to display information on User, Status Code and
Message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2449) background servlets: enable tracking of user, status-code, content-type, length and encoding
[
https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Peter updated SLING-2449:
-
Labels: patch (was: )
background servlets: enable tracking of user, status-code, content-type,
length and encoding
Key: SLING-2449
URL: https://issues.apache.org/jira/browse/SLING-2449
Project: Sling
Issue Type: Improvement
Components: Extensions
Reporter: Ben Peter
Labels: patch
Attachments:
SLING-2449_background_servlets__enable_tracking_of_user,_status-code,_content-type,_length.patch
Enable background jobs to store the user on whose behalf the request was
backgrounded
Enable background job to store the following data from the result of the
backgrounded request:
* HTTP Status
* Status Message
* Content-Type
* Content-Length
* Character-Encoding
Change {{JobStreamServlet}} to return the stored data appropriately
Change {{JobConsolePlugin}} to display information on User, Status Code and
Message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2448) org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference
[ https://issues.apache.org/jira/browse/SLING-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2448: --- Attachment: eclipse-errors.png org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference -- Key: SLING-2448 URL: https://issues.apache.org/jira/browse/SLING-2448 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Robert Munteanu Priority: Minor Attachments: SLING-2448.txt, eclipse-errors.png org.apache.sling.jcr.resource embeds parts of the guava bundle inconsistently. It embeds the Map class, but not the MapDifference interface, which is directly refered from the Maps class. This error is typically flagged in Eclipse with a very cryptic message: 'The project was not built since its build path is incomplete. Cannot find the class file for com.google.common.collect.MapDifference$ValueDifference. Fix the build path then try building this project'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2441) AuthenticationInfo.put() throws if method is null
[ https://issues.apache.org/jira/browse/SLING-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2441: -- Fix Version/s: Auth Core 1.1.0 AuthenticationInfo.put() throws if method is null - Key: SLING-2441 URL: https://issues.apache.org/jira/browse/SLING-2441 Project: Sling Issue Type: Bug Components: Authentication Affects Versions: Auth Core 1.0.6 Reporter: Jeff Young Assignee: Justin Edelson Labels: newbie, patch Fix For: Auth Core 1.1.0 Attachments: auth_info_put.patch Historically the AUTH_TYPE of an AuthenitcationInfo had to be defined (ie: non-null), but we're now using it for anonymous access as well, with a null AUTH_TYPE. The put() method, however, throws if passed a null AUTH_TYPE. (This is triggered, for instance, by CQ's AuthenticationInfoPostProcessorBridge, which does a putAll().) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2446) Add support for BigDecimal JCR values
[
https://issues.apache.org/jira/browse/SLING-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-2446:
--
Issue Type: New Feature (was: Bug)
Add support for BigDecimal JCR values
-
Key: SLING-2446
URL: https://issues.apache.org/jira/browse/SLING-2446
Project: Sling
Issue Type: New Feature
Components: JCR
Reporter: Jeff Young
Assignee: Justin Edelson
Labels: newbie, patch
Fix For: JCR Resource 2.1.0
JCR supports the typehint {Decimal} for java.math.BigDecimal, but
JcrPropertyMap doesn't know about it so doing a map.get(propName,
BigDecimal.class) returns null.
Likewise, you should be able to adapt a Property Resource into a BigDecimal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2446) Add support for BigDecimal JCR values
[
https://issues.apache.org/jira/browse/SLING-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-2446:
--
Description:
JCR supports the typehint {Decimal} for java.math.BigDecimal, but
JcrPropertyMap doesn't know about it so doing a map.get(propName,
BigDecimal.class) returns null.
Likewise, you should be able to adapt a Property Resource into a BigDecimal.
was:JCR supports the typehint {Decimal} for java.math.BigDecimal, but
JcrPropertyMap doesn't know about it so doing a map.get(propName,
BigDecimal.class) returns null.
Summary: Add support for BigDecimal JCR values (was: JCR-1609 added
DecimalType, but it didn't get in to Sling's JcrPropertyMap)
Add support for BigDecimal JCR values
-
Key: SLING-2446
URL: https://issues.apache.org/jira/browse/SLING-2446
Project: Sling
Issue Type: Bug
Components: JCR
Reporter: Jeff Young
Assignee: Justin Edelson
Labels: newbie, patch
Fix For: JCR Resource 2.1.0
JCR supports the typehint {Decimal} for java.math.BigDecimal, but
JcrPropertyMap doesn't know about it so doing a map.get(propName,
BigDecimal.class) returns null.
Likewise, you should be able to adapt a Property Resource into a BigDecimal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2446) Add support for BigDecimal JCR values
[
https://issues.apache.org/jira/browse/SLING-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Young updated SLING-2446:
--
Attachment: BigDecimal_tests_.patch
Add support for BigDecimal JCR values
-
Key: SLING-2446
URL: https://issues.apache.org/jira/browse/SLING-2446
Project: Sling
Issue Type: New Feature
Components: JCR
Reporter: Jeff Young
Assignee: Justin Edelson
Labels: newbie, patch
Fix For: JCR Resource 2.1.0
Attachments: BigDecimal_tests_.patch
JCR supports the typehint {Decimal} for java.math.BigDecimal, but
JcrPropertyMap doesn't know about it so doing a map.get(propName,
BigDecimal.class) returns null.
Likewise, you should be able to adapt a Property Resource into a BigDecimal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2448) org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference
[ https://issues.apache.org/jira/browse/SLING-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2448: --- Attachment: SLING-2448.txt org.apache.sling.jcr.resource should embed com.google.common.collect.MapDifference -- Key: SLING-2448 URL: https://issues.apache.org/jira/browse/SLING-2448 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Robert Munteanu Priority: Minor Attachments: SLING-2448.txt org.apache.sling.jcr.resource embeds parts of the guava bundle inconsistently. It embeds the Map class, but not the MapDifference interface, which is directly refered from the Maps class. This error is typically flagged in Eclipse with a very cryptic message: 'The project was not built since its build path is incomplete. Cannot find the class file for com.google.common.collect.MapDifference$ValueDifference. Fix the build path then try building this project'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2441) AuthenticationInfo.put() throws if method is null
[ https://issues.apache.org/jira/browse/SLING-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2441: -- Attachment: auth_info_put.patch AuthenticationInfo.put() throws if method is null - Key: SLING-2441 URL: https://issues.apache.org/jira/browse/SLING-2441 Project: Sling Issue Type: Bug Components: Authentication Affects Versions: Auth Core 1.0.6 Reporter: Jeff Young Labels: newbie, patch Attachments: auth_info_put.patch Historically the AUTH_TYPE of an AuthenitcationInfo had to be defined (ie: non-null), but we're now using it for anonymous access as well, with a null AUTH_TYPE. The put() method, however, throws if passed a null AUTH_TYPE. (This is triggered, for instance, by CQ's AuthenticationInfoPostProcessorBridge, which does a putAll().) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2432) java.lang.NoClassDefFoundError when using Freemarker ScriptingEngine [patch included]
[ https://issues.apache.org/jira/browse/SLING-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2432: -- Fix Version/s: Scripting Freemarker 2.0.0 java.lang.NoClassDefFoundError when using Freemarker ScriptingEngine [patch included] - Key: SLING-2432 URL: https://issues.apache.org/jira/browse/SLING-2432 Project: Sling Issue Type: Bug Components: Scripting Reporter: Sean Kleinjung Assignee: Justin Edelson Labels: freemarker, patch, scripting Fix For: Scripting Freemarker 2.0.0 Attachments: Removed_Freemarker_script_engine_dependency_on_slf4j_.patch The most recent 2.0.0-SNAPSHOT of org.apache.sling.scripting.freemarker contains a direct dependency on org.slf4j.Logger and org.slf4j.LoggerFactory. This bundle explicitly does NOT import these packages, however, and so at runtime script execution will fail with a NoClassDefFoundError because the org.apache.sling.scripting.freemarker.FreemarkerScriptEngine class cannot be initialized. Freemarker provides a suitable logging facility that will degrade gracefully if slf4j is missing, but the aforementioned FreemarkerScriptEngine class does not utilize it. The attached patch removes the slf4j dependency, and resolves this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2439) Move Launchpad API embedding to launchpad base bundle
[ https://issues.apache.org/jira/browse/SLING-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2439: - Attachment: SLING-2439.patch Proposed patch moving the launchpad API to the launchpad base bundle Move Launchpad API embedding to launchpad base bundle - Key: SLING-2439 URL: https://issues.apache.org/jira/browse/SLING-2439 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.3.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.4.0 Attachments: SLING-2439.patch Currently the Launchpad API classes are in the Launchpad Base launcher code (standalone app or web app) and are inherited through the class loader hierarchy by the launchpad base bundle and exposed through system bundle exports into the OSGi Framework. This would be ok, if the launcher would actually use/require the launchpad API. This is not the case. On the other hand, this setup prevents updating existing Sling setups with a new launchpad base bundle because newer builds require up-to-date launchpad API. Since the launcher does not use the launchpad API it is more appropriate to actually include the launchpad API with the Launchpad Base bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2434) Sling Lauchpad pulls in dependency not available on Maven Central
[ https://issues.apache.org/jira/browse/SLING-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2434: --- Remaining Estimate: 0.05h Original Estimate: 0.05h Sling Lauchpad pulls in dependency not available on Maven Central - Key: SLING-2434 URL: https://issues.apache.org/jira/browse/SLING-2434 Project: Sling Issue Type: Bug Components: Maven Plugins and Archetypes Affects Versions: Maven Launchpad Plugin 2.1.0 Reporter: Robert Munteanu Priority: Minor Original Estimate: 0.05h Remaining Estimate: 0.05h The ./maven/maven-launchpad-plugin/pom.xml file contains a reference org.drools:drools-compiler:5.1.1 and to the jboss Maven repository. POMs declaring external repositories have been historically allowed on Maven Central, but that practice is discouraged [discouraged|http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/] and being [phased out|http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/]. Versions 5.2.0.Final to 5.4.0.Beta2 are available on Maven Central and should be preferred. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2426) SlingSafeMethodsServlet's default HEAD implementation not completely RFC compliant
[ https://issues.apache.org/jira/browse/SLING-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Pruessmann updated SLING-2426: Affects Version/s: (was: Servlets Get 2.1.2) API 2.2.0 SlingSafeMethodsServlet's default HEAD implementation not completely RFC compliant -- Key: SLING-2426 URL: https://issues.apache.org/jira/browse/SLING-2426 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: API 2.2.0 Reporter: Boris Pruessmann RFC 2616 states: The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The current implementation of the SlingSafeMethodsServlet does not guarantee what's stated above - if the GET call's response gets too big, the servlet engine might switch to chunked transfer. However, the HEAD call returns a valid Content-Length header no matter what, resulting in HEAD returning different headers than the corresponding GET call. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2427) HtmlRendererServlet allows outputting arbitrary HTML
[ https://issues.apache.org/jira/browse/SLING-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Hall updated SLING-2427: - Description: When using HtmlRendererServlet to return content in an HTML format, it is possible to inject arbitrary HTML into the returned page. To reproduce: 1. Add a node of content * curl -u admin:admin -F test=true http://localhost:8080/test_node 2. Get the new node in HTML format and append extra data to the URL * http://localhost:8080/test_node.html/font size='88' color='red'VOTE SLING/fontiframe height=800 width=600 src='http://www.uva.nl' //iframe JIRA will escape the above URL. The unescaped URL is here: http://pastie.org/3451245 was: When using HtmlRendererServlet to return content in an HTML format, it is possible to inject arbitrary HTML into the returned page. To reproduce: 1. Add a node of content * curl -u admin:admin -F test=true http://localhost:8080/test_node 2. Get the new node in HTML format and append extra data to the URL * http://localhost:8080/test_node.html/font size='88' color='red'VOTE SLING/fontiframe height=800 width=600 src='http://www.uva.nl' //iframe HtmlRendererServlet allows outputting arbitrary HTML Key: SLING-2427 URL: https://issues.apache.org/jira/browse/SLING-2427 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.2 Reporter: Carl Hall Assignee: Carl Hall When using HtmlRendererServlet to return content in an HTML format, it is possible to inject arbitrary HTML into the returned page. To reproduce: 1. Add a node of content * curl -u admin:admin -F test=true http://localhost:8080/test_node 2. Get the new node in HTML format and append extra data to the URL * http://localhost:8080/test_node.html/font size='88' color='red'VOTE SLING/fontiframe height=800 width=600 src='http://www.uva.nl' //iframe JIRA will escape the above URL. The unescaped URL is here: http://pastie.org/3451245 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2411) ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently
[ https://issues.apache.org/jira/browse/SLING-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2411: -- Fix Version/s: API 2.2.6 JCR Resource 2.1.0 Assignee: Justin Edelson setting fix versions ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently --- Key: SLING-2411 URL: https://issues.apache.org/jira/browse/SLING-2411 Project: Sling Issue Type: Improvement Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.1.0, API 2.2.6 Attachments: SLING-2411-jsedding.patch The ResourceDecorator currently has two methods: decorate(Resource) decorate(Resource, HttpServletRequest) The JcrResourceResolver uses the latter method when resolve(HttpServletRequest,String) is invoked. In all other cases, the former method is used. This behavior is correct. However, the JcrResourceResolver (and any future ResourceResolver implementation for that matter) really doesn't have any control over how it is invoked. For example, at present sling:include and sling:forward call resolve(String), not resolve(HttpServletRequest,String) (see http://s.apache.org/lL5). But even if we did a code audit within Sling and fixed all the cases like this, we don't have any control over downstream applications which may or may not invoke the two-argument resolve() method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2411) ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently
[ https://issues.apache.org/jira/browse/SLING-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2411: -- Component/s: JCR API ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently --- Key: SLING-2411 URL: https://issues.apache.org/jira/browse/SLING-2411 Project: Sling Issue Type: Improvement Components: API, JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.1.0, API 2.2.6 Attachments: SLING-2411-jsedding.patch The ResourceDecorator currently has two methods: decorate(Resource) decorate(Resource, HttpServletRequest) The JcrResourceResolver uses the latter method when resolve(HttpServletRequest,String) is invoked. In all other cases, the former method is used. This behavior is correct. However, the JcrResourceResolver (and any future ResourceResolver implementation for that matter) really doesn't have any control over how it is invoked. For example, at present sling:include and sling:forward call resolve(String), not resolve(HttpServletRequest,String) (see http://s.apache.org/lL5). But even if we did a code audit within Sling and fixed all the cases like this, we don't have any control over downstream applications which may or may not invoke the two-argument resolve() method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2412) add peak call and recursion depth statistics to RequestProcessor mbean
[ https://issues.apache.org/jira/browse/SLING-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2412: -- Assignee: Justin Edelson add peak call and recursion depth statistics to RequestProcessor mbean -- Key: SLING-2412 URL: https://issues.apache.org/jira/browse/SLING-2412 Project: Sling Issue Type: Improvement Components: Engine Reporter: Justin Edelson Assignee: Justin Edelson The SlingMainServlet has include and recursion depth limit setting, but there's no way to determine what the peak level actually is. These should be available via JMX. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2411) ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently
[ https://issues.apache.org/jira/browse/SLING-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-2411: -- Attachment: SLING-2411-jsedding.patch I attached a patch to illustrate what I have in mind. Currently, I am not 100% satisfied with the patch, but maybe someone has a good idea, how to address the following issues. 1. The RequestScopedResourceResolverWrapper class needs to be exported from the bundle, if it should be available for use by e.g. the ResourceDecoratorTracker. Should it be in the API bundle or exported by the engine bundle (that's how it's done in the patch)? My gut feeling is that the ResourceDecorator(Tracker) does not actually belong into the jcr.resources bundle. This should become more evident when the ResourceResolver is decoupled from the JCR-ResourceProvider (see SLING-2396). 2. I'm not certain whether it can be dangerous/undesired that RequestScopedResourceResolverWrapper redirects map(String) to map(Request, String). Eventually, if we decide to go down this route, it may make sense to allow registering ResourceResolverDecorator services, in a similar way to the current ResourceDecorator services. Curiously, I belive that the ResourceDecorator mechanism could be fairly easily implemented as a ResourceResolverDecorator. ResourceDecorator(Resource, HttpServletRequest) doesn't get called consistently --- Key: SLING-2411 URL: https://issues.apache.org/jira/browse/SLING-2411 Project: Sling Issue Type: Improvement Reporter: Justin Edelson Attachments: SLING-2411-jsedding.patch The ResourceDecorator currently has two methods: decorate(Resource) decorate(Resource, HttpServletRequest) The JcrResourceResolver uses the latter method when resolve(HttpServletRequest,String) is invoked. In all other cases, the former method is used. This behavior is correct. However, the JcrResourceResolver (and any future ResourceResolver implementation for that matter) really doesn't have any control over how it is invoked. For example, at present sling:include and sling:forward call resolve(String), not resolve(HttpServletRequest,String) (see http://s.apache.org/lL5). But even if we did a code audit within Sling and fixed all the cases like this, we don't have any control over downstream applications which may or may not invoke the two-argument resolve() method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2418) registering a legacy SlingPostOperation wihout a causes the proxy provider to fail to activate, preventing other legacy operations from being registered
[ https://issues.apache.org/jira/browse/SLING-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2418: -- Summary: registering a legacy SlingPostOperation wihout a causes the proxy provider to fail to activate, preventing other legacy operations from being registered (was: registering a legacy SlingPostOperation wihout a name property fails) registering a legacy SlingPostOperation wihout a causes the proxy provider to fail to activate, preventing other legacy operations from being registered -- Key: SLING-2418 URL: https://issues.apache.org/jira/browse/SLING-2418 Project: Sling Issue Type: Bug Reporter: Justin Edelson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2419) SlingTestBase, SlingRemoteTestRunner, and SlingRemoteExecutionRule should support the ability to use non-default credentials
[ https://issues.apache.org/jira/browse/SLING-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Adamcin updated SLING-2419: Attachment: madamcin_added_test_server_username_and_test_server_password_properties.patch I added support for test.server.username and test.server.password properties to the SlingTestBase and SlingRemoteTestRunner classes for specifying a non-default set of credentials for server readiness checking and for remote execution of sling junit tests. I also added constructor overloads to several classes to accept a username and password as arguments, and added getters to SlingTestBase to expose those values to integration tests for use in other HTTP requests. Finally, for the sake of completeness, I updated the sample integration test pom to demonstrate the use of these properties. SlingTestBase, SlingRemoteTestRunner, and SlingRemoteExecutionRule should support the ability to use non-default credentials Key: SLING-2419 URL: https://issues.apache.org/jira/browse/SLING-2419 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: JUnit Remote Tests Runners 1.0.6, Sample Integration Tests 1.0.6, org.apache.sling.testing.tools 1.0.4 Environment: Windows 7 64bit, Maven 3.0.3, Adobe CQ 5.4 Reporter: Mark Adamcin Priority: Minor Fix For: JUnit Remote Tests Runners 1.0.8, Sample Integration Tests 1.0.8, org.apache.sling.testing.tools 1.0.6 Attachments: madamcin_added_test_server_username_and_test_server_password_properties.patch For those who have gotten to the point of using the sling junit framework on an IT administered CQ5 development server, the fact that default admin credentials are hardcoded throughout the testing modules will present an inconvenient problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2413) RequestProcessorMBeanImpl needs internal refactoring to be extended
[ https://issues.apache.org/jira/browse/SLING-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2413: -- Component/s: Engine RequestProcessorMBeanImpl needs internal refactoring to be extended --- Key: SLING-2413 URL: https://issues.apache.org/jira/browse/SLING-2413 Project: Sling Issue Type: Improvement Components: Engine Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Engine 2.2.6 the instance variable names are too generic (min/max/sum) and the add data method is too specific. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2364) ResourceUtil should provide a method to get the parent on an arbitrary level
[ https://issues.apache.org/jira/browse/SLING-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya Atreya updated SLING-2364: Attachment: getParent.patch Patch for String getParent(String path, int level); and associated tests. ResourceUtil should provide a method to get the parent on an arbitrary level Key: SLING-2364 URL: https://issues.apache.org/jira/browse/SLING-2364 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.2.2 Reporter: Konrad Windszus Attachments: getParent.patch Please provide the method String getAbsoluteParent(String path, int level) to return the parent path on the given level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2404) maven-sling-plugin install-file goal needs to support Maven artifacts that use classifiers in their coordinates
[ https://issues.apache.org/jira/browse/SLING-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig S. Dickson updated SLING-2404: Attachment: SLING-2404.diff Proposed resolution to 2404. Changes are contained to the org.apache.sling.maven.bundlesupport.BundleInstallFileMojo class only. maven-sling-plugin install-file goal needs to support Maven artifacts that use classifiers in their coordinates --- Key: SLING-2404 URL: https://issues.apache.org/jira/browse/SLING-2404 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven Sling Plugin 2.1.0 Reporter: Craig S. Dickson Attachments: SLING-2404.diff Users should be able to specify an additional plugin configuration property for the install-file goal that would allow an artifact classifer to be used when resolving artifacts (in addition to groupId, artifactId, version and type). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2398) Sling Mappings creates new threads to reload mappings
[ https://issues.apache.org/jira/browse/SLING-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hakim Sadikali updated SLING-2398: -- Attachment: MapEntries.java a possible patch. Sling Mappings creates new threads to reload mappings - Key: SLING-2398 URL: https://issues.apache.org/jira/browse/SLING-2398 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Hakim Sadikali Labels: performance Attachments: MapEntries.java Original Estimate: 1h Remaining Estimate: 1h Whenever the /etc/map or a sling:vanityPath, sling:vanityOrder or sling:redirect is modified a new thread is created to recreate the maps. If these values get modified very quickly, then its possible to create too many new threads and kill the system. A better implementation would be to check to see if a thread is running and reuse that thread. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1974) Accept header issues in the Sling POST Servlet
[ https://issues.apache.org/jira/browse/SLING-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1974: Fix Version/s: (was: Servlets Post 2.1.2) Servlets Post 2.1.4 Moved to next version Accept header issues in the Sling POST Servlet -- Key: SLING-1974 URL: https://issues.apache.org/jira/browse/SLING-1974 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Post 2.1.0 Reporter: Felix Meschberger Fix For: Servlets Post 2.1.4 Attachments: SLING-1974.patch As of SLING-1336 the Sling POST Servlet can interpret the Accept request header to select what response content type to render. Unfortunately that handling seems broken as for an Accept header like (as generated by FireFox with the JSONovich plugin installed) : Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,application/json the JSON response might be selected but sometimes also text/html (we can observe both behaviours for different server platforms with our application). The Accept header should probably consider equivalent q values (as for text/html and application/json in the example) to solve the tie by selecting the first type list; thus text/html in this example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2217) Need a good way to downgrade a bundle
[ https://issues.apache.org/jira/browse/SLING-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Khoury updated SLING-2217: - Comment: was deleted (was: I will be out of the office until Monday. Please contact my manager Eren Aydin eay...@adobe.com in my absense. Thanks, Andrew ) Need a good way to downgrade a bundle - Key: SLING-2217 URL: https://issues.apache.org/jira/browse/SLING-2217 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.2.0 Reporter: Andrew Khoury Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.3.0 The JCR install module should allow for downgrading to an older version of a bundle if the bundle jar is replaced. This is relevant when you do a release of a bundle in a QA or Staging environment and later decide that the release should be rolled back to the old version. It might make sense to just to simplify things by reinstalling the bundle to the osgi container whenever the jar file is replaced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2386) It should be possible to remove bundles from an inherited partial bundle list
[ https://issues.apache.org/jira/browse/SLING-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timo Naroska updated SLING-2386: Attachment: SLING-2386.patch It should be possible to remove bundles from an inherited partial bundle list - Key: SLING-2386 URL: https://issues.apache.org/jira/browse/SLING-2386 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Maven Launchpad Plugin 2.1.2 Attachments: SLING-2386.patch When a bundle list / launchpad project depends on a partial bundle list, it gets all the bundles from that list included. In some cases, it would be nice to exclude some of them to be able to replace them with a different implementation/bundle The easiest way would be to allow something like: startLevel level=remove bundle groupIdcommons-io/groupId artifactIdcommons-io/artifactId /bundle /startLevel in the bundle list. The version information is optional, If it is specified the bundle is only removed if it matches the given version or version range -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2369) upgrade Felix to 4.0.2
[ https://issues.apache.org/jira/browse/SLING-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timo Naroska updated SLING-2369: Attachment: SLING-2369-2.diff Also update Java platform package exports to be in sync with felix.framework/default.properties. upgrade Felix to 4.0.2 -- Key: SLING-2369 URL: https://issues.apache.org/jira/browse/SLING-2369 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.3.0 Reporter: Timo Naroska Attachments: SLING-2369-2.diff, SLING-2369.diff Upgrade to Felix Framework 4.0.2 which implements OSGi R4.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2254) ConcurrentModificationException in AdapterManagerImpl.createAdapterFactoryMap
[ https://issues.apache.org/jira/browse/SLING-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2254: Fix Version/s: Adapter 2.0.12 ConcurrentModificationException in AdapterManagerImpl.createAdapterFactoryMap - Key: SLING-2254 URL: https://issues.apache.org/jira/browse/SLING-2254 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Adapter 2.0.8 Reporter: Bertrand Delacretaz Priority: Minor Fix For: Adapter 2.0.12 Attachments: FELIX-2254.patch Got this exception at least once during testing: org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught Throwable java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1100) at java.util.TreeMap$ValueIterator.next(TreeMap.java:1145) at org.apache.sling.adapter.internal.AdapterManagerImpl.createAdapterFactoryMap(AdapterManagerImpl.java:385) at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapterFactories(AdapterManagerImpl.java:354) at org.apache.sling.adapter.internal.AdapterManagerImpl.copyAdapterFactories(AdapterManagerImpl.java:432) at org.apache.sling.adapter.internal.AdapterManagerImpl.createAdapterFactoryMap(AdapterManagerImpl.java:401) at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapterFactories(AdapterManagerImpl.java:354) at org.apache.sling.adapter.internal.AdapterManagerImpl.copyAdapterFactories(AdapterManagerImpl.java:432) at org.apache.sling.adapter.internal.AdapterManagerImpl.createAdapterFactoryMap(AdapterManagerImpl.java:407) at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapterFactories(AdapterManagerImpl.java:354) at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapterFactories(AdapterManagerImpl.java:331) at org.apache.sling.adapter.internal.AdapterManagerImpl.getAdapter(AdapterManagerImpl.java:114) at org.apache.sling.api.adapter.SlingAdaptable.adaptTo(SlingAdaptable.java:82) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2337) allow the session created by the SlingMainServlet to be left open after the request ends
[ https://issues.apache.org/jira/browse/SLING-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2337: - Fix Version/s: (was: API 2.2.4) (was: Engine 2.2.6) (was: Auth Core 1.1.0) Remove Fix Versions since this should probably not appear in Release Notes allow the session created by the SlingMainServlet to be left open after the request ends Key: SLING-2337 URL: https://issues.apache.org/jira/browse/SLING-2337 Project: Sling Issue Type: Improvement Components: Authentication, Engine Reporter: Justin Edelson Assignee: Justin Edelson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2384) Can't remove Derby from running instance of launchpad
[ https://issues.apache.org/jira/browse/SLING-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Nijhawan updated SLING-2384: -- Description: In the steps given to change jackrabbit persistence outlined here http://sling.apache.org/site/jackrabbit-persistence.html The first step asking you to uninstall the Derby Bundle causes the whole thing collapse. How then can one use these steps to add another database? Here's what the log file showed 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent STOPPED 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNRESOLVED 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNINSTALLED 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent INSTALLED 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent RESOLVED 25.01.2012 16:31:38.312 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent STARTED snip 1. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager execute failed, about to reconnect... 1a. org.apache.sling.jcr.jackrabbit.server stopRepository: Uncaught problem unregistering the repository service (java.lang.IllegalStateException: Service already unregistered.) java.lang.IllegalStateException: Service already unregistered. at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:125) at org.apache.sling.jcr.base.AbstractSlingRepository.unregisterService(AbstractSlingRepository.java:536) at org.apache.sling.jcr.base.AbstractSlingRepository.stopRepository(AbstractSlingRepository.java:861) at org.apache.sling.jcr.base.AbstractSlingRepository.deactivate(AbstractSlingRepository.java:638) 2. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to re-establish connection java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager at org.apache.derby.jdbc.AutoloadedDriver.getDriverModule(Unknown Source) at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294) 3. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to check existence of node state: fbc3862a-ff93-e87f-7b11-4d9b674580fa java.sql.SQLNonTransientConnectionException: No current connection. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) 3a. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to re-establish connection java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager I took out the exception stack but this is the order in which they came. was: In the steps given to change jackrabbit persistence outlined here http://sling.apache.org/site/jackrabbit-persistence.html The first step asking you to uninstall the Derby Bundle causes the whole thing collapse. How then can one use these steps to add another database? Here's what the log file showed 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent STOPPED 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNRESOLVED 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNINSTALLED 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent INSTALLED 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent RESOLVED 25.01.2012 16:31:38.312 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent STARTED lt;snip 1. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager execute failed, about to reconnect... 1a. org.apache.sling.jcr.jackrabbit.server stopRepository: Uncaught problem unregistering the repository service (java.lang.IllegalStateException: Service already unregistered.) java.lang.IllegalStateException: Service already unregistered. at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:125) at org.apache.sling.jcr.base.AbstractSlingRepository.unregisterService(AbstractSlingRepository.java:536) at org.apache.sling.jcr.base.AbstractSlingRepository.stopRepository(AbstractSlingRepository.java:861) at org.apache.sling.jcr.base.AbstractSlingRepository.deactivate(AbstractSlingRepository.java:638) 2. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to re-establish connection java.sql.SQLException
[jira] [Updated] (SLING-2380) Make RepositoryTestBase's repository usable from JUnit 4.x style tests
[ https://issues.apache.org/jira/browse/SLING-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2380: --- Affects Version/s: Commons Testing 2.0.8 Fix Version/s: Commons Testing 2.0.10 Make RepositoryTestBase's repository usable from JUnit 4.x style tests -- Key: SLING-2380 URL: https://issues.apache.org/jira/browse/SLING-2380 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: Commons Testing 2.0.8 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Testing 2.0.10 Tests currently need to inherit from that class to get a TestRepository, which forces them to use the old JUnit3.x style. I'll add a static method to that class, that JUnit 4.x tests can use to get a repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2369) upgrade Felix to 4.0.2
[ https://issues.apache.org/jira/browse/SLING-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timo Naroska updated SLING-2369: Attachment: SLING-2369.diff upgrade Felix to 4.0.2 -- Key: SLING-2369 URL: https://issues.apache.org/jira/browse/SLING-2369 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.3.0 Reporter: Timo Naroska Attachments: SLING-2369.diff Upgrade to Felix Framework 4.0.2 which implements OSGi R4.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2236) Default POST servlet reports invalid operation when it should report 404
[ https://issues.apache.org/jira/browse/SLING-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2236: -- Priority: Minor (was: Major) adjusting priority due to availability of a workaround. inclined to close this as Won't Fix, but I'll defer that for now. Default POST servlet reports invalid operation when it should report 404 Key: SLING-2236 URL: https://issues.apache.org/jira/browse/SLING-2236 Project: Sling Issue Type: Bug Components: Servlets Reporter: Jeff Young Priority: Minor In sling/servlets/post/impl/SlingPostServlet.java's doPost() method, we look up the operation (and report an unknown operation) before checking privileges. I'd like to propose that when the operation is not understood, we first check for read access to the resource, and if unsuccessful, report that instead of reporting invalid operation. Here's the issue: say I define my own POST servlet which supports :operation=foo. I set a sling:resourceType so that my POST servlet gets invoked. All fine and good. Now someone without read access to the resource tries to do an :operation=foo. Sling can't read the sling:resourceType (no read access), and so invokes the default POST servlet instead of my custom POST servlet. It looks up :operation=foo and reports invalid operation (which is pretty misleading). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2376) New Startup Features
[ https://issues.apache.org/jira/browse/SLING-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2376: Fix Version/s: Launchpad API 1.1.0 New Startup Features Key: SLING-2376 URL: https://issues.apache.org/jira/browse/SLING-2376 Project: Sling Issue Type: New Feature Components: Launchpad Affects Versions: Launchpad Installer 1.0.6, Launchpad Base 2.3.0, Launchpad API 1.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Installer 1.0.8, Launchpad Base 2.4.0, Launchpad API 1.1.0 With SLING-2372 we have now a mechanism to decide what kind of startup currently is processed We could leverage this to create new functionality: Enhance lauchpad api with the startup mode, the possibility to register listener which are informed about the startup mode and progress. Another feature would be to not directly go to the beginning start level of the framework, but stop at an intermediate level on installs and updates and from there increase the start level one by one. This makes updates and installs much smoother For more information I'll write an email to the dev list :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory
[
https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated SLING-2215:
-
Attachment: 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch
It turns out that the jackrabbit/tmp path was hardcoded in the
SlingDavExServlet class. The code dates back to revision 1199645 of SLING-2275,
where the temporary folder path got set to ${sling.home}/jackrabbit/tmp to
avoid the default plain jackrabbit/tmp path.
The attached patch removes the hardcoded path. Nowadays the default is to use
the standard ${java.io.tmpdir} folder for temporary files.
DavEx servlet creates a jackrabbit/tmp directory
Key: SLING-2215
URL: https://issues.apache.org/jira/browse/SLING-2215
Project: Sling
Issue Type: Bug
Affects Versions: JCR DavEx 1.0.0
Reporter: Jukka Zitting
Priority: Minor
Fix For: JCR DavEx 1.1.0
Attachments:
0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch,
0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch
The DavEx servlet bundle added in SLING-1393 doesn't set the home and
temp-directory init parameters of the JcrRemotingServlet base class it uses
from Jackrabbit. As a result Jackrabbit defaults to jackrabbit/tmp as the
location
for temporary files, and creates such a directory under the current working
directory.
This problem is solved in the latest Jackrabbit trunk as of JCR-3029 where
the default location for temporary files was set
to the standard one defined by the java.io.tmpdir system property, so I guess
the easiest way to solve this is simply to
upgrade the dependency in Sling once the Jackrabbit 2.3.0 release is
available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2375) Allow Immediate And Then Periodic Task Execution In Whiteboard Scheduling
[
https://issues.apache.org/jira/browse/SLING-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-2375:
Affects Version/s: (was: Commons Scheduler 2.3.4)
Commons Scheduler 2.3.2
Fix Version/s: Commons Scheduler 2.3.4
Assignee: Carsten Ziegeler
Allow Immediate And Then Periodic Task Execution In Whiteboard Scheduling
-
Key: SLING-2375
URL: https://issues.apache.org/jira/browse/SLING-2375
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons Scheduler 2.3.2
Reporter: Dominique Jäggi
Assignee: Carsten Ziegeler
Fix For: Commons Scheduler 2.3.4
currently the whiteboard pattern allows creation of scheduled tasks as such:
DictionaryString, Object props = new HashtableString,
Object();
props.put(scheduler.period, pc.getInterval());
props.put(scheduler.concurrent, false);
props.put(scheduler.name, pc.getSource());
props.put(Constants.SERVICE_DESCRIPTION, pc.toString());
Runnable task = new Runnable() {
final PollConfig pollConfig = pc;
public void run() {
importData(pollConfig);
}
};
pc.setScheduledTask(context.getBundleContext().registerService(
Runnable.class.getName(), task, props));
nevertheless, it is not possible via the whiteboard pattern to execute a task
immediately upon scheduling and henceforth in the interval defined in the
scheduler.period property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2353) Prevent sling:include resource=%= null % / to include itself
[ https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2353: Fix Version/s: Scripting JSP-Taglib 2.1.4 Prevent sling:include resource=%= null % / to include itself -- Key: SLING-2353 URL: https://issues.apache.org/jira/browse/SLING-2353 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP-Taglib 2.1.2 Reporter: Tobias Bocanegra Priority: Minor Fix For: Scripting JSP-Taglib 2.1.4 If you add this sling:include to a JSP sling:include resource=%= null % / then it will cause the page to keep including itself recursively making the server slow. there is a recursion limitation though to prevent endless loops. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2209) Replace JavaDoc SCR annotations with Java SCR annotations
[ https://issues.apache.org/jira/browse/SLING-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2209: Fix Version/s: File System Resource Provider 1.0.4 Replace JavaDoc SCR annotations with Java SCR annotations - Key: SLING-2209 URL: https://issues.apache.org/jira/browse/SLING-2209 Project: Sling Issue Type: Task Components: Extensions, JCR, Scripting Reporter: Justin Edelson Fix For: Scripting Core 2.0.20, JCR Resource 2.1.0, File System Resource Provider 1.0.4, Adapter 2.0.10 general issue for all SCR annotation changes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1504) Enable pluggable node name generation
[ https://issues.apache.org/jira/browse/SLING-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1504: -- Component/s: (was: Samples) Servlets Enable pluggable node name generation - Key: SLING-1504 URL: https://issues.apache.org/jira/browse/SLING-1504 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Servlets Post 2.1.0 Bundles should be able to implement a NodeNameGenerator interface and customize the node name generation logic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2313) Create annotations and an enhancement to the maven-sling-plugin to generate Adapter metadata
[ https://issues.apache.org/jira/browse/SLING-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2313: -- Fix Version/s: (was: Maven Sling Plugin 2.0.6) Maven Sling Plugin 2.0.8 Create annotations and an enhancement to the maven-sling-plugin to generate Adapter metadata Key: SLING-2313 URL: https://issues.apache.org/jira/browse/SLING-2313 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Adapter Annotations 1.0.0, Maven Sling Plugin 2.0.8 To support SLING-2295, there should be a relatively simple way to annotate adaptable classes and generate the appropriate JSON metadata. See also http://sling.markmail.org/thread/bolgpzm2cevruitz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2354) There should be a way to add multiple Adapter annotations to a class
[ https://issues.apache.org/jira/browse/SLING-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2354: -- Fix Version/s: (was: Maven Sling Plugin 2.0.6) Maven Sling Plugin 2.0.8 There should be a way to add multiple Adapter annotations to a class Key: SLING-2354 URL: https://issues.apache.org/jira/browse/SLING-2354 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Adapter Annotations 1.0.0, Maven Sling Plugin 2.0.8 For AdapterFactory instances which support multiple adaptable classes, it would be useful to be able to support multiple annotations per class. Since the language spec doesn't allow this, we need a container annotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2355) An Adapter annotation should be able to declare that it replaces the service properties metadata
[ https://issues.apache.org/jira/browse/SLING-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2355: -- Component/s: Maven Plugins and Archetypes An Adapter annotation should be able to declare that it replaces the service properties metadata Key: SLING-2355 URL: https://issues.apache.org/jira/browse/SLING-2355 Project: Sling Issue Type: Improvement Components: Extensions, Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Justin Edelson Currently, the Adapters web console plugin merges metadata from the JSON files with the metadata extracted from the OSGi service properties for AdapterFactory services. It should be possible for the JSON metadata to declare that it overrides the metadata from the AdapterFactory service (just for the purposes of the web console plugin). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2349) [Authentication] Osgi event creation for successful login
[ https://issues.apache.org/jira/browse/SLING-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2349: - Attachment: SLING-2349-fmeschbe.patch Proposed patch. I am not 100% sure about the new constant in AuthConstants but it is probably the best compromise in providing new functionality for AuthenticationHandler implementations without invalidating all implementations not interested in these. [Authentication] Osgi event creation for successful login - Key: SLING-2349 URL: https://issues.apache.org/jira/browse/SLING-2349 Project: Sling Issue Type: New Feature Components: Authentication Affects Versions: Auth Core 1.0.6 Reporter: Nicolas Peltier Assignee: Justin Edelson Priority: Minor Fix For: Auth Core 1.1.0 Attachments: SLING-2349-fmeschbe.patch Successful authentication (with credentials only?) should create an a logged in osgi event mentionning userid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2353) Prevent sling:include resource=%= null % / to include itself
[ https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra updated SLING-2353: Component/s: Scripting Affects Version/s: Scripting JSP-Taglib 2.1.2 Prevent sling:include resource=%= null % / to include itself -- Key: SLING-2353 URL: https://issues.apache.org/jira/browse/SLING-2353 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP-Taglib 2.1.2 Reporter: Tobias Bocanegra Priority: Minor If you add this sling:include to a JSP sling:include resource=%= null % / then it will cause the page to keep including itself recursively making the server slow. there is a recursion limitation though to prevent endless loops. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2349) [Authentication] Osgi event creation for successful login
[ https://issues.apache.org/jira/browse/SLING-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2349: -- Assignee: Justin Edelson [Authentication] Osgi event creation for successful login - Key: SLING-2349 URL: https://issues.apache.org/jira/browse/SLING-2349 Project: Sling Issue Type: New Feature Components: Authentication Affects Versions: Auth Core 1.0.6 Reporter: Nicolas Peltier Assignee: Justin Edelson Priority: Minor Successful authentication (with credentials only?) should create an a logged in osgi event mentionning userid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2312) Add Adapter Annotations
[ https://issues.apache.org/jira/browse/SLING-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2312: -- Fix Version/s: Extensions Rewriter 1.0.2 added to rewriter in r1229714 Add Adapter Annotations --- Key: SLING-2312 URL: https://issues.apache.org/jira/browse/SLING-2312 Project: Sling Issue Type: Improvement Components: Extensions, JCR Reporter: Justin Edelson Fix For: JCR Resource 2.1.0, File System Resource Provider 1.0.4, Extensions Rewriter 1.0.2, JCR Jackrabbit User Manager 2.2.2 Container issue for adding annotations introduced in SLING-2313 to various bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: jspc-test.zip Attaching a small maven project that uses maven-jspc-plugin 2.0.5-SNAPSHOT and exhibits the build error cannot find LoggerFactory Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Assignee: Carsten Ziegeler Labels: maven-bundle-plugin Attachments: jspc-test.zip, pom.xml, pom.xml.diff Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: pom.xml.diff SVN Patch for udpates to pom.xml Updated org.apache.sling.scripting.jsp dependency to rely on version 2.0.8 Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Assignee: Carsten Ziegeler Labels: maven-bundle-plugin Attachments: pom.xml, pom.xml.diff Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Comment: was deleted (was: SVN Patch for udpates to pom.xml Updated org.apache.sling.scripting.jsp dependency to rely on version 2.0.8) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Assignee: Carsten Ziegeler Labels: maven-bundle-plugin Attachments: pom.xml Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: (was: pom.xml.diff) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Assignee: Carsten Ziegeler Labels: maven-bundle-plugin Attachments: pom.xml Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: pom.xml.diff Patched pom.xml from trunk. Updated org.apache.sling.scripting.jsp dependency to rely on version 2.0.8) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Assignee: Carsten Ziegeler Labels: maven-bundle-plugin Attachments: pom.xml, pom.xml.diff Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: pom.xml Updated pom.xml that uses org.apache.sling.scripting.jsp v2.0.8 which in turn uses org.apache.sling.api v2.0.8 (which provides required adaptable support) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Labels: maven-bundle-plugin Attachments: pom.xml Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: pom.xml Replaced previous attachment pom.xml to maintain the same 2.0.4-incubator version Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Labels: maven-bundle-plugin Attachments: pom.xml Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects
[ https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Gonzalez updated SLING-2350: -- Attachment: (was: pom.xml) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects Key: SLING-2350 URL: https://issues.apache.org/jira/browse/SLING-2350 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Maven JSPC Plugin 2.0.4 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac Reporter: David Gonzalez Labels: maven-bundle-plugin Attachments: pom.xml Original Estimate: 0.5h Remaining Estimate: 0.5h Buiding Sling-based project using the Maven JSPC Plugin but am getting compilation errors because SlingHttpServletRequest object doesn't have .adaptTo(...) defined. Latest Sling API docs state: Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface also extends the Adaptable interface. Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on Sling Scripting 2.0.2-incubator [2] which in turn depends on Sling API 2.0.2-incubator which is older than 2.0.6 thus no Adaptable support. [1] http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml [2] http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2348) Running the Lauchpad throws an ArrayIndexOutOfBoundException
[ https://issues.apache.org/jira/browse/SLING-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Barin updated SLING-2348: --- Summary: Running the Lauchpad throws an ArrayIndexOutOfBoundException (was: Running the Lauchpad throws an ArrayOutOfBoundIndex) Running the Lauchpad throws an ArrayIndexOutOfBoundException Key: SLING-2348 URL: https://issues.apache.org/jira/browse/SLING-2348 Project: Sling Issue Type: Bug Environment: Java 7, Windows XP Reporter: Bruno Barin Priority: Blocker When trying to run the launchpad example I get the following exception: 02.01.2012 10:57:06.808 *ERROR* [main] Failed to Start OSGi framework org.osgi.framework.BundleException: Uncaught Instantiation Issue: java.lang.Arra yIndexOutOfBoundsException: -1 at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:245) at org.apache.sling.launchpad.base.app.MainDelegate$1.init(MainDelegat e.java:159) at org.apache.sling.launchpad.base.app.MainDelegate.start(MainDelegate.j ava:159) at org.apache.sling.launchpad.app.Main.startSling(Main.java:244) at org.apache.sling.launchpad.app.Main.init(Main.java:107) at org.apache.sling.launchpad.app.Main.main(Main.java:56) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:371) at java.util.ArrayList.get(ArrayList.java:384) at org.apache.felix.framework.BundleImpl.getCurrentModule(BundleImpl.jav a:1046) at org.apache.felix.framework.BundleImpl.getSymbolicName(BundleImpl.java :863) at org.apache.sling.launchpad.base.impl.SlingFelix.getSymbolicName(Sling Felix.java:32) at org.apache.felix.framework.Felix.toString(Felix.java:1012) at org.apache.felix.framework.Logger.doLog(Logger.java:128) at org.apache.felix.framework.Logger._log(Logger.java:181) at org.apache.felix.framework.Logger.log(Logger.java:114) at org.apache.felix.framework.ExtensionManager.init(ExtensionManager.j ava:201) at org.apache.felix.framework.Felix.init(Felix.java:374) at org.apache.sling.launchpad.base.impl.SlingFelix.init(SlingFelix.jav a:39) at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:235) ... 5 more 02.01.2012 10:57:06.824 *ERROR* [main] There was a problem launching Sling 02.01.2012 10:57:06.824 *INFO* [Sling Terminator] Java VM is shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2060) Refresh bundles with optional dependencies if such dependency is installed
[ https://issues.apache.org/jira/browse/SLING-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2060: Fix Version/s: (was: Installer Core 3.2.4) Unscheduling to not block a release Refresh bundles with optional dependencies if such dependency is installed -- Key: SLING-2060 URL: https://issues.apache.org/jira/browse/SLING-2060 Project: Sling Issue Type: New Feature Components: Installer Affects Versions: Installer Core 3.1.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler When a bundle has an optional dependency and a new bundle is installed afterwards having this dependency, the first bundle should be refreshed See [1] for some discussions on the topic [1] http://markmail.org/thread/qiqfb3uvrb6apimt#query:+page:1+mid:yarhksmfadr6hu3r+state:results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2341) SlingScriptHelper#getServices() causes ClassCastException
[ https://issues.apache.org/jira/browse/SLING-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-2341: -- Attachment: SLING-2341.patch proposed patch SlingScriptHelper#getServices() causes ClassCastException - Key: SLING-2341 URL: https://issues.apache.org/jira/browse/SLING-2341 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Core 2.0.18 Reporter: Julian Sedding Fix For: Scripting Core 2.0.20 Attachments: SLING-2341.patch The implementation of ScriptHelper#getServices() creates an Object[] and tries to cast it to the generics class. This results in a ClassCastException, as an Object[] cannot be cast to a more specific array (i.e. ServiceType[]). The solution is to create an array of the correct type and size using java.util.reflect.Array#newInstance(), see discussion on stackoverflow[0]. [0] http://stackoverflow.com/questions/529085/java-how-to-generic-array-creation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2335) Provide support for versioned resources
[ https://issues.apache.org/jira/browse/SLING-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2335: Summary: Provide support for versioned resources (was: Provide support for versionioned resources) Provide support for versioned resources --- Key: SLING-2335 URL: https://issues.apache.org/jira/browse/SLING-2335 Project: Sling Issue Type: New Feature Components: Installer Affects Versions: Installer Core 3.2.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.2.4 Currently, a TransformationResult can only set an id and arbitrary attributes. There is currently no support for a specific version attribute which in turn can be picked up by the core to compare resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2325) SlingDavExServlet uses impersonation to get session. Doesn't work nicely if user doesn't have right to impersonate.
[
https://issues.apache.org/jira/browse/SLING-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-2325:
--
Fix Version/s: JCR DavEx 1.1.0
Assignee: Justin Edelson
SlingDavExServlet uses impersonation to get session. Doesn't work nicely if
user doesn't have right to impersonate.
---
Key: SLING-2325
URL: https://issues.apache.org/jira/browse/SLING-2325
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR DavEx 1.0.0
Reporter: Christanto
Assignee: Justin Edelson
Priority: Blocker
Labels: davex
Fix For: JCR DavEx 1.1.0
SlingDavExServlet uses impersonation to get session. Doesn't work nicely if
user doesn't have right to impersonate.
LoginException will be thrown: javax.jcr.LoginException: attempt to
impersonate denied for user
Code excerpt from SlingDavExServlet:
final Session session = resolver.adaptTo(Session.class);
// as the session might be longer used by davex than the request
// we have to create a new session!
if ( session != null ) {
final Credentials credentials = new
SimpleCredentials(session.getUserID(), EMPTY_PW);
final Session newSession = session.impersonate(credentials);
return newSession;
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1140) Rewriter Filter not called when error is handled
[ https://issues.apache.org/jira/browse/SLING-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1140: Affects Version/s: Extensions Rewriter 1.0.0 Fix Version/s: Extensions Rewriter 1.0.2 Rewriter Filter not called when error is handled Key: SLING-1140 URL: https://issues.apache.org/jira/browse/SLING-1140 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Rewriter 1.0.0 Reporter: Honwai Wong Assignee: Carsten Ziegeler Priority: Minor Fix For: Extensions Rewriter 1.0.2 Attachments: SLING-1140-asanso-patch.txt In case an errorhandler is triggered (e.g. 404 occurred), the Rewriter Filter and thus custom filters in the pipeline are ignored. Filters should be triggered even when an error occurred beforehand. Use-case: - have a custom 404-errorhandler in place, /apps/sling/servlet/errorhandler/404.jsp - do a RequestDispatcher#forward to a resource whose output is usually being rewritten -- filters are ignored, output of forwarded resource is not rewritten -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2320: -- Attachment: json_get_servlet_rewrite.patch No worries, Justin. I've got one more anyway ;) Hopefully this is the final installment. Rewrite of JSON GET servlet to: a) not throw two exceptions per node finding the parent (in fact, we don't look for the parent at all anymore as the JSON rendering is now done via a second-pass, depth-first traversal rather than during the breadth-first depthCheck) b) not serialize/de-serialize/re-serialize the JSON (also due to the above two-pass approach) c) use ArrayLists instead of LinkedLists for breadth-first traversal (to reduce memory allocation calls) d) not use exceptions for limiting depth Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Assignee: Justin Edelson Labels: newbie, patch Fix For: Servlets Get 2.1.4 Attachments: jsonRenderer.diff, json_get_servlet_rewrite.patch, servlet_tests.patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2251) RedirectServlet should create relative Location headers as often as possible
[ https://issues.apache.org/jira/browse/SLING-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Caldwell updated SLING-2251: - Attachment: SLING-2251-VanityPathTest.patch Remove HTTP_BASE_URL from expected values RedirectServlet should create relative Location headers as often as possible Key: SLING-2251 URL: https://issues.apache.org/jira/browse/SLING-2251 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Get 2.1.2 Reporter: Alexander Klimetschek Attachments: SLING-2251-VanityPathTest.patch, SLING-2251.patch SLING-1965 (more specifically http://svn.apache.org/viewvc?view=revisionrevision=903175 ) changed the redirect servlet so that it _always_ generates an absolute location header. The issue does not give much reasoning for that. The problem is that this breaks cases where a Sling server is run behind a proxy (which does not or cannot rewrite the Location header), as the redirect (http://localhost:8080/some/path;) might not match the externally visible domain (e.g. https://my.domain.com;). Also, the schema is fixed (e.g. might switch external https back to http). A solution would be to generate absolute URLs only if a resource resolver mapping (/etc/map) includes an explicit domain and thus generates an absolute URL. For all other cases, relative URLs should be generated. AFAICS, this was the case before SLING-1965. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2320: -- Attachment: jsonRenderer.diff Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Assignee: Felix Meschberger Labels: newbie, patch Fix For: Servlets Get 2.1.4 Attachments: jsonRenderer.diff, jsonRenderer.diff, servlet_tests.patch, servlet_tests.patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2320: -- Attachment: servlet_tests.patch Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Assignee: Felix Meschberger Labels: newbie, patch Fix For: Servlets Get 2.1.4 Attachments: jsonRenderer.diff, jsonRenderer.diff, servlet_tests.patch, servlet_tests.patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2320: Attachment: (was: servlet_tests.patch) Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Assignee: Felix Meschberger Labels: newbie, patch Fix For: Servlets Get 2.1.4 Attachments: jsonRenderer.diff, servlet_tests.patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2320: Attachment: (was: jsonRenderer.diff) Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Assignee: Felix Meschberger Labels: newbie, patch Fix For: Servlets Get 2.1.4 Attachments: jsonRenderer.diff, servlet_tests.patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2324) The recursion selector value for the JsonRenderServlet is limited to Integer.MAX_VALUE
[ https://issues.apache.org/jira/browse/SLING-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-2324: - Attachment: SLING-2324-patch.txt Thanks Carsten, proposed patch attached. I will happily leverage [0] (when committed) to integrate some unit test for this case. [0] https://issues.apache.org/jira/browse/SLING-2320 The recursion selector value for the JsonRenderServlet is limited to Integer.MAX_VALUE -- Key: SLING-2324 URL: https://issues.apache.org/jira/browse/SLING-2324 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.2 Reporter: Antonio Sanso Assignee: Carsten Ziegeler Priority: Minor Attachments: SLING-2324-patch.txt A request of resource.$(Integer.MAX_VALUE+1).json or higher fails with Invalid recursion selector value '2147483648' (400) Arguably (due the really high number) IMHO would be more correct to transform the request to resource.infinity.json rather than return 400. Should you agree patch to follow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1081) fsresource: allow to adapt to ValueMap
[ https://issues.apache.org/jira/browse/SLING-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1081: Affects Version/s: File System Resource Provider 1.0.2 Fix Version/s: File System Resource Provider 1.0.4 fsresource: allow to adapt to ValueMap -- Key: SLING-1081 URL: https://issues.apache.org/jira/browse/SLING-1081 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: File System Resource Provider 1.0.2 Reporter: Stefan Seifert Assignee: Carsten Ziegeler Fix For: File System Resource Provider 1.0.4 Attachments: 090812_SLING-1081_fsresource_valuemap.patch, 111202_SLING-1081_fsresource_valuemap.patch the fsresource provider is used often to map a maven bundle project in the sling instance allowing to see changes in file without redeployment of the bundle. some sling applications accessing such resources always assume they are reading from JCR and try to adapt the resource to a ValueMap, which returns null for fsresources. this is of course a bug in this some applications, but because fsresource is often used in such a scenario it would be helpful to support a simple adapting to ValueMap in the FsResource class. patch attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2320: -- Description: A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. was:A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Labels: newbie, patch Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children
[ https://issues.apache.org/jira/browse/SLING-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Young updated SLING-2320: -- Attachment: jsonRenderer.diff Ostensibly, this would just be a one-liner. However, I discovered that the routine ResourceTraversor:check() had a rather large side-effect: it collects all the JSON objects which will later be output. So if you don't do a check(), you don't get any output. So I also renamed the routine (and some of its subroutines) such that the primary action is no longer a side-effect. Current DOS-prevention for infinity.json can prevent enumeration of children Key: SLING-2320 URL: https://issues.apache.org/jira/browse/SLING-2320 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.0 Reporter: Jeff Young Labels: newbie, patch Attachments: jsonRenderer.diff Original Estimate: 1h Remaining Estimate: 1h A request of resource.1.json should always succeed, as it's the primary method for JSON introspection of the repository hierarchy. DOS protection should only apply to deep traversals; that is, anything with a depth greater than 1 (and, in particular, resource.infinity.json). For a fuller discussion, see: http://www.mail-archive.com/dev@sling.apache.org/msg13961.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1081) fsresource: allow to adapt to ValueMap
[ https://issues.apache.org/jira/browse/SLING-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-1081: -- Attachment: 111202_SLING-1081_fsresource_valuemap.patch i think as well that there is not an urgent need for a generic adapter factory returning value maps for resources that do not provide one for themselves. but coming back to the initial cause of this ticket: i think it still would be a good idea to return a valid value map specific for the resource provider. the FsResource class simulates a JCR node by returning a resource type nt:file / nt:folder already. in this case it should the same properties as value maps as the jcr resource provider. i've attached an updated patch: 111202_SLING-1081_fsresource_valuemap.patch fsresource: allow to adapt to ValueMap -- Key: SLING-1081 URL: https://issues.apache.org/jira/browse/SLING-1081 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Stefan Seifert Attachments: 090812_SLING-1081_fsresource_valuemap.patch, 111202_SLING-1081_fsresource_valuemap.patch the fsresource provider is used often to map a maven bundle project in the sling instance allowing to see changes in file without redeployment of the bundle. some sling applications accessing such resources always assume they are reading from JCR and try to adapt the resource to a ValueMap, which returns null for fsresources. this is of course a bug in this some applications, but because fsresource is often used in such a scenario it would be helpful to support a simple adapting to ValueMap in the FsResource class. patch attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2316) Adapters WebConsole Plugin doesn't correct handle an AdapterFactory service with more than one adaptable
[ https://issues.apache.org/jira/browse/SLING-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2316: -- Component/s: Extensions Adapters WebConsole Plugin doesn't correct handle an AdapterFactory service with more than one adaptable Key: SLING-2316 URL: https://issues.apache.org/jira/browse/SLING-2316 Project: Sling Issue Type: Bug Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Adapter 2.0.10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2314) FSResourcerProvider: Use SCR Java Annotations
[ https://issues.apache.org/jira/browse/SLING-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2314: -- Fix Version/s: File System Resource Provider 1.0.4 FSResourcerProvider: Use SCR Java Annotations - Key: SLING-2314 URL: https://issues.apache.org/jira/browse/SLING-2314 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: File System Resource Provider 1.0.2 Reporter: Stefan Seifert Assignee: Justin Edelson Priority: Minor Fix For: File System Resource Provider 1.0.4 Attachments: 111202_SLING-2314_fsresource_annotations.patch the FSResourceProvider should use SCR java annotations instead of the javadoc annotations (which will be deprecated soon). Patch attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2311) Sling Performance Testing tool
[ https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-2311: - Attachment: SLING-2311-patch.txt I have attached a prototype of the tool that I have used to produce [0]. There are still a lot of things to tweak (pom files, scripts to produce the graph, etc) but it gives an idea of the approach. It is basically a 'porting' of what already exists in Jackrabbit so all credits go to the Jackrabbit project. [0] https://issues.apache.org/jira/secure/attachment/12500677/performance.pdf Sling Performance Testing tool -- Key: SLING-2311 URL: https://issues.apache.org/jira/browse/SLING-2311 Project: Sling Issue Type: New Feature Components: Testing Reporter: Antonio Sanso Priority: Minor Attachments: SLING-2311-patch.txt As described/discussed in [0] it would be nice to have a performance test tool in Sling . This can be useful in different situations (e.g. micro benchmarks of a feature and so on). Patch to follow [0] http://sling.markmail.org/message/bz44im7aqeae4r57 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2312) Add Adapter Annotations
[ https://issues.apache.org/jira/browse/SLING-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2312: -- Description: Container issue for adding annotations introduced in SLING-2313 to various bundles. (was: Container issue for adding annotations introduced in SLING-2295 to various bundles.) Add Adapter Annotations --- Key: SLING-2312 URL: https://issues.apache.org/jira/browse/SLING-2312 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Container issue for adding annotations introduced in SLING-2313 to various bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2313) Create annotations and an enhancement to the maven-sling-plugin to generate Adapter metadata
[ https://issues.apache.org/jira/browse/SLING-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2313: -- Summary: Create annotations and an enhancement to the maven-sling-plugin to generate Adapter metadata (was: Create annotation and an enhancement to the maven-sling-plugin to generate Adapter metadata) Create annotations and an enhancement to the maven-sling-plugin to generate Adapter metadata Key: SLING-2313 URL: https://issues.apache.org/jira/browse/SLING-2313 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Justin Edelson To support SLING-2295, there should be a relatively simple way to annotate adaptable classes and generate the appropriate JSON metadata. See also http://sling.markmail.org/thread/bolgpzm2cevruitz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2312) Add Adapter Annotations
[ https://issues.apache.org/jira/browse/SLING-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2312: -- Component/s: Extensions Fix Version/s: File System Resource Provider 1.0.4 JCR Resource 2.1.0 Add Adapter Annotations --- Key: SLING-2312 URL: https://issues.apache.org/jira/browse/SLING-2312 Project: Sling Issue Type: Improvement Components: Extensions, JCR Reporter: Justin Edelson Fix For: JCR Resource 2.1.0, File System Resource Provider 1.0.4 Container issue for adding annotations introduced in SLING-2313 to various bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2312) Add Adapter Annotations
[ https://issues.apache.org/jira/browse/SLING-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2312: -- Fix Version/s: JCR Jackrabbit User Manager 2.2.2 JCR UserManager done in r1209347 Add Adapter Annotations --- Key: SLING-2312 URL: https://issues.apache.org/jira/browse/SLING-2312 Project: Sling Issue Type: Improvement Components: Extensions, JCR Reporter: Justin Edelson Fix For: JCR Resource 2.1.0, File System Resource Provider 1.0.4, JCR Jackrabbit User Manager 2.2.2 Container issue for adding annotations introduced in SLING-2313 to various bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2307) Additional per-request Loggers results in NullPointerException
[ https://issues.apache.org/jira/browse/SLING-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2307: - Affects Version/s: Engine 2.2.4 Fix Version/s: Engine 2.2.6 Additional per-request Loggers results in NullPointerException -- Key: SLING-2307 URL: https://issues.apache.org/jira/browse/SLING-2307 Project: Sling Issue Type: Bug Components: Engine Affects Versions: Engine 2.2.4 Environment: Sling Trunk Reporter: Thomas März Assignee: Felix Meschberger Priority: Minor Fix For: Engine 2.2.6 Add Additional per-request Loggers as described here http://sling.apache.org/site/client-request-logging.html Log Format: %T %f Logger Name: custom-request.log Logger Type: File Name Logger Type: Checked Open http://localhost:8080/.explorer.html Nothing is rendered, just an empty page error.log 29.11.2011 14:29:17.052 *ERROR* [0:0:0:0:0:0:0:1%0 [1322573357048] GET /favicon.ico HTTP/1.1] org.apache.sling.engine.impl.SlingMainServlet service: Uncaught Problem handling the request java.lang.NullPointerException at org.apache.sling.engine.impl.SlingHttpServletRequestImpl.getResource(SlingHttpServletRequestImpl.java:98) at org.apache.sling.engine.impl.log.CustomLogFormat$ContentPathParameter.getValue(CustomLogFormat.java:752) at org.apache.sling.engine.impl.log.CustomLogFormat$BaseParameter.print(CustomLogFormat.java:401) at org.apache.sling.engine.impl.log.CustomLogFormat.format(CustomLogFormat.java:80) at org.apache.sling.engine.impl.log.RequestLoggerService.log(RequestLoggerService.java:125) at org.apache.sling.engine.impl.log.RequestLogger.logRequestEntry(RequestLogger.java:143) at org.apache.sling.engine.impl.SlingRequestProcessorImpl.processRequest(SlingRequestProcessorImpl.java:144) at org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:206) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2303) The default PersistanceManager used by sling launchpad is deprecated
[ https://issues.apache.org/jira/browse/SLING-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-2303: --- Attachment: SLING-2303.patch Attached potential patch. One problem is that the new derby PM doesn't have the shudownOnClose parameter anymore. So the change for SLING-1568 isn't possible without changing the jackrabbit code. Is that important for anyone? The default PersistanceManager used by sling launchpad is deprecated Key: SLING-2303 URL: https://issues.apache.org/jira/browse/SLING-2303 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit Server 2.1.0 Reporter: Eric Norman Assignee: Eric Norman Priority: Minor Attachments: SLING-2303.patch The derby persistance manager class in the repository.xml file has been deprecated. It should be replaced with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2305) UserManager - Convert @scr Java Doc Tags to SCR Annotations
[ https://issues.apache.org/jira/browse/SLING-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-2305: --- Component/s: (was: Authentication) JCR Priority: Minor (was: Major) Affects Version/s: (was: Form Based Authentication 1.0.0) JCR Jackrabbit User Manager 2.2.0 Fix Version/s: (was: Form Based Authentication 1.0.2) JCR Jackrabbit User Manager 2.2.2 Assignee: Eric Norman (was: Felix Meschberger) UserManager - Convert @scr Java Doc Tags to SCR Annotations --- Key: SLING-2305 URL: https://issues.apache.org/jira/browse/SLING-2305 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit User Manager 2.2.0 Reporter: Eric Norman Assignee: Eric Norman Priority: Minor Fix For: JCR Jackrabbit User Manager 2.2.2 The SCR Annotations provides more flexibility and support with respect to referring to actual Java Code thus reducing the risk of copy/paste errors. In additions annotations are fully supported by IDEs and thus provide support while editing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2301) Simple WebDAV bundle should not embed and export the Jackrabbit WebDAV library
[ https://issues.apache.org/jira/browse/SLING-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2301: - Description: The Simple WebDAV bundle embeds the Jackrabbit JCR-Server, WebDAV and JCR Commons libraries. All three have been converted into bundles, where WebDAV and JCR Commons export theire packages fully. The Simple WebDAV bundle should not embed these latter bundles (just the JCR Server for its internal setup). Rather the API should be imported. This requires an update to Jackrabbit JCR Server 2.3.4 which is currently voted on. was: The Simple WebDAV bundle embeds the Jackrabbit JCR-Server, WebDAV and JCR Commons libraries. All three have been converted into bundles, where WebDAV and JCR Commons export theire packages fully. The Simple WebDAV bundle should not embed these latter bundles (just the JCR Server for its internal setup). Rather the API should be imported. Summary: Simple WebDAV bundle should not embed and export the Jackrabbit WebDAV library (was: Simple WebDAV bundle should not export the Jackrabbit WebDAV API) Simple WebDAV bundle should not embed and export the Jackrabbit WebDAV library -- Key: SLING-2301 URL: https://issues.apache.org/jira/browse/SLING-2301 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Webdav 2.1.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Webdav 2.1.2 The Simple WebDAV bundle embeds the Jackrabbit JCR-Server, WebDAV and JCR Commons libraries. All three have been converted into bundles, where WebDAV and JCR Commons export theire packages fully. The Simple WebDAV bundle should not embed these latter bundles (just the JCR Server for its internal setup). Rather the API should be imported. This requires an update to Jackrabbit JCR Server 2.3.4 which is currently voted on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2301) Simple WebDAV bundle should not embed and export the Jackrabbit WebDAV library
[ https://issues.apache.org/jira/browse/SLING-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2301: - Attachment: SLING-2301.patch Proposed patch to the POM: * Update to Jackrabbit JCR Server 2.3.4 * Don't embed transitives * Fine-tune embedded packages and classes This fine-tuning reduces the bundle size from roughly 880KB to roughly 150KB. Waiting for this patch to be applied until the Jackrabbit 2.3.4 artifacts have been deployed to maven central. Simple WebDAV bundle should not embed and export the Jackrabbit WebDAV library -- Key: SLING-2301 URL: https://issues.apache.org/jira/browse/SLING-2301 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Webdav 2.1.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Webdav 2.1.2 Attachments: SLING-2301.patch The Simple WebDAV bundle embeds the Jackrabbit JCR-Server, WebDAV and JCR Commons libraries. All three have been converted into bundles, where WebDAV and JCR Commons export theire packages fully. The Simple WebDAV bundle should not embed these latter bundles (just the JCR Server for its internal setup). Rather the API should be imported. This requires an update to Jackrabbit JCR Server 2.3.4 which is currently voted on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2302) Update DavEx to Jackrabbit JCR Server 2.3.4 and fine-tune embedding
[ https://issues.apache.org/jira/browse/SLING-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2302: - Attachment: SLING-2302.patch Proposed patch as desribed. Side effect: The size of the DavEx bundle is reduced from roughly 550KB to roughly 230 KB. Update DavEx to Jackrabbit JCR Server 2.3.4 and fine-tune embedding --- Key: SLING-2302 URL: https://issues.apache.org/jira/browse/SLING-2302 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR DavEx 1.0.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR DavEx 1.1.0 Attachments: SLING-2302.patch Similar to SLING-2301 for Simple WebDAV the DavEx bundle should be updated to use the upcomig Jackrabbit JCR Server library 2.3.4 but only selectively embed this library as needed. Particulary the Jackrabbit WebDAV library should not be included any longer. As a side effect to this update, the Jackrabbit WebDAV, SPI, and SPI Commons bundles have to be updated in the launchpad build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2300) Add support to select the primary workspace for authentication
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-2300: - Component/s: JCR Affects Version/s: JCR Resource 2.0.10 Fix Version/s: JCR Resource 2.1.0 Add support to select the primary workspace for authentication -- Key: SLING-2300 URL: https://issues.apache.org/jira/browse/SLING-2300 Project: Sling Issue Type: New Feature Components: Authentication, JCR Affects Versions: JCR Resource 2.0.10, Auth Core 1.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.1.0, Auth Core 1.1.0 The JCR based ResourceResolverFactory supports selecting the Workspace to which a session should be created by specifying the user.jcr.workspace property of the credentials map. Currently the Sling authenticator does not support feeding that property from a request. To fully support certain use cases -- particularly WebDAV which accesses different workspaces through the URL space (e.g. /server/wsp1/content accesses the /content item on the wsp1 workspace through WebDAVEx) -- the Sling Authenticator should support accessing select workspaces directly. This can be indicated by a j_workspace request parameter or request attribute. The request attribute case can be used by the WebDAVEx bundle to extract the workspace name from the URL and feed the attribute for authentication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2290) Updating a fragment with a different version but the same content does not work
[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2290: Summary: Updating a fragment with a different version but the same content does not work (was: Updating a bundle with a different version but the same content does not work) Changing title Updating a fragment with a different version but the same content does not work --- Key: SLING-2290 URL: https://issues.apache.org/jira/browse/SLING-2290 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.2.4, JCR Installer 3.1.2 Reporter: Konrad Windszus Attachments: simplebundle-0.0.1-SNAPSHOT.jar, simplebundle-0.0.2-SNAPSHOT.jar, simplebundle-0.0.2-SNAPSHOT.jar If you update a bundle through a JCR package, it is only updated in Apache Felix if the actual content has changed. It is not enough to have the version number changed. This is a problem, because usually in multimodule maven builds I increase the version for all contained bundles although they might not have changed in that release. Unfortunately the new version is not deployed, therefore the Webconsole still shows the old version. The same problem applies to Bundle Fragments. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2136) Sling POST Servlet: Configuration of Allowed Paths
[ https://issues.apache.org/jira/browse/SLING-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra updated SLING-2136: Attachment: post_servlet_filter-1205238.patch Patch that introduces a new configuration for a simple allow/deny path filter list. Sling POST Servlet: Configuration of Allowed Paths -- Key: SLING-2136 URL: https://issues.apache.org/jira/browse/SLING-2136 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Post 2.1.2 Reporter: Andrew Khoury Attachments: post_servlet_filter-1205238.patch It would be nice if you could configure rules or regular expressions for paths the sling post servlet is allowed to work under. This would be good for both security reasons and for protecting against conflicts with other servlets. For example: Let's say you have a servlet ReplicationServlet registered to receive POST requests under path /bin/replicate. However, during startup, before the ReplicationServlet component has been enabled, a user tries to do a POST to /bin/replicate. In this case, instead of executing the ReplicationServlet, the POST servlet is executed and it creates a node under /bin/replicate. Now, as long as the node /bin/replicate exists... the ReplicationServlet will not be executed for requests to /bin/replicate. This presents a problem and explains the necessity for this feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2294) JcrPropertyResource should be adaptable to a Node if the property type is WeakReference
[ https://issues.apache.org/jira/browse/SLING-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2294: -- Component/s: JCR Fix Version/s: JCR Resource 2.1.0 JcrPropertyResource should be adaptable to a Node if the property type is WeakReference --- Key: SLING-2294 URL: https://issues.apache.org/jira/browse/SLING-2294 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.1.0 currently, only Reference-type properties are adaptable to nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2255) Improve JcrResourceResolver#resolve performance when big number of vanityPath are present
[ https://issues.apache.org/jira/browse/SLING-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2255: Affects Version/s: JCR Resource 2.0.10 Fix Version/s: JCR Resource 2.1.0 Assignee: Carsten Ziegeler Improve JcrResourceResolver#resolve performance when big number of vanityPath are present - Key: SLING-2255 URL: https://issues.apache.org/jira/browse/SLING-2255 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.10 Reporter: Antonio Sanso Assignee: Carsten Ziegeler Priority: Minor Fix For: JCR Resource 2.1.0 Attachments: SLING-2255.txt, performance.pdf At the moment the performance of JcrResourceResolver#resolve is tight with the number of sling:vanityPath present in the repository. Large number of vanityPath means large response time specially in the worse case scenario (namely huge number of vanityPath and request that doesn't match any vanityPath) but also in the average cases. Sling currently employs generic regexps also for vanityPath, but since the regex behind a vanityPath is well know there is room for optimization. I'll attach a graphs that shows the situation and a potential patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
