Hi Rowan,
I have a followup question if I may.
In trying to resolve this myself I had a look at the 'perthis',
'pertarget', and even 'pertypewithin' qualifiers for the aspect
definintion. Are these supported in equinox aspects? I do not see any
difference when I try to use them. If I want a
Stuart said:
>another possibility would be to import and export the 'widgets'
>package from both widget bundles, then they would both see
>the same class regardless of the order they were installed.
>
>eg:
>
> Export-Package: widgets
> Import-Package: org.osgi.framework, widgets
>
>see:
>http://www
Hi Stuard,
another possibility would be to import and export the 'widgets'
package from both widget bundles, then they would both see
the same class regardless of the order they were installed.
eg:
Export-Package: widgets
Import-Package: org.osgi.framework, widgets
see:
http://www.osgi.or
2008/6/29 Martin Lippert <[EMAIL PROTECTED]>:
> Hi Stuart,
>
> another possibility would be to import and export the 'widgets'
>> package from both widget bundles, then they would both see
>> the same class regardless of the order they were installed.
>>
>> eg:
>>
>> Export-Package: widgets
>>
Hi Stuart,
another possibility would be to import and export the 'widgets'
package from both widget bundles, then they would both see
the same class regardless of the order they were installed.
eg:
Export-Package: widgets
Import-Package: org.osgi.framework, widgets
see:
http://www.osgi.or
2008/6/29 Martin Lippert <[EMAIL PROTECTED]>:
> Hi Rowan,
>
> I looked at your example and I think I have found the problem. Your aspect
> bundle imports the package "widgets" and can therefore refer to your class
> Widget. But since both widget bundles export the same package including the
> same
Hi Rowan,
I looked at your example and I think I have found the problem. Your
aspect bundle imports the package "widgets" and can therefore refer to
your class Widget. But since both widget bundles export the same package
including the same class (Widget), the aspect definition is wired to
on
Martin wrote:
>Hi Rowan,
>
>I assume the problem is that the aspect should weave the same class from
>>different bundles. For the aspect both Widget classes are visible (because
>both >should be woven) and the weaver does not know which one to use for type
>>resolution. But this is just a first
Hi Rowan,
I assume the problem is that the aspect should weave the same class from
different bundles. For the aspect both Widget classes are visible
(because both should be woven) and the weaver does not know which one to
use for type resolution. But this is just a first guess on the
problem.
I suspect I can't do what I want to, but here goes anyway
I have two 'applications' as bundles in equinox. Each use the same
code, they only differ in configuration and Bundle-SymbolicName. By
same code I mean they have identical copies, not shared code/services
or anything. Like this:
Bundle
10 matches
Mail list logo
