[jira] Updated: (SLING-1016) Make membership management depend on the principal name not the URI of the principal, since the principal name is already unique.
[ https://issues.apache.org/jira/browse/SLING-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-1016: - Affects Version/s: (was: JCR Jackrabbit User Manager 2.0.4) Remaining Estimate: 0h Original Estimate: 0h Patch applied in rev. 787207. Thank Ian for providing this patch. Please check and close if this works for you. > Make membership management depend on the principal name not the URI of the > principal, since the principal name is already unique. > - > > Key: SLING-1016 > URL: https://issues.apache.org/jira/browse/SLING-1016 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Ian Boston > Attachments: SLING-1016.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > As per thread on sling-dev > --- > You are probably right, the principal name is sufficient to find the > authorizable. Can you make the patch? > Thanks! > On Fri, Jun 19, 2009 at 7:43 AM, Ian Boston wrote: > I was wondering, > curl -F:member=/system/userManager/user/ieb http://admin:ad...@localhost > :8080/system/userManager/group/g-group1.update.json > appears to be the way to add members to groups > or > curl -F:member=../../ieb http://admin:ad...@localhost > :8080/system/userManager/group/g-group1.update.json > I can see where this is in the code, but it looks a bit odd and slightly > hard for a UI developer to work with when > curl -F:member=ieb http://admin:ad...@localhost > :8080/system/userManager/group/g-group1.update.json > would have worked. Was there a reason I am missing this is like it is ? > I would like to change it, happy to do a patch. > Ian > -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717724#action_12717724 ] Juan Jose Vazquez Delgado commented on SLING-990: - Congrats Christophe, looks good!. Regarding SmartGwt, I´d prefer to keep more simple with just GWT :). > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart > Attachments: Sling Explorer.zip > > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-736) Ensure getPathInfo returns correct (expected) value
[ https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695361#action_12695361 ] Juan Jose Vazquez Delgado commented on SLING-736: - Right, I think it´s fixed. > Ensure getPathInfo returns correct (expected) value > --- > > Key: SLING-736 > URL: https://issues.apache.org/jira/browse/SLING-736 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.0.2 >Reporter: Felix Meschberger >Assignee: Juan Jose Vazquez Delgado > Fix For: Engine 2.0.4 > > Attachments: SLING-736.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > According to the servlet specification, a servlet registered with path "/" in > its web application is considered a default servlet. For such a default > servlet the HttpServletRequest.getServletPath() and > HttpServletRequest.getPathInfo() methods return different results as would be > expected: getServletPath() returns the request URI path (minus the servlet > context path) and getPathInfo() always returns null. > When Sling is deployed using the PAX Web 0.5.1 this situation happens since > the SlingMainServlet is registered with path "/" with the HttpService. > To fix this situation for Sling and ensuring the expected getServletPath() > (of minor use in Sling) and getPathInfo() (very important for all > authentication as well as resource resolution), the Sling engine is modified > as follows: > * The SlingMainServlet is always registered with the HttpService with the > servlet path "/". This cannot be configurable. > * The SlingHttpServletRequestImpl, which is instantiated by the > SlingMainServlet to provide the SlingHttpServletRequest interface, is > modified to overwrite the getServletPath() and getPathInfo() methods as > follows (see also Section SRV.4.4 in Servlet API 2.4 spec) : >* getServletPath() always returns "" >* getPathInfo() always returns the getServletPath()+getPathInfo() > called on the servlet container (or HttpService provided) > HttpServletRequest object > More information on this issue is available in the Mail Thread > http://markmail.org/message/34cithemwzadolw3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-893) Pipeline support
[ https://issues.apache.org/jira/browse/SLING-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-893. - Resolution: Fixed First version in [1]. Close this issue and open new ones for bugs and enhancements. [1] http://svn.apache.org/repos/asf/incubator/sling/trunk/contrib/scripting/xproc > Pipeline support > > > Key: SLING-893 > URL: https://issues.apache.org/jira/browse/SLING-893 > Project: Sling > Issue Type: Improvement > Components: Xproc >Affects Versions: 3 >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in [1] we should have some sort of pipeline support in Sling. > This stuff will be provided as a contrib or extension. > [1] http://markmail.org/thread/33h5nhk5e3mswrue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-908) Xproc response does not indicate errors
[ https://issues.apache.org/jira/browse/SLING-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694548#action_12694548 ] Juan Jose Vazquez Delgado commented on SLING-908: - Good point. Thanks for fixing it. > Xproc response does not indicate errors > --- > > Key: SLING-908 > URL: https://issues.apache.org/jira/browse/SLING-908 > Project: Sling > Issue Type: Bug > Components: Xproc >Reporter: Bertrand Delacretaz >Priority: Minor > > Trying the xproc scripting engine with an invalid xpl script produces an > empty response with a 200 ok status code. > The cause is the PipelineImpl class, which retrieves the OutputStream from > the SlingHttpServletResponse. When an error handler tries to do the same > later on to report the error, it gets an "OutputStream already retrieved" > exception -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-896) Allow installation of Sling as a feature in ServiceMix Kernel
[ https://issues.apache.org/jira/browse/SLING-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-896. - Resolution: Fixed Assignee: Juan Jose Vazquez Delgado Applied patch inside contrib/launchpad (revision 758342). I had to modify a little the features.xml file. Updated README.txt too. Thanks to Sebastián Gómez for contribution. > Allow installation of Sling as a feature in ServiceMix Kernel > - > > Key: SLING-896 > URL: https://issues.apache.org/jira/browse/SLING-896 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Sebastian Gomez >Assignee: Juan Jose Vazquez Delgado >Priority: Minor > Attachments: sling-feature.zip > > > Sling works perfectly in ServiceMix Kernel if we add one by one all the > bundles the launchpad needs in the correct order (depending on the start > level), but there is a much easier way of doing this by creating what's > called a "feature" in ServiceMix. This is a group of bundles that will be > deployed in the order specified that will give the Kernel a new functionality. > The installation of Sling as a feature in ServiceMix would be done in just > two lines, without the need of copying bundles from one folder to another: > s...@root:/>features/addUrl > mvn:my.groupId/sling-feature/1.0.0-SNAPSHOT/xml/features > s...@root:/>features/install sling > I'll attach ASAP a patch with the necessary files to use Sling as a feature > in ServiceMix Kernel. Hope both commiters and users find the patch useful. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-736) Ensure getPathInfo returns correct (expected) value
[ https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-736. - Resolution: Fixed At first sight, everything seems to be ok. Close this issue. > Ensure getPathInfo returns correct (expected) value > --- > > Key: SLING-736 > URL: https://issues.apache.org/jira/browse/SLING-736 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.0.2 >Reporter: Felix Meschberger >Assignee: Juan Jose Vazquez Delgado > Fix For: Engine 2.0.4 > > Attachments: SLING-736.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > According to the servlet specification, a servlet registered with path "/" in > its web application is considered a default servlet. For such a default > servlet the HttpServletRequest.getServletPath() and > HttpServletRequest.getPathInfo() methods return different results as would be > expected: getServletPath() returns the request URI path (minus the servlet > context path) and getPathInfo() always returns null. > When Sling is deployed using the PAX Web 0.5.1 this situation happens since > the SlingMainServlet is registered with path "/" with the HttpService. > To fix this situation for Sling and ensuring the expected getServletPath() > (of minor use in Sling) and getPathInfo() (very important for all > authentication as well as resource resolution), the Sling engine is modified > as follows: > * The SlingMainServlet is always registered with the HttpService with the > servlet path "/". This cannot be configurable. > * The SlingHttpServletRequestImpl, which is instantiated by the > SlingMainServlet to provide the SlingHttpServletRequest interface, is > modified to overwrite the getServletPath() and getPathInfo() methods as > follows (see also Section SRV.4.4 in Servlet API 2.4 spec) : >* getServletPath() always returns "" >* getPathInfo() always returns the getServletPath()+getPathInfo() > called on the servlet container (or HttpService provided) > HttpServletRequest object > More information on this issue is available in the Mail Thread > http://markmail.org/message/34cithemwzadolw3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-736) Ensure getPathInfo returns correct (expected) value
[ https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-736: Remaining Estimate: 0h Original Estimate: 0h The path info was overwritten when "servletRequest.getPathInfo() != null". Although, we were using the underlying "HttpServletRequest", instead of "SlingHttpServletRequest", in RequestData.initResource, so path info was still the original one. Patch applied in revision 757774. Feedback about this change would be appreciate. > Ensure getPathInfo returns correct (expected) value > --- > > Key: SLING-736 > URL: https://issues.apache.org/jira/browse/SLING-736 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.0.2 >Reporter: Felix Meschberger >Assignee: Juan Jose Vazquez Delgado > Fix For: Engine 2.0.4 > > Attachments: SLING-736.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > According to the servlet specification, a servlet registered with path "/" in > its web application is considered a default servlet. For such a default > servlet the HttpServletRequest.getServletPath() and > HttpServletRequest.getPathInfo() methods return different results as would be > expected: getServletPath() returns the request URI path (minus the servlet > context path) and getPathInfo() always returns null. > When Sling is deployed using the PAX Web 0.5.1 this situation happens since > the SlingMainServlet is registered with path "/" with the HttpService. > To fix this situation for Sling and ensuring the expected getServletPath() > (of minor use in Sling) and getPathInfo() (very important for all > authentication as well as resource resolution), the Sling engine is modified > as follows: > * The SlingMainServlet is always registered with the HttpService with the > servlet path "/". This cannot be configurable. > * The SlingHttpServletRequestImpl, which is instantiated by the > SlingMainServlet to provide the SlingHttpServletRequest interface, is > modified to overwrite the getServletPath() and getPathInfo() methods as > follows (see also Section SRV.4.4 in Servlet API 2.4 spec) : >* getServletPath() always returns "" >* getPathInfo() always returns the getServletPath()+getPathInfo() > called on the servlet container (or HttpService provided) > HttpServletRequest object > More information on this issue is available in the Mail Thread > http://markmail.org/message/34cithemwzadolw3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SLING-736) Ensure getPathInfo returns correct (expected) value
[ https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado reopened SLING-736: - Assignee: Juan Jose Vazquez Delgado (was: Felix Meschberger) Issue reopened because of behaviour reported in [1]. [1] http://markmail.org/thread/2afkni7anhc7eujv > Ensure getPathInfo returns correct (expected) value > --- > > Key: SLING-736 > URL: https://issues.apache.org/jira/browse/SLING-736 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.0.2 >Reporter: Felix Meschberger >Assignee: Juan Jose Vazquez Delgado > Fix For: Engine 2.0.4 > > Attachments: SLING-736.patch > > > According to the servlet specification, a servlet registered with path "/" in > its web application is considered a default servlet. For such a default > servlet the HttpServletRequest.getServletPath() and > HttpServletRequest.getPathInfo() methods return different results as would be > expected: getServletPath() returns the request URI path (minus the servlet > context path) and getPathInfo() always returns null. > When Sling is deployed using the PAX Web 0.5.1 this situation happens since > the SlingMainServlet is registered with path "/" with the HttpService. > To fix this situation for Sling and ensuring the expected getServletPath() > (of minor use in Sling) and getPathInfo() (very important for all > authentication as well as resource resolution), the Sling engine is modified > as follows: > * The SlingMainServlet is always registered with the HttpService with the > servlet path "/". This cannot be configurable. > * The SlingHttpServletRequestImpl, which is instantiated by the > SlingMainServlet to provide the SlingHttpServletRequest interface, is > modified to overwrite the getServletPath() and getPathInfo() methods as > follows (see also Section SRV.4.4 in Servlet API 2.4 spec) : >* getServletPath() always returns "" >* getPathInfo() always returns the getServletPath()+getPathInfo() > called on the servlet container (or HttpService provided) > HttpServletRequest object > More information on this issue is available in the Mail Thread > http://markmail.org/message/34cithemwzadolw3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-893) Pipeline support
Pipeline support Key: SLING-893 URL: https://issues.apache.org/jira/browse/SLING-893 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: 3 Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado As discussed in [1] we should have some sort of pipeline support in Sling. This stuff will be provided as a contrib or extension. [1] http://markmail.org/thread/33h5nhk5e3mswrue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-879) New Bundle to provide actions for interacting with the jackrabbit AccessManager
[ https://issues.apache.org/jira/browse/SLING-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-879. - Resolution: Fixed Assignee: Juan Jose Vazquez Delgado Integration tests applied in rev. 756376. Thank Eric Norman for contribution. > New Bundle to provide actions for interacting with the jackrabbit > AccessManager > --- > > Key: SLING-879 > URL: https://issues.apache.org/jira/browse/SLING-879 > Project: Sling > Issue Type: New Feature > Components: Servlets Get, Servlets Post >Reporter: Eric Norman >Assignee: Juan Jose Vazquez Delgado > Attachments: accessManager_patch.diff, > org.apache.sling.jcr.jackrabbit.accessmanager.zip > > Original Estimate: 0h > Remaining Estimate: 0h > > This is a new bundle that provides servlets to support modifying the > jackrabbit access control policies for JCR nodes. > 1. The servlet bound to [nodePath].modifyAce.html can be invoked to add or > modify the access control privileges for a given principal. > 2. The servlet bound to [nodePath].deleteAce.html can be invoked to remove > the access control entries for one or more principals. > 3. The servlet bound to [nodePath].acl.json can be invoked to get a JSON > representation of the ACL for a node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-891) Some usermanager integration tests are failing
[ https://issues.apache.org/jira/browse/SLING-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-891. - Resolution: Invalid Finally, this seems to be a memory issue. MAVEN_OPTS=-Xmx512M and doesn´t fail anymore. Resolve this issue as invalid. Maybe we have to think about clean build memory requirements. > Some usermanager integration tests are failing > -- > > Key: SLING-891 > URL: https://issues.apache.org/jira/browse/SLING-891 > Project: Sling > Issue Type: Bug > Components: Testing >Affects Versions: 3 > Environment: Maven version: 2.0.10 > Java version: 1.5.0_14 > OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows" >Reporter: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > mvn clean install in trunk fails for me: > Results : > Failed tests: > > testUpdateUser(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) > > testChangeUserPassword(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) > > testChangeUserPasswordWrongOldPwd(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) > > testChangeUserPasswordWrongConfirmPwd(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-879) New Bundle to provide actions for interacting with the jackrabbit AccessManager
[ https://issues.apache.org/jira/browse/SLING-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-879: Remaining Estimate: 0h Original Estimate: 0h jackrabbit-accessmanager bundle created in trunk (rev. 755539). Integration tests stuff not applied because fail. Leave this issue opened until integration tests pass. > New Bundle to provide actions for interacting with the jackrabbit > AccessManager > --- > > Key: SLING-879 > URL: https://issues.apache.org/jira/browse/SLING-879 > Project: Sling > Issue Type: New Feature > Components: Servlets Get, Servlets Post >Reporter: Eric Norman > Attachments: accessManager_patch.diff, > org.apache.sling.jcr.jackrabbit.accessmanager.zip > > Original Estimate: 0h > Remaining Estimate: 0h > > This is a new bundle that provides servlets to support modifying the > jackrabbit access control policies for JCR nodes. > 1. The servlet bound to [nodePath].modifyAce.html can be invoked to add or > modify the access control privileges for a given principal. > 2. The servlet bound to [nodePath].deleteAce.html can be invoked to remove > the access control entries for one or more principals. > 3. The servlet bound to [nodePath].acl.json can be invoked to get a JSON > representation of the ACL for a node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-891) Some usermanager integration tests are failing
Some usermanager integration tests are failing -- Key: SLING-891 URL: https://issues.apache.org/jira/browse/SLING-891 Project: Sling Issue Type: Bug Components: Testing Affects Versions: 3 Environment: Maven version: 2.0.10 Java version: 1.5.0_14 OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows" Reporter: Juan Jose Vazquez Delgado mvn clean install in trunk fails for me: Results : Failed tests: testUpdateUser(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) testChangeUserPassword(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) testChangeUserPasswordWrongOldPwd(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) testChangeUserPasswordWrongConfirmPwd(org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateUserTest) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-885) External JCR configuration file is not resolved properly
[ https://issues.apache.org/jira/browse/SLING-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-885. - Resolution: Fixed Fixed in rev. 752067 > External JCR configuration file is not resolved properly > > > Key: SLING-885 > URL: https://issues.apache.org/jira/browse/SLING-885 > Project: Sling > Issue Type: Bug > Components: JCR >Affects Versions: JCR Jackrabbit Server 2.0.2 > Environment: Windows >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > The SlingServerRepository "Configuration File" property in is not resolved > properly when "sling.repository.config.file.url" is point to local > repository.xml file. > For instance: > sling.repository.config.file.url=C:\\jcr\\repository.xml > is resolved to "\jcr\repository.xml". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-885) External JCR configuration file is not resolved properly
External JCR configuration file is not resolved properly Key: SLING-885 URL: https://issues.apache.org/jira/browse/SLING-885 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Jackrabbit Server 2.0.2 Environment: Windows Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado The SlingServerRepository "Configuration File" property in is not resolved properly when "sling.repository.config.file.url" is point to local repository.xml file. For instance: sling.repository.config.file.url=C:\\jcr\\repository.xml is resolved to "\jcr\repository.xml". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-871) Add new method to AccessControlUtil to determine if an AccessControlEntry contains granted privileges or denied privileges
[ https://issues.apache.org/jira/browse/SLING-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-871. - Resolution: Fixed Assignee: Juan Jose Vazquez Delgado Patch applied in revision 747309. Thanks to Eric Norman for the contribution. > Add new method to AccessControlUtil to determine if an AccessControlEntry > contains granted privileges or denied privileges > -- > > Key: SLING-871 > URL: https://issues.apache.org/jira/browse/SLING-871 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Eric Norman >Assignee: Juan Jose Vazquez Delgado >Priority: Minor > Attachments: AccessControlUtil_isAllow.diff > > > The AccessControlUtil.addEntry(..) methods enable creating an > AccessControlEntry for denied privileges, but there is no easy way to lookup > that information at a later time. > My proposal is to add a new 'isAllow' method to the AccessControlUtil class > to enable looking up the 'isAllow' flag for an AccessControlEntry. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-867) AccesControlUtil addEntry fails
[ https://issues.apache.org/jira/browse/SLING-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado closed SLING-867. --- Resolution: Fixed Resolved in rev. 746943 > AccesControlUtil addEntry fails > --- > > Key: SLING-867 > URL: https://issues.apache.org/jira/browse/SLING-867 > Project: Sling > Issue Type: Bug > Components: JCR >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in [1], method addEntry in AccessControlUtil fails > (NoSuchMethodException). This method uses reflection to invoke underlying > jackrabbit core method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-867) AccesControlUtil addEntry fails
[ https://issues.apache.org/jira/browse/SLING-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-867: Sorry, [1] http://dev.day.com/discussion-groups/content/lists/incubator-sling-dev/2009-02/2009-02-18_AccessControlUtil_addEntry___scr_private__deactivate_bundles_in_mvn__Marc_Speck.html?q=AccessControlUtil.addEntry > AccesControlUtil addEntry fails > --- > > Key: SLING-867 > URL: https://issues.apache.org/jira/browse/SLING-867 > Project: Sling > Issue Type: Bug > Components: JCR >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in [1], method addEntry in AccessControlUtil fails > (NoSuchMethodException). This method uses reflection to invoke underlying > jackrabbit core method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-867) AccesControlUtil addEntry fails
AccesControlUtil addEntry fails --- Key: SLING-867 URL: https://issues.apache.org/jira/browse/SLING-867 Project: Sling Issue Type: Bug Components: JCR Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado As discussed in [1], method addEntry in AccessControlUtil fails (NoSuchMethodException). This method uses reflection to invoke underlying jackrabbit core method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-859) option overwrite:=true
[
https://issues.apache.org/jira/browse/SLING-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado updated SLING-859:
"no definition found in parent node's node type for new node: no matching child
node definition found for {}servicemix
javax.jcr.nodetype.ConstraintViolationException"
This exception says you´re trying to create a "servicemix" node as child of a
no "nt:unstructured" node. Please, can you attach how is your node hierarchy?.
> option overwrite:=true
> --
>
> Key: SLING-859
> URL: https://issues.apache.org/jira/browse/SLING-859
> Project: Sling
> Issue Type: Bug
> Components: JCR Contentloader
> Environment: MS Windows XP, intel core 2 duo
>Reporter: Vladislav Krejcirik
>Assignee: Juan Jose Vazquez Delgado
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I have this in my pom.xml:
>
>org.apache.felix
>maven-bundle-plugin
>true
>
>
>
>initial-content;overwrite:=true
>
>
>
>
> But if I reinstall bundle I have still old files in Sling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-859) option overwrite:=true
[ https://issues.apache.org/jira/browse/SLING-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-859: Assignee: Juan Jose Vazquez Delgado Remaining Estimate: 0h Original Estimate: 0h option overwrite:=true works form me in Sling trunk revision 744966. Can you look for any stack trace in Sling error log?. In the other hand, how are you re-installing the bundle? with the Felix web console?. > option overwrite:=true > -- > > Key: SLING-859 > URL: https://issues.apache.org/jira/browse/SLING-859 > Project: Sling > Issue Type: Bug > Components: JCR Contentloader > Environment: MS Windows XP, intel core 2 duo >Reporter: Vladislav Krejcirik >Assignee: Juan Jose Vazquez Delgado > Original Estimate: 0h > Remaining Estimate: 0h > > I have this in my pom.xml: > >org.apache.felix >maven-bundle-plugin >true > > > >initial-content;overwrite:=true > > > > > But if I reinstall bundle I have still old files in Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-830) Startup failure when after a full build of Sling.
[ https://issues.apache.org/jira/browse/SLING-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664141#action_12664141 ] Juan Jose Vazquez Delgado commented on SLING-830: - Works for me (rev. 734729), windows vista 64. java 1.5.0_14 > Startup failure when after a full build of Sling. > - > > Key: SLING-830 > URL: https://issues.apache.org/jira/browse/SLING-830 > Project: Sling > Issue Type: Bug > Components: General >Affects Versions: Launchpad Base 2.0.4, Launchpad App 4, Launchpad Webapp 4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger >Priority: Critical > Fix For: Launchpad Base 2.0.4, Launchpad App 4, Launchpad Webapp 4 > > > When doing a full build of Sling from the root of the trunk using the Maven > Reactor, the final launchpad/app JAR file cannot be started because a JAR is > said to not be verifiable (see also [1]): > sling/launchpad/app/target# java -jar > org.apache.sling.launchpad.app-5-incubator-SNAPSHOT.jar -c sling -f - > Exception in thread "main" java.lang.SecurityException: Invalid signature > file digest for Manifest main attributes > at > sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:221) > at > sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176) > at java.util.jar.JarVerifier.processEntry(JarVerifier.java:277) > at java.util.jar.JarVerifier.update(JarVerifier.java:188) > at java.util.jar.JarFile.initializeVerifier(JarFile.java:321) > at java.util.jar.JarFile.getInputStream(JarFile.java:386) > at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:689) > at sun.misc.Resource.cachedInputStream(Resource.java:59) > at sun.misc.Resource.getByteBuffer(Resource.java:154) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:249) > at java.net.URLClassLoader.access$000(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:252) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > Could not find the main class: org.apache.sling.launcher.app.main.Main. > Program will exit. > It seems that on a full build, the signature files from the Eclipse > HttpService Bridge are included, which cause the JAR class loader to try to > verify the jar file, which of course fails. The files are META-INF/ECLIPSE.SF > and META-INF/ECLIPSE.RSA. If these files are not in the final JAR, it starts > up flawlessly. > When doing a single-module build of the the launchpad/base first and then > launchpad/app, the JAR file is correctly created without these Eclipse > signature files. So it looks like this problem is related to the reactor > build. In addition, the launchpad/base build is defined to ignore the > META-INF folders of the included libraries. This does not seem to be obeyed > in the reactor build case. > So, I assume this is related to the maven-dependency-plugin being used to > glue the launchpad/base library together is not the correct version, since > multiple versions are used throughout the build process and there is no > managed version number in the parent pom. > Adding the maven-dependency-plugin to the parent pom's pluginManagement with > version 2.0 and removing all explicit version references actually fixes this > problem and the resulting jar starts correctly, even after a reactor build. > [1] http://markmail.org/message/4fxvcvm4jhiveb7l -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-818) Create a utility class to simplify accessing JSR283 classes in Jackrabbit 1.5
[ https://issues.apache.org/jira/browse/SLING-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-818. - Resolution: Fixed Implemented in rev. 732981. (AccessControlUtil class). Please report any issues. > Create a utility class to simplify accessing JSR283 classes in Jackrabbit 1.5 > - > > Key: SLING-818 > URL: https://issues.apache.org/jira/browse/SLING-818 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Base 2.0.4 >Reporter: Rory Douglas >Assignee: Juan Jose Vazquez Delgado >Priority: Trivial > Attachments: AccessControlUtil.java > > Original Estimate: 0h > Remaining Estimate: 0h > > Create a utility class to wrap up accessing JSR283 classes: UserManager, > PrincipalManager and AccessControlManager. Also provide utility methods for > accessing Jacrabbit-specific ACL features (allow/deny ACLs). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-818) Create a utility class to simplify accessing JSR283 classes in Jackrabbit 1.5
[ https://issues.apache.org/jira/browse/SLING-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-818: Assignee: Juan Jose Vazquez Delgado Remaining Estimate: 0h Original Estimate: 0h Go for it. This class should replace previous RepositoryUtil class > Create a utility class to simplify accessing JSR283 classes in Jackrabbit 1.5 > - > > Key: SLING-818 > URL: https://issues.apache.org/jira/browse/SLING-818 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Base 2.0.4 >Reporter: Rory Douglas >Assignee: Juan Jose Vazquez Delgado >Priority: Trivial > Attachments: AccessControlUtil.java > > Original Estimate: 0h > Remaining Estimate: 0h > > Create a utility class to wrap up accessing JSR283 classes: UserManager, > PrincipalManager and AccessControlManager. Also provide utility methods for > accessing Jacrabbit-specific ACL features (allow/deny ACLs). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-739) Improve the Sling Embedded repository config to make it more flexible
[ https://issues.apache.org/jira/browse/SLING-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-739. - Resolution: Fixed Done as described before. > Improve the Sling Embedded repository config to make it more flexible > - > > Key: SLING-739 > URL: https://issues.apache.org/jira/browse/SLING-739 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: 3 >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado >Priority: Minor > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in [1], it would be necessary to make the Sling embedded > repository configuration more flexible. Use cases for this can be: > * Work with another persistent manager for nodes (rather than default one but > already supported by Jackrabbit. See [2]). > * Custom login module and access manager. > * Change the name of the repository. > The propossal is having three new properties: > # > # The name of the JCR repository. Default is "jackrabbit". > # sling.repository.name = > # > # The JCR repository home directory. Default is > sling.home/sling.repository.name. > # sling.repository.home = > # > # The JCR repository url config file (repository.xml). Default is > repository.xml in > # bundle Embedded JCR Repository > # sling.repository.config.file.url = > These properties can be set in sling.properties, as system properties or as > web app init-params. The properties are not mandatory. The default beahaviour > is a "jackrabbit" repo under sling home if the properties are not set. > [1] http://markmail.org/search/Customizing+the+Sling+embedded+repository > [2] > http://markmail.org/message/2mtvc3egw5omcrbd?q=Customizing+the+Sling+embedded+repository -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-739) Improve the Sling Embedded repository config to make it more flexible
Improve the Sling Embedded repository config to make it more flexible - Key: SLING-739 URL: https://issues.apache.org/jira/browse/SLING-739 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: 3 Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado Priority: Minor As discussed in [1], it would be necessary to make the Sling embedded repository configuration more flexible. Use cases for this can be: * Work with another persistent manager for nodes (rather than default one but already supported by Jackrabbit. See [2]). * Custom login module and access manager. * Change the name of the repository. The propossal is having three new properties: # # The name of the JCR repository. Default is "jackrabbit". # sling.repository.name = # # The JCR repository home directory. Default is sling.home/sling.repository.name. # sling.repository.home = # # The JCR repository url config file (repository.xml). Default is repository.xml in # bundle Embedded JCR Repository # sling.repository.config.file.url = These properties can be set in sling.properties, as system properties or as web app init-params. The properties are not mandatory. The default beahaviour is a "jackrabbit" repo under sling home if the properties are not set. [1] http://markmail.org/search/Customizing+the+Sling+embedded+repository [2] http://markmail.org/message/2mtvc3egw5omcrbd?q=Customizing+the+Sling+embedded+repository -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-681) Servlet listeners support in Sling
[ https://issues.apache.org/jira/browse/SLING-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-681. - Resolution: Duplicate Duplicate SLING-682 > Servlet listeners support in Sling > -- > > Key: SLING-681 > URL: https://issues.apache.org/jira/browse/SLING-681 > Project: Sling > Issue Type: Improvement > Components: Engine >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado >Priority: Minor > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in http://markmail.org/message/cdhzd6ol7x3qg65m, it might be > useful to have some kind of Servlet listener support in Sling. > First of all, we will cover the Sling Web App Launchpad case. Following > Felix´s suggestions, the algorithm would be more or less: > 1. Make a ServletListenerProxy implementing all Servlet API listener services. > 2. This class is registered in the launchpad web app using the > element as defined in the Servlet API Spec. > 3. Upon context creation of the Sling Web App, the proxy places itself into > the context as a context attribute. > 4. When the SlingServlet is initialized it looks at the ServletContext for > the ServletListenerProxy instance. It hands over the BundleContext > of the system bundle, which is actually the result of calling > getBundleContext() on the Felix instance (since the Felix class launching the > framework is the system bundle). Using this BundleContext, the proxy would > use ServiceTrackers for all Servlet API Listener services. > 5. When a Servlet API event arrives, the proxy checks the respective > ServiceTracker for services and forwards the event to the services. > 6. When Sling is shutdown in the SlingServlet.destroy method, the proxy is > also terminated and closes the ServiceTrackers. > 7. Finally the proxy removes itself from the servlet context. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-682) Servlet listeners support in Sling
Servlet listeners support in Sling -- Key: SLING-682 URL: https://issues.apache.org/jira/browse/SLING-682 Project: Sling Issue Type: Improvement Components: Engine Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado Priority: Minor As discussed in http://markmail.org/message/cdhzd6ol7x3qg65m, it might be useful to have some kind of Servlet listener support in Sling. First of all, we will cover the Sling Web App Launchpad case. Following Felix´s suggestions, the algorithm would be more or less: 1. Make a ServletListenerProxy implementing all Servlet API listener services. 2. This class is registered in the launchpad web app using the element as defined in the Servlet API Spec. 3. Upon context creation of the Sling Web App, the proxy places itself into the context as a context attribute. 4. When the SlingServlet is initialized it looks at the ServletContext for the ServletListenerProxy instance. It hands over the BundleContext of the system bundle, which is actually the result of calling getBundleContext() on the Felix instance (since the Felix class launching the framework is the system bundle). Using this BundleContext, the proxy would use ServiceTrackers for all Servlet API Listener services. 5. When a Servlet API event arrives, the proxy checks the respective ServiceTracker for services and forwards the event to the services. 6. When Sling is shutdown in the SlingServlet.destroy method, the proxy is also terminated and closes the ServiceTrackers. 7. Finally the proxy removes itself from the servlet context. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-681) Servlet listeners support in Sling
Servlet listeners support in Sling -- Key: SLING-681 URL: https://issues.apache.org/jira/browse/SLING-681 Project: Sling Issue Type: Improvement Components: Engine Reporter: Juan Jose Vazquez Delgado Assignee: Juan Jose Vazquez Delgado Priority: Minor As discussed in http://markmail.org/message/cdhzd6ol7x3qg65m, it might be useful to have some kind of Servlet listener support in Sling. First of all, we will cover the Sling Web App Launchpad case. Following Felix´s suggestions, the algorithm would be more or less: 1. Make a ServletListenerProxy implementing all Servlet API listener services. 2. This class is registered in the launchpad web app using the element as defined in the Servlet API Spec. 3. Upon context creation of the Sling Web App, the proxy places itself into the context as a context attribute. 4. When the SlingServlet is initialized it looks at the ServletContext for the ServletListenerProxy instance. It hands over the BundleContext of the system bundle, which is actually the result of calling getBundleContext() on the Felix instance (since the Felix class launching the framework is the system bundle). Using this BundleContext, the proxy would use ServiceTrackers for all Servlet API Listener services. 5. When a Servlet API event arrives, the proxy checks the respective ServiceTracker for services and forwards the event to the services. 6. When Sling is shutdown in the SlingServlet.destroy method, the proxy is also terminated and closes the ServiceTrackers. 7. Finally the proxy removes itself from the servlet context. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-453) Initial content loading to target location
[ https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado resolved SLING-453. - Resolution: Fixed Has been fixed using the new ManifestHeader class (https://svn.apache.org/repos/asf/incubator/sling/trunk/commons/osgi/src/main/java/org/apache/sling/commons/osgi/ManifestHeader.java). > Initial content loading to target location > -- > > Key: SLING-453 > URL: https://issues.apache.org/jira/browse/SLING-453 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: 2.0.0 >Reporter: Juan Jose Vazquez Delgado >Priority: Minor > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in the mailing list: > Use case > == > A Sling application needs to load content over a previous and deep hierarchy > nodes. It could be annoying have to repeat the previous hierarchy to deploy > the application particular content. > Propossal > === > >> Put the application content into the bundle, e.g. at SLING-INF/content > >> Define the content in the manifest as: > SLING-INF/content;path:=/root/location -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-453) Initial content loading to target location
[ https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado updated SLING-453: Assignee: (was: Juan Jose Vazquez Delgado) Afaik, until now the Sling-Initial-Content OSGi header could be: bundle/content/path;overwrite:=(true|false);uninstall:=(true|false) Because of this issue, the Sling-Initial-Content header will be: bundle/content/path;overwrite:=(true|false);uninstall:=(true|false);path:=/root/location IMHO, this implies the next changes in o.a.s.jcr.contenloader: >> PathEntry: add a property rootLocation (get;set) >> PathEntry: modify the constructor to parse the new property >> Loader: modify "installContent" method for invoking "installFromPath" with >> the correct parent node if "rootLocation" is not null. Otherwise, invoke >> "installFromPath" >> with the root node. > Initial content loading to target location > -- > > Key: SLING-453 > URL: https://issues.apache.org/jira/browse/SLING-453 > Project: Sling > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0.0 >Reporter: Juan Jose Vazquez Delgado >Priority: Minor > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in the mailing list: > Use case > == > A Sling application needs to load content over a previous and deep hierarchy > nodes. It could be annoying have to repeat the previous hierarchy to deploy > the application particular content. > Propossal > === > >> Put the application content into the bundle, e.g. at SLING-INF/content > >> Define the content in the manifest as: > SLING-INF/content;path:=/root/location -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-453) Initial content loading to target location
[ https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Jose Vazquez Delgado reassigned SLING-453: --- Assignee: Juan Jose Vazquez Delgado > Initial content loading to target location > -- > > Key: SLING-453 > URL: https://issues.apache.org/jira/browse/SLING-453 > Project: Sling > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0.0 >Reporter: Juan Jose Vazquez Delgado >Assignee: Juan Jose Vazquez Delgado >Priority: Minor > Original Estimate: 0h > Remaining Estimate: 0h > > As discussed in the mailing list: > Use case > == > A Sling application needs to load content over a previous and deep hierarchy > nodes. It could be annoying have to repeat the previous hierarchy to deploy > the application particular content. > Propossal > === > >> Put the application content into the bundle, e.g. at SLING-INF/content > >> Define the content in the manifest as: > SLING-INF/content;path:=/root/location -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-453) Initial content loading to target location
Initial content loading to target location -- Key: SLING-453 URL: https://issues.apache.org/jira/browse/SLING-453 Project: Sling Issue Type: Improvement Components: Repository Affects Versions: 2.0.0 Reporter: Juan Jose Vazquez Delgado Priority: Minor As discussed in the mailing list: Use case == A Sling application needs to load content over a previous and deep hierarchy nodes. It could be annoying have to repeat the previous hierarchy to deploy the application particular content. Propossal === >> Put the application content into the bundle, e.g. at SLING-INF/content >> Define the content in the manifest as: SLING-INF/content;path:=/root/location -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
