You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/06/05 11:24:21 UTC

[jira] [Resolved] (SLING-2904) Simplify handling of multiple references (post processors, node name generators, post operations)

     [ https://issues.apache.org/jira/browse/SLING-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2904.
-------------------------------------

    Resolution: Fixed

Rewrote the hole reference handling in revision 1489764 - this includes also the PostResponseCreator services.

In addition to directly deal with the service instances and update the caches directly, I did some additional performance updates like replacing StringBuffer with StringBuilder and handling setup of internal helper classes.
                
> Simplify handling of multiple references (post processors, node name generators, post operations)
> -------------------------------------------------------------------------------------------------
>
>                 Key: SLING-2904
>                 URL: https://issues.apache.org/jira/browse/SLING-2904
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Post 2.3.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Servlets Post 2.3.2
>
>
> The current handling of the multiple references to post processors, node name generators and post operations is based on old DS specifications and requires a lot of additional syncing and handling.
> With newer DS versions we can get the service and it's properties during the bind/unbind methods without any additional method calls - this simplifies the handling of such references as we don't have to wait in bind until the component is activated and all the delayed handling can be removed

--
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