[jira] Created: (SLING-1013) Feed Entry IDs are URL-encoded
Feed Entry IDs are URL-encoded -- Key: SLING-1013 URL: https://issues.apache.org/jira/browse/SLING-1013 Project: Sling Issue Type: Bug Components: Scripting JSP Reporter: Lars Trieloff The JSP taglib will URL-encode all IDs, but actually IDs should be URLs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Selectors and URL paths
I am trying to handle requests for certain resourceTypes (e.g.
sakai/contactstore) a special way.
What I really want to do is handle something like:
/_user/contacts/key1.key2.json
Where key1 has an unlimited set of values (it would not be a real
node) and key2 has a set of about 8 values.
The current approach involces creating a file (contacts.json) at
/_user and then lots of servlets (8) which work with selectors like
so:
* @scr.component metatype=no immediate=true
* @scr.service interface=javax.servlet.Servlet
* @scr.property name=sling.servlet.resourceTypes values=sakai/contactstore
* @scr.property name=sling.servlet.methods value=POST
* @scr.property name=sling.servlet.selectors value=accept
*/
public class AcceptConnectionServlet extends SlingAllMethodsServlet {
...
}
(in this case key2 would be accept)
The servlets end up having a lot of repetition in them and the code is
not so easy to manage so I am wondering if there is a better (more
slingy) way to do this.
Any suggestions or thoughts? Is this the best way already?
-AZ
--
Aaron Zeckoski (azeckoski (at) vt.edu)
Senior Research Engineer - CARET - University of Cambridge
https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
http://aaronz-sakai.blogspot.com/ -
http://confluence.sakaiproject.org/confluence/display/~aaronz/
[jira] Commented: (SLING-1013) Feed Entry IDs are URL-encoded
[ https://issues.apache.org/jira/browse/SLING-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721789#action_12721789 ] Felix Meschberger commented on SLING-1013: -- Can you be a bit more specific with respect to the concrete issue ? Thanks. Feed Entry IDs are URL-encoded -- Key: SLING-1013 URL: https://issues.apache.org/jira/browse/SLING-1013 Project: Sling Issue Type: Bug Components: Scripting JSP Reporter: Lars Trieloff The JSP taglib will URL-encode all IDs, but actually IDs should be URLs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Selectors and URL paths
Hi Aaron, On Fri, Jun 19, 2009 at 4:00 PM, Aaron Zeckoskiaar...@vt.edu wrote: I am trying to handle requests for certain resourceTypes (e.g. sakai/contactstore) a special way. What I really want to do is handle something like: /_user/contacts/key1.key2.json Where key1 has an unlimited set of values (it would not be a real node) and key2 has a set of about 8 values. If you can, the simplest might be to add another selector that's constant: /_user/contacts/key1.key2.userinfo.json Then, declare your servlet to handle the userinfo selector, and use SlingHttpServletRequest.getRequestPathInfo() .getSelectors() to list all selectors. -Bertrand
[jira] Updated: (SLING-1013) Feed Entry IDs are URL-encoded
[ https://issues.apache.org/jira/browse/SLING-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Trieloff updated SLING-1013: - Attachment: SLING-1013.patch calling UrlEncoding.encode(id) will encode all slashes, etc. on the ID, which means it is no longer a valid URL. This patch fixes it, Feed Entry IDs are URL-encoded -- Key: SLING-1013 URL: https://issues.apache.org/jira/browse/SLING-1013 Project: Sling Issue Type: Bug Components: Scripting JSP Reporter: Lars Trieloff Attachments: SLING-1013.patch The JSP taglib will URL-encode all IDs, but actually IDs should be URLs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1014) Atom JSP Taglib bundle needs manual re-activation in Felix console before the Abdera object is available
Atom JSP Taglib bundle needs manual re-activation in Felix console before the Abdera object is available Key: SLING-1014 URL: https://issues.apache.org/jira/browse/SLING-1014 Project: Sling Issue Type: Bug Components: Scripting JSP Reporter: Lars Trieloff Using the JSP Taglib on a fresh install will not work (empty response created), because the Abdera object is not available in the pageContext. Only after restarting the bundle manually, it becomes available. It looks like this is a problem with the startup order of the JSP Taglib and the Abdera bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Selectors and URL paths
On 19 Jun 2009, at 15:00, Aaron Zeckoski wrote: The servlets end up having a lot of repetition in them and the code is not so easy to manage so I am wondering if there is a better (more slingy) way to do this. Any suggestions or thoughts? Is this the best way already? -AZ How about an abstract base class, just for this set of servlets? All the code can go in 1 base class. Thats what is done in the jackrabbit-accessmanager and jackrabbit- usermanager. Ian
User Manager, adding groups
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
Re: Selectors and URL paths
Not really on topic but a hint:
On Fri, Jun 19, 2009 at 4:00 PM, Aaron Zeckoski aar...@vt.edu wrote:
The current approach involces creating a file (contacts.json) at
/_user and then lots of servlets (8) which work with selectors like
so:
* @scr.component metatype=no immediate=true
* @scr.service interface=javax.servlet.Servlet
* @scr.property name=sling.servlet.resourceTypes
values=sakai/contactstore
* @scr.property name=sling.servlet.methods value=POST
* @scr.property name=sling.servlet.selectors value=accept
*/
public class AcceptConnectionServlet extends SlingAllMethodsServlet {
...
}
can now be replaced by Java 5 Annotation:
@SlingServlet(methods=POST, resourceTypes=sakai/contactstore,
selectors=accept)
..when using the latest maven-scr-plugin (was enabled with maven-scr-plugin
1.2.0)
Regards,
Dominik
[jira] Resolved: (SLING-1015) Make Date Handling more convenient
[ https://issues.apache.org/jira/browse/SLING-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Trieloff resolved SLING-1015. -- Resolution: Invalid a JSP attribute can only have one type, so having updated as long, String and Date will not work without touching the PropertyEditorManager, which operates VM-wide. Make Date Handling more convenient -- Key: SLING-1015 URL: https://issues.apache.org/jira/browse/SLING-1015 Project: Sling Issue Type: Improvement Components: Scripting JSP Reporter: Lars Trieloff Priority: Minor The JSP Atom taglib expects dates to be specified as java.util.Date - it would be convenient, if the taglib would also allow specification as String, Calendar or long. If the date is specified as String two options would be helpful: SimpleDateFormat and auto, which would take in the case of the feed the minimum updated Date of all entries and in the case of an Entry the current date. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: User Manager and Charset
On Wed, Jun 17, 2009 at 04:54:25PM +0200, Juan José Vázquez Delgado wrote: There is an issue with accented chars and the sling user manager. You can try with a hidden field of the name _charset_ containing the encoding in your form. Have a look at this [1]. [1] http://incubator.apache.org/sling/site/request-parameters.html Thank you. That was it, what I was missing. -- peter
Re: Sling graduates from the Apache Incubator!
Congratulations to the whole team and thanks for the good work :) Claude On Thu, Jun 18, 2009 at 9:33 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: (ccing jackrabbit PMC as our incubation sponsor) (and friends!) Hi Sling community, I'm pleased to announce that our Board of Directors, at yesterday's meeting, approved the graduation of Sling as a top-level project. I abstained from that vote (as working on Sling is part of my job), so it's not my fault ;-) Felix Meschberger is the chair of the new PMC, composed of * Alexandru Popescu apopescu * Bertrand Delacretaz bdelacretaz * Christophe Lombart clombart * Carsten Ziegeler cziegeler * Felix Meschberger fmeschbe * Gianugo Rabellino gianugo * Padraic Hannon hannonpi * Juan José Vázquez Delgado juanjo * Karl Pauls pauls * Vidar Ramdal vramdal Mike Müller is not listed above but of course remains a documentor as mentioned at http://incubator.apache.org/sling/site/project-team.html. This is just not part of the board's vote, which is about establishing the new project and PMC. Felix is preparing the infrastructure move and will keep us informed. Thanks very much to all involved and let's take Apache Sling to the next level! -- Bertrand
