[
https://issues.apache.org/jira/browse/FELIX-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542903#comment-13542903
]
Jérémy Cazaux commented on FELIX-3837:
--------------------------------------
Yes, as you have added the possibility to modify the component definition
before the component(=factory) creation at runtime, this feature is great and
will be really useful for a lots of peoples.
However, just from my personal point of view, I always prefer to make a feature
at compile time rather than at runtime (it's always cheaper) if the feature is
really similar (like this one). I think it could be a good thing to add the
possibility to modify elments metadata either at compile time or at runtime.
After what, it'll be to the user to determine if he prefers to modify elements
metadata at compile time or at runtime.
> 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
