[jira] Created: (SLING-1830) Improve write acesses for job execution
Improve write acesses for job execution --- Key: SLING-1830 URL: https://issues.apache.org/jira/browse/SLING-1830 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently, the flow for a job is: - write the job to the repository - lock the node - add the PROCESSOR info - remove the node or unlock it and set some props We can at least skip the PROCESSOR info and set it at the end. In addition we should base the job handling completly on observation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1828) Provide queue operations like suspend/resume
Provide queue operations like suspend/resume Key: SLING-1828 URL: https://issues.apache.org/jira/browse/SLING-1828 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Queue operations for supsending (to stop processing for a while), resuming, clearing the queue (without removing the jobs) and removing all jobs from the queue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1829) Provide statistics about job processing
Provide statistics about job processing --- Key: SLING-1829 URL: https://issues.apache.org/jira/browse/SLING-1829 Project: Sling Issue Type: New Feature Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 It would be nice to have some statistics about the job handling like home many jobs have been processed, are queued, are in processing etc. We could have one general set and a set per queue for drill down -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1823) Use ConfigAdmin configurations for queues
[ https://issues.apache.org/jira/browse/SLING-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919279#action_12919279 ] Carsten Ziegeler commented on SLING-1823: - Using configurations allows reconfiguration at runtime, however it is difficult to really reconfigure a queue at runtime. In such cases we contine the old queue with the old config and start a new queue with the new config. (Queues are only started if required) > Use ConfigAdmin configurations for queues > - > > Key: SLING-1823 > URL: https://issues.apache.org/jira/browse/SLING-1823 > Project: Sling > Issue Type: New Feature > Components: Extensions >Affects Versions: Extensions Event 2.4.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: Extensions Event 3.0.0 > > > Currently the jobs send to the job handler might contain queue configuration > information, like a queue name, parallel settings etc. These props are used > to create queues. This approach has a least two potential problems: > - What happens if two jobs specify the same queue name with different > settings? > - The developer creating the code to send the job might not be the person > deciding what is processed in which queue and how > Therefore it would make more sense to have a queue as a configuration in the > ConfigAdmin . this would make maintenance easier and allows to have a single > place for queue configurations. Of course the old props should still be > supported for compatibility. > The configurations can then be easily added, viewed and monitored through the > web console. > The main queue is a configuration which is always available -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1827) Mechanism to process specific jobs on specific machines
Mechanism to process specific jobs on specific machines --- Key: SLING-1827 URL: https://issues.apache.org/jira/browse/SLING-1827 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 When the job mechanism is used for expensive operations like movie encodings etc. it would be nice to have dedicated machines processing these jobs. We could simply restrict queues to process jobs on specific nodes in a cluster through the Sling application id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1823) Use ConfigAdmin configurations for queues
[
https://issues.apache.org/jira/browse/SLING-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919278#action_12919278
]
Carsten Ziegeler commented on SLING-1823:
-
A queue configuration gets a list of topics (kind of regexps) which match the
job topic. Through this matching algorithm a queue can process a set of topics.
It should also be possible to have a single configuration which creates various
topics, like
topic matcher: org.apache.x.y.*
queue name: {0}
This queue processes all topics starting with org.apache.x.y. and a new queue
is used for every sub topic, so if jobs org.apache.x.y.A and org.apache.x.y.B
are processed, two queues A and B are created
> Use ConfigAdmin configurations for queues
> -
>
> Key: SLING-1823
> URL: https://issues.apache.org/jira/browse/SLING-1823
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Affects Versions: Extensions Event 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.0.0
>
>
> Currently the jobs send to the job handler might contain queue configuration
> information, like a queue name, parallel settings etc. These props are used
> to create queues. This approach has a least two potential problems:
> - What happens if two jobs specify the same queue name with different
> settings?
> - The developer creating the code to send the job might not be the person
> deciding what is processed in which queue and how
> Therefore it would make more sense to have a queue as a configuration in the
> ConfigAdmin . this would make maintenance easier and allows to have a single
> place for queue configurations. Of course the old props should still be
> supported for compatibility.
> The configurations can then be easily added, viewed and monitored through the
> web console.
> The main queue is a configuration which is always available
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1826) Provide a round robin queue based on the topic
Provide a round robin queue based on the topic -- Key: SLING-1826 URL: https://issues.apache.org/jira/browse/SLING-1826 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently we have two queues: parallel or ordered. We could also do a topic round robin queue, which picks a different a job with a topic. This allows to limit the number of jobs processed in parallel for these topics while each topic is processed as fast as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1825) Use in memory searches for jobs
Use in memory searches for jobs --- Key: SLING-1825 URL: https://issues.apache.org/jira/browse/SLING-1825 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Jobs are currently searched through a JCR query - the query can be very slow and as most of the information is already available in memory anyway, we could directly search in memory and don't need any jcr access -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1824) Clean up implementation
Clean up implementation --- Key: SLING-1824 URL: https://issues.apache.org/jira/browse/SLING-1824 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 The job handling implementation has grown over time and got overly complicated now. It is time to clean it up and refactor it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1824) Clean up implementation
[ https://issues.apache.org/jira/browse/SLING-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919277#action_12919277 ] Carsten Ziegeler commented on SLING-1824: - We should also try to separate the persistence handling from the job handling. This should create a cleaner separation of concerns and simplify the implementation > Clean up implementation > --- > > Key: SLING-1824 > URL: https://issues.apache.org/jira/browse/SLING-1824 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: Extensions Event 2.4.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: Extensions Event 3.0.0 > > > The job handling implementation has grown over time and got overly > complicated now. It is time to clean it up and refactor it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1823) Use ConfigAdmin configurations for queues
Use ConfigAdmin configurations for queues - Key: SLING-1823 URL: https://issues.apache.org/jira/browse/SLING-1823 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently the jobs send to the job handler might contain queue configuration information, like a queue name, parallel settings etc. These props are used to create queues. This approach has a least two potential problems: - What happens if two jobs specify the same queue name with different settings? - The developer creating the code to send the job might not be the person deciding what is processed in which queue and how Therefore it would make more sense to have a queue as a configuration in the ConfigAdmin . this would make maintenance easier and allows to have a single place for queue configurations. Of course the old props should still be supported for compatibility. The configurations can then be easily added, viewed and monitored through the web console. The main queue is a configuration which is always available -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] [VOTE] Release Sling Servlets Resolver 2.1.0, Servlets GET 2.1.0, Servlets POST 2.1.0
ehrm ... s/not/now/ ;-) Thanks and Regards Felix On 08.10.2010 13:10, Carsten Ziegeler wrote: > Felix Meschberger wrote >> I will not continue publishing the artifacts. > Hmm and I thought 1st of April is six months away... > > Carsten
Re: [RESULT] [VOTE] Release Sling Servlets Resolver 2.1.0, Servlets GET 2.1.0, Servlets POST 2.1.0
Felix Meschberger wrote > I will not continue publishing the artifacts. Hmm and I thought 1st of April is six months away... Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Closed: (SLING-1718) text/html property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-1718.
Closes issue after bundle release.
> text/html property rendering of multi-valued properties doesn't work
>
>
> Key: SLING-1718
> URL: https://issues.apache.org/jira/browse/SLING-1718
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Reporter: Justin Edelson
> Fix For: Servlets Get 2.1.0
>
>
> $ curl -u admin:admin -F a=b -F "a...@typehint=string[]"
> http://localhost:/test/node1
> $ curl http://localhost:/test/node1.html
>
> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
> http://www.w3.org/1999/xhtml"; xml:lang="en">
> />
>
> Resource dumped by HtmlRendererServlet
> Resource path: /test/node1
> Resource metadata: {sling.resolutionPathInfo=.html,
> sling.resolutionPath=/test/node1}
> Resource type: nt:unstructured
> Resource super type: -
> Resource properties
>
> a: [b]
> jcr:primaryType: nt:unstructured
>
>
> $ curl http://localhost:/test/node1/a.html
> returns a 204 No Content message
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1814) Add support for Range requests to the StreamRendererServlet
[ https://issues.apache.org/jira/browse/SLING-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1814. Closes issue after bundle release. > Add support for Range requests to the StreamRendererServlet > --- > > Key: SLING-1814 > URL: https://issues.apache.org/jira/browse/SLING-1814 > Project: Sling > Issue Type: Improvement > Components: Servlets >Affects Versions: Servlets Get 2.0.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Servlets Get 2.1.0 > > > To support some kind of streaming support for the Range HTTP header can be > built into the StreamRendererServlet. > The Tomcat DefaultServlet [1] can be used as the basis for this > implementation. > [1] > http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/servlets/DefaultServlet.java?view=markup -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (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 ] Felix Meschberger closed SLING-1776. Closes issue after bundle release. > 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: Servlets > Environment: InternetExplorer >Reporter: Clemens Wyss >Assignee: Justin Edelson > Fix For: Servlets Get 2.1.0 > > > 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] Closed: (SLING-1574) DefaultGetServlet does not set response content type when rendering an index file for a directory
[ https://issues.apache.org/jira/browse/SLING-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1574. Closes issue after bundle release. > DefaultGetServlet does not set response content type when rendering an index > file for a directory > - > > Key: SLING-1574 > URL: https://issues.apache.org/jira/browse/SLING-1574 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Get 2.0.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Servlets Get 2.1.0 > > > When generating the response to a directory (trailing slash in the request > URL), the default GET servlet checks whether one of a configured list of > index files exists. If such a file exists it is returned. This mechanism, > though, fails to set the response content type because the index file is > included in the request and included request handling does not (always) set > the response content type. > This is particulary the case if the file to include is a file to be spooled > back by the Default GET servlet itself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1503) Allow subclasses of JsonQueryServlet to modify the statement and query type
[ https://issues.apache.org/jira/browse/SLING-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1503. Closes issue after bundle release. > Allow subclasses of JsonQueryServlet to modify the statement and query type > --- > > Key: SLING-1503 > URL: https://issues.apache.org/jira/browse/SLING-1503 > Project: Sling > Issue Type: Improvement > Components: Servlets >Reporter: Justin Edelson >Assignee: Justin Edelson > Fix For: Servlets Get 2.1.0 > > > It would be useful if JsonQueryServlet enables subclasses to override the > statement and/or query type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1408) text/plain property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-1408.
Closes issue after bundle release.
> text/plain property rendering of multi-valued properties doesn't work
> -
>
> Key: SLING-1408
> URL: https://issues.apache.org/jira/browse/SLING-1408
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Get 2.0.8
>Reporter: Justin Edelson
> Fix For: Servlets Get 2.1.0
>
>
> $ curl -u admin:admin -F a=b -F "a...@typehint=string[]"
> http://localhost:/test/node1
> $ curl http://localhost:/test/node1.txt
> ** Resource dumped by PlainTextRendererServlet**
> Resource path:/test/node1
> Resource metadata: {sling.resolutionPathInfo=.txt,
> sling.resolutionPath=/test/node1}
> Resource type: nt:unstructured
> Resource super type: -
> ** Resource properties **
> a: [b]
> jcr:primaryType: nt:unstructured
> $ curl http://localhost:/test/node1/a.txt
> (nothing output here)
> should be [b] IMHO
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1632) The JsonQueryServlet should support the tidy selector to provide pretty printed results
[ https://issues.apache.org/jira/browse/SLING-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1632. Closes issue after bundle release. > The JsonQueryServlet should support the tidy selector to provide pretty > printed results > --- > > Key: SLING-1632 > URL: https://issues.apache.org/jira/browse/SLING-1632 > Project: Sling > Issue Type: Improvement > Components: Servlets >Affects Versions: Servlets Get 2.0.2, Servlets Get 2.0.4, Servlets Get > 2.0.6, Servlets Get 2.0.8 >Reporter: Eric Norman >Assignee: Eric Norman > Fix For: Servlets Get 2.1.0 > > > SLING-562 provided the ability to apply a tidy rendering for the > JsonRendererServlet. The same technique would be useful for formatting the > results of the JsonQueryServlet. > For example: > http://localhost:/.query.tidy.json?queryType=xpath&statement=//element(*,nt:unstructured) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1706) Add authentication type info to the result of the SessionInfoServlet
[ https://issues.apache.org/jira/browse/SLING-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1706. Closes issue after bundle release. > Add authentication type info to the result of the SessionInfoServlet > > > Key: SLING-1706 > URL: https://issues.apache.org/jira/browse/SLING-1706 > Project: Sling > Issue Type: Improvement > Components: Servlets >Affects Versions: Servlets Get 2.0.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Servlets Get 2.1.0 > > > The SessionInfoServlet currently returns the id and workspace of the > logged-in JCR Session. To determine, whether the current request is actually > authenticated or not, this is not enough information. > Adding a new property "authType" set to the value of the > HttpServletRequest.getAuthType() method serves this purpose: >* The property is not set if the getAuthType() method returns null. The > request is not authenticated in this case >* The value of the property not only indicates that the request is > authenticated but also the kind of authentication which was used -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1549) Servlet cache can grow infinitely
[ https://issues.apache.org/jira/browse/SLING-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1549. Closes issue after bundle release. > Servlet cache can grow infinitely > - > > Key: SLING-1549 > URL: https://issues.apache.org/jira/browse/SLING-1549 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Critical > Fix For: Servlets Resolver 2.1.0 > > > Thought there is a configuration for the maximum size of the servlet resolver > this config is not used to limit the cache; therefore the cache can grow > infinitely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1610) StreamRendererServlet creates endless redirect for non-default workspace root node
[ https://issues.apache.org/jira/browse/SLING-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1610. Closes issue after bundle release. > StreamRendererServlet creates endless redirect for non-default workspace root > node > -- > > Key: SLING-1610 > URL: https://issues.apache.org/jira/browse/SLING-1610 > Project: Sling > Issue Type: Bug > Components: Servlets >Reporter: Justin Edelson >Assignee: Justin Edelson > Fix For: Servlets Get 2.1.0 > > > if you request the root node of a non-default workspace, Sling create an > endless redirect loop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1512) Make script execution paths configurable
[ https://issues.apache.org/jira/browse/SLING-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1512. Closes issue after bundle release. > Make script execution paths configurable > > > Key: SLING-1512 > URL: https://issues.apache.org/jira/browse/SLING-1512 > Project: Sling > Issue Type: New Feature > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: Servlets Resolver 2.1.0 > > > Currently the script resolver executes scripts from any path in the > repository. This can be limited by using a special script resolver user and > configuring ACL's in the repository. > However that approach is sometimes difficult to manage and does not work at > all with scripts outside the repository. > Therefore we should make script execution paths configurable -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1514) Remove the dependency to the Sling JCR API
[ https://issues.apache.org/jira/browse/SLING-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1514. Closes issue after bundle release. > Remove the dependency to the Sling JCR API > -- > > Key: SLING-1514 > URL: https://issues.apache.org/jira/browse/SLING-1514 > Project: Sling > Issue Type: Improvement > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Minor > Fix For: Servlets Resolver 2.1.0 > > > Currently the servlet resolver depends on the Sling JCR API - with the new > ResourceResolverFactory in the Sling API we can directly use that and remove > the dependency to the Sling JCR API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1496) A GET request to a directory results in a response with no content type, confusing some browsers.
[ https://issues.apache.org/jira/browse/SLING-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1496. Closes issue after bundle release. > A GET request to a directory results in a response with no content type, > confusing some browsers. > - > > Key: SLING-1496 > URL: https://issues.apache.org/jira/browse/SLING-1496 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Get 2.0.8 >Reporter: Ian Boston >Assignee: Ian Boston > Fix For: Servlets Get 2.1.0 > > > As per http://markmail.org/thread/2kxoab4eg5sqhdz6 > a request to a directory eg /dev/ which contains an index.html file results > in a response with no content type. > Identified that included resources that are streamed dont set any response > headers indicating that the headers must be set before the body is included. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-585) New functionality to resolve scripts by name
[ https://issues.apache.org/jira/browse/SLING-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-585. --- Closes issue after bundle release. > New functionality to resolve scripts by name > > > Key: SLING-585 > URL: https://issues.apache.org/jira/browse/SLING-585 > Project: Sling > Issue Type: New Feature > Components: API, Servlets >Affects Versions: Servlets Resolver 2.0.8, API 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Servlets Resolver 2.1.0, API 2.1.0 > > Attachments: SLING585.patch > > > I'm looking for a way to include a jsp script from within another but > respecting the resource type hierarchy. so for example: > + myapp > + A > + A.jsp > + content.jsp > + B > - sling:resourceSuperType = "A" > + B.jsp > and in my B.jsp i want to include the "content.jsp" but respecting the > resource type hierarchy. > suggest to add: that internally > overwrites the request selector during the script selection phase. > see http://markmail.org/message/la4rvmcdd6whpvhl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1580) SlingServletResolver registers OSGi services from synchronized blocks
[ https://issues.apache.org/jira/browse/SLING-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1580. Closes issue after bundle release. > SlingServletResolver registers OSGi services from synchronized blocks > - > > Key: SLING-1580 > URL: https://issues.apache.org/jira/browse/SLING-1580 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Bertrand Delacretaz >Assignee: Carsten Ziegeler >Priority: Minor > Fix For: Servlets Resolver 2.1.0 > > > The synchronized bindServlet method calls createServlet which in turns calls > context.getBundleContext().registerService(...). > This means OSGi framework calls are done from a synchronized method, which > can lead to deadlocks. > I think we can synchronize much less, it's probably just the changes to the > servletsByReference and pendingServlets collections that need to be > synchronized. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1160) Allow the DefaultErrorHandlerServlet to be overwritten
[ https://issues.apache.org/jira/browse/SLING-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1160. Closes issue after bundle release. > Allow the DefaultErrorHandlerServlet to be overwritten > -- > > Key: SLING-1160 > URL: https://issues.apache.org/jira/browse/SLING-1160 > Project: Sling > Issue Type: New Feature > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Servlets Resolver 2.1.0 > > > Currently the DefaultErrorHandlerServlet is used as the fall back if no other > applying error handling servlet/script can be found. This default servlet > cannot be replaced. This is problematic since developers might want to > provide custom default handlers, for example to suppress thread dumps etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1329) Multiple-value Reference Properties
[ https://issues.apache.org/jira/browse/SLING-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1329. Closes issue after bundle release. > Multiple-value Reference Properties > --- > > Key: SLING-1329 > URL: https://issues.apache.org/jira/browse/SLING-1329 > Project: Sling > Issue Type: Bug > Environment: Karaf 1.2.0, trunk build of sling installed using > features.xml (rev 902845), java 1.6, maven 2.2.1 >Reporter: Jason Rose > Fix For: Servlets Get 2.1.0 > > Attachments: jiracase.zip > > > I am creating 2 node subtrees for two entities with a many-to-many > relationship to each other. I am implementing this relationship as a strong > reference, multiple value property on each entity node under the subtrees. > I'm loading in the data as nt:unstructured with mix:referenceable as the only > addition, so I can make references between the two. The tree looks like this: > /multiple-reference-property (root for this test) >|--users > |--user a(random uuid as its name) > |--regions-single (single property reference to region a, seems to > work) > |--regions (multiple-valued reference property to regions a-e, > renders fine as text but doesn't act as relationship if I try to traverse it > via URL) > |--users b-e, set up identically to user a >|--regions > |--region a(random uuid as its name) > |--users-single (single property reference to user a, seems to work) > |--users (multiple-valued reference property to users a-e, renders > fine as text but doesn't act as a relationship if I try to traverse it via > URL) > I can successfully use URLs like > localhost:8181/multiple-reference-property/regions/ a>/users-single. > What does not work is a URL like > localhost:8181/multiple-reference-property/regions/ a>/users. > The data is loaded via a bundle, since using the contentloader with flat > files will be unfeasible later in my project's future, because it will need a > very large and randomized dataset, which only seems easily doable by directly > interacting with the JCR api. > Of course if there is a more preferred way to implement a relationship like > this, please let me know. I would strongly prefer to not use weak references > in this case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1446) Scripts should be resolved against the current workspace
[ https://issues.apache.org/jira/browse/SLING-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1446. Closes issue after bundle release. > Scripts should be resolved against the current workspace > > > Key: SLING-1446 > URL: https://issues.apache.org/jira/browse/SLING-1446 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Justin Edelson >Assignee: Carsten Ziegeler > Fix For: Servlets Resolver 2.1.0 > > > currently, if a non-default workspace is specified in AuthenticationInfo, > scripts are still resolved against the default workspace. > Scripts should be resolved first against the workspace used in the Request > (i.e. from AuthenticationInfo) and then a default workspace as a backup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1529) Endless iteration in LocationIterator with circular resource super types
[ https://issues.apache.org/jira/browse/SLING-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1529. Closes issue after bundle release. > Endless iteration in LocationIterator with circular resource super types > > > Key: SLING-1529 > URL: https://issues.apache.org/jira/browse/SLING-1529 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Tobias Bocanegra >Assignee: Carsten Ziegeler > Fix For: Servlets Resolver 2.1.0 > > > The location iterator does not detect resource super type circular references > and causes script resolution to loop endlessly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1466) Deprecate AbstractServiceReferenceConfig
[ https://issues.apache.org/jira/browse/SLING-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1466. Closes issue after bundle release. > Deprecate AbstractServiceReferenceConfig > > > Key: SLING-1466 > URL: https://issues.apache.org/jira/browse/SLING-1466 > Project: Sling > Issue Type: Improvement > Components: Engine >Affects Versions: Servlets Resolver 2.0.8, Engine 2.0.6 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: Servlets Resolver 2.1.0, Engine 2.1.0 > > > This class is only used internally by the engine and the servlet resolver > bundle. > Therefore we should deprecate it (and remove it in a later version) and cut > this dependency between the engine and the servlet resolver bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1069) Servlets registered with for resourceTypes = sling/servlet/default responds to all extensions
[ https://issues.apache.org/jira/browse/SLING-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1069. Closes issue after bundle release. > Servlets registered with for resourceTypes = sling/servlet/default responds > to all extensions > - > > Key: SLING-1069 > URL: https://issues.apache.org/jira/browse/SLING-1069 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Resolver 2.0.4 >Reporter: Vidar S. Ramdal >Assignee: Felix Meschberger > Fix For: Servlets Resolver 2.1.0 > > Attachments: RogueServlet.java, SLING-1069-fmeschbe.patch, > SLING-1069-test.patch, SLING-1069.patch > > > A servlet registered with > @scr.property name="sling.servlet.extensions" value="html" > @scr.property name="sling.servlet.resourceTypes" > value="sling/servlet/default" > in the Javadoc, responds to all requests, in effect ignoring the > "sling.servlet.extensions" property. > To reproduce: > 1. Install servlet from attachment (coming up) > 2. Let the browser fetch /somenode.json > Expected result: > The server returns the JSON rendering of /somenode > Actual result: > The server returns "Rogue Servlet" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-892) Allow servlets to be registered with extensions for all request methods
[ https://issues.apache.org/jira/browse/SLING-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-892. --- Closes issue after bundle release. > Allow servlets to be registered with extensions for all request methods > --- > > Key: SLING-892 > URL: https://issues.apache.org/jira/browse/SLING-892 > Project: Sling > Issue Type: Improvement > Components: Servlets >Affects Versions: Servlets Resolver 2.0.8 >Reporter: Alexander Klimetschek >Assignee: Felix Meschberger > Fix For: Servlets Resolver 2.1.0 > > Attachments: SLING-892.patch > > > As SLING-754 introduced/fixed registering servlets for non-GET methods with > selectors (eg. /apps/myapp/selector.POST.servlet), the same should be > possible for extensions: /apps/myapp/extension.POST.servlet > Use case: symmetric URLs when you import and export stuff at a given resource > path: > Export = GET @ /some/path/foo.ext > Import/Update = POST @ /some/path/foo.ext > Currently you are forced to either use a selector for the POST case > (/some/path/foo.ext.ext) or to have a sling resource type set on the > /some/path/foo, but then you could only have a single POST servlet for that > resource type, regardless of the extension (which is unpractical if you for > example have a resource type like "calendar", but want to import various > calendar formats, separated by their file extension). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] Release Sling Servlets Resolver 2.1.0, Servlets GET 2.1.0, Servlets POST 2.1.0
Hi, Time to tally the vote. We have received the following votes (bindings marked with *): +1 Felix Meschberger*, Carsten Ziegeler*, Justin Edelson*, Mike Müller*, Eric Norman 0 - -1 - This votes passes with 5 +1 votes (4 of which binding). No other votes have been received. Thanks for your votes. I will not continue publishing the artifacts. Regards Felix On 03.10.2010 20:48, Felix Meschberger wrote: > Hi, > > I hereby start the vote for the release of the Servlet support bundles: > Sling Servlets Resolver 2.1.0, Sling Servlets GET 2.1.0, and Sling > Servlets POST 2.1.0. All bundles include some kind of extended > functionalities besides a number of bugs fixed. > > For Sling Servlets Resolver 2.1.0 we solved 13 issues: > https://issues.apache.org/jira/browse/SLING/fixforversion/12314292 > > For Sling Servlets GET 2.1.0 we solved 13 issues: > https://issues.apache.org/jira/browse/SLING/fixforversion/12314473 > > For Sling Servlets POST 2.1.0 we solved 35 issues: > https://issues.apache.org/jira/browse/SLING/fixforversion/12314180 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-003/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 003 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This vote will be open for 72 hours. > > Regards > Felix
