Ioannis, How about we add a project description in the POM and use resource filtering to inject that into the component source itself and into the blueprint descriptor? While we're at it, we can also add it to OSGi metadata as a Bundle-Description header so it shows up in the Felix Webconsole.
BTW, the reason we're not using Blueprint yet for CXF is because the Spring file for that component is importing other Spring files that are being maintained by the CXF project. We'd either need to find a way to import the same file into a Blueprint file or else provide Blueprint files to replace the CXF Spring files. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Thu, Jan 13, 2011 at 6:27 PM, Ioannis Canellos <[email protected]> wrote: > I was checking issue *SMX4-726<https://issues.apache.org/jira/browse/SMX4-726> > * > *It seems that the jbi:list command properly lists the description of the > component. However, the components do not set it. * > The solution would be to update the blueprint descriptor for all the > components. I was wondering if we could somehow make use of the @description > xbean annotation which is set already on the components, to avoid > duplicating the description. > > -- > *Ioannis Canellos* > http://iocanel.blogspot.com > Integration Engineer @ Upstream S.A. <http://www.upstreamsystems.com> >
