Hi Ryan, In concrete terms, what am I supposed to do ?
JP [@@ THALES GROUP INTERNAL @@] De : Ryan Moquin [mailto:[email protected]] Envoyé : mardi 7 janvier 2014 16:49 À : [email protected] Objet : Re: Non standard Blueprint properties I THINK this might work, at least it does with certain DI frameworks by nature of how they need to work. When a property is looked up, it isn't visible because it's private. As a result, I don't think the property is actually looked up, I think the setter for whatever "setterified or getterfied" name of the propery specified in the config is actually looked up. So basically, you can reference a non existing property, as long as it translates into a setter or getter that exists, irregardless of whether the property exists. Also, sometimes you can annotate a setter or getter and change the name of thw property associated with it. If the Aries guys didn't respond with that, maybe it's not an option. I'd give my first suggestion a try.. it's not pretty, but it may work. The setter and getter lookup is based on a standard conversion of the property name anyhow. Hope that helps and works. Ryan On Jan 7, 2014 6:10 AM, "CLEMENT Jean-Philippe" <[email protected]<mailto:[email protected]>> wrote: Dear Karaf experts, I asked the following question to the Aries team, but maybe there is a solution outside Aries. As far as I know Blueprint properties injection work as long as the implementation method name is in the "setXXX" format, where "XXX" is the property name. Unfortunately a lot of classes, including brand new JavaFX ones does not follow this convention. Is there a way to handle non-standard method names with the properties? PS: Happy new year! Best regards, Jean-Philippe
