[sip-comm] Removing some useless modules?


#1

Hi guys,

I'm developing a prototype of a communication system using SIP and
I chose a SIP commicator as a client. It was working great on my laptop.

Now that I want to port it on a handheld machine. I'm using a device
emulator in Windows Mobile 6 Professional SDK by Microsoft and properly
installed JVM (I used Mysaifu JVM). And then I downloaded the generic
installation file for All OSs and ran it. Everything was working fine until
I got
the message that the storage memory is critically low. (Aditionally, the
runtime speed is very low.)

So here is my question:
I want to make SIP communicator as light as possible. The only
functionalities
I need are ability to connect to SIP server, presence, and instant
messaging.
I think I should modify build.xml somehow to throw away some modules that
I don't need... but I'm stuck in here.

Can someone have a lesson on me how to remove it or provide me some ideas?
Thank you for reading!

Best wishes,
James H. LEE


#2

It would be great if the S-C installer had a checklist right at the
beginning of each optional package and the core, for de/selection.
Perfect would be if the installer could generate not just an
installation, but also a custom installer with just those selected
features.

···

On Fri, 2008-05-30 at 15:50 -0400, James H Lee wrote:

Hi guys,

I'm developing a prototype of a communication system using SIP and
I chose a SIP commicator as a client. It was working great on my
laptop.

Now that I want to port it on a handheld machine. I'm using a device
emulator in Windows Mobile 6 Professional SDK by Microsoft and
properly
installed JVM (I used Mysaifu JVM). And then I downloaded the generic
installation file for All OSs and ran it. Everything was working fine
until I got
the message that the storage memory is critically low. (Aditionally,
the
runtime speed is very low.)

So here is my question:
I want to make SIP communicator as light as possible. The only
functionalities
I need are ability to connect to SIP server, presence, and instant
messaging.
I think I should modify build.xml somehow to throw away some modules
that
I don't need... but I'm stuck in here.

Can someone have a lesson on me how to remove it or provide me some
ideas?
Thank you for reading!

Best wishes,
James H. LEE

--

(C) Matthew Rubenstein

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi James,

you could modify the build.xml, but could also do it the following way:

To "remove" the bundles you don't need, remove all the entries for
bundles in the file "felix.client.run.properties" (if you have SC
installed, this will be in <yourInstallDir>/lib>/).
So for example there is a section:

felix.auto.start.40= \
reference:file:sc-bundles/configuration.jar \
reference:file:sc-bundles/version.jar \
reference:file:sc-bundles/version-impl.jar \
reference:file:sc-bundles/splashscreen.jar \

To remove the "Spashscreen", just delete the last line (this will
prevent felix from starting this bundle)

Additionally, you can then delete those bundles from the "sc-bundles"
directory.

Bundles that you could definitely remove are all the protocol-specific
ones (don't remove protocol.jar), the wizards that accord to those and
all the *slick* bundles (those are not mentioned in the properties file,
but are in the sc-bundles dir - just for testing purpose):
protocol-<protocolYouWantToRemove>.jar
<protocolYouWantToRemove>accregwizz.jar

Hope that helps
Sebastian

James H Lee schrieb:

···

Hi guys,

I'm developing a prototype of a communication system using SIP and
I chose a SIP commicator as a client. It was working great on my laptop.

Now that I want to port it on a handheld machine. I'm using a device
emulator in Windows Mobile 6 Professional SDK by Microsoft and properly
installed JVM (I used Mysaifu JVM). And then I downloaded the generic
installation file for All OSs and ran it. Everything was working fine until
I got
the message that the storage memory is critically low. (Aditionally, the
runtime speed is very low.)

So here is my question:
I want to make SIP communicator as light as possible. The only
functionalities
I need are ability to connect to SIP server, presence, and instant
messaging.
I think I should modify build.xml somehow to throw away some modules that
I don't need... but I'm stuck in here.

Can someone have a lesson on me how to remove it or provide me some ideas?
Thank you for reading!

Best wishes,
James H. LEE

--
/**
* Sebastian Heib
* Software Developer
*
* Synyx GmbH & Co. KG
* Business in Components
* Karlstr. 68
* 76137 Karlsruhe
*
* phone +49(0)721 66 24 866
* fax +49(0)721 66 48 877
* eMail heib@synyx.de
* www http://www.synyx.de
* irc irc.synyx.de
*
* Sitz der Gesellschaft: Karlsruhe
* Registergericht: Mannheim
* Handelsregisternummer: HRA 4793
* USt-IdNr.: DE249264296
*
* Komplement�rin: Elatech Verwaltungs GmbH
* Sitz der Gesellschaft: Karlsruhe
* Gesch�ftsf�hrer: Markus Daniel
* Registergericht: Mannheim
* Handelsregisternummer: HRB 7250
*/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#4

       It would be great if the S-C installer had a checklist right at the
beginning of each optional package and the core, for de/selection.
Perfect would be if the installer could generate not just an
installation, but also a custom installer with just those selected
features.

Great idea! It can be a gsoc project of next year. :slight_smile:

···

2008/5/31 Matthew Rubenstein <email@mattruby.com>:

On Fri, 2008-05-30 at 15:50 -0400, James H Lee wrote:
> Hi guys,
>
> I'm developing a prototype of a communication system using SIP and
> I chose a SIP commicator as a client. It was working great on my
> laptop.
>
> Now that I want to port it on a handheld machine. I'm using a device
> emulator in Windows Mobile 6 Professional SDK by Microsoft and
> properly
> installed JVM (I used Mysaifu JVM). And then I downloaded the generic
> installation file for All OSs and ran it. Everything was working fine
> until I got
> the message that the storage memory is critically low. (Aditionally,
> the
> runtime speed is very low.)
>
> So here is my question:
> I want to make SIP communicator as light as possible. The only
> functionalities
> I need are ability to connect to SIP server, presence, and instant
> messaging.
> I think I should modify build.xml somehow to throw away some modules
> that
> I don't need... but I'm stuck in here.
>
> Can someone have a lesson on me how to remove it or provide me some
> ideas?
> Thank you for reading!
>
> Best wishes,
> James H. LEE
--

(C) Matthew Rubenstein

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hey there James,

You simply need to edit felix.client.run.properties and remove from
there all bundles that you don't need. A good rule of thumb is to
consider bundles that appear last in the auto.start list as least important.

Good luck!
Emil

DaiZW написа:

···

2008/5/31 Matthew Rubenstein <email@mattruby.com
<mailto:email@mattruby.com>>:

           It would be great if the S-C installer had a checklist right
    at the
    beginning of each optional package and the core, for de/selection.
    Perfect would be if the installer could generate not just an
    installation, but also a custom installer with just those selected
    features.

Great idea! It can be a gsoc project of next year. :slight_smile:

    On Fri, 2008-05-30 at 15:50 -0400, James H Lee wrote:
    > Hi guys,
    >
    > I'm developing a prototype of a communication system using SIP and
    > I chose a SIP commicator as a client. It was working great on my
    > laptop.
    >
    > Now that I want to port it on a handheld machine. I'm using a device
    > emulator in Windows Mobile 6 Professional SDK by Microsoft and
    > properly
    > installed JVM (I used Mysaifu JVM). And then I downloaded the generic
    > installation file for All OSs and ran it. Everything was working fine
    > until I got
    > the message that the storage memory is critically low. (Aditionally,
    > the
    > runtime speed is very low.)
    >
    > So here is my question:
    > I want to make SIP communicator as light as possible. The only
    > functionalities
    > I need are ability to connect to SIP server, presence, and instant
    > messaging.
    > I think I should modify build.xml somehow to throw away some modules
    > that
    > I don't need... but I'm stuck in here.
    >
    > Can someone have a lesson on me how to remove it or provide me some
    > ideas?
    > Thank you for reading!
    >
    > Best wishes,
    > James H. LEE
    --

    (C) Matthew Rubenstein

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Is there somewhere documenting each of the bundles included in S-C
by felix.client.run.properties ? There are a lot of bundles, many with
cryptic filenames, and it's hard to tell which bundles are required for
which use case. Is there even some simple list of dependencies among
those included bundles?

  The current SVN revision (rev3744, at
https://sip-communicator.dev.java.net/source/browse/sip-communicator/trunk/lib/felix.client.run.properties?rev=3744&view=markup ) has a long list that includes a lot that seem required for S-C to function at all, even if it just sits there doing nothing, before adding even one that makes it do something worth running. What do each of the following do, and how do the interdependencies work?

[from /lib/felix.client.run.properties ]:
-------------------------------------------------------------------------
felix.auto.start.10=
reference:file:lib/bundle/org.apache.felix.bundlerepository-1.0.0.jar \
reference:file:lib/bundle/org.apache.felix.servicebinder-0.9.0-SNAPSHOT.jar
#reference:file:lib/bundle/org.apache.felix.bundlerepository-0.8.0-SNAPSHOT.jar
#\
# file:lib/bundle/shell.jar \
# \
# file:lib/bundle/servicebinder.jar \
# file:lib/bundle/tablelayout.jar

felix.auto.start.20= \
reference:file:sc-bundles/util.jar \
reference:file:lib/bundle/log4j.jar

felix.auto.start.30= \
reference:file:sc-bundles/fileaccess.jar

felix.auto.start.40= \
reference:file:sc-bundles/configuration.jar \
reference:file:sc-bundles/version.jar \
reference:file:sc-bundles/version-impl.jar \
reference:file:sc-bundles/branding.jar \

felix.auto.start.50= \
reference:file:sc-bundles/browserlauncher.jar \
reference:file:sc-bundles/protocol.jar \
reference:file:sc-bundles/contactlist.jar \
reference:file:sc-bundles/media.jar \
reference:file:sc-bundles/protocol-icq.jar \
reference:file:sc-bundles/protocol-sip.jar \
reference:file:sc-bundles/smacklib.jar \
reference:file:sc-bundles/protocol-jabber.jar \
reference:file:sc-bundles/protocol-msn.jar \
reference:file:sc-bundles/protocol-yahoo.jar \
reference:file:sc-bundles/protocol-gibberish.jar \
reference:file:sc-bundles/protocol-ssh.jar \
reference:file:sc-bundles/netaddr.jar \
reference:file:sc-bundles/protocol-rss.jar \
reference:file:sc-bundles/protocol-zeroconf.jar \
reference:file:sc-bundles/protocol-irc.jar \
reference:file:sc-bundles/meta-cl.jar \
reference:file:sc-bundles/protocol-dict.jar

felix.auto.start.60= \
reference:file:sc-bundles/history.jar \
reference:file:sc-bundles/msghistory.jar \
reference:file:sc-bundles/callhistory.jar \
reference:file:sc-bundles/audionotifier.jar \
reference:file:sc-bundles/notification.jar

felix.auto.start.66= \
reference:file:sc-bundles/swing-ui.jar \
reference:file:sc-bundles/updatechecker.jar \
reference:file:sc-bundles/systray.jar

felix.auto.start.67= \
reference:file:sc-bundles/pluginmanager.jar \
reference:file:sc-bundles/whiteboard.jar \
reference:file:sc-bundles/icqaccregwizz.jar \
reference:file:sc-bundles/aimaccregwizz.jar \
reference:file:sc-bundles/sipaccregwizz.jar \
reference:file:sc-bundles/jabberaccregwizz.jar \
reference:file:sc-bundles/msnaccregwizz.jar \
reference:file:sc-bundles/yahooaccregwizz.jar \
reference:file:sc-bundles/gibberishaccregwizz.jar \
reference:file:sc-bundles/sshaccregwizz.jar \
reference:file:sc-bundles/extendedcallhistorysearch.jar \
reference:file:sc-bundles/rssaccregwizz.jar \
reference:file:sc-bundles/zeroconfaccregwizz.jar \
reference:file:sc-bundles/ircaccregwizz.jar \
reference:file:sc-bundles/simpleaccreg.jar \
reference:file:sc-bundles/contacteventhandler.jar \
reference:file:sc-bundles/contactinfo.jar \
reference:file:sc-bundles/accountinfo.jar \
reference:file:sc-bundles/chatalerter.jar \
reference:file:sc-bundles/shutdown.jar \
reference:file:sc-bundles/statusupdate.jar \
reference:file:sc-bundles/generalconfig.jar \
reference:file:sc-bundles/dictaccregwizz.jar

# Uncomment the following lines if you want to run the architect viewer
# bundle.
#oscar.auto.start.100= \
# file:lib/bundle/architectureviewer1.1.jar
-------------------------------------------------------------------------

···

On Sat, 2008-06-14 at 17:19 +0200, Emil Ivov wrote:

Hey there James,

You simply need to edit felix.client.run.properties and remove from
there all bundles that you don't need. A good rule of thumb is to
consider bundles that appear last in the auto.start list as least important.

Good luck!
Emil

DaiZW написа:
> 2008/5/31 Matthew Rubenstein <email@mattruby.com
> <mailto:email@mattruby.com>>:
>
> It would be great if the S-C installer had a checklist right
> at the
> beginning of each optional package and the core, for de/selection.
> Perfect would be if the installer could generate not just an
> installation, but also a custom installer with just those selected
> features.
>
> Great idea! It can be a gsoc project of next year. :slight_smile:
>
>
>
> On Fri, 2008-05-30 at 15:50 -0400, James H Lee wrote:
> > Hi guys,
> >
> > I'm developing a prototype of a communication system using SIP and
> > I chose a SIP commicator as a client. It was working great on my
> > laptop.
> >
> > Now that I want to port it on a handheld machine. I'm using a device
> > emulator in Windows Mobile 6 Professional SDK by Microsoft and
> > properly
> > installed JVM (I used Mysaifu JVM). And then I downloaded the generic
> > installation file for All OSs and ran it. Everything was working fine
> > until I got
> > the message that the storage memory is critically low. (Aditionally,
> > the
> > runtime speed is very low.)
> >
> > So here is my question:
> > I want to make SIP communicator as light as possible. The only
> > functionalities
> > I need are ability to connect to SIP server, presence, and instant
> > messaging.
> > I think I should modify build.xml somehow to throw away some modules
> > that
> > I don't need... but I'm stuck in here.
> >
> > Can someone have a lesson on me how to remove it or provide me some
> > ideas?
> > Thank you for reading!
> >
> > Best wishes,
> > James H. LEE
> --
>
> (C) Matthew Rubenstein
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@sip-communicator.dev.java.net
> <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
> For additional commands, e-mail:
> dev-help@sip-communicator.dev.java.net
> <mailto:dev-help@sip-communicator.dev.java.net>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--

(C) Matthew Rubenstein

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net