[jira] Resolved: (SLING-1890) JCR Explorer - improvements
[ https://issues.apache.org/jira/browse/SLING-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss resolved SLING-1890. - Resolution: Fixed commited in r1043469 > JCR Explorer - improvements > --- > > Key: SLING-1890 > URL: https://issues.apache.org/jira/browse/SLING-1890 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Clemens Wyss >Assignee: Clemens Wyss > > + improved error handling/reporting > + create sub node(s) on root node > + ajax timeout handling > + prevent concurrent branch/subtree loading > + multivalue property editing > + prevent multiple search requests -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1890) JCR Explorer - improvements
JCR Explorer - improvements --- Key: SLING-1890 URL: https://issues.apache.org/jira/browse/SLING-1890 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Sling Explorer 1.0.0 Reporter: Clemens Wyss Assignee: Clemens Wyss + improved error handling/reporting + create sub node(s) on root node + ajax timeout handling + prevent concurrent branch/subtree loading + multivalue property editing + prevent multiple search requests -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1723) jQuery JCR Explorer - step 2
[ https://issues.apache.org/jira/browse/SLING-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1723: Description: + switch between JCR and resource view on the repo + choose/change workspace + reference support + import/export subtrees + nt:file -> file upload + mixin-type specific editor widgets which are included "inline" in edit.esp. E.g. (maybe the only ;-) ?): mixin:versionable could provide a checkin/checkout button, dropdown list of its versions, ... was: + switch between JCR and resource view on the repo + choose/change workspace + reference support + import/export subtrees + nt:file -> file upload > jQuery JCR Explorer - step 2 > > > Key: SLING-1723 > URL: https://issues.apache.org/jira/browse/SLING-1723 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > Fix For: Sling Explorer 1.0.2 > > > + switch between JCR and resource view on the repo > + choose/change workspace > + reference support > + import/export subtrees > + nt:file -> file upload > + mixin-type specific editor widgets which are included "inline" in edit.esp. > E.g. (maybe the only ;-) ?): mixin:versionable could provide a > checkin/checkout button, dropdown list of its versions, ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SLING-1859) Multi-value string properties are not displayed correctly
[ https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931838#action_12931838 ] Clemens Wyss edited comment on SLING-1859 at 11/14/10 11:00 AM: If resource.adaptTo(ValueMap) fails (i.e returns null) I try your "cast-approach" through ResourceUtil#getValueMap, so this does not seem to be the problem. >not sure you want strings, I guess you could also ask for Long[0] etc. the Property should not only tell me if the property is mutivalued (Property#isMultiple()), but also the type the multiple values (Property#getType()), no matter whether it's empty or not. I expect to always get a Property from the ValueMap-casted resource... Maybe a false implication? was (Author: clemensdev): If resource.adaptTo(ValueMap) fails (i.e returns null) I try your "cast-approach" through ResourceUtil#getValueMap, so this does not seem to be the problem. >not sure you want strings, I guess you could also ask for Long[0] etc. the PropertyDefinition (Property#getDefinition()) should not only tell me if the property is mutivalued (PropertyDefinition#isMultiple()), but also the type the multiple values (PropertyDefinition#getRequiredType()), no matter whether it's empty or not. I expect to always get a Property from the ValueMap-casted resource... Maybe a false implication? > Multi-value string properties are not displayed correctly > - > > Key: SLING-1859 > URL: https://issues.apache.org/jira/browse/SLING-1859 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Carsten Ziegeler >Assignee: Clemens Wyss > > I have a node with a multi value string property, and the explorer displays > the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not 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-1859) Multi-value string properties are not displayed correctly
[ https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1859: --- Assignee: Clemens Wyss (was: Mike Müller) > Multi-value string properties are not displayed correctly > - > > Key: SLING-1859 > URL: https://issues.apache.org/jira/browse/SLING-1859 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Carsten Ziegeler >Assignee: Clemens Wyss > > I have a node with a multi value string property, and the explorer displays > the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not 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-1859) Multi-value string properties are not displayed correctly
[ https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931838#action_12931838 ] Clemens Wyss commented on SLING-1859: - If resource.adaptTo(ValueMap) fails (i.e returns null) I try your "cast-approach" through ResourceUtil#getValueMap, so this does not seem to be the problem. >not sure you want strings, I guess you could also ask for Long[0] etc. the PropertyDefinition (Property#getDefinition()) should not only tell me if the property is mutivalued (PropertyDefinition#isMultiple()), but also the type the multiple values (PropertyDefinition#getRequiredType()), no matter whether it's empty or not. I expect to always get a Property from the ValueMap-casted resource... Maybe a false implication? > Multi-value string properties are not displayed correctly > - > > Key: SLING-1859 > URL: https://issues.apache.org/jira/browse/SLING-1859 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Carsten Ziegeler >Assignee: Mike Müller > > I have a node with a multi value string property, and the explorer displays > the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not 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-1870) Sling should url decode the request url before trying to resolve to a resource
[
https://issues.apache.org/jira/browse/SLING-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931358#action_12931358
]
Clemens Wyss commented on SLING-1870:
-
Felix:
what exactly ist our Jetty-Wrapper? Where can I find the sources?
I looked at jetty/felix sources (eg..HttpURI and a Util class which call
setPathInfo on jettys-Request). They seem to decode the uri's...
> Sling should url decode the request url before trying to resolve to a resource
> --
>
> Key: SLING-1870
> URL: https://issues.apache.org/jira/browse/SLING-1870
> Project: Sling
> Issue Type: Bug
>Reporter: Clemens Wyss
>Priority: Critical
>
> e.g.:
> JCR supports nodes with spaces (in its name), such as "Nice World".
> When accessing this node in Sling, the request url would look something like
> http:Nice%20World
> unfortunately we then try to resolve //Nice%20World in the
> JcrResourceRersolver which, of course, does NOT match/resolve!
> Hence somewhere before resolving the resource we should URLDecoder.decode the
> request URL ( request.getPathInfo() )
> Possible solution:
> SlingHttpServletRequest could provide
> public String getResourceLookupPath()
> {
>return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
> }
> This method could be used in RequestData#initResource and possibly other
> places...
> public Resource initResource(ResourceResolver resourceResolver) {
> ...
> Resource resource = resourceResolver.resolve(request,
> request.getResourceLookupPath() );
> ...
> Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SLING-1859) Multi-value string properties are not displayed correctly
[ https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931146#action_12931146 ] Clemens Wyss edited comment on SLING-1859 at 11/11/10 3:08 PM: --- the mentioned (mis-)behavior arises when a multivalued property is empty. In that case (esp code follows): var properties = resource.adaptTo(Packages.org.apache.sling.api.resource.ValueMap); ... var property = properties.get( id, Packages.javax.jcr.Property ); ... property is null!, i.e. cannot be casted. Is this a bug, or am I doing something wrong? was (Author: clemensdev): the given behavior arises when a multivalued property is empty. In that case (esp code follows): var properties = resource.adaptTo(Packages.org.apache.sling.api.resource.ValueMap); ... var property = properties.get( id, Packages.javax.jcr.Property ); ... property is null!, i.e. cannot be casted. Is this a bug, or am I doing something wrong? > Multi-value string properties are not displayed correctly > - > > Key: SLING-1859 > URL: https://issues.apache.org/jira/browse/SLING-1859 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Carsten Ziegeler >Assignee: Mike Müller > > I have a node with a multi value string property, and the explorer displays > the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not 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-1859) Multi-value string properties are not displayed correctly
[ https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931146#action_12931146 ] Clemens Wyss commented on SLING-1859: - the given behavior arises when a multivalued property is empty. In that case (esp code follows): var properties = resource.adaptTo(Packages.org.apache.sling.api.resource.ValueMap); ... var property = properties.get( id, Packages.javax.jcr.Property ); ... property is null!, i.e. cannot be casted. Is this a bug, or am I doing something wrong? > Multi-value string properties are not displayed correctly > - > > Key: SLING-1859 > URL: https://issues.apache.org/jira/browse/SLING-1859 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Sling Explorer 1.0.0 >Reporter: Carsten Ziegeler >Assignee: Mike Müller > > I have a node with a multi value string property, and the explorer displays > the value as "[Ljava.lang.Object;@1a6b7e", together with the hint "[not 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-1870) Sling should url decode the request url before trying to resolve to a resource
[
https://issues.apache.org/jira/browse/SLING-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930611#action_12930611
]
Clemens Wyss commented on SLING-1870:
-
SlingHttpServletRequestImpl is the wrong place as we could (e.g. within a
Tomcat) end up with a double-decoded URL... IMHO best would be if our
Jetty-wrapper returned (as a workaround) the decoded url
> Sling should url decode the request url before trying to resolve to a resource
> --
>
> Key: SLING-1870
> URL: https://issues.apache.org/jira/browse/SLING-1870
> Project: Sling
> Issue Type: Bug
>Reporter: Clemens Wyss
>Priority: Critical
>
> e.g.:
> JCR supports nodes with spaces (in its name), such as "Nice World".
> When accessing this node in Sling, the request url would look something like
> http:Nice%20World
> unfortunately we then try to resolve //Nice%20World in the
> JcrResourceRersolver which, of course, does NOT match/resolve!
> Hence somewhere before resolving the resource we should URLDecoder.decode the
> request URL ( request.getPathInfo() )
> Possible solution:
> SlingHttpServletRequest could provide
> public String getResourceLookupPath()
> {
>return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
> }
> This method could be used in RequestData#initResource and possibly other
> places...
> public Resource initResource(ResourceResolver resourceResolver) {
> ...
> Resource resource = resourceResolver.resolve(request,
> request.getResourceLookupPath() );
> ...
> Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1870) Sling should url decode the request url before trying to resolve to a resource
[
https://issues.apache.org/jira/browse/SLING-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930597#action_12930597
]
Clemens Wyss commented on SLING-1870:
-
OTH:
jetty does not seem do to its job...i.e. return a "decoded String"
The spec
http://download.oracle.com/javaee/1.4/api/javax/servlet/http/HttpServletRequest.html#getPathInfo()
explicitly says "decoded by the container"
> Sling should url decode the request url before trying to resolve to a resource
> --
>
> Key: SLING-1870
> URL: https://issues.apache.org/jira/browse/SLING-1870
> Project: Sling
> Issue Type: Bug
>Reporter: Clemens Wyss
>Priority: Critical
>
> e.g.:
> JCR supports nodes with spaces (in its name), such as "Nice World".
> When accessing this node in Sling, the request url would look something like
> http:Nice%20World
> unfortunately we then try to resolve //Nice%20World in the
> JcrResourceRersolver which, of course, does NOT match/resolve!
> Hence somewhere before resolving the resource we should URLDecoder.decode the
> request URL ( request.getPathInfo() )
> Possible solution:
> SlingHttpServletRequest could provide
> public String getResourceLookupPath()
> {
>return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
> }
> This method could be used in RequestData#initResource and possibly other
> places...
> public Resource initResource(ResourceResolver resourceResolver) {
> ...
> Resource resource = resourceResolver.resolve(request,
> request.getResourceLookupPath() );
> ...
> Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SLING-1870) Sling should url decode the request url before trying to resolve to a resource
[
https://issues.apache.org/jira/browse/SLING-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930589#action_12930589
]
Clemens Wyss edited comment on SLING-1870 at 11/10/10 8:37 AM:
---
1) So SlingHttpServletRequestImpl should return the decoded URL in its
getPathInfo()-method?
Or
2) SlingHttpServletRequestImpl::ctor should save the decoded URL into its
pathInfo-memeber which is ebing returned by getPathInfo()?
As getPathInfo() is the only method which accesses pathInfo, 2) seems to make
more sense...
was (Author: clemensdev):
So SlingHttpServletRequestImpl should return the decoded URL in its
getPathInfo()-method?
Or
SlingHttpServletRequestImpl::ctor should save the decoded URL into its
pathInfo-memeber which is ebing returned by getPathInfo()?
> Sling should url decode the request url before trying to resolve to a resource
> --
>
> Key: SLING-1870
> URL: https://issues.apache.org/jira/browse/SLING-1870
> Project: Sling
> Issue Type: Bug
>Reporter: Clemens Wyss
>Priority: Critical
>
> e.g.:
> JCR supports nodes with spaces (in its name), such as "Nice World".
> When accessing this node in Sling, the request url would look something like
> http:Nice%20World
> unfortunately we then try to resolve //Nice%20World in the
> JcrResourceRersolver which, of course, does NOT match/resolve!
> Hence somewhere before resolving the resource we should URLDecoder.decode the
> request URL ( request.getPathInfo() )
> Possible solution:
> SlingHttpServletRequest could provide
> public String getResourceLookupPath()
> {
>return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
> }
> This method could be used in RequestData#initResource and possibly other
> places...
> public Resource initResource(ResourceResolver resourceResolver) {
> ...
> Resource resource = resourceResolver.resolve(request,
> request.getResourceLookupPath() );
> ...
> Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1870) Sling should url decode the request url before trying to resolve to a resource
[
https://issues.apache.org/jira/browse/SLING-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930589#action_12930589
]
Clemens Wyss commented on SLING-1870:
-
So SlingHttpServletRequestImpl should return the decoded URL in its
getPathInfo()-method?
Or
SlingHttpServletRequestImpl::ctor should save the decoded URL into its
pathInfo-memeber which is ebing returned by getPathInfo()?
> Sling should url decode the request url before trying to resolve to a resource
> --
>
> Key: SLING-1870
> URL: https://issues.apache.org/jira/browse/SLING-1870
> Project: Sling
> Issue Type: Bug
>Reporter: Clemens Wyss
>Priority: Critical
>
> e.g.:
> JCR supports nodes with spaces (in its name), such as "Nice World".
> When accessing this node in Sling, the request url would look something like
> http:Nice%20World
> unfortunately we then try to resolve //Nice%20World in the
> JcrResourceRersolver which, of course, does NOT match/resolve!
> Hence somewhere before resolving the resource we should URLDecoder.decode the
> request URL ( request.getPathInfo() )
> Possible solution:
> SlingHttpServletRequest could provide
> public String getResourceLookupPath()
> {
>return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
> }
> This method could be used in RequestData#initResource and possibly other
> places...
> public Resource initResource(ResourceResolver resourceResolver) {
> ...
> Resource resource = resourceResolver.resolve(request,
> request.getResourceLookupPath() );
> ...
> Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1870) Sling should url decode the request url before trying to resolve to a resource
Sling should url decode the request url before trying to resolve to a resource
--
Key: SLING-1870
URL: https://issues.apache.org/jira/browse/SLING-1870
Project: Sling
Issue Type: Bug
Reporter: Clemens Wyss
Priority: Critical
e.g.:
JCR supports nodes with spaces (in its name), such as "Nice World".
When accessing this node in Sling, the request url would look something like
http:Nice%20World
unfortunately we then try to resolve //Nice%20World in the
JcrResourceRersolver which, of course, does NOT match/resolve!
Hence somewhere before resolving the resource we should URLDecoder.decode the
request URL ( request.getPathInfo() )
Possible solution:
SlingHttpServletRequest could provide
public String getResourceLookupPath()
{
return URLDecoder.decode( request.getPathInfo(), "UTF-8" ) );
}
This method could be used in RequestData#initResource and possibly other
places...
public Resource initResource(ResourceResolver resourceResolver) {
...
Resource resource = resourceResolver.resolve(request,
request.getResourceLookupPath() );
...
Or is it up to the JcrResourceResolver to decode the URL it gets?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1812) Sling Explorer - Delete Node does not work
[ https://issues.apache.org/jira/browse/SLING-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1812: rev 1003540 > Sling Explorer - Delete Node does not work > -- > > Key: SLING-1812 > URL: https://issues.apache.org/jira/browse/SLING-1812 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss > Fix For: Sling Explorer 1.0.0 > > > dito -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1812) Sling Explorer - Delete Node does not work
[ https://issues.apache.org/jira/browse/SLING-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss resolved SLING-1812. - Fix Version/s: Sling Explorer 1.0.0 Resolution: Fixed was just a path/escaping problem > Sling Explorer - Delete Node does not work > -- > > Key: SLING-1812 > URL: https://issues.apache.org/jira/browse/SLING-1812 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss > Fix For: Sling Explorer 1.0.0 > > > dito -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1812) Sling Explorer - Delete Node does not work
Sling Explorer - Delete Node does not work -- Key: SLING-1812 URL: https://issues.apache.org/jira/browse/SLING-1812 Project: Sling Issue Type: Bug Components: Extensions Reporter: Clemens Wyss Assignee: Clemens Wyss dito -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1776) Caching should be disabled for /system/sling/info.sessionInfo(.json)
[ https://issues.apache.org/jira/browse/SLING-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1776: Summary: Caching should be disabled for /system/sling/info.sessionInfo(.json) (was: Caching should be disbaled for /system/sling/info.sessionInfo) > Caching should be disabled for /system/sling/info.sessionInfo(.json) > > > Key: SLING-1776 > URL: https://issues.apache.org/jira/browse/SLING-1776 > Project: Sling > Issue Type: Bug > Components: Authentication > Environment: InternetExplorer >Reporter: Clemens Wyss > > IE seems to cache the /system/sling/info.sessionInfo.json page/result. > If you perform an authentication in the browser and then gather the current > session info through Sling.getSessionInfo the outdated info is returned > instead. > Solution: > the following http header should be attached to the given url/resource: > Cache-Control : private, no-store, no-cache, max-age=0, must-revalidate > Additionally the Sling#getSessionInfor method in sling.js could make the URI > unique by adding a time tag and hence preventing any browser from caching the > result. > ... > var res=Sling.httpGet(Sling.baseurl+"/system/sling/info.sessionInfo."+new > Date().getTime()+".json"); > ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1776) Caching should be disbaled for /system/sling/info.sessionInfo
Caching should be disbaled for /system/sling/info.sessionInfo - Key: SLING-1776 URL: https://issues.apache.org/jira/browse/SLING-1776 Project: Sling Issue Type: Bug Components: Authentication Environment: InternetExplorer Reporter: Clemens Wyss IE seems to cache the /system/sling/info.sessionInfo.json page/result. If you perform an authentication in the browser and then gather the current session info through Sling.getSessionInfo the outdated info is returned instead. Solution: the following http header should be attached to the given url/resource: Cache-Control : private, no-store, no-cache, max-age=0, must-revalidate Additionally the Sling#getSessionInfor method in sling.js could make the URI unique by adding a time tag and hence preventing any browser from caching the result. ... var res=Sling.httpGet(Sling.baseurl+"/system/sling/info.sessionInfo."+new Date().getTime()+".json"); ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1765) Problems with authentication if basic auth was used before opening Sling Explorer
[ https://issues.apache.org/jira/browse/SLING-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908799#action_12908799 ] Clemens Wyss commented on SLING-1765: - wouldn't the "clean" solution be for the explorer to not only check if authType is set, but that authType == 'Form' ? > Problems with authentication if basic auth was used before opening Sling > Explorer > - > > Key: SLING-1765 > URL: https://issues.apache.org/jira/browse/SLING-1765 > Project: Sling > Issue Type: Bug >Reporter: Mike Müller >Assignee: Felix Meschberger >Priority: Minor > Fix For: Sling Explorer 1.0.0 > > > If you login to /system/console and then go back to /.explorer.html the > explorer shows that you're logged in, which is not the case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1759) [explorer] logo shouldn't refer to incubator.apache.org
[ https://issues.apache.org/jira/browse/SLING-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1759: --- Assignee: Clemens Wyss > [explorer] logo shouldn't refer to incubator.apache.org > --- > > Key: SLING-1759 > URL: https://issues.apache.org/jira/browse/SLING-1759 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Justin Edelson >Assignee: Clemens Wyss >Priority: Trivial > Fix For: Sling Explorer 1.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-1757) [explorer] can't select root node
[ https://issues.apache.org/jira/browse/SLING-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1757: --- Assignee: Clemens Wyss > [explorer] can't select root node > - > > Key: SLING-1757 > URL: https://issues.apache.org/jira/browse/SLING-1757 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Justin Edelson >Assignee: Clemens Wyss >Priority: Critical > Fix For: Sling Explorer 1.0.0 > > > this makes it impossible (AFAICT) to create a new child directly under the > root node -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1758) [explorer] refer to "child node" instead of "sub-node"
[ https://issues.apache.org/jira/browse/SLING-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1758: --- Assignee: Clemens Wyss > [explorer] refer to "child node" instead of "sub-node" > -- > > Key: SLING-1758 > URL: https://issues.apache.org/jira/browse/SLING-1758 > Project: Sling > Issue Type: Bug > Components: Extensions >Reporter: Justin Edelson >Assignee: Clemens Wyss > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1740) Sling Explorer - Displaying/showing server side errors
[ https://issues.apache.org/jira/browse/SLING-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1740: Attachment: sling-1740-2.patch patch which provides the described functionality (merged with Justin's path commit) > Sling Explorer - Displaying/showing server side errors > -- > > Key: SLING-1740 > URL: https://issues.apache.org/jira/browse/SLING-1740 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Mike Müller >Priority: Minor > Attachments: sling-1740-2.patch > > > Almost all operation of Sling Explorer are performed through Ajax. So far any > error that occurred was "ignored". This patch makes 'em visible through > displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1740) Sling Explorer - Displaying/showing server side errors
[ https://issues.apache.org/jira/browse/SLING-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1740: Attachment: (was: sling-1740.patch) > Sling Explorer - Displaying/showing server side errors > -- > > Key: SLING-1740 > URL: https://issues.apache.org/jira/browse/SLING-1740 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Mike Müller >Priority: Minor > > Almost all operation of Sling Explorer are performed through Ajax. So far any > error that occurred was "ignored". This patch makes 'em visible through > displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1741) An exception should be thrown when trying to add a subnode to an nt:file-node
An exception should be thrown when trying to add a subnode to an nt:file-node - Key: SLING-1741 URL: https://issues.apache.org/jira/browse/SLING-1741 Project: Sling Issue Type: Bug Components: JCR Reporter: Clemens Wyss The nt:file nodetype (without any other mixin node types assigned to the node) only supports one single child node whose name is "jcr:content". Hence when you try to add a subnode to an nt:file node you should be getting an error/exception... This is not the case though -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1740) Sling Explorer - Displaying/showing server side errors
[ https://issues.apache.org/jira/browse/SLING-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1740: Attachment: sling-1740.patch patch which resolves/implements the described improvement > Sling Explorer - Displaying/showing server side errors > -- > > Key: SLING-1740 > URL: https://issues.apache.org/jira/browse/SLING-1740 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > Attachments: sling-1740.patch > > > Almost all operation of Sling Explorer are performed through Ajax. So far any > error that occurred was "ignored". This patch makes 'em visible through > displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1740) Sling Explorer - Displaying/showing server side errors
[ https://issues.apache.org/jira/browse/SLING-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1740: --- Assignee: Clemens Wyss > Sling Explorer - Displaying/showing server side errors > -- > > Key: SLING-1740 > URL: https://issues.apache.org/jira/browse/SLING-1740 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > > Almost all operation of Sling Explorer are performed through Ajax. So far any > error that occurred was "ignored". This patch makes 'em visible through > displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1740) Sling Explorer - Displaying/showing server side errors
Sling Explorer - Displaying/showing server side errors -- Key: SLING-1740 URL: https://issues.apache.org/jira/browse/SLING-1740 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Clemens Wyss Priority: Minor Almost all operation of Sling Explorer are performed through Ajax. So far any error that occurred was "ignored". This patch makes 'em visible through displaying errors in a modal pop-up-dialog. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1723) jQuery JCR Explorer - step 2
jQuery JCR Explorer - step 2 Key: SLING-1723 URL: https://issues.apache.org/jira/browse/SLING-1723 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Clemens Wyss Assignee: Clemens Wyss Priority: Minor + switch between JCR and resource view on the repo + choose/change workspace + reference support + import/export subtrees + nt:file -> file upload -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1713) jQuery JCR Explorer - step 1 - improvements
[ https://issues.apache.org/jira/browse/SLING-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1713: Attachment: (was: sling-1671-clemens-2.patch) > jQuery JCR Explorer - step 1 - improvements > --- > > Key: SLING-1713 > URL: https://issues.apache.org/jira/browse/SLING-1713 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss > Attachments: sling-1713-clemens.patch > > > + improved multivalue editing > + mixin's > + last but not least: layout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1713) jQuery JCR Explorer - step 1 - improvements
[ https://issues.apache.org/jira/browse/SLING-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1713: Attachment: sling-1713-clemens.patch This patch "provides" the described improvements > jQuery JCR Explorer - step 1 - improvements > --- > > Key: SLING-1713 > URL: https://issues.apache.org/jira/browse/SLING-1713 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss > Attachments: sling-1713-clemens.patch > > > + improved multivalue editing > + mixin's > + last but not least: layout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1713) jQuery JCR Explorer - step 1 - improvements
[ https://issues.apache.org/jira/browse/SLING-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1713: Attachment: sling-1671-clemens-2.patch this patch "provides" the dscribed improvements > jQuery JCR Explorer - step 1 - improvements > --- > > Key: SLING-1713 > URL: https://issues.apache.org/jira/browse/SLING-1713 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss > Attachments: sling-1671-clemens-2.patch > > > + improved multivalue editing > + mixin's > + last but not least: layout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1713) jQuery JCR Explorer - step 1 - improvements
jQuery JCR Explorer - step 1 - improvements --- Key: SLING-1713 URL: https://issues.apache.org/jira/browse/SLING-1713 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Clemens Wyss Assignee: Clemens Wyss + improved multivalue editing + mixin's + last but not least: layout -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1603) SlingServlet service
[ https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904934#action_12904934 ] Clemens Wyss commented on SLING-1603: - I guess Engine is implemented with the strategy pattern in mind? Strategies for request processing? If so, I would call the interface "Engine" more appropriately "RequestProcessing", or "RequestProcessor" and hence EngineImpl would become "SlingRequestProcessing" or "SlingRequestProcessor". #processRequest could then become #process. As this is only a naming-issue it's not really that important... :-) > SlingServlet service > > > Key: SLING-1603 > URL: https://issues.apache.org/jira/browse/SLING-1603 > Project: Sling > Issue Type: Improvement > Components: Engine >Affects Versions: Engine 2.0.6 >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > Attachments: SLING-1603-fmeschbe.patch, SLING-1603.patch, > SLING-1603.patch > > > For SLING-550 I need to call the SlingMainServlet outside of the web > container's request/response cycle. > I'll attach a patch that introduces a new SlingServlet interface that > SlingMainServlet implements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903403#action_12903403 ] Clemens Wyss commented on SLING-1671: - regarding the "pluggable resource/node editors": within the /libs/sling/servlet/default/explorer/edit folder you can place custom esp's to override the default editor for specific sling:resourceTypes. As an example I placed the sling_redirect.esp in there, which handles nodes of sling:resourceType == 'sling:redirect', such as the root-node/folder. This "feature"/behavior is of course (and not only, I guess ;-) ) to be discussed > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > Attachments: sling-1671-clemens.patch > > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1671: Attachment: sling-1671-clemens.patch as promised an initial commit of the jQuery JCR Explorer. More to come. Build/installation instructions remain the same: 1) build the plugin >mvn package 2) install the plugin 3) http://localhost:8080/.explorer.html 4) Login browse the repo, add/modify nodes/properties, Query the repo > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > Attachments: sling-1671-clemens.patch > > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss reassigned SLING-1671: --- Assignee: Clemens Wyss > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Assignee: Clemens Wyss >Priority: Minor > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902823#action_12902823 ] Clemens Wyss commented on SLING-1671: - + ajaxified + make multivalued properties editable > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Priority: Minor > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902824#action_12902824 ] Clemens Wyss commented on SLING-1671: - we intend to "release" an initial version this afternoon, or tomorrow > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Priority: Minor > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902825#action_12902825 ] Clemens Wyss commented on SLING-1671: - btw, I am the "Assignee" ;-) but can't assign myself... > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Priority: Minor > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1671) New features for jQuery JCR Explorer - step 1
[ https://issues.apache.org/jira/browse/SLING-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Wyss updated SLING-1671: Description: + property (type) specific editors (e.g. date, boolean) + search (SQL2, JQDOM, sql and xpath) + optimized tree (navigation) + pluggable resource/node editors was: + property (type) specific editors (e.g. date, boolean) + search (SQL2, JQOM, sql and xpath) + optimized tree (navigation) + pluggable resource/node editors > New features for jQuery JCR Explorer - step 1 > - > > Key: SLING-1671 > URL: https://issues.apache.org/jira/browse/SLING-1671 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Clemens Wyss >Priority: Minor > > + property (type) specific editors (e.g. date, boolean) > + search (SQL2, JQDOM, sql and xpath) > + optimized tree (navigation) > + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1680) FsResourceProvider takes VERY long to register/unregister AND finally throws an OutOfMemoryError
[ https://issues.apache.org/jira/browse/SLING-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901417#action_12901417 ] Clemens Wyss commented on SLING-1680: - I can confirm that c:/ tmp is very "deep" and has many, many files( >100'000)/folders(>40'000 ) ;-) I guess this bug/issue, being not a real world use case, can be ignored? > FsResourceProvider takes VERY long to register/unregister AND finally throws > an OutOfMemoryError > > > Key: SLING-1680 > URL: https://issues.apache.org/jira/browse/SLING-1680 > Project: Sling > Issue Type: Bug > Components: JCR > Environment: WinXP, latest-greatest Sling (from trunk) >Reporter: Clemens Wyss > > Given the Sling Web Console > When I configure an instance of the filesystem resource provider in terms of > provider root and filesystem location, e.g.: > Provider root: /tmp > Filesystem Root: c:/tmp > it takes very long to handle the request an finally ends in an > OutOfMemoryError: > 23.08.2010 15:56:08.446 *ERROR* [FelixStartLevel] org.apache.sling.fsresource > [org.apache.sling.fsprovider.internal.FsResourceProvider] The activate method > has thrown an exception (java.lang.OutOfMemoryError: Java heap space) > java.lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2882) > at > java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) > at > java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:572) > at java.lang.StringBuilder.append(StringBuilder.java:203) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:253) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > at > org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) > at > org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) > at > org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) > 23.08.2010 15:56:08.446 *ERROR* [FelixStartLevel] org.apache.sling.fsresource > [org.apache.sling.fsprovider.internal.FsResourceProvider] Failed creating the > component instance; see log for reason > 23.08.2010 15:56:08.446 *ERROR* [FelixDispatchQueue] > org.apache.sling.fsresource > FrameworkEvent ERROR (org.osgi.framework.ServiceException: Service factory > returned null.) org.osgi.framework.ServiceException: Service factory returned
[jira] Created: (SLING-1680) FsResourceProvider takes VERY long to register/unregister AND finally throws an OutOfMemoryError
FsResourceProvider takes VERY long to register/unregister AND finally throws an OutOfMemoryError Key: SLING-1680 URL: https://issues.apache.org/jira/browse/SLING-1680 Project: Sling Issue Type: Bug Components: JCR Environment: WinXP, latest-greatest Sling (from trunk) Reporter: Clemens Wyss Given the Sling Web Console When I configure an instance of the filesystem resource provider in terms of provider root and filesystem location, e.g.: Provider root: /tmp Filesystem Root: c:/tmp it takes very long to handle the request an finally ends in an OutOfMemoryError: 23.08.2010 15:56:08.446 *ERROR* [FelixStartLevel] org.apache.sling.fsresource [org.apache.sling.fsprovider.internal.FsResourceProvider] The activate method has thrown an exception (java.lang.OutOfMemoryError: Java heap space) java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2882) at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:572) at java.lang.StringBuilder.append(StringBuilder.java:203) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:253) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) at org.apache.sling.fsprovider.internal.FileMonitor.createStatus(FileMonitor.java:219) at org.apache.sling.fsprovider.internal.FileMonitor.access$000(FileMonitor.java:36) at org.apache.sling.fsprovider.internal.FileMonitor$DirStatus.(FileMonitor.java:255) 23.08.2010 15:56:08.446 *ERROR* [FelixStartLevel] org.apache.sling.fsresource [org.apache.sling.fsprovider.internal.FsResourceProvider] Failed creating the component instance; see log for reason 23.08.2010 15:56:08.446 *ERROR* [FelixDispatchQueue] org.apache.sling.fsresource FrameworkEvent ERROR (org.osgi.framework.ServiceException: Service factory returned null.) org.osgi.framework.ServiceException: Service factory returned null. at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:340) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:221) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:295) at org.apache.felix.framework.Felix.getService(Felix.java:3007) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:329) at org.osgi.util.tracker.ServiceTracker.addingService(ServiceTracker.java:385) at org.apac
[jira] Created: (SLING-1672) resource.resourceResolver.listChildren only enlists jcr nodes but not all child resources
resource.resourceResolver.listChildren only enlists jcr nodes but not all child resources - Key: SLING-1672 URL: https://issues.apache.org/jira/browse/SLING-1672 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.6 Environment: sling from trunk (as of August 20th 2010) Reporter: Clemens Wyss in my esp-script I have the follwoing line: var childResources = request.resourceResolver.listChildren(resource ); In my pom.xml I have the follwoing declaration: /res/sling/explorer;overwrite:=true;uninstall=true;path:=/libs/sling/explorer i.e. I map /res/sling/explorer to /libs/sling/explorer. And I can directly access the files beneath /res/sling/explorer, e.g. http://localhost:8080/res/sling/explorer/css/explorer.css. I.e. resolving seems to work But when I enlist (which end up in BundleResourceProvider#listChildren()) on the root (/) I don't see 'res' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1671) New features for jQuery JCR Explorer - step 1
New features for jQuery JCR Explorer - step 1 - Key: SLING-1671 URL: https://issues.apache.org/jira/browse/SLING-1671 Project: Sling Issue Type: New Feature Components: Extensions Reporter: Clemens Wyss Priority: Minor + property (type) specific editors (e.g. date, boolean) + search (SQL2, JQOM, sql and xpath) + optimized tree (navigation) + pluggable resource/node editors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1645) jQuery explorer (contrib/explorers/jQuery) does not display properly in Firefox
[
https://issues.apache.org/jira/browse/SLING-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemens Wyss updated SLING-1645:
Attachment: explorer.js.diff
a patch/diff to solve this bug
> jQuery explorer (contrib/explorers/jQuery) does not display properly in
> Firefox
> ---
>
> Key: SLING-1645
> URL: https://issues.apache.org/jira/browse/SLING-1645
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Environment: Firefox
>Reporter: Clemens Wyss
>Priority: Minor
> Attachments: explorer.js.diff, jQuery_explorer_in_FF.png
>
>
> when launching the explorer in Firefox the root nodes are being "replicated"
> beneath the root nodes. See screenshot.
> reason:
> On the repo's root function init_load unnecessarily calls loadPath with an
> empty path. jQuery's $('p#') maps to all p's and ppends the root nodes to all
> root nodes
> workaround:
> in loadPath, check whether it is being called with an empty path, i.e. for
> root
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1645) jQuery explorer (contrib/explorers/jQuery) does not display properly in Firefox
[
https://issues.apache.org/jira/browse/SLING-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemens Wyss updated SLING-1645:
Attachment: jQuery_explorer_in_FF.png
> jQuery explorer (contrib/explorers/jQuery) does not display properly in
> Firefox
> ---
>
> Key: SLING-1645
> URL: https://issues.apache.org/jira/browse/SLING-1645
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Environment: Firefox
>Reporter: Clemens Wyss
>Priority: Minor
> Attachments: jQuery_explorer_in_FF.png
>
>
> when launching the explorer in Firefox the root nodes are being "replicated"
> beneath the root nodes. See screenshot.
> reason:
> On the repo's root function init_load unnecessarily calls loadPath with an
> empty path. jQuery's $('p#') maps to all p's and ppends the root nodes to all
> root nodes
> workaround:
> in loadPath, check whether it is being called with an empty path, i.e. for
> root
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1645) jQuery explorer (contrib/explorers/jQuery) does not display properly in Firefox
jQuery explorer (contrib/explorers/jQuery) does not display properly in Firefox
---
Key: SLING-1645
URL: https://issues.apache.org/jira/browse/SLING-1645
Project: Sling
Issue Type: Bug
Components: Extensions
Environment: Firefox
Reporter: Clemens Wyss
Priority: Minor
when launching the explorer in Firefox the root nodes are being "replicated"
beneath the root nodes. See screenshot.
reason:
On the repo's root function init_load unnecessarily calls loadPath with an
empty path. jQuery's $('p#') maps to all p's and ppends the root nodes to all
root nodes
workaround:
in loadPath, check whether it is being called with an empty path, i.e. for root
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
