Hi Daniel I thought its good to discuss the issue you rise re. double registration before closing the issue.
With the current ScalaServerPagesService the service needs to be unregistered by the registering component, do you think this should be different? To allow registering the ssp with the bundleContext of the registering component we could add a method which return the TypeRenderlet leaving it to the caller to register it. Alternatively an oveloaded registerScalaServerPage could take a BundleContext. What do you think? Cheers, Reto 2011/5/2 Reto Bachmann-Gmür (JIRA) <[email protected]> > > [ > https://issues.apache.org/jira/browse/CLEREZZA-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Reto Bachmann-Gmür reopened CLEREZZA-460: > ----------------------------------------- > > > forgot about ScalaServerPagesService unregistering. > > > 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 >
