[ https://issues.apache.org/jira/browse/SLING-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718322#comment-13718322 ]
Robert Munteanu commented on SLING-2666: ---------------------------------------- I'm thinking about the current way of addressing the problem: I. Create a server-side support bundle which will handle requests, instead of using the Default{Get,Post}Servlet directly 1. Create a Servlet which is mapped at /bin/idesupport ( for lack of a better location ). This servlet handles resources based on requestPathInfo.getSuffixResource() 2. For GET requests, return the resource mapped as JSON. 2.1 If the request has a 'children' selector, also dump the first-level children 2.2 If the request does not have a suffix, dump bundle information in JSon format - for now the bundle version. 3. For POST requests, delegate to the POST servlet ( lookup the component with Servlet.class and pid=org.apache.sling.servlets.post.impl.SlingPostServlet ) II. Update the IDE integration to hook into this bundle 1. Build the support bundle as part of the reactor and embed it inside the eclipse-core plugin. 2. When creating a new Sling Launchpad Server in Eclipse check if the support bundle is available. If it is, or if we have a newer version, offer to install it. 3. Allow the user to install/upgrade/remove this support bundle using the Server editor 4. Update the RepositoryImpl to communicate with the new servlet [~asanso], [~dklco], [~egli] - any thoughts on this? > [Tooling] Checking out resources fails if the DefaultGetServlet does not > serve the content > ------------------------------------------------------------------------------------------ > > Key: SLING-2666 > URL: https://issues.apache.org/jira/browse/SLING-2666 > Project: Sling > Issue Type: Sub-task > Components: Extensions > Reporter: Antonio Sanso > Assignee: Robert Munteanu > > see discussion at [0] > [0] http://sling.markmail.org/message/rsmysnx6ombk4u4s -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira