You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Sauthier (JIRA)" <ji...@apache.org> on 2013/01/03 11:34:12 UTC

[jira] [Commented] (FELIX-3837) PojoizationPlugin should be more extensible

    [ https://issues.apache.org/jira/browse/FELIX-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542841#comment-13542841 ] 

Guillaume Sauthier commented on FELIX-3837:
-------------------------------------------

I had something similar in mind, but at runtime.
Something that looks like the auto-handlers behavior, but based on service.
You could modify the component definition before a Factory is created from it.

Could that feature be useful for you ?
                
> PojoizationPlugin should be more extensible
> -------------------------------------------
>
>                 Key: FELIX-3837
>                 URL: https://issues.apache.org/jira/browse/FELIX-3837
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>            Reporter: Jérémy Cazaux
>         Attachments: 0001-PojoizationPlugin-should-be-more-extensible.patch
>
>
> I would like to extend Pojoization plugin without duplication of code in order to manipulate metadata elements from the CacheableMetadataProvider object just before the pojoization operation (for example to automate the definition of my own handlers in the manifest).
> So all fields and methods should be protected instead of private and a new mechanism should be add in order to allow to manipulate cacheable metadata easily.
> I have attached a patch to fix this issue if the extensibility of the plugin is acceptable.

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