[
https://issues.apache.org/jira/browse/CLEREZZA-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016349#comment-13016349
]
Reto Bachmann-Gmür commented on CLEREZZA-460:
---------------------------------------------
Hi Daniel,
The situation I was thinking at is:
Bundle A registered an SSP x with RenderletManager.
Bundle B wants to override the Renderlet created for SSP x by implementing a
typerenderlet.
If A is restared the service provided by B will disappear and only the
typerenderlet provided by RenderletManagerImpl will be available, ven though
the other typerenderlet would have a higher priority.
Problems also occur when one registers a service via
ScalaServePagesService.registerScalaServerPage and duly unregisters it in the
deactivate method.
> Use whiteboard pattern for Renderlets
> -------------------------------------
>
> Key: CLEREZZA-460
> URL: https://issues.apache.org/jira/browse/CLEREZZA-460
> Project: Clerezza
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
> Assignee: Reto Bachmann-Gmür
> Attachments: patch-typerendering-core.diff, renderletmgr_patch.diff
>
>
> The current mechanism for renderlets is overly complex. Instead of describing
> renderlets in a graph rendelets should be services that have properties
> indicating the rdf type and the mode-pattern they handle.
> The priority for selecting renderlets should be:
> - type, according to type-priority list
> - length of regex math (the matching regex with the most alphanumeric
> characters wins)
> - startlevel of the bundle providing the service
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
