You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by Raymond Auge <ra...@liferay.com> on 2016/08/12 18:15:20 UTC
[spi-fly] using pure wiring API
Hey guys,
It would appear that spi-fly is not purely using the osgi wiring's view of
requirements and capabilities as opt-in.
i.e. <hand-waving>if I augment at runtime</hand-waving> the bundles I want
to enhance with spi-fly with the proper capabilities it doesn't work.
However, if I attach a fragment to the bundle which adds the requirements
it works.
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
Re: [spi-fly] using pure wiring API
Posted by Raymond Auge <ra...@liferay.com>.
Well, I wouldn't call it a bug so much as an implementation that could be
improved.
As for a test case, it would have to be contrived and wouldn't be something
you could technically put into the main test suite.
but I'll try to make a change to see if I can improve it.
- Ray
On Mon, Aug 15, 2016 at 3:42 AM, David Bosschaert <
david.bosschaert@gmail.com> wrote:
> Hi Ray,
>
> This sounds like a bug to me... Could you please file a JIRA with a small
> test case?
>
> Cheers,
>
> David
>
> On 12 August 2016 at 19:15, Raymond Auge <ra...@liferay.com> wrote:
>
>> Hey guys,
>>
>> It would appear that spi-fly is not purely using the osgi wiring's view
>> of requirements and capabilities as opt-in.
>>
>> i.e. <hand-waving>if I augment at runtime</hand-waving> the bundles I
>> want to enhance with spi-fly with the proper capabilities it doesn't work.
>>
>> However, if I attach a fragment to the bundle which adds the requirements
>> it works.
>>
>> --
>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>> (@rotty3000)
>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>> (@Liferay)
>> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
>> (@OSGiAlliance)
>>
>
>
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
Re: [spi-fly] using pure wiring API
Posted by David Bosschaert <da...@gmail.com>.
Hi Ray,
This sounds like a bug to me... Could you please file a JIRA with a small
test case?
Cheers,
David
On 12 August 2016 at 19:15, Raymond Auge <ra...@liferay.com> wrote:
> Hey guys,
>
> It would appear that spi-fly is not purely using the osgi wiring's view of
> requirements and capabilities as opt-in.
>
> i.e. <hand-waving>if I augment at runtime</hand-waving> the bundles I want
> to enhance with spi-fly with the proper capabilities it doesn't work.
>
> However, if I attach a fragment to the bundle which adds the requirements
> it works.
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
> (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
> (@OSGiAlliance)
>