felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Sauthier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3837) PojoizationPlugin should be more extensible
Date Thu, 03 Jan 2013 13:40:12 GMT

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

Guillaume Sauthier commented on FELIX-3837:

I understand your POV, I was just wondering how much we want to have 2 ways to do the same
thing ?

BTW, the compile time way is still harder to use (you'll have to both extends the PojoizationPlugin
and write your MetadataManipulator). I'm not sure how we could do something easier for the
For the runtime way, you just have to write a transformer (equivalent to your MetadataManipulator).
> 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

View raw message