List Info

Thread: What about upgrading to Felix?




What about upgrading to Felix?
user name
2006-11-16 11:44:26
Hi developers,

we are now using Oscar 2.0 (build from cvs sometimes ago, in
july 2005) 
as our OSGI implementation, which is lacking an important
feature for 
us. It is impossible right now to install bundles by
reference, which 
means that the content of every bundle is copied to the
bundle cache for 
every user. This is problematic in a multi-user environment.

The Felix implementation of OSGI (formerly oscar 2.0) allows
reference 
URL for bundles. Maybe this is time to upgrade to felix?

Until we switch, the SIP Communicator will duplicate
unnecessarily its 
bundles in a multi-user environment.

Martin

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-16 17:10:19
Hello Martin,

I just upgraded my own sandbox to felix and this didn't
really change 
anything. My cache directory (sip-communicator.bin) gets
created just as 
before. I didn't change anything special for my tests apart
from 
modifying oscar.client.run.properties and renaiming all
properties that 
had "oscar" in their name to felix.
This means that bundles are now loaded through lines that
look like 
this: felix.auto.start=file:lib/bundle.name.jar....
Is there another property that I need to use for the bundles
to be used 
by reference and not get installed in the cache?

damencho

Martin André wrote:
> Hi developers,
>
> we are now using Oscar 2.0 (build from cvs sometimes
ago, in july 
> 2005) as our OSGI implementation, which is lacking an
important 
> feature for us. It is impossible right now to install
bundles by 
> reference, which means that the content of every bundle
is copied to 
> the bundle cache for every user. This is problematic in
a multi-user 
> environment.
>
> The Felix implementation of OSGI (formerly oscar 2.0)
allows reference 
> URL for bundles. Maybe this is time to upgrade to
felix?
>
> Until we switch, the SIP Communicator will duplicate
unnecessarily its 
> bundles in a multi-user environment.
>
> Martin
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-16 23:42:24
Hi Damian,

You should install the bundles with something like this:
felix.auto.start=reference:file:lib/bundle.name.jar

Check out this thread on Felix dev mailing list for more
information:
http://www.mail
-archive.com/felix-devincubator.apache.org/msg00615.html

Cheers,
Martin

Damian Minkov wrote:
> Hello Martin,
> 
> I just upgraded my own sandbox to felix and this didn't
really change 
> anything. My cache directory (sip-communicator.bin)
gets created just as 
> before. I didn't change anything special for my tests
apart from 
> modifying oscar.client.run.properties and renaiming all
properties that 
> had "oscar" in their name to felix.
> This means that bundles are now loaded through lines
that look like 
> this: felix.auto.start=file:lib/bundle.name.jar....
> Is there another property that I need to use for the
bundles to be used 
> by reference and not get installed in the cache?
> 
> damencho
> 
> Martin André wrote:
>> Hi developers,
>>
>> we are now using Oscar 2.0 (build from cvs
sometimes ago, in july 
>> 2005) as our OSGI implementation, which is lacking
an important 
>> feature for us. It is impossible right now to
install bundles by 
>> reference, which means that the content of every
bundle is copied to 
>> the bundle cache for every user. This is
problematic in a multi-user 
>> environment.
>>
>> The Felix implementation of OSGI (formerly oscar
2.0) allows reference 
>> URL for bundles. Maybe this is time to upgrade to
felix?
>>
>> Until we switch, the SIP Communicator will
duplicate unnecessarily its 
>> bundles in a multi-user environment.
>>
>> Martin
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-17 07:20:37
Hello Martin,

Yes thats it ) now its
just create the cache dir and its sub dirs but 
without caching the bundles just caching the embeded libs. I
have still 
work to do before merging to the felix. I will test it and
move to it as 
soon as possible.

damencho

Martin André wrote:
> Hi Damian,
>
> You should install the bundles with something like
this:
> felix.auto.start=reference:file:lib/bundle.name.jar
>
> Check out this thread on Felix dev mailing list for
more information:
> http://www.mail
-archive.com/felix-devincubator.apache.org/msg00615.html
>
> Cheers,
> Martin
>
> Damian Minkov wrote:
>> Hello Martin,
>>
>> I just upgraded my own sandbox to felix and this
didn't really change 
>> anything. My cache directory (sip-communicator.bin)
gets created just 
>> as before. I didn't change anything special for my
tests apart from 
>> modifying oscar.client.run.properties and renaiming
all properties 
>> that had "oscar" in their name to felix.
>> This means that bundles are now loaded through
lines that look like 
>> this: felix.auto.start=file:lib/bundle.name.jar....
>> Is there another property that I need to use for
the bundles to be 
>> used by reference and not get installed in the
cache?
>>
>> damencho
>>
>> Martin André wrote:
>>> Hi developers,
>>>
>>> we are now using Oscar 2.0 (build from cvs
sometimes ago, in july 
>>> 2005) as our OSGI implementation, which is
lacking an important 
>>> feature for us. It is impossible right now to
install bundles by 
>>> reference, which means that the content of
every bundle is copied to 
>>> the bundle cache for every user. This is
problematic in a multi-user 
>>> environment.
>>>
>>> The Felix implementation of OSGI (formerly
oscar 2.0) allows 
>>> reference URL for bundles. Maybe this is time
to upgrade to felix?
>>>
>>> Until we switch, the SIP Communicator will
duplicate unnecessarily 
>>> its bundles in a multi-user environment.
>>>
>>> Martin
>>>
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>>
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-17 08:01:59
Hi,

I have a problem launching ConfigurationService. Here is the
exception

     [java] 09:52:22.196 FINEST: 
impl.configuration.ConfigurationServiceImpl.start() [exit]
start
     [java] java.lang.NoClassDefFoundError:
org/kxml/parser/XmlParser

But the kxml package is not used and not imported in 
ConfigurationService. Maybe its used from Felix. Any ideas ?

damencho

Martin André wrote:
> Hi Damian,
>
> You should install the bundles with something like
this:
> felix.auto.start=reference:file:lib/bundle.name.jar
>
> Check out this thread on Felix dev mailing list for
more information:
> http://www.mail
-archive.com/felix-devincubator.apache.org/msg00615.html
>
> Cheers,
> Martin
>
> Damian Minkov wrote:
>> Hello Martin,
>>
>> I just upgraded my own sandbox to felix and this
didn't really change 
>> anything. My cache directory (sip-communicator.bin)
gets created just 
>> as before. I didn't change anything special for my
tests apart from 
>> modifying oscar.client.run.properties and renaiming
all properties 
>> that had "oscar" in their name to felix.
>> This means that bundles are now loaded through
lines that look like 
>> this: felix.auto.start=file:lib/bundle.name.jar....
>> Is there another property that I need to use for
the bundles to be 
>> used by reference and not get installed in the
cache?
>>
>> damencho
>>
>> Martin André wrote:
>>> Hi developers,
>>>
>>> we are now using Oscar 2.0 (build from cvs
sometimes ago, in july 
>>> 2005) as our OSGI implementation, which is
lacking an important 
>>> feature for us. It is impossible right now to
install bundles by 
>>> reference, which means that the content of
every bundle is copied to 
>>> the bundle cache for every user. This is
problematic in a multi-user 
>>> environment.
>>>
>>> The Felix implementation of OSGI (formerly
oscar 2.0) allows 
>>> reference URL for bundles. Maybe this is time
to upgrade to felix?
>>>
>>> Until we switch, the SIP Communicator will
duplicate unnecessarily 
>>> its bundles in a multi-user environment.
>>>
>>> Martin
>>>
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>>
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-20 15:58:47
Hello,

I fixed the previous problems and the SC starts OK with
felix. Now I'm 
tring to pass the tests but there is a problem when
unregistering a service
and when an event for that is received here is an example
exception :

     [java] ERROR: EventDispatcher: Error during dispatch. 
(java.lang.IllegalStateException: Invalid BundleContext.)
     [java] java.lang.IllegalStateException: Invalid
BundleContext.
     [java]     at 
org.apache.felix.framework.BundleContextImpl.checkValidity(B
undleContextImpl.java:552)
     [java]     at 
org.apache.felix.framework.BundleContextImpl.getService(Bund
leContextImpl.java:475)
     [java]     at 
net.java.sip.communicator.impl.contactlist.MetaContactListSe
rviceImpl.serviceChanged(MetaContactListServiceImpl.java:166
2)
     [java]     at 
org.apache.felix.framework.util.EventDispatcher.invokeServic
eListenerCallback(EventDispatcher.java:712)
     [java]     at 
org.apache.felix.framework.util.EventDispatcher.fireEventImm
ediately(EventDispatcher.java:570)
     [java]     at 
org.apache.felix.framework.util.EventDispatcher.fireServiceE
vent(EventDispatcher.java:502)
     [java]     at 
org.apache.felix.framework.Felix.fireServiceEvent(Felix.java
:2843)
     [java]     at 
org.apache.felix.framework.Felix.access$100(Felix.java:36)
     [java]     at 
org.apache.felix.framework.Felix$1.serviceChanged(Felix.java
:242)
     [java]     at 
org.apache.felix.framework.ServiceRegistry.fireServiceChange
d(ServiceRegistry.java:435)
     [java]     at 
org.apache.felix.framework.ServiceRegistry.unregisterService
(ServiceRegistry.java:86)
     [java]     at 
org.apache.felix.framework.ServiceRegistrationImpl.unregiste
r(ServiceRegistrationImpl.java:99)
     [java]     at 
org.apache.felix.framework.ServiceRegistry.unregisterService
s(ServiceRegistry.java:119)
     [java]     at 
org.apache.felix.framework.Felix._stopBundle(Felix.java:1601
)
     [java]     at 
org.apache.felix.framework.Felix.stopBundle(Felix.java:1524)
     [java]     at 
org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:3
76)
     [java]     at 
net.java.sip.communicator.slick.contactlist.TestMetaContactL
istPersistence.testReloadMetaContactListBundle(TestMetaConta
ctListPersistence.java:123)


I cannot figure out from where is coming this invalid
context.
Any ideas are welcome )

damencho






Martin André wrote:
> Hi Damian,
>
> You should install the bundles with something like
this:
> felix.auto.start=reference:file:lib/bundle.name.jar
>
> Check out this thread on Felix dev mailing list for
more information:
> http://www.mail
-archive.com/felix-devincubator.apache.org/msg00615.html
>
> Cheers,
> Martin
>
> Damian Minkov wrote:
>> Hello Martin,
>>
>> I just upgraded my own sandbox to felix and this
didn't really change 
>> anything. My cache directory (sip-communicator.bin)
gets created just 
>> as before. I didn't change anything special for my
tests apart from 
>> modifying oscar.client.run.properties and renaiming
all properties 
>> that had "oscar" in their name to felix.
>> This means that bundles are now loaded through
lines that look like 
>> this: felix.auto.start=file:lib/bundle.name.jar....
>> Is there another property that I need to use for
the bundles to be 
>> used by reference and not get installed in the
cache?
>>
>> damencho
>>
>> Martin André wrote:
>>> Hi developers,
>>>
>>> we are now using Oscar 2.0 (build from cvs
sometimes ago, in july 
>>> 2005) as our OSGI implementation, which is
lacking an important 
>>> feature for us. It is impossible right now to
install bundles by 
>>> reference, which means that the content of
every bundle is copied to 
>>> the bundle cache for every user. This is
problematic in a multi-user 
>>> environment.
>>>
>>> The Felix implementation of OSGI (formerly
oscar 2.0) allows 
>>> reference URL for bundles. Maybe this is time
to upgrade to felix?
>>>
>>> Until we switch, the SIP Communicator will
duplicate unnecessarily 
>>> its bundles in a multi-user environment.
>>>
>>> Martin
>>>
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>>
>>>
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-22 13:45:48
Hi Devs,

I've just committed and now SIP Communicator is using the
latest felix 
release.
The only thing left is to fix the debian package and the
macosx one if 
needed as the libs, property file names, and main class
has changed. The other installations I have moved to the
changes.

Any questions about the changes are welcome 

damencho

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-22 14:05:33
Damian Minkov wrote:
> Hi Devs,
> 
> I've just committed and now SIP Communicator is using
the latest felix 
> release.
> The only thing left is to fix the debian package and
the macosx one if 
> needed as the libs, property file names, and main class
> has changed. The other installations I have moved to
the changes.
> 
> Any questions about the changes are welcome 
> 

I noticed there have been some classpath changes. Has anyone
updated the 
eclipse .classpath file in /ide/ yet?

I will make the corresponding changes to the netbeans
project.xml once 
you believe the classpath has stabilised.

Regards,

Brian

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-22 14:09:10
Brian Burch wrote:
> I noticed there have been some classpath changes. Has
anyone updated 
> the eclipse .classpath file in /ide/ yet?
>
> I will make the corresponding changes to the netbeans
project.xml once 
> you believe the classpath has stabilised.
No I haven't changed the files in the ide dir.

damencho

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

What about upgrading to Felix?
user name
2006-11-26 03:55:21
Hi Damian,

The macosx package survived to the transition 
But here is a small patch to apply to build.xml that
slightly reduces 
the macosx package size (I remove the slicks and useless jar
from the 
package).

Thanks,

Romain

Damian Minkov wrote:
> Hi Devs,
> 
> I've just committed and now SIP Communicator is using
the latest felix 
> release.
> The only thing left is to fix the debian package and
the macosx one if 
> needed as the libs, property file names, and main class
> has changed. The other installations I have moved to
the changes.
> 
> Any questions about the changes are welcome 
> 
> damencho
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 

-- 
Romain KUNTZ
kuntzsfc.wide.ad.jp
--- sip-communicator-20061126/build.xml	2006-11-26
11:52:48.000000000 +0900
+++ sip-communicator-20061126-dmg-fixed/build.xml	2006-11-26
12:51:29.000000000 +0900
 -310,9
+310,12 
 
         <jarfileset dir=".">
           <include name="$/*.jar" />
+          <exclude name="$/junit.jar"
/>
           <include name="$/bundle/*.jar"
/>
+          <exclude
name="$/bundle/junit.jar" />
           <include name="${jmf.home}/*.jar"
/>
           <include
name="${bundles.dest}/*.jar" />
+          <exclude
name="${bundles.dest}/*-slick.jar" />
         </jarfileset>
         <javafilelist dir="$"
                       files="logging.properties,
felix.client.run.properties"/>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
[1-10]

about | contact  Other archives ( Real Estate discussion Medical topics )