I have tried to fix this bug, please try it out ...
Kind regards,
Peter Kriens
On 3 nov 2008, at 05:48, Sriharsha wrote:
Hi..,
I am developing a swing application framework on Felix
implementation of
OSGi. I am using Felix OBR and bindex tool for my repository
automation.
PROB
2008/11/3 Sriharsha <[EMAIL PROTECTED]>
>
> In continuation with the first thread,
>
> I tried with the following options with bindex.
>
> Instead of specifying Require-Bundle in Bundle1's manifest, I specified
> package level dependency for Bundle1 as follows.
>
> Manifest-Version: 1.0
> Bundle-N
2008/11/3 Sriharsha <[EMAIL PROTECTED]>
>
> Hi..,
>
> I am developing a swing application framework on Felix implementation of
> OSGi. I am using Felix OBR and bindex tool for my repository automation.
>
> PROBLEM:
> The bindex tool is unable to retain the require-bundle/bundle-version info
> in
In continuation with the first thread,
I tried with the following options with bindex.
Instead of specifying Require-Bundle in Bundle1's manifest, I specified
package level dependency for Bundle1 as follows.
Manifest-Version: 1.0
Bundle-Name: Bundle1
Bundle-Activator: com.consumer.ConsumerActi
Hi Richard.
Thanks for your suggestion. I made the upgrade and understandably, it
wasn't without some fun; some constructors and methods had changed their
signatures, etc. I have got the application up and running with the new
version and haven't run into my old issue yet so hopefully that has
Hi..,
I am developing a swing application framework on Felix implementation of
OSGi. I am using Felix OBR and bindex tool for my repository automation.
PROBLEM:
The bindex tool is unable to retain the require-bundle/bundle-version info
in the repository.xml. Hence the bundle repository xml is n
On Sun, Nov 2, 2008 at 7:05 PM, Clement Escoffier
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> This message just informs
Maybe it should be an INFO then rather then a WARNING :-)
regards,
Karl
> that the instance was detected and set as
> 'immediate'. An immediate instance creates a POJO object as soo
Hi,
This message just informs that the instance was detected and set as
'immediate'. An immediate instance creates a POJO object as soon as the
instance becomes valid, i.e. call the POJO's constructor.
iPOJO set an instance to immediate, when the immediate attribute is not set,
and if the instan
Hello,
As I was playing with the Hello example the following warning kept popping up
until I declared the
as immediate.
[HelloClient] WARNING: The component HelloClient becomes immediate
HelloClient is the component running a thread that calls Hello.sayHello().
Curiously when I declared
immedia
2008/11/1 Todor Boev <[EMAIL PROTECTED]>
> clement escoffier wrote:
>
> > That is not directly possible. However, you can do this as following:
> > public class ConsumerImpl {
> > // Temporal dependency on FooService
> > FooService fs;
> >
> > // An helper object
> > ConsumerHelper
Hello,
2008/11/1 Todor Boev <[EMAIL PROTECTED]>
> Hello,
> I plan to use iPojo on an OSGi framework different from Felix. So:
>
> 1) Will the iPojo bundles work on a generic OSGi 4.2 + service compendium
> environment?
Yes. iPOJO is tested on Equinox, KF2 and Felix (and their technical services
11 matches
Mail list logo
