Re: Error Messaging/Validation
Hi, Alexander Klimetschek schrieb: > On Sun, Oct 19, 2008 at 10:20 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: >> RequestDispatcher rd = request.getRequestDispatcher( >> request.getResource(), >> new >> RequestDispatcherOptions(ServletResolverConstants.DEFAULT_SERVLET_NAME) >> ); >> rd.forward(request, response); >> >> For the forward to succeed you need a current snapshot build of the >> engine module (forward has just been added last week). > > Cool! Is there a taglib tag for doing this directly in JSPs? If not, > might be useful and simpler than to remember these lines and the > correct request dispatcher options. Something like , > similar to sling:include. Yes, this is a TODO. And I think at least one form of SlingScriptHelper.forward method should also be provided. Regards Felix
Re: Error Messaging/Validation
Felix Meschberger wrote: > Hi, > > Alexander Klimetschek schrieb: >> On Sun, Oct 19, 2008 at 10:20 PM, Felix Meschberger <[EMAIL PROTECTED]> >> wrote: >>> RequestDispatcher rd = request.getRequestDispatcher( >>> request.getResource(), >>> new >>> RequestDispatcherOptions(ServletResolverConstants.DEFAULT_SERVLET_NAME) >>> ); >>> rd.forward(request, response); >>> >>> For the forward to succeed you need a current snapshot build of the >>> engine module (forward has just been added last week). >> Cool! Is there a taglib tag for doing this directly in JSPs? If not, >> might be useful and simpler than to remember these lines and the >> correct request dispatcher options. Something like , >> similar to sling:include. > > Yes, this is a TODO. And I think at least one form of > SlingScriptHelper.forward method should also be provided. > +1 Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
[jira] Created: (SLING-703) Add tag
Add tag --- Key: SLING-703 URL: https://issues.apache.org/jira/browse/SLING-703 Project: Sling Issue Type: New Feature Components: Scripting JSP Affects Versions: Scripting JSP-Taglib 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Scripting JSP-Taglib 2.0.4 SLING-692 implements the RequestDispatcher.forward method. The Sling TagLib should now be enhanced to include a forward tag. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-704) Add SlingScriptHelper.forward method
Add SlingScriptHelper.forward method Key: SLING-704 URL: https://issues.apache.org/jira/browse/SLING-704 Project: Sling Issue Type: New Feature Affects Versions: Scripting Core 2.0.2, Scripting API 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Scripting Core 2.0.4, API 2.0.4 SLING-692 implements the RequestDispatcher.forward method. The SlingScriptHelper interface should now be enhanced with a forward method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-705) Set current thread name while handling requests
[ https://issues.apache.org/jira/browse/SLING-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-705. --- Resolution: Fixed Implemented setting and resetting the thread name in Rev. 706163. The thread name is constructed like this: 127.0.0.1 [1224156108055] GET /system/console/config HTTP/1.1 where the fields have the following meaning: 1 - IP address of client (or last proxy) 2 - current system time at start of request processing 3 - request method 4 - request URI (path) 5 - request protocol > Set current thread name while handling requests > --- > > Key: SLING-705 > URL: https://issues.apache.org/jira/browse/SLING-705 > Project: Sling > Issue Type: Improvement > Components: Engine >Affects Versions: Engine 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger >Priority: Trivial > Fix For: Engine 2.0.4 > > > To help in problem determination, it would be usefull to have the > SlingMainServlet set the current thread's name to some request information > while servicing the request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-703) Add tag
[ https://issues.apache.org/jira/browse/SLING-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640958#action_12640958 ] Felix Meschberger commented on SLING-703: - Added the forward tag in Rev. 706167 Keeping the issue open for addition of integration tests > Add tag > --- > > Key: SLING-703 > URL: https://issues.apache.org/jira/browse/SLING-703 > Project: Sling > Issue Type: New Feature > Components: Scripting JSP >Affects Versions: Scripting JSP-Taglib 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Scripting JSP-Taglib 2.0.4 > > > SLING-692 implements the RequestDispatcher.forward method. The Sling TagLib > should now be enhanced to include a forward tag. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-704) Add SlingScriptHelper.forward method
[ https://issues.apache.org/jira/browse/SLING-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640962#action_12640962 ] Felix Meschberger commented on SLING-704: - Added forward method to SlingScriptHelper interface in Rev. 706168 and provided implementation in scripting/core's ScriptHelper class in Rev. 706169 Keeping this issue open for addition of integration tests > Add SlingScriptHelper.forward method > > > Key: SLING-704 > URL: https://issues.apache.org/jira/browse/SLING-704 > Project: Sling > Issue Type: New Feature >Affects Versions: Scripting API 2.0.2, Scripting Core 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Scripting Core 2.0.4, API 2.0.4 > > > SLING-692 implements the RequestDispatcher.forward method. The > SlingScriptHelper interface should now be enhanced with a forward 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-706) Change default value of max idle pool sessions to 0
Change default value of max idle pool sessions to 0 --- Key: SLING-706 URL: https://issues.apache.org/jira/browse/SLING-706 Project: Sling Issue Type: Wish Components: JCR Affects Versions: JCR Jackrabbit Client 2.0.2 Reporter: Tobias Bocanegra the JCR repository client session pool should initially be disabled. change the default value of max idle pool sessions to 0. the overhead of acquiring and releasing sessions is bigger than the performance gain from keeping the cached sessions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-706) Change default value of max idle pool sessions to 0
[ https://issues.apache.org/jira/browse/SLING-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-706: --- Assignee: Felix Meschberger > Change default value of max idle pool sessions to 0 > --- > > Key: SLING-706 > URL: https://issues.apache.org/jira/browse/SLING-706 > Project: Sling > Issue Type: Wish > Components: JCR >Affects Versions: JCR Jackrabbit Client 2.0.2 >Reporter: Tobias Bocanegra >Assignee: Felix Meschberger > > the JCR repository client session pool should initially be disabled. change > the default value of max idle pool sessions to 0. > the overhead of acquiring and releasing sessions is bigger than the > performance gain from keeping the cached sessions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-706) Change default value of max idle pool sessions to 0
[ https://issues.apache.org/jira/browse/SLING-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-706: Affects Version/s: (was: JCR Jackrabbit Client 2.0.2) JCR Base 2.0.2 > Change default value of max idle pool sessions to 0 > --- > > Key: SLING-706 > URL: https://issues.apache.org/jira/browse/SLING-706 > Project: Sling > Issue Type: Wish > Components: JCR >Affects Versions: JCR Base 2.0.2 >Reporter: Tobias Bocanegra >Assignee: Felix Meschberger > Fix For: JCR Base 2.0.4 > > > the JCR repository client session pool should initially be disabled. change > the default value of max idle pool sessions to 0. > the overhead of acquiring and releasing sessions is bigger than the > performance gain from keeping the cached sessions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-706) Change default value of max idle pool sessions to 0
[ https://issues.apache.org/jira/browse/SLING-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-706. - Resolution: Fixed Fix Version/s: JCR Base 2.0.4 Set the default session pool size to zero, thus disabling session pooling, in Rev. 706287. Thanks for reporting this issue. If this fix is ok for you, please close this issue. Thanks. > Change default value of max idle pool sessions to 0 > --- > > Key: SLING-706 > URL: https://issues.apache.org/jira/browse/SLING-706 > Project: Sling > Issue Type: Wish > Components: JCR >Affects Versions: JCR Base 2.0.2 >Reporter: Tobias Bocanegra >Assignee: Felix Meschberger > Fix For: JCR Base 2.0.4 > > > the JCR repository client session pool should initially be disabled. change > the default value of max idle pool sessions to 0. > the overhead of acquiring and releasing sessions is bigger than the > performance gain from keeping the cached sessions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-700) Send notification event when a job is cancelled
[ https://issues.apache.org/jira/browse/SLING-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-700: --- Fix Version/s: (was: Extensions Event 2.0.4) > Send notification event when a job is cancelled > --- > > Key: SLING-700 > URL: https://issues.apache.org/jira/browse/SLING-700 > Project: Sling > Issue Type: New Feature > Components: Event >Affects Versions: Extensions Event 2.0.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > > If a job is cancelled currently no notification is sent. > A new "job cancelled event" should be sent if the job is cancelled through > the ui or removed from the repository directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-701) HtmlResponse should replace all place holders
[ https://issues.apache.org/jira/browse/SLING-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-701. -- Resolution: Fixed The placeholder is now always removed. If the corresponding property value is not available it is replaced with an empty string Fixed in Revision 706296 > HtmlResponse should replace all place holders > - > > Key: SLING-701 > URL: https://issues.apache.org/jira/browse/SLING-701 > Project: Sling > Issue Type: Bug > Components: API >Affects Versions: API 2.0.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: API 2.0.4 > > > Currently the HtlmResponse leaves the placeholders in the response if there > is no value for a placeholder. Instead it should remove the placeholder as > otherwise the client has to take extra care to detect if a value is really > missing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-705) Set current thread name while handling requests
Set current thread name while handling requests --- Key: SLING-705 URL: https://issues.apache.org/jira/browse/SLING-705 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Priority: Trivial Fix For: Engine 2.0.4 To help in problem determination, it would be usefull to have the SlingMainServlet set the current thread's name to some request information while servicing the request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
