[jira] Created: (SLING-391) Create base launchpad module for better reuse
Create base launchpad module for better reuse - Key: SLING-391 URL: https://issues.apache.org/jira/browse/SLING-391 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 For better reuse in own projects, the common stuff from the launchpad app/webapp is moved to an own module. This module is then used by app/webapp - we have to find a way to define the bundles at a common place that are used by the app/webapp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-392) JSON Import: serialization fails with node type denying child nodes even though mixin allows it
[
https://issues.apache.org/jira/browse/SLING-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-392:
--
Assignee: Carsten Ziegeler
> JSON Import: serialization fails with node type denying child nodes even
> though mixin allows it
> ---
>
> Key: SLING-392
> URL: https://issues.apache.org/jira/browse/SLING-392
> Project: Sling
> Issue Type: Bug
> Components: JSON
>Affects Versions: 2.0.0
> Environment: Darwin 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4
> 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
>Reporter: Dominique Jäggi
>Assignee: Carsten Ziegeler
>
> when importing the following JSON file:
> {
>"jcr:language":"de",
>"jcr:mixinTypes":[
> "mix:language"
>],
> "jcr:primaryType":"nt:unstructured",
> "general_yes":{
> "sling:message":"Ja",
> "sling:key":"apps.mycompany.general.yes",
> "jcr:primaryType":"sling:messageEntry"
> }
> }
> using the sling initial content functionality, an exception is thrown because
> the mixins don't seem to be respected:
> 23.04.2008 14:47:29.092 *ERROR* [Background Updatech.com.mycompany.mymodule
> (91)] org.apache.sling.jcr.resource.internal.loader.Loader Cannot load
> initial content for bundle com.mycompany.mymodule : no definition found in
> parent node's node type for new node: no matching child node definition found
> for {}general_yes javax.jcr.nodetype.ConstraintViolationException: no
> definition found in parent node's node type for new node: no matching child
> node definition found for {}general_yes: no matching child node definition
> found for {}general_yes
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:752)
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:718)
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:665)
> at org.apache.jackrabbit.core.NodeImpl.addNode(NodeImpl.java:1987)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:351)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.setupNode(Loader.java:399)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:355)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:317)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:256)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.installContent(Loader.java:175)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.registerBundleInternal(Loader.java:130)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.registerBundle(Loader.java:107)
> at
> org.apache.sling.jcr.resource.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:103)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619)
> at
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568)
> at org.apache.felix.framework.Felix._startBundle(Felix.java:1570)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1519)
> at
> org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4025)
> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3267)
> at org.apache.felix.framework.Felix._updateBundle(Felix.java:1871)
> at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719)
> at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
> at
> org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242)
> at
> org.apache.sling.osgi.console.web.internal.core.InstallAction$InstallHelper.run(InstallAction.java:278)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: no matching child
> node defin
[jira] Resolved: (SLING-392) JSON Import: serialization fails with node type denying child nodes even though mixin allows it
[
https://issues.apache.org/jira/browse/SLING-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-392.
Resolution: Invalid
Your json is incorrect: you apply the mixin "mix:language", but this mixin has
no definition for a child node "sling:messageEntry".
So I guess either your child node name is wrong or you need a different mixin.
> JSON Import: serialization fails with node type denying child nodes even
> though mixin allows it
> ---
>
> Key: SLING-392
> URL: https://issues.apache.org/jira/browse/SLING-392
> Project: Sling
> Issue Type: Bug
> Components: JSON
>Affects Versions: 2.0.0
> Environment: Darwin 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4
> 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
>Reporter: Dominique Jäggi
>Assignee: Carsten Ziegeler
>
> when importing the following JSON file:
> {
>"jcr:language":"de",
>"jcr:mixinTypes":[
> "mix:language"
>],
> "jcr:primaryType":"nt:unstructured",
> "general_yes":{
> "sling:message":"Ja",
> "sling:key":"apps.mycompany.general.yes",
> "jcr:primaryType":"sling:messageEntry"
> }
> }
> using the sling initial content functionality, an exception is thrown because
> the mixins don't seem to be respected:
> 23.04.2008 14:47:29.092 *ERROR* [Background Updatech.com.mycompany.mymodule
> (91)] org.apache.sling.jcr.resource.internal.loader.Loader Cannot load
> initial content for bundle com.mycompany.mymodule : no definition found in
> parent node's node type for new node: no matching child node definition found
> for {}general_yes javax.jcr.nodetype.ConstraintViolationException: no
> definition found in parent node's node type for new node: no matching child
> node definition found for {}general_yes: no matching child node definition
> found for {}general_yes
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:752)
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:718)
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddNode(NodeImpl.java:665)
> at org.apache.jackrabbit.core.NodeImpl.addNode(NodeImpl.java:1987)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:351)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.setupNode(Loader.java:399)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:355)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.createNode(Loader.java:317)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:256)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.install(Loader.java:243)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.installContent(Loader.java:175)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.registerBundleInternal(Loader.java:130)
> at
> org.apache.sling.jcr.resource.internal.loader.Loader.registerBundle(Loader.java:107)
> at
> org.apache.sling.jcr.resource.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:103)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619)
> at
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532)
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568)
> at org.apache.felix.framework.Felix._startBundle(Felix.java:1570)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1519)
> at
> org.apache.felix.framework.Felix$RefreshHelper.restart(Felix.java:4025)
> at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3267)
> at org.apache.felix.framework.Felix._updateBundle(Felix.java:1871)
> at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719)
> at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372)
> at
> org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242)
> a
[jira] Commented: (SLING-367) change sling:post: to sling: for "command" prefixes in form names
[ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592401#action_12592401 ] Carsten Ziegeler commented on SLING-367: I think there is a difference between stuff that is stored in the repository and commands which perform some action on the repository. Using the same prefix for both is imho confusing. I don't really see why this complicates the simple use case - in the simple use case, you might not need commands at all and just post stuff to change or add content :) In addition, we have a client lib that hides this stuff anyway (though I still don't think that it is complicated) :) > change sling:post: to sling: for "command" prefixes in form names > - > > Key: SLING-367 > URL: https://issues.apache.org/jira/browse/SLING-367 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: David Nuescheler > > I think it is fair to also prefix the form elements that express certain > "commands" > with "sling:" since they are sling related. > i see it more as a side effect that the "sling:resourceType" also gets > persisted. > generally, i think everything that has something to with "sling" should be > prefixed > with "sling". > I think we need to make sure that we don't complicate the most simple cases > just > to a avoid possible collisions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-367) change sling:post: to sling: for "command" prefixes in form names
[ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592587#action_12592587 ] Carsten Ziegeler commented on SLING-367: Hmm, I totally agree that things should be as simple as possible and people should be able to start using Sling without having to mess with too many details. But :) if you look at a POST request it should be clearly visible which parameters make up the content and which not - having to learn a special exclusion list is neither simple nor intuitiv. I don't care that much what the prefixes are, but it should be possible to distinguish them. We could reach the same goal by renaming the sling prefix for the repository to something else. > change sling:post: to sling: for "command" prefixes in form names > - > > Key: SLING-367 > URL: https://issues.apache.org/jira/browse/SLING-367 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: David Nuescheler > > I think it is fair to also prefix the form elements that express certain > "commands" > with "sling:" since they are sling related. > i see it more as a side effect that the "sling:resourceType" also gets > persisted. > generally, i think everything that has something to with "sling" should be > prefixed > with "sling". > I think we need to make sure that we don't complicate the most simple cases > just > to a avoid possible collisions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-367) change sling:post: to sling: for "command" prefixes in form names
[ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592752#action_12592752 ] Carsten Ziegeler commented on SLING-367: Ok, rethinking the issue, I still would prefer to separate between something which is stored in the repo during a post and something that has an influence on how/what is stored. Using the prefix "sling" for node types, node and property names seems to be the best choice. What about just using a ":" for prefixing commands? It then looks like a command shell with a command (ok, sort of at least) ":move" etc. It's short, can be easily explained and avoids collisions. > change sling:post: to sling: for "command" prefixes in form names > - > > Key: SLING-367 > URL: https://issues.apache.org/jira/browse/SLING-367 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: David Nuescheler > > I think it is fair to also prefix the form elements that express certain > "commands" > with "sling:" since they are sling related. > i see it more as a side effect that the "sling:resourceType" also gets > persisted. > generally, i think everything that has something to with "sling" should be > prefixed > with "sling". > I think we need to make sure that we don't complicate the most simple cases > just > to a avoid possible collisions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-394) remove "sling:post:saveParamPrefix";
[ https://issues.apache.org/jira/browse/SLING-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592779#action_12592779 ] Carsten Ziegeler commented on SLING-394: Do we need this prefix at all? I think it complicates the use. > remove "sling:post:saveParamPrefix"; > > > Key: SLING-394 > URL: https://issues.apache.org/jira/browse/SLING-394 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: David Nuescheler >Priority: Minor > > since i have not seen a usecase where it would be helpful to specify the > saveParamPrefix to something > different than "./" i would recommend that we remove this option. > does someone have a good usecase for that? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-367) change sling:post: to sling: for "command" prefixes in form names
[ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-367: -- Assignee: Carsten Ziegeler > change sling:post: to sling: for "command" prefixes in form names > - > > Key: SLING-367 > URL: https://issues.apache.org/jira/browse/SLING-367 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Affects Versions: 2.0.0 >Reporter: David Nuescheler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > I think it is fair to also prefix the form elements that express certain > "commands" > with "sling:" since they are sling related. > i see it more as a side effect that the "sling:resourceType" also gets > persisted. > generally, i think everything that has something to with "sling" should be > prefixed > with "sling". > I think we need to make sure that we don't complicate the most simple cases > just > to a avoid possible collisions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-298) FormEncoding parameter should be ignored during POST processing
[ https://issues.apache.org/jira/browse/SLING-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592824#action_12592824 ] Carsten Ziegeler commented on SLING-298: Ok, can we come to a consensus here and use the same prefix for FormEncoding as we use for other special post commands? (That's currently "sling:post:", but we'll change that to ":" soon) > FormEncoding parameter should be ignored during POST processing > --- > > Key: SLING-298 > URL: https://issues.apache.org/jira/browse/SLING-298 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The FormEncoding parameter should be ignored during post processing and not > be set as a property. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-311: -- Assignee: Carsten Ziegeler > Record loaded content to not reload inadvertedly. > - > > Key: SLING-311 > URL: https://issues.apache.org/jira/browse/SLING-311 > Project: Sling > Issue Type: Improvement > Components: Resource >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > Currently, the content loader always reloads content indicated as initial > content from the bundles if the repository does not contain the respective > content. Sometimes it may be desirable to remove the content from the > repository and not get the content reloaded on bundle (or system) restart. > To prevent such content reload, the content loader should take note of loaded > content and not try to reload content, which is marked as "loaded", > regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-190) The Sling class of the launcher should verify minimum JDK requirement and fail properly
[ https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592830#action_12592830 ] Carsten Ziegeler commented on SLING-190: I'm not 100% sure, but as the launcher uses some other Sling modules which are built against 1.5 it might not be possible to load the launcher even if we are able to built just the launcher for 1.4. I agree that the error you get when trying to run a 1.5 app with 1.4 is not very intuitiv, but I think this is out of our scope. It would be great if we could add a manifest entry to the jar, indicating that this only runs on 1.5+ > The Sling class of the launcher should verify minimum JDK requirement and > fail properly > --- > > Key: SLING-190 > URL: https://issues.apache.org/jira/browse/SLING-190 > Project: Sling > Issue Type: Improvement > Components: Launcher >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: 2.0.0 > > > Currently, there is no check for the minimum Java Runtime environment > required by Sling so, Sling will just fail with nasty exceptions if the > requirement is not met. The Sling launcher (standalone app and web app) > should be modified to fail gently in such cases: >* The launcher is built agains JDK 1.4 >* The launcher checks for the required runtime version >* If the runtime version is not correct, Sling should be terminated: > -> standalone should just write the message to stderr and terminate > the VM > -> web app should log a message to the servlet container and throw > a permanent UnavailableException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-391) Create base launchpad module for better reuse
[ https://issues.apache.org/jira/browse/SLING-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-391: -- Assignee: Carsten Ziegeler > Create base launchpad module for better reuse > - > > Key: SLING-391 > URL: https://issues.apache.org/jira/browse/SLING-391 > Project: Sling > Issue Type: Improvement > Components: Launchpad >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > Original Estimate: 0h > Remaining Estimate: 0h > > For better reuse in own projects, the common stuff from the launchpad > app/webapp is moved to an own module. > This module is then used by app/webapp - we have to find a way to define the > bundles at a common place that are used by the > app/webapp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-190) The Sling class of the launcher should verify minimum JDK requirement and fail properly
[ https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-190: --- Affects Version/s: 2.0.0 Fix Version/s: (was: 2.0.0) 2.0.1 > The Sling class of the launcher should verify minimum JDK requirement and > fail properly > --- > > Key: SLING-190 > URL: https://issues.apache.org/jira/browse/SLING-190 > Project: Sling > Issue Type: Improvement > Components: Launcher >Affects Versions: 2.0.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: 2.0.1 > > > Currently, there is no check for the minimum Java Runtime environment > required by Sling so, Sling will just fail with nasty exceptions if the > requirement is not met. The Sling launcher (standalone app and web app) > should be modified to fail gently in such cases: >* The launcher is built agains JDK 1.4 >* The launcher checks for the required runtime version >* If the runtime version is not correct, Sling should be terminated: > -> standalone should just write the message to stderr and terminate > the VM > -> web app should log a message to the servlet container and throw > a permanent UnavailableException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-190) The Sling class of the launcher should verify minimum JDK requirement and fail properly
[ https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-190: --- Fix Version/s: (was: 2.0.1) > The Sling class of the launcher should verify minimum JDK requirement and > fail properly > --- > > Key: SLING-190 > URL: https://issues.apache.org/jira/browse/SLING-190 > Project: Sling > Issue Type: Improvement > Components: Launcher >Affects Versions: 2.0.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > > Currently, there is no check for the minimum Java Runtime environment > required by Sling so, Sling will just fail with nasty exceptions if the > requirement is not met. The Sling launcher (standalone app and web app) > should be modified to fail gently in such cases: >* The launcher is built agains JDK 1.4 >* The launcher checks for the required runtime version >* If the runtime version is not correct, Sling should be terminated: > -> standalone should just write the message to stderr and terminate > the VM > -> web app should log a message to the servlet container and throw > a permanent UnavailableException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-298) FormEncoding parameter should be ignored during POST processing
[ https://issues.apache.org/jira/browse/SLING-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592965#action_12592965 ] Carsten Ziegeler commented on SLING-298: The alternative would be to use "_charset_" which is set by IE and Firefox, see http://www.crazysquirrel.com/computing/general/form-encoding.jspx > FormEncoding parameter should be ignored during POST processing > --- > > Key: SLING-298 > URL: https://issues.apache.org/jira/browse/SLING-298 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The FormEncoding parameter should be ignored during post processing and not > be set as a property. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-399) Remove useless launchpad.app bundle from launchpad.webapp
[ https://issues.apache.org/jira/browse/SLING-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593043#action_12593043 ] Carsten Ziegeler commented on SLING-399: I have a patch for this on my machine as well (together with a number of other patches) > Remove useless launchpad.app bundle from launchpad.webapp > - > > Key: SLING-399 > URL: https://issues.apache.org/jira/browse/SLING-399 > Project: Sling > Issue Type: Bug > Components: Launchpad >Reporter: Bertrand Delacretaz >Priority: Minor > Attachments: SLING-399.patch > > > The launchpad.app bundle is not used by the webapp, which only depends on it > to get the same list of dependencies. > Removing the extra bundle will make the webapp 20MB slimmer ;-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-400) Separate content loading from resource bundle
[ https://issues.apache.org/jira/browse/SLING-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-400: -- Assignee: Carsten Ziegeler > Separate content loading from resource bundle > - > > Key: SLING-400 > URL: https://issues.apache.org/jira/browse/SLING-400 > Project: Sling > Issue Type: Improvement > Components: Resource >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The content loading and the jcr resource handling should be split in two > different bundles, the jcr.contentloader bundle will have the content loading. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-402) Move osgi/commons to commons/osgi
Move osgi/commons to commons/osgi - Key: SLING-402 URL: https://issues.apache.org/jira/browse/SLING-402 Project: Sling Issue Type: Improvement Components: OSGi Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: 2.0.0 The goal is to keep all commons stuff in commons/* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-403) Move jcr.default-rtp to samples
Move jcr.default-rtp to samples --- Key: SLING-403 URL: https://issues.apache.org/jira/browse/SLING-403 Project: Sling Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 This is a sample. We have to change the integration tests as they're testing this sample code as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-405) Move web-console and obr servlet to Apache Felix
[ https://issues.apache.org/jira/browse/SLING-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593273#action_12593273 ] Carsten Ziegeler commented on SLING-405: And the install part of the sling plugin > Move web-console and obr servlet to Apache Felix > > > Key: SLING-405 > URL: https://issues.apache.org/jira/browse/SLING-405 > Project: Sling > Issue Type: Task >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The web-console and the obr servlet are common implementations which are > better hosted at the Apache Felix project. > This also includes the deploy part of the sling plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-405) Move web-console and obr servlet to Apache Felix
Move web-console and obr servlet to Apache Felix Key: SLING-405 URL: https://issues.apache.org/jira/browse/SLING-405 Project: Sling Issue Type: Task Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The web-console and the obr servlet are common implementations which are better hosted at the Apache Felix project. This also includes the deploy part of the sling plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-406) Move osgi/log to commons/log
Move osgi/log to commons/log Key: SLING-406 URL: https://issues.apache.org/jira/browse/SLING-406 Project: Sling Issue Type: Task Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The commons folder is a better place for the common log implementation packages will be renamed to o.a.s.commons.* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-404) Move assembly stuff to whiteboard
Move assembly stuff to whiteboard - Key: SLING-404 URL: https://issues.apache.org/jira/browse/SLING-404 Project: Sling Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The assembly stuff is currently not used, therefore we move the osgi/assembly bundle to the whiteboard and move the assembly stuff from the sling maven plugin to a new sling-assembly maven plugin which will be hosted in the whiteboard as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-391) Create base launchpad module for better reuse
[ https://issues.apache.org/jira/browse/SLING-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-391. -- Resolution: Fixed The base module has been created. > Create base launchpad module for better reuse > - > > Key: SLING-391 > URL: https://issues.apache.org/jira/browse/SLING-391 > Project: Sling > Issue Type: Improvement > Components: Launchpad >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > Original Estimate: 0h > Remaining Estimate: 0h > > For better reuse in own projects, the common stuff from the launchpad > app/webapp is moved to an own module. > This module is then used by app/webapp - we have to find a way to define the > bundles at a common place that are used by the > app/webapp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-404) Move assembly stuff to whiteboard
[ https://issues.apache.org/jira/browse/SLING-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-404: --- Component/s: OSGi > Move assembly stuff to whiteboard > - > > Key: SLING-404 > URL: https://issues.apache.org/jira/browse/SLING-404 > Project: Sling > Issue Type: Improvement > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The assembly stuff is currently not used, therefore we move the osgi/assembly > bundle to the whiteboard and move the assembly stuff from the sling maven > plugin to a new sling-assembly maven plugin which will be hosted in the > whiteboard as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-406) Move osgi/log to commons/log
[ https://issues.apache.org/jira/browse/SLING-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-406: --- Component/s: OSGi > Move osgi/log to commons/log > > > Key: SLING-406 > URL: https://issues.apache.org/jira/browse/SLING-406 > Project: Sling > Issue Type: Task > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The commons folder is a better place for the common log implementation > packages will be renamed to o.a.s.commons.* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-405) Move web-console and obr servlet to Apache Felix
[ https://issues.apache.org/jira/browse/SLING-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-405: --- Component/s: OSGi > Move web-console and obr servlet to Apache Felix > > > Key: SLING-405 > URL: https://issues.apache.org/jira/browse/SLING-405 > Project: Sling > Issue Type: Task > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The web-console and the obr servlet are common implementations which are > better hosted at the Apache Felix project. > This also includes the deploy part of the sling plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-400) Separate content loading from resource bundle
[ https://issues.apache.org/jira/browse/SLING-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-400. -- Resolution: Fixed Created new contentloader bundle. > Separate content loading from resource bundle > - > > Key: SLING-400 > URL: https://issues.apache.org/jira/browse/SLING-400 > Project: Sling > Issue Type: Improvement > Components: Resource >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The content loading and the jcr resource handling should be split in two > different bundles, the jcr.contentloader bundle will have the content loading. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-311) Record loaded content to not reload inadvertedly.
[ https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-311. -- Resolution: Fixed Added implementation of content loaded marker Added overwrite and uninstall properties. > Record loaded content to not reload inadvertedly. > - > > Key: SLING-311 > URL: https://issues.apache.org/jira/browse/SLING-311 > Project: Sling > Issue Type: Improvement > Components: Resource >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > Currently, the content loader always reloads content indicated as initial > content from the bundles if the repository does not contain the respective > content. Sometimes it may be desirable to remove the content from the > repository and not get the content reloaded on bundle (or system) restart. > To prevent such content reload, the content loader should take note of loaded > content and not try to reload content, which is marked as "loaded", > regardless of whether the actual content (still) exists or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-404) Move assembly stuff to whiteboard
[ https://issues.apache.org/jira/browse/SLING-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-404: -- Assignee: Carsten Ziegeler > Move assembly stuff to whiteboard > - > > Key: SLING-404 > URL: https://issues.apache.org/jira/browse/SLING-404 > Project: Sling > Issue Type: Improvement > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The assembly stuff is currently not used, therefore we move the osgi/assembly > bundle to the whiteboard and move the assembly stuff from the sling maven > plugin to a new sling-assembly maven plugin which will be hosted in the > whiteboard as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-409) Create own bundle for jackrabbit api and remove the export of jackrabbit classes from the jcr/api bundle
Create own bundle for jackrabbit api and remove the export of jackrabbit classes from the jcr/api bundle Key: SLING-409 URL: https://issues.apache.org/jira/browse/SLING-409 Project: Sling Issue Type: Task Components: API Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-410) Add Utility class derived from the JcrResourceUtil
Add Utility class derived from the JcrResourceUtil -- Key: SLING-410 URL: https://issues.apache.org/jira/browse/SLING-410 Project: Sling Issue Type: New Feature Components: API Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The JcrResourceUtil class from the jcr.resource bundle contains some nice utility methods for handling resources. It would be better to have some of these methods (like getName, getPath etc.) in the api bundle to be able to call these methods directly without wiring the code to the jcr resource bundle We could also add a getParentPath(String path, int level) going "level" levels up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-410) Add Utility class derived from the JcrResourceUtil
[ https://issues.apache.org/jira/browse/SLING-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-410: -- Assignee: Carsten Ziegeler > Add Utility class derived from the JcrResourceUtil > -- > > Key: SLING-410 > URL: https://issues.apache.org/jira/browse/SLING-410 > Project: Sling > Issue Type: New Feature > Components: API >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The JcrResourceUtil class from the jcr.resource bundle contains some nice > utility methods for handling resources. > It would be better to have some of these methods (like getName, getPath etc.) > in the api bundle to be able to call these methods directly without wiring > the code to the jcr resource bundle > We could also add a getParentPath(String path, int level) going "level" > levels up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-328) access to node props in esp
[
https://issues.apache.org/jira/browse/SLING-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-328:
---
Component/s: Scripting
> access to node props in esp
> ---
>
> Key: SLING-328
> URL: https://issues.apache.org/jira/browse/SLING-328
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Reporter: Michael Marth
>
> My .esp looks like
> for (var i in currentNode.getNodes()) {
> if(currentNode.getNodes()[i].getProperty("approved").getString()
> == "true") {
> ...
> Bertrand tells me that in the second line this should work as well:
> if(currentNode.getNodes()[i].approved (...)
> It does not give an exception but the property is undefined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-393) default renderer for .xml
[ https://issues.apache.org/jira/browse/SLING-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-393: --- Component/s: Default Servlets > default renderer for .xml > - > > Key: SLING-393 > URL: https://issues.apache.org/jira/browse/SLING-393 > Project: Sling > Issue Type: Improvement > Components: Default Servlets >Reporter: Michael Marth >Priority: Minor > > I would like to suggest a default renderer for .xml requests, similar to the > .json renderer that exists already. This would allow zero-config remote > access for clients that do not understand json, e.g. desktop apps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-403) Move jcr.default-rtp to samples
[ https://issues.apache.org/jira/browse/SLING-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-403: --- Component/s: Core > Move jcr.default-rtp to samples > --- > > Key: SLING-403 > URL: https://issues.apache.org/jira/browse/SLING-403 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > This is a sample. We have to change the integration tests as they're testing > this sample code as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-329) cannot access node when node name is a number
[
https://issues.apache.org/jira/browse/SLING-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-329:
---
Component/s: Scripting
> cannot access node when node name is a number
> -
>
> Key: SLING-329
> URL: https://issues.apache.org/jira/browse/SLING-329
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Reporter: Michael Marth
>Priority: Minor
>
> the line
> currentNode.getNodes()[i].getProperty("approved").getString()
> gives
> TypeError: Cannot call method "getProperty" of undefined
> (/apps/tss/list/html.esp#8) (500)
> If the node name consists of numbers only (like "11" - but "1" is OK)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-318) UjaxDateValuesTest fails if Sling instance under test has a different timezone setting
[ https://issues.apache.org/jira/browse/SLING-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-318: --- Component/s: Testing > UjaxDateValuesTest fails if Sling instance under test has a different > timezone setting > -- > > Key: SLING-318 > URL: https://issues.apache.org/jira/browse/SLING-318 > Project: Sling > Issue Type: Bug > Components: Testing >Reporter: Bertrand Delacretaz >Priority: Minor > > UjaxDateValuesTest assumes that the target Sling instance uses the same > timezone setting as its own. > No big deal, but we should fix that eventually. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-368) Upgrade Dojo Toolkit bundling to Version 1.1
[ https://issues.apache.org/jira/browse/SLING-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-368: --- Component/s: Extensions > Upgrade Dojo Toolkit bundling to Version 1.1 > - > > Key: SLING-368 > URL: https://issues.apache.org/jira/browse/SLING-368 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Felix Meschberger > > As proposed by Peter in SLING-261, the Dojo Toolkit bundling should be > upgraded to version 1.1 (currently it is 1.0.2) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-386) rules for creating node names should be uniform
[ https://issues.apache.org/jira/browse/SLING-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-386: --- Component/s: Post Servlets > rules for creating node names should be uniform > --- > > Key: SLING-386 > URL: https://issues.apache.org/jira/browse/SLING-386 > Project: Sling > Issue Type: Improvement > Components: Post Servlets >Reporter: Michael Marth > > I have an issue when nodes are created through a form post: consider that I > have a weird string xyz that is not fit as a JCR node name, e.g. because it > contains umlauts or slashes or so. > If I do a post to /content/mynode/* > and give this parameter > name=xyz > this is used as a name hint and xyz is converted something sane (let's call > it xyy_conversion1) > In the next step I want to post to /content/mynode/xyz/* > in order to create a child node of xyz > It seems that in these two cases xyz is converted differently. Thus, in my > example above the second post would not create a child node of the first one, > but rather something like: > -content > |-mynode > |- xyy_conversion1 > |- xyz_conversion_2 >|- node_from_second_post > the conversation algorithms should be the same in both cases -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-302) Create a bundle providing Dojo as resources
[ https://issues.apache.org/jira/browse/SLING-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-302: --- Component/s: Extensions > Create a bundle providing Dojo as resources > --- > > Key: SLING-302 > URL: https://issues.apache.org/jira/browse/SLING-302 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Attachments: dojo-release-1.0.2.zip > > > We have two contributions which provide client-side application (parts) both > based on the dojo toolkit [1]. To make it easier to integrate these two > contributions and to enable future works in this area, I suggest we create a > bundle, which exposes dojo as bundle resources for use by different client > side apps. > [1] http://dojotoolkit.org/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-45) Sling leaks PermSpace memory on restart of the webapp
[ https://issues.apache.org/jira/browse/SLING-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-45: -- Component/s: Core > Sling leaks PermSpace memory on restart of the webapp > - > > Key: SLING-45 > URL: https://issues.apache.org/jira/browse/SLING-45 > Project: Sling > Issue Type: Improvement > Components: Core >Reporter: David Nuescheler >Priority: Minor > > After restarting the Sling webapp a number of times in a Servlet Container I > ran out of PermSpace. > It seems like some classes or other objects are not entirely removed upon > restart of the webapp. > Unfortunately I don't have any detailed memory profiler dump, but I think it > should be reasonably > evident once someone attaches a memory profiler and restarts the webapp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-353) Script engines need DynamicImport-Package *
[ https://issues.apache.org/jira/browse/SLING-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-353: --- Component/s: Scripting > Script engines need DynamicImport-Package * > --- > > Key: SLING-353 > URL: https://issues.apache.org/jira/browse/SLING-353 > Project: Sling > Issue Type: Bug > Components: Scripting >Reporter: Bertrand Delacretaz > > The > * > statement is needed in the pom.xml of all script engines, so that they're > aware of classes contributed by all bundles. > The JSP engine is ok, I'll add this to the javascript engine now, and we need > to check all the others. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-249) Allow mapping nodes to internet domains
[ https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-249: --- Component/s: Core > Allow mapping nodes to internet domains > --- > > Key: SLING-249 > URL: https://issues.apache.org/jira/browse/SLING-249 > Project: Sling > Issue Type: New Feature > Components: Core >Reporter: Vidar S. Ramdal > > Sling should support hosting multiple domains, with different JCR roots. > E.g.: > http://www.domain1.com could map to /content/domain1.com > http://www.domain2.com could map to /content/domain2.com > While developing a website, the fully qualified domain might not be > available. Ideally, the mapping could be configured in a flexible way. One > option would be to maintain a set of regular expressions to match against > URLs. Each regexp would then match to a path in the JCR. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-333) Implement object cleanup mechanism
[ https://issues.apache.org/jira/browse/SLING-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-333: --- Component/s: Core I'm not sure if we should do something like this - the Spring project provides a request listener (perhaps there is a filter as well) which allows to do this kind of stuff, so we should rather reuse this. > Implement object cleanup mechanism > -- > > Key: SLING-333 > URL: https://issues.apache.org/jira/browse/SLING-333 > Project: Sling > Issue Type: New Feature > Components: Core >Reporter: Felix Meschberger > > In a message on the dev list [1] Bertrand stipulated a cleanup feature along > these lines: > I'm talking about *automatic* cleanup of such objects at the end of a > request, scenario: > 1. Object A calls a method M of class C, that creates something that must be > cleaned up (ThreadLocal variable for example) > 2. Before returning, Method M registers itself to be called for cleanup at > the end of request processing > 3. Object A doesn't have to care about cleanup, it will happen automatically. > This is much more foolproof than requiring A to call cleanup explicitely, > hence my suggestion to implement a general (request-scope for now) cleanup > mechanism. > [1] http://markmail.org/message/eeilivxyrm7s5z42 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-404) Move assembly stuff to whiteboard
[ https://issues.apache.org/jira/browse/SLING-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-404. -- Resolution: Fixed Moved the assembly module and the parts from the maven-sling-plugin to the whiteboard. Disabled everything in the web-console that uses assembly classes. > Move assembly stuff to whiteboard > - > > Key: SLING-404 > URL: https://issues.apache.org/jira/browse/SLING-404 > Project: Sling > Issue Type: Improvement > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The assembly stuff is currently not used, therefore we move the osgi/assembly > bundle to the whiteboard and move the assembly stuff from the sling maven > plugin to a new sling-assembly maven plugin which will be hosted in the > whiteboard as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-412) Inconsistent name handling when importing json stuff
Inconsistent name handling when importing json stuff Key: SLING-412 URL: https://issues.apache.org/jira/browse/SLING-412 Project: Sling Issue Type: Bug Components: JSON Reporter: Carsten Ziegeler Fix For: 2.0.0 The json importer looks for a property named "name" to use its value for a node name. Only if this is not available, the json object name is used as the node name. This is an inconsistent behaviour compared to a default json export. As soon as a node has a "name" property this value is used for the name. So exporting nodes with random name properties and importing same results in different node names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-267) Need a better name for the jcr/base module
[ https://issues.apache.org/jira/browse/SLING-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593745#action_12593745 ] Carsten Ziegeler commented on SLING-267: With the recent discussions about renaming and reorganizing, we probably should rename this to jackrabbit-base. Setting this to be fixed for 2.0.0 to get a final consensus. > Need a better name for the jcr/base module > -- > > Key: SLING-267 > URL: https://issues.apache.org/jira/browse/SLING-267 > Project: Sling > Issue Type: Improvement > Components: Repository >Reporter: Bertrand Delacretaz >Priority: Minor > > Currently being discussed on list, > http://markmail.org/message/jln65ifegh3pi5qm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-267) Need a better name for the jcr/base module
[ https://issues.apache.org/jira/browse/SLING-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-267: --- Fix Version/s: 2.0.0 > Need a better name for the jcr/base module > -- > > Key: SLING-267 > URL: https://issues.apache.org/jira/browse/SLING-267 > Project: Sling > Issue Type: Improvement > Components: Repository >Reporter: Bertrand Delacretaz >Priority: Minor > Fix For: 2.0.0 > > > Currently being discussed on list, > http://markmail.org/message/jln65ifegh3pi5qm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-414) Environment properties like sling.id, or sling.home are not available when launchpad is not used.
Environment properties like sling.id, or sling.home are not available when launchpad is not used. - Key: SLING-414 URL: https://issues.apache.org/jira/browse/SLING-414 Project: Sling Issue Type: Bug Components: Core Affects Versions: 2.0.0 Reporter: Carsten Ziegeler The Sling core defines some environment properties like sling.id or sling.home; these props are set by the Sling class from the launchpad. However if you deploy Sling as bundles in a running OSGi container, these props are not available which might cause some bundles to fail. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-416) Sling Post Processor should try to create nodes using longest path first
Sling Post Processor should try to create nodes using longest path first Key: SLING-416 URL: https://issues.apache.org/jira/browse/SLING-416 Project: Sling Issue Type: Bug Components: Post Servlets Reporter: Carsten Ziegeler Fix For: 2.0.0 The current deepGetOrCreateNode method implementation starts from the root node to get/create a complete path. Assumging that /tmp/a/b is passed into the method, first the root node, then tmp, followed by tmp/a and tmp/a/b is tried to get. Each time such a node is not available it is created. This approach has problems when it comes to ACLs; assuming that the current user has only read/write access to a sub tree, this algorithm fails as soon as the root node or the parent node is accessed. Example: user is allowed to read/write to /foo/bar but is neiter allowed to read/write to /foo. In this case as soon as /foo is accessed the processing stops by an exception although the operation is completly legal. The algorithm has to be reverted by using longest path match first, like first checking if /tmp/a/b exists, if not if /tmp/a exists and so on. As soon as a node is found, the creation can start in the same order as currently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-416) Sling Post Processor should try to create nodes using longest path first
[ https://issues.apache.org/jira/browse/SLING-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-416: -- Assignee: Carsten Ziegeler > Sling Post Processor should try to create nodes using longest path first > > > Key: SLING-416 > URL: https://issues.apache.org/jira/browse/SLING-416 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The current deepGetOrCreateNode method implementation starts from the root > node to get/create a complete path. > Assumging that /tmp/a/b is passed into the method, first the root node, then > tmp, followed by tmp/a and tmp/a/b is tried to get. Each time such a node is > not available it is created. > This approach has problems when it comes to ACLs; assuming that the current > user has only read/write access to a sub tree, this algorithm fails as soon > as the root node or the parent node is accessed. Example: user is allowed to > read/write to /foo/bar but is neiter allowed to read/write to /foo. In this > case as soon as /foo is accessed the processing stops by an exception > although the operation is completly legal. > The algorithm has to be reverted by using longest path match first, like > first checking if /tmp/a/b exists, if not if /tmp/a exists and so on. As soon > as a node is found, the creation can start in the same order as currently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-367) change sling:post: to sling: for "command" prefixes in form names
[ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-367. -- Resolution: Fixed I changed the prefix to ":" in revision 652804 > change sling:post: to sling: for "command" prefixes in form names > - > > Key: SLING-367 > URL: https://issues.apache.org/jira/browse/SLING-367 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Affects Versions: 2.0.0 >Reporter: David Nuescheler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > I think it is fair to also prefix the form elements that express certain > "commands" > with "sling:" since they are sling related. > i see it more as a side effect that the "sling:resourceType" also gets > persisted. > generally, i think everything that has something to with "sling" should be > prefixed > with "sling". > I think we need to make sure that we don't complicate the most simple cases > just > to a avoid possible collisions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-416) Sling Post Processor should try to create nodes using longest path first
[ https://issues.apache.org/jira/browse/SLING-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-416. -- Resolution: Fixed Fixed in 652805 > Sling Post Processor should try to create nodes using longest path first > > > Key: SLING-416 > URL: https://issues.apache.org/jira/browse/SLING-416 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The current deepGetOrCreateNode method implementation starts from the root > node to get/create a complete path. > Assumging that /tmp/a/b is passed into the method, first the root node, then > tmp, followed by tmp/a and tmp/a/b is tried to get. Each time such a node is > not available it is created. > This approach has problems when it comes to ACLs; assuming that the current > user has only read/write access to a sub tree, this algorithm fails as soon > as the root node or the parent node is accessed. Example: user is allowed to > read/write to /foo/bar but is neiter allowed to read/write to /foo. In this > case as soon as /foo is accessed the processing stops by an exception > although the operation is completly legal. > The algorithm has to be reverted by using longest path match first, like > first checking if /tmp/a/b exists, if not if /tmp/a exists and so on. As soon > as a node is found, the creation can start in the same order as currently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-409) Create own bundle for jackrabbit api and remove the export of jackrabbit classes from the jcr/api bundle
[ https://issues.apache.org/jira/browse/SLING-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-409. -- Resolution: Fixed Created new bundle. > Create own bundle for jackrabbit api and remove the export of jackrabbit > classes from the jcr/api bundle > > > Key: SLING-409 > URL: https://issues.apache.org/jira/browse/SLING-409 > Project: Sling > Issue Type: Task > Components: API >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-410) Add Utility class derived from the JcrResourceUtil
[ https://issues.apache.org/jira/browse/SLING-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-410. -- Resolution: Fixed Moved some methods from the JcrResourceUtils to new class ResourceUtil. > Add Utility class derived from the JcrResourceUtil > -- > > Key: SLING-410 > URL: https://issues.apache.org/jira/browse/SLING-410 > Project: Sling > Issue Type: New Feature > Components: API >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The JcrResourceUtil class from the jcr.resource bundle contains some nice > utility methods for handling resources. > It would be better to have some of these methods (like getName, getPath etc.) > in the api bundle to be able to call these methods directly without wiring > the code to the jcr resource bundle > We could also add a getParentPath(String path, int level) going "level" > levels up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-418) Move Eventing and scheduling to extensions
Move Eventing and scheduling to extensions -- Key: SLING-418 URL: https://issues.apache.org/jira/browse/SLING-418 Project: Sling Issue Type: Improvement Components: Core Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-417) Move sling/threads to commons/threads
Move sling/threads to commons/threads - Key: SLING-417 URL: https://issues.apache.org/jira/browse/SLING-417 Project: Sling Issue Type: Improvement Components: Core Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-416) Sling Post Processor should try to create nodes using longest path first
[ https://issues.apache.org/jira/browse/SLING-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594142#action_12594142 ] Carsten Ziegeler commented on SLING-416: Hi, this has been fixed in the SlingPostProcessor. > Sling Post Processor should try to create nodes using longest path first > > > Key: SLING-416 > URL: https://issues.apache.org/jira/browse/SLING-416 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The current deepGetOrCreateNode method implementation starts from the root > node to get/create a complete path. > Assumging that /tmp/a/b is passed into the method, first the root node, then > tmp, followed by tmp/a and tmp/a/b is tried to get. Each time such a node is > not available it is created. > This approach has problems when it comes to ACLs; assuming that the current > user has only read/write access to a sub tree, this algorithm fails as soon > as the root node or the parent node is accessed. Example: user is allowed to > read/write to /foo/bar but is neiter allowed to read/write to /foo. In this > case as soon as /foo is accessed the processing stops by an exception > although the operation is completly legal. > The algorithm has to be reverted by using longest path match first, like > first checking if /tmp/a/b exists, if not if /tmp/a exists and so on. As soon > as a node is found, the creation can start in the same order as currently. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-412) Inconsistent name handling when importing json stuff
[
https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594143#action_12594143
]
Carsten Ziegeler commented on SLING-412:
Yes, I think this is what needs to be fixed. Imagine I export node "A" which
has a "name" property with value "B". My json of the export looks like this:
{
"name":"B"
}
Importing this by putting it into a file named "A.json" results in a new node
named "B".
I think we should use an artifical property which is not allowed as a real
property name, like we do in the sling post servlets (where we use ":name")
> Inconsistent name handling when importing json stuff
>
>
> Key: SLING-412
> URL: https://issues.apache.org/jira/browse/SLING-412
> Project: Sling
> Issue Type: Bug
> Components: JSON
>Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
>
> The json importer looks for a property named "name" to use its value for a
> node name. Only if this is not available, the json object name is used as the
> node name.
> This is an inconsistent behaviour compared to a default json export. As soon
> as a node has a "name" property this value is used for the name. So exporting
> nodes with random name properties and importing same results in different
> node names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-406) Move osgi/log to commons/log
[ https://issues.apache.org/jira/browse/SLING-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-406: -- Assignee: Carsten Ziegeler > Move osgi/log to commons/log > > > Key: SLING-406 > URL: https://issues.apache.org/jira/browse/SLING-406 > Project: Sling > Issue Type: Task > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The commons folder is a better place for the common log implementation > packages will be renamed to o.a.s.commons.* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-417) Move sling/threads to commons/threads
[ https://issues.apache.org/jira/browse/SLING-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-417. -- Resolution: Fixed Moved. > Move sling/threads to commons/threads > - > > Key: SLING-417 > URL: https://issues.apache.org/jira/browse/SLING-417 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-406) Move osgi/log to commons/log
[ https://issues.apache.org/jira/browse/SLING-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-406. -- Resolution: Fixed Moved > Move osgi/log to commons/log > > > Key: SLING-406 > URL: https://issues.apache.org/jira/browse/SLING-406 > Project: Sling > Issue Type: Task > Components: OSGi >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The commons folder is a better place for the common log implementation > packages will be renamed to o.a.s.commons.* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-413) Unloading initial content during bundle update fails with NPE and subsequent locked bundle content node
[ https://issues.apache.org/jira/browse/SLING-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-413: -- Assignee: Carsten Ziegeler > Unloading initial content during bundle update fails with NPE and subsequent > locked bundle content node > --- > > Key: SLING-413 > URL: https://issues.apache.org/jira/browse/SLING-413 > Project: Sling > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0 > Environment: Darwin 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4 > 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386, > java version "1.5.0_13" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237) > Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing) >Reporter: Dominique Jäggi >Assignee: Carsten Ziegeler > > when deploying a bundle using the maven-sling-plugin to a running sling > instance the following errors produce themselves should the bundle contain > initial content: > 02.05.2008 11:52:07.237 *ERROR* [Background Update com.mycompany.mybundle > (77)] org.apache.sling.jcr.contentloader.internal.ContentLoaderService > bundleChanged: Problem unloading initial content of bundle > com.mycompany.mybundle (77) java.lang.NullPointerException > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.contentIsUninstalled(ContentLoaderService.java:320) > at > org.apache.sling.jcr.contentloader.internal.Loader.unregisterBundle(Loader.java:193) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:134) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568) > at org.apache.felix.framework.Felix._stopBundle(Felix.java:2010) > at org.apache.felix.framework.Felix.stopBundle(Felix.java:1920) > at org.apache.felix.framework.Felix._updateBundle(Felix.java:1757) > at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719) > at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$InstallHelper.run(InstallAction.java:278) > with a subsequent "pending changes" state of the associated bundle content > node: > 02.05.2008 11:52:07.288 *ERROR* [Background Update com.mycompany.mybundle > (77)] org.apache.sling.jcr.contentloader.internal.Loader Cannot load initial > content for bundle com.mycompany.mybundle : Unable to lock node. Node has > pending changes: /var/sling/bundle-content/com.mycompany.mybundle > javax.jcr.InvalidItemStateException: Unable to lock node. Node has pending > changes: /var/sling/bundle-content/com.mycompany.mybundle > at org.apache.jackrabbit.core.NodeImpl.lock(NodeImpl.java:4092) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.getBundleContentInfo(ContentLoaderService.java:279) > at > org.apache.sling.jcr.contentloader.internal.Loader.registerBundleInternal(Loader.java:143) > at > org.apache.sling.jcr.contentloader.internal.Loader.registerBundle(Loader.java:107) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:123) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568) > at org.apache.felix.framework.Felix._updateBundle(Felix.java:1848) > at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719) > at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$InstallHelper.run(InstallAction.java:278) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-412) Inconsistent name handling when importing json stuff
[ https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594186#action_12594186 ] Carsten Ziegeler commented on SLING-412: I'm fine with removing this feature completly as well. There could only be the case, when it is too difficult (not possible) to use the correct file name for the json file; but so far I don't see this as a problem atm; we can fix this when the problem arises. > Inconsistent name handling when importing json stuff > > > Key: SLING-412 > URL: https://issues.apache.org/jira/browse/SLING-412 > Project: Sling > Issue Type: Bug > Components: JSON >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The json importer looks for a property named "name" to use its value for a > node name. Only if this is not available, the json object name is used as the > node name. > This is an inconsistent behaviour compared to a default json export. As soon > as a node has a "name" property this value is used for the name. So exporting > nodes with random name properties and importing same results in different > node names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-418) Move Eventing and scheduling to extensions
[ https://issues.apache.org/jira/browse/SLING-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-418. -- Resolution: Fixed Moved > Move Eventing and scheduling to extensions > -- > > Key: SLING-418 > URL: https://issues.apache.org/jira/browse/SLING-418 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-412) Inconsistent name handling when importing json stuff
[ https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-412: -- Assignee: Carsten Ziegeler > Inconsistent name handling when importing json stuff > > > Key: SLING-412 > URL: https://issues.apache.org/jira/browse/SLING-412 > Project: Sling > Issue Type: Bug > Components: JSON >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The json importer looks for a property named "name" to use its value for a > node name. Only if this is not available, the json object name is used as the > node name. > This is an inconsistent behaviour compared to a default json export. As soon > as a node has a "name" property this value is used for the name. So exporting > nodes with random name properties and importing same results in different > node names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-412) Inconsistent name handling when importing json stuff
[ https://issues.apache.org/jira/browse/SLING-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-412. -- Resolution: Fixed Removed in 653413 > Inconsistent name handling when importing json stuff > > > Key: SLING-412 > URL: https://issues.apache.org/jira/browse/SLING-412 > Project: Sling > Issue Type: Bug > Components: JSON >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The json importer looks for a property named "name" to use its value for a > node name. Only if this is not available, the json object name is used as the > node name. > This is an inconsistent behaviour compared to a default json export. As soon > as a node has a "name" property this value is used for the name. So exporting > nodes with random name properties and importing same results in different > node names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-267) Need a better name for the jcr/base module
[ https://issues.apache.org/jira/browse/SLING-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-267. -- Resolution: Won't Fix I see your point, so let's leave it like it it and close this issue. > Need a better name for the jcr/base module > -- > > Key: SLING-267 > URL: https://issues.apache.org/jira/browse/SLING-267 > Project: Sling > Issue Type: Improvement > Components: Repository >Reporter: Bertrand Delacretaz >Priority: Minor > Fix For: 2.0.0 > > > Currently being discussed on list, > http://markmail.org/message/jln65ifegh3pi5qm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-403) Move jcr.default-rtp to samples
[ https://issues.apache.org/jira/browse/SLING-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-403: -- Assignee: Carsten Ziegeler > Move jcr.default-rtp to samples > --- > > Key: SLING-403 > URL: https://issues.apache.org/jira/browse/SLING-403 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > This is a sample. We have to change the integration tests as they're testing > this sample code as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-403) Move jcr.default-rtp to samples
[ https://issues.apache.org/jira/browse/SLING-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-403. -- Resolution: Fixed Moved to path based rtp sample > Move jcr.default-rtp to samples > --- > > Key: SLING-403 > URL: https://issues.apache.org/jira/browse/SLING-403 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > This is a sample. We have to change the integration tests as they're testing > this sample code as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-423) TimedJobHandler: error is thrown while executing timed job
[ https://issues.apache.org/jira/browse/SLING-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-423: --- Fix Version/s: 2.0.0 > TimedJobHandler: error is thrown while executing timed job > -- > > Key: SLING-423 > URL: https://issues.apache.org/jira/browse/SLING-423 > Project: Sling > Issue Type: Bug > Components: Event >Reporter: Philipp Koch >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > Attachments: event.patch > > > the eventing resp. event processing works but the post processing (cleaning > up) the persisted event (node) fails: > 1. the timedjobhandler creates a node of type slingevent:TimedEvent. the node > name got created by cancatenating the topicId and the jobid. > 2. the event handler executes the job abnd loads the persisted node(for > deletion) and creates a slightly different jobid which is then used to > retrieve the node. this fails with the following stacktrace: > 05.05.2008 16:38:15.540 *ERROR* [pool-1-thread-3] > org.apache.sling.event.impl.TimedJobHandler Unable to create a session. > javax.jcr.RepositoryException: failed to resolve path TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019 > relative to /var/eventing/timed-jobs: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:237) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.execute(TimedJobHandler.java:469) > at > org.apache.sling.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:66) > at org.quartz.core.JobRunShell.run(JobRunShell.java:203) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > ... 7 more > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.execute(TimedJobHandler.java:469) > at > org.apache.sling.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:66) > at org.quartz.core.JobRunShell.run(JobRunShell.java:203) > at java.util.con
[jira] Assigned: (SLING-423) TimedJobHandler: error is thrown while executing timed job
[ https://issues.apache.org/jira/browse/SLING-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-423: -- Assignee: Carsten Ziegeler > TimedJobHandler: error is thrown while executing timed job > -- > > Key: SLING-423 > URL: https://issues.apache.org/jira/browse/SLING-423 > Project: Sling > Issue Type: Bug > Components: Event >Reporter: Philipp Koch >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > Attachments: event.patch > > > the eventing resp. event processing works but the post processing (cleaning > up) the persisted event (node) fails: > 1. the timedjobhandler creates a node of type slingevent:TimedEvent. the node > name got created by cancatenating the topicId and the jobid. > 2. the event handler executes the job abnd loads the persisted node(for > deletion) and creates a slightly different jobid which is then used to > retrieve the node. this fails with the following stacktrace: > 05.05.2008 16:38:15.540 *ERROR* [pool-1-thread-3] > org.apache.sling.event.impl.TimedJobHandler Unable to create a session. > javax.jcr.RepositoryException: failed to resolve path TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019 > relative to /var/eventing/timed-jobs: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:237) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.execute(TimedJobHandler.java:469) > at > org.apache.sling.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:66) > at org.quartz.core.JobRunShell.run(JobRunShell.java:203) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > ... 7 more > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.execute(TimedJobHandler.java:469) > at > org.apache.sling.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:66) > at org.quartz.core.JobRunShell.run(JobRunShell.java:203) > at j
[jira] Updated: (SLING-423) TimedJobHandler: error is thrown while executing timed job
[ https://issues.apache.org/jira/browse/SLING-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-423: --- Remaining Estimate: 0h Original Estimate: 0h I applied a slightly modified version which should have the same behaviour. Can you please cross check and then close this bug? Thanks! > TimedJobHandler: error is thrown while executing timed job > -- > > Key: SLING-423 > URL: https://issues.apache.org/jira/browse/SLING-423 > Project: Sling > Issue Type: Bug > Components: Event >Reporter: Philipp Koch >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > Attachments: event.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > the eventing resp. event processing works but the post processing (cleaning > up) the persisted event (node) fails: > 1. the timedjobhandler creates a node of type slingevent:TimedEvent. the node > name got created by cancatenating the topicId and the jobid. > 2. the event handler executes the job abnd loads the persisted node(for > deletion) and creates a slightly different jobid which is then used to > retrieve the node. this fails with the following stacktrace: > 05.05.2008 16:38:15.540 *ERROR* [pool-1-thread-3] > org.apache.sling.event.impl.TimedJobHandler Unable to create a session. > javax.jcr.RepositoryException: failed to resolve path TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019 > relative to /var/eventing/timed-jobs: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start: 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:237) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.execute(TimedJobHandler.java:469) > at > org.apache.sling.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:66) > at org.quartz.core.JobRunShell.run(JobRunShell.java:203) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > ... 7 more > org.apache.jackrabbit.spi.commons.conversion.MalformedPathException: > 'TimedEvent: > com/day/cq/workflow/timeout/job::/home/groups/a/administrators/workflow-inbox/node3_etc_workflow_instances_2008-05-05_testli_2285454820460019' > is not a valid path. ' ' not valid name start > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:223) > at > org.apache.jackrabbit.spi.commons.conversion.PathParser.parse(PathParser.java:57) > at > org.apache.jackrabbit.spi.commons.conversion.ParsingPathResolver.getQPath(ParsingPathResolver.java:60) > at > org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getQPath(CachingPathResolver.java:77) > at > org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQPath(DefaultNamePathResolver.java:69) > at org.apache.jackrabbit.core.SessionImpl.getQPath(SessionImpl.java:649) > at > org.apache.jackrabbit.core.NodeImpl.resolveRelativeNodePath(NodeImpl.java:209) > at org.apache.jackrabbit.core.NodeImpl.hasNode(NodeImpl.java:2563) > at > org.apache.sling.event.impl.TimedJobHandler.exe
[jira] Updated: (SLING-398) [Patch] Separate bundle details page in sling web console
[ https://issues.apache.org/jira/browse/SLING-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-398: --- Remaining Estimate: 0h Original Estimate: 0h Could you please submit an updated patch against the latest svn? > [Patch] Separate bundle details page in sling web console > - > > Key: SLING-398 > URL: https://issues.apache.org/jira/browse/SLING-398 > Project: Sling > Issue Type: New Feature > Components: Console >Reporter: Alexander Klimetschek > Attachments: bundle-details-html-page.patch, > bundle-details-html-page.patch, bundle-details-html-page.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > This patch adds a separate HTML page showing bundle details to the Sling web > console. It displays the same details as those displayed by the ajax-based > "popup". > Use case: I found myself configuring a bundle with Export-Package etc. and > continuously installing it to Sling to see if all package dependencies could > be resolved. It is quite tedious to reload the bundle list page, scroll down > to the bundle in question and click on the link to get the ajax-based details > popup. A simpler (and more restful) way is to have a separate URL and HTML > page for a single bundle's details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-431) Unexplained NPE in AbstractSlingRepository.pingAndCheck
[
https://issues.apache.org/jira/browse/SLING-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594904#action_12594904
]
Carsten Ziegeler commented on SLING-431:
I experienced the same strange log entry about the ClassNotFoundException. The
reason was that my repository client bundle did not have an import for
org.osgi.service.log. This *should* be generated by the maven plugin, but for
some strange reasons it did not. Even more strange: the app did run without any
problems.
So have a look if this import is in the client bundle; if not it should be
added.
> Unexplained NPE in AbstractSlingRepository.pingAndCheck
> ---
>
> Key: SLING-431
> URL: https://issues.apache.org/jira/browse/SLING-431
> Project: Sling
> Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Priority: Minor
>
> I've found this trace in the log of my custom launchpad-based Sling webapp:
> Exception in thread "Repository Pinger" java.lang.NullPointerException
> at
> org.apache.sling.jcr.base.AbstractSlingRepository.pingAndCheck(AbstractSlingRepository.java:481)
> at
> org.apache.sling.jcr.base.AbstractSlingRepository.run(AbstractSlingRepository.java:898)
> at java.lang.Thread.run(Thread.java:613)
> This happened at startup, but only once with many successful startups with
> the same code and configuration.
> The corresponding code line is the log.log call in
> } catch(RepositoryException re) {
> log.log(LogService.LOG_INFO, "pingAndCheck;
> loginAdministrative failed", re);
> }
> So the only explanation is that log is null, which is "impossible" looking at
> the source code: the thread that calls pingAndCheck is created in activate(),
> which must be called by the OSGi framework after initializing the log member
> variable:
> /** @scr.reference bind="bindLog" unbind="unbindLog" */
> private LogService log;
> There is something weird about the log class, in the error log:
> 07.05.2008 13:20:39.574 *ERROR* [SCR Component Actor]
> org.apache.sling.jcr.jackrabbit.client
> [org.apache.sling.jcr.jackrabbit.client.SlingClientRepository] Cannot load
> class used as parameter org.osgi.service.log.Lo
> gService (java.lang.ClassNotFoundException: org.osgi.service.log.LogService)
> java.lang.ClassNotFoundException: org.osgi.service.log.LogService
> at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1504)
> That happens before the above NPE.
> I won't investigate further for now, but this looks like a weird
> timing-related bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-298) FormEncoding parameter should be ignored during POST processing
[ https://issues.apache.org/jira/browse/SLING-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-298. -- Resolution: Fixed > FormEncoding parameter should be ignored during POST processing > --- > > Key: SLING-298 > URL: https://issues.apache.org/jira/browse/SLING-298 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The FormEncoding parameter should be ignored during post processing and not > be set as a property. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-425) SlingLogFileWriter fails three test cases
[ https://issues.apache.org/jira/browse/SLING-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-425: --- Fix Version/s: 2.0.0 This should be fixed for the first release > SlingLogFileWriter fails three test cases > - > > Key: SLING-425 > URL: https://issues.apache.org/jira/browse/SLING-425 > Project: Sling > Issue Type: Bug > Components: Testing > Environment: Windows >Reporter: Paul Noden >Priority: Minor > Fix For: 2.0.0 > > Attachments: SlingLogFileWriterTest.java > > > The test for SlingLogFileWriter failed in the three test cases in > SlingLogFileWriterTest where assertTrue(test.exists() && test.length() > 0) > is made. I took the liberty of commenting out from this line to the end of > each test case and found that all the other tests in the build process on > windows still reported successful - with the exception of the tests run once > sling has started up, all of which fail with "Sling services not > available."- I'm hoping this is a consequence of these logging issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-413) Unloading initial content during bundle update fails with NPE and subsequent locked bundle content node
[ https://issues.apache.org/jira/browse/SLING-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-413. -- Resolution: Fixed Fix Version/s: 2.0.0 > Unloading initial content during bundle update fails with NPE and subsequent > locked bundle content node > --- > > Key: SLING-413 > URL: https://issues.apache.org/jira/browse/SLING-413 > Project: Sling > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0 > Environment: Darwin 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4 > 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386, > java version "1.5.0_13" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237) > Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing) >Reporter: Dominique Jäggi >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > when deploying a bundle using the maven-sling-plugin to a running sling > instance the following errors produce themselves should the bundle contain > initial content: > 02.05.2008 11:52:07.237 *ERROR* [Background Update com.mycompany.mybundle > (77)] org.apache.sling.jcr.contentloader.internal.ContentLoaderService > bundleChanged: Problem unloading initial content of bundle > com.mycompany.mybundle (77) java.lang.NullPointerException > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.contentIsUninstalled(ContentLoaderService.java:320) > at > org.apache.sling.jcr.contentloader.internal.Loader.unregisterBundle(Loader.java:193) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:134) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568) > at org.apache.felix.framework.Felix._stopBundle(Felix.java:2010) > at org.apache.felix.framework.Felix.stopBundle(Felix.java:1920) > at org.apache.felix.framework.Felix._updateBundle(Felix.java:1757) > at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719) > at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$InstallHelper.run(InstallAction.java:278) > with a subsequent "pending changes" state of the associated bundle content > node: > 02.05.2008 11:52:07.288 *ERROR* [Background Update com.mycompany.mybundle > (77)] org.apache.sling.jcr.contentloader.internal.Loader Cannot load initial > content for bundle com.mycompany.mybundle : Unable to lock node. Node has > pending changes: /var/sling/bundle-content/com.mycompany.mybundle > javax.jcr.InvalidItemStateException: Unable to lock node. Node has pending > changes: /var/sling/bundle-content/com.mycompany.mybundle > at org.apache.jackrabbit.core.NodeImpl.lock(NodeImpl.java:4092) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.getBundleContentInfo(ContentLoaderService.java:279) > at > org.apache.sling.jcr.contentloader.internal.Loader.registerBundleInternal(Loader.java:143) > at > org.apache.sling.jcr.contentloader.internal.Loader.registerBundle(Loader.java:107) > at > org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:123) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:532) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3568) > at org.apache.felix.framework.Felix._updateBundle(Felix.java:1848) > at org.apache.felix.framework.Felix.updateBundle(Felix.java:1719) > at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:372) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$2.doRun(InstallAction.java:242) > at > org.apache.sling.osgi.console.web.internal.core.InstallAction$InstallHelper.run(InstallAction.java:278) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-439) Clean up node type definitions
Clean up node type definitions -- Key: SLING-439 URL: https://issues.apache.org/jira/browse/SLING-439 Project: Sling Issue Type: Improvement Components: Core Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: 2.0.0 The following node types will be removed: sling/core: references.cnd and selection.cnd together with the *.objects.* classes from core The content.cnd will be moved to the jcr.resource module (together with docs) In the i18n module, message.cnd and slinglanguage.cnd will be combined into a single file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-247: -- Assignee: Carsten Ziegeler > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595187#action_12595187 ] Carsten Ziegeler commented on SLING-247: I think we should remove the resource resolver. To get the resource resolver, it's just "slingRequest.getResourceResolver()" The service locator has already gone. > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595192#action_12595192 ] Carsten Ziegeler commented on SLING-247: Rethinking again, I'll keep the resource resolver :) > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595223#action_12595223 ] Carsten Ziegeler commented on SLING-247: As discussed on the mailing list: no need to support "flush" Bindings won't be made available as request attributes, the SlingBindings will be available as a request attribute instead. > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595225#action_12595225 ] Carsten Ziegeler commented on SLING-247: As discussed on the mailing list, the support for object mapping will be removed as well. > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-247) Provide Scripting variables as request attributes for JSP
[ https://issues.apache.org/jira/browse/SLING-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-247. -- Resolution: Fixed > Provide Scripting variables as request attributes for JSP > - > > Key: SLING-247 > URL: https://issues.apache.org/jira/browse/SLING-247 > Project: Sling > Issue Type: Improvement > Components: JSP >Reporter: Felix Meschberger >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The scripting variables defined in the SlingBIndings class are defined as > global variables in script language bindings such as JavaScript and Velocity. > In JSP this binding does not exist yet. > The issue with JSP is, that JSPs are translated using a text-transformation > to a Java class implementing the Servlet interface. As such there is no such > thing as a global variable. A workaround to inject well known objects is > implemented with tag. But this tag does not make the > same defined variables available. > I suggest to enhance JSP scripting as follows: > (1) Bindings as Request Attributes > All bindings defined in the SlingBindings object prepared for the script > evaluation are stored as request attributes for use by the JSP. > (2) Predefined bindings as variables through > Some of the predefined bindings in the SlingBIndings object are mapped as > variables in the JSP when using the tag. Some variable > require special treatment: > - request: The request variable already exists and is of type > HttpServletRequest, the SlingHttpServletRequest object is bound as the > slingRequest variable. > - response: Same as for the request. The SlingHttpServletResponse object is > bound as slingResponse > - sling: Bound as is of type SlingScriptHelper > - resource: Bound as is of type Resource > - out: already bound by the JSP spec, nothing to be done > - flush: Bound as is of type boolean > - log: Bound as is of type org.slf4j.Logger > The variable names listed above (slingRequest, slingResponse, sling, > resource, flush, log) may be overwritten by specifying another name in the > defineObjects tag, such as do use > "logger" as the name of the "Logger". > (3) additional bindings only for JSP when using > Currently the sling:defineObjects tag provides further variables: the JCR > Node to which the resource adapts, (optionally) the mapped object to which > the resource adapts (if the respective class is declared), the resource > resolver and the service locator. I suggest we just keep these variables, > though they are most probably definitely overkill -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-439) Clean up node type definitions
[ https://issues.apache.org/jira/browse/SLING-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595254#action_12595254 ] Carsten Ziegeler commented on SLING-439: Cleaned up i18n, removed references.cnd and moved content.cnd I'll wait a little bit longer to give people time to respond to the remaining changes: removal of selection.cnd etc. > Clean up node type definitions > -- > > Key: SLING-439 > URL: https://issues.apache.org/jira/browse/SLING-439 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The following node types will be removed: > sling/core: references.cnd and selection.cnd together with the *.objects.* > classes from core > The content.cnd will be moved to the jcr.resource module (together with docs) > In the i18n module, message.cnd and slinglanguage.cnd will be combined into a > single file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-440) testInfiniteLoopDetection fails in full build with Maven 2.0.9
[ https://issues.apache.org/jira/browse/SLING-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595339#action_12595339 ] Carsten Ziegeler commented on SLING-440: This works for me; same environment. > testInfiniteLoopDetection fails in full build with Maven 2.0.9 > -- > > Key: SLING-440 > URL: https://issues.apache.org/jira/browse/SLING-440 > Project: Sling > Issue Type: Bug > Environment: macosx 10.4.11, java version "1.5.0_13", mvn 2.0.9 >Reporter: Bertrand Delacretaz > > The IncludeTest.testInfiniteLoopDetection fails (AssertionFailedError: > Response contains infinite loop error message) when doing "mvn clean install" > from the top of the Sling code tree. > The same test works with mvn 2.0.7, or when doing "mvn clean install" > directly in the launchpad/webapp directory with either mvn version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-414) Environment properties like sling.id, or sling.home are not available when launchpad is not used.
[ https://issues.apache.org/jira/browse/SLING-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-414: --- Fix Version/s: 2.0.0 One of the main goals of Sling should be to run in any OSGi container. As we have to find a way of providing these values independent from the used container, this might come with api changes, therefore setting this to be fixed for 2.0.0 > Environment properties like sling.id, or sling.home are not available when > launchpad is not used. > - > > Key: SLING-414 > URL: https://issues.apache.org/jira/browse/SLING-414 > Project: Sling > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > > The Sling core defines some environment properties like sling.id or > sling.home; these props are set by the Sling class from the launchpad. > However if you deploy Sling as bundles in a running OSGi container, these > props are not available which might cause some bundles to fail. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-442) Check osgi exports, imports, manifest entries (nodetypes etc.) and dependencies
Check osgi exports, imports, manifest entries (nodetypes etc.) and dependencies --- Key: SLING-442 URL: https://issues.apache.org/jira/browse/SLING-442 Project: Sling Issue Type: Task Components: Core Reporter: Carsten Ziegeler Fix For: 2.0.0 We should check all poms for accurancy before the release as due to the refactoring some poms might not be correct anymore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-439) Clean up node type definitions
[ https://issues.apache.org/jira/browse/SLING-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-439. -- Resolution: Fixed Removed selector node type together with object handling stuff from core. > Clean up node type definitions > -- > > Key: SLING-439 > URL: https://issues.apache.org/jira/browse/SLING-439 > Project: Sling > Issue Type: Improvement > Components: Core >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > The following node types will be removed: > sling/core: references.cnd and selection.cnd together with the *.objects.* > classes from core > The content.cnd will be moved to the jcr.resource module (together with docs) > In the i18n module, message.cnd and slinglanguage.cnd will be combined into a > single file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-394) remove "sling:post:saveParamPrefix";
[ https://issues.apache.org/jira/browse/SLING-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-394: --- Fix Version/s: 2.0.0 This is something we should consider for the first release > remove "sling:post:saveParamPrefix"; > > > Key: SLING-394 > URL: https://issues.apache.org/jira/browse/SLING-394 > Project: Sling > Issue Type: Bug > Components: Post Servlets >Reporter: David Nuescheler >Priority: Minor > Fix For: 2.0.0 > > > since i have not seen a usecase where it would be helpful to specify the > saveParamPrefix to something > different than "./" i would recommend that we remove this option. > does someone have a good usecase for that? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-441) Windows Users receiving java.lang.NoClassDefFoundError: org/apache/sling/launcher/webapp/SlingServlet$ServletContextResourceProvider
[ https://issues.apache.org/jira/browse/SLING-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-441: --- Fix Version/s: 2.0.0 > Windows Users receiving java.lang.NoClassDefFoundError: > org/apache/sling/launcher/webapp/SlingServlet$ServletContextResourceProvider > > > Key: SLING-441 > URL: https://issues.apache.org/jira/browse/SLING-441 > Project: Sling > Issue Type: Bug > Components: Testing > Environment: Windows >Reporter: Paul Noden >Priority: Minor > Fix For: 2.0.0 > > Attachments: failure.txt > > > Windows Users recieve java.lang.NoClassDefFoundError: > org/apache/sling/launcher/webapp/SlingServlet$ServletContextResourceProvider > when running tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-445) RequestPathInfo.getResourcePath returns complete path including extension
[ https://issues.apache.org/jira/browse/SLING-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-445: -- Assignee: Carsten Ziegeler > RequestPathInfo.getResourcePath returns complete path including extension > - > > Key: SLING-445 > URL: https://issues.apache.org/jira/browse/SLING-445 > Project: Sling > Issue Type: Bug > Components: API >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > It seems that at least in some cases, the RequestPathInfo.getResourcePath() > includes the selectors and extensions (which it should omit) > I have a request to a non existing resource: /a/b.html and getResourcePath() > returns "/a/b.html" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-445) RequestPathInfo.getResourcePath returns complete path including extension
RequestPathInfo.getResourcePath returns complete path including extension - Key: SLING-445 URL: https://issues.apache.org/jira/browse/SLING-445 Project: Sling Issue Type: Bug Components: API Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 It seems that at least in some cases, the RequestPathInfo.getResourcePath() includes the selectors and extensions (which it should omit) I have a request to a non existing resource: /a/b.html and getResourcePath() returns "/a/b.html" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-445) RequestPathInfo.getResourcePath returns complete path including extension
[ https://issues.apache.org/jira/browse/SLING-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-445. -- Resolution: Invalid The current behaviour is correct as this is a non existing resource, so it is unclear what makes up the selectors or extensions. > RequestPathInfo.getResourcePath returns complete path including extension > - > > Key: SLING-445 > URL: https://issues.apache.org/jira/browse/SLING-445 > Project: Sling > Issue Type: Bug > Components: API >Affects Versions: 2.0.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: 2.0.0 > > > It seems that at least in some cases, the RequestPathInfo.getResourcePath() > includes the selectors and extensions (which it should omit) > I have a request to a non existing resource: /a/b.html and getResourcePath() > returns "/a/b.html" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-446) Move Scheduling to commons
Move Scheduling to commons -- Key: SLING-446 URL: https://issues.apache.org/jira/browse/SLING-446 Project: Sling Issue Type: Task Components: Scheduler Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The scheduler is a common bundle which has no dependencies to Sling itself, so we should move it to commons. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-447) Schedule jobs n times
Schedule jobs n times - Key: SLING-447 URL: https://issues.apache.org/jira/browse/SLING-447 Project: Sling Issue Type: Improvement Components: Scheduler Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Priority: Minor Currently its only possible to schedule a job either ones or forever; it would be nice to schedule a job n times perhaps also starting at a given time etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-448) Schedule jobs n times
Schedule jobs n times - Key: SLING-448 URL: https://issues.apache.org/jira/browse/SLING-448 Project: Sling Issue Type: Improvement Components: Event Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Currently its only possible to schedule a job either ones or forever; it would be nice to schedule a job n times perhaps also starting at a given time etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-450) Move bundles from "sling" to extensions
Move bundles from "sling" to extensions --- Key: SLING-450 URL: https://issues.apache.org/jira/browse/SLING-450 Project: Sling Issue Type: Task Components: Core Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Fix For: 2.0.0 The following bundles should be moved to the extensions directory: adapter, bundleresource, httpauth, i18n -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
