[sip-comm-dev] Question about adding a library to the project.


#1

Hello devs,

  I'm playing around with SC and Apache Felix OSGi Bundle Repository. I
noticed that the jar file for the bundle repository was already in the
lib/bundle folder. I added it to the project to be able to use it. When I
run SC, I get errors. It says the packages org.osgi.service.obr is not
imported in the manifest. I then add it to the manifest file of the bundle.
After that, I get an error for org.apache.felix.bundlerepository package
stating that it's not imported by the bundle and that it's not exported by
any other bundle. From there I'm unsure of what to do in order to solve the
problem. The error "recommended" me to add the package in the
org.osgi.framework.system.packages property and import it in the bundle's
manifest. I did all that, but now I get the BundleException: Unresolved
package in bundle 34: package;
(&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))

Anyone can help me with that?

Thanks!


#2

Hey Mathieu,

This might be because the package is not on the classpath.

Every time you start SIP Communicator it dumps all its system properties
to the log file and among them you have the system.class.path one. Have
a look there and check whether the bundlerepository jar is in it.

Hope this helps
Emil

Mathieu Plourde написа:

···

Hello devs,

  I'm playing around with SC and Apache Felix OSGi Bundle Repository. I
noticed that the jar file for the bundle repository was already in the
lib/bundle folder. I added it to the project to be able to use it. When
I run SC, I get errors. It says the packages org.osgi.service.obr is not
imported in the manifest. I then add it to the manifest file of the
bundle. After that, I get an error for org.apache.felix.bundlerepository
package stating that it's not imported by the bundle and that it's not
exported by any other bundle. From there I'm unsure of what to do in
order to solve the problem. The error "recommended" me to add the
package in the org.osgi.framework.system.packages property and import it
in the bundle's manifest. I did all that, but now I get the
BundleException: Unresolved package in bundle 34: package;
(&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))

Anyone can help me with that?

Thanks!

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


#3

I found the problem...I forgot a semicolon in the
felix.client.run.properties file. It almost works now...I have another
problem about the class loaders.

Here's what I did step by step:
I added the package org.apache.felix.bundlerepository to the property
org.osgi.framework.system.packages. Then I imported both org.osgi.service.obr
and org.apache.felix.bundlerepository packages in the pluginmanager's
manifest file.
In the start method of the PluginManagerActivator, I added the following:

RepositoryAdminImpl rai = *new* RepositoryAdminImpl(bc);
Resolver res = rai.resolver();
URL url = *null*;
File f = *new* File("test.xml");
url = f.toURI().toURL();
rai.addRepository(url);
Repository [] repArray = rai.listRepositories();
System.*out*.println(repArray[0].getURL().toString());

This will NOT work. I'm getting this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar
(org.osgi.framework.BundleException: Activator start error.)
java.lang.LinkageError: loader constraint violation: loader (instance of
org/apache/felix/framework/searchpolicy/ContentClassLoader) previously
initiated loading for a different type with name
"org/osgi/service/obr/Repository"

I can't call any methods of the class Repository, even though I can use
their obj.

Replacing the last line with the following works:
System.*out*.println(((RepositoryImpl)repArray[0]).getURL().toString());

I also can't use RepositoryAdmin methods. I HAVE to use RepositoryAdminImpl.
If I replace the first two lines of the code above with this:
RepositoryAdmin rai = *new* RepositoryAdminImpl(bc);
Resolver res = *rai*.resolver();
I get this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar (*
org.osgi.framework.BundleException*: Activator start
error.)java.lang.IncompatibleClassChangeError:
Class org.apache.felix.bundlerepository.RepositoryAdminImpl does not
implement the requested interface org.osgi.service.obr.RepositoryAdmin

I googled it and tried to find a solution, but I found nothing that could
help me. I suppose you guys that have played with OSGi / SC for a while can
help me with this issue.

Thanks again!

···

2008/5/14 Emil Ivov <emcho@sip-communicator.org>:

Hey Mathieu,

This might be because the package is not on the classpath.

Every time you start SIP Communicator it dumps all its system properties
to the log file and among them you have the system.class.path one. Have
a look there and check whether the bundlerepository jar is in it.

Hope this helps
Emil

Mathieu Plourde написа:
> Hello devs,
>
> I'm playing around with SC and Apache Felix OSGi Bundle Repository. I
> noticed that the jar file for the bundle repository was already in the
> lib/bundle folder. I added it to the project to be able to use it. When
> I run SC, I get errors. It says the packages org.osgi.service.obr is not
> imported in the manifest. I then add it to the manifest file of the
> bundle. After that, I get an error for org.apache.felix.bundlerepository
> package stating that it's not imported by the bundle and that it's not
> exported by any other bundle. From there I'm unsure of what to do in
> order to solve the problem. The error "recommended" me to add the
> package in the org.osgi.framework.system.packages property and import it
> in the bundle's manifest. I did all that, but now I get the
> BundleException: Unresolved package in bundle 34: package;
> (&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))
>
> Anyone can help me with that?
>
> Thanks!

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


#4

What is the setup here? Is the the OBR bundle being loaded as a bundle or is it on the class path? If it is being loaded as a bundle, then you shouldn't be putting anything on the system class path for it.

-> richard

Mathieu Plourde wrote:

···

I found the problem...I forgot a semicolon in the felix.client.run.properties file. It almost works now...I have another problem about the class loaders.
Here's what I did step by step:
I added the package org.apache.felix.bundlerepository to the property org.osgi.framework.system.packages. Then I imported both org.osgi.service.obr and org.apache.felix.bundlerepository packages in the pluginmanager's manifest file.
In the start method of the PluginManagerActivator, I added the following:

RepositoryAdminImpl rai = *new* RepositoryAdminImpl(bc);
Resolver res = rai.resolver();
URL url = *null*;
File f = *new* File("test.xml");
url = f.toURI().toURL();
rai.addRepository(url);
Repository [] repArray = rai.listRepositories();
System./out/.println(repArray[0].getURL().toString());
This will NOT work. I'm getting this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar (org.osgi.framework.BundleException: Activator start error.)
java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/searchpolicy/ContentClassLoader) previously initiated loading for a different type with name "org/osgi/service/obr/Repository"
I can't call any methods of the class Repository, even though I can use their obj.
Replacing the last line with the following works:
System./out/.println(((RepositoryImpl)repArray[0]).getURL().toString());
I also can't use RepositoryAdmin methods. I HAVE to use RepositoryAdminImpl. If I replace the first two lines of the code above with this:
RepositoryAdmin rai = *new* RepositoryAdminImpl(bc);
Resolver res = _rai_.resolver();
I get this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar (_org.osgi.framework.BundleException_: Activator start error.)java.lang.IncompatibleClassChangeError: Class org.apache.felix.bundlerepository.RepositoryAdminImpl does not implement the requested interface org.osgi.service.obr.RepositoryAdmin
I googled it and tried to find a solution, but I found nothing that could help me. I suppose you guys that have played with OSGi / SC for a while can help me with this issue.
Thanks again!

    Hey Mathieu,

    This might be because the package is not on the classpath.

    Every time you start SIP Communicator it dumps all its system
    properties
     to the log file and among them you have the system.class.path
    one. Have
    a look there and check whether the bundlerepository jar is in it.

    Hope this helps
    Emil

    Mathieu Plourde ������:
    > Hello devs,
    >
    > I'm playing around with SC and Apache Felix OSGi Bundle
    Repository. I
    > noticed that the jar file for the bundle repository was already
    in the
    > lib/bundle folder. I added it to the project to be able to use
    it. When
    > I run SC, I get errors. It says the packages
    org.osgi.service.obr is not
    > imported in the manifest. I then add it to the manifest file of the
    > bundle. After that, I get an error for
    org.apache.felix.bundlerepository
    > package stating that it's not imported by the bundle and that
    it's not
    > exported by any other bundle. From there I'm unsure of what to do in
    > order to solve the problem. The error "recommended" me to add the
    > package in the org.osgi.framework.system.packages property and
    import it
    > in the bundle's manifest. I did all that, but now I get the
    > BundleException: Unresolved package in bundle 34: package;
    > (&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))
    >
    > Anyone can help me with that?
    >
    > Thanks!

    ---------------------------------------------------------------------
    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


#5

I don't think it's loaded as a bundle. It's just a jar file I added to the
classpath. I don't see how it could be loaded as a bundle as it's just a
library of classes. The only place I import the package is in the
pluginmanager activator. I don't understand how there could be a conflict in
the class loader...

···

2008/5/15 Richard S. Hall <heavy@ungoverned.org>:

What is the setup here? Is the the OBR bundle being loaded as a bundle or
is it on the class path? If it is being loaded as a bundle, then you
shouldn't be putting anything on the system class path for it.

-> richard

Mathieu Plourde wrote:

I found the problem...I forgot a semicolon in the
felix.client.run.properties file. It almost works now...I have another
problem about the class loaders.
Here's what I did step by step:
I added the package org.apache.felix.bundlerepository to the property
org.osgi.framework.system.packages. Then I imported both
org.osgi.service.obr and org.apache.felix.bundlerepository packages in the
pluginmanager's manifest file.
In the start method of the PluginManagerActivator, I added the following:

RepositoryAdminImpl rai = *new* RepositoryAdminImpl(bc);
Resolver res = rai.resolver();
URL url = *null*;
File f = *new* File("test.xml");
url = f.toURI().toURL();
rai.addRepository(url);
Repository [] repArray = rai.listRepositories();
System./out/.println(repArray[0].getURL().toString());
This will NOT work. I'm getting this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar
(org.osgi.framework.BundleException: Activator start error.)
java.lang.LinkageError: loader constraint violation: loader (instance of
org/apache/felix/framework/searchpolicy/ContentClassLoader) previously
initiated loading for a different type with name
"org/osgi/service/obr/Repository"
I can't call any methods of the class Repository, even though I can use
their obj.
Replacing the last line with the following works:
System./out/.println(((RepositoryImpl)repArray[0]).getURL().toString());
I also can't use RepositoryAdmin methods. I HAVE to use
RepositoryAdminImpl. If I replace the first two lines of the code above with
this:
RepositoryAdmin rai = *new* RepositoryAdminImpl(bc);
Resolver res = _rai_.resolver();
I get this error:
ERROR: Error starting reference:file:sc-bundles/pluginmanager.jar
(_org.osgi.framework.BundleException_: Activator start
error.)java.lang.IncompatibleClassChangeError: Class
org.apache.felix.bundlerepository.RepositoryAdminImpl does not implement the
requested interface org.osgi.service.obr.RepositoryAdmin
I googled it and tried to find a solution, but I found nothing that could
help me. I suppose you guys that have played with OSGi / SC for a while can
help me with this issue.
Thanks again!
  2008/5/14 Emil Ivov <emcho@sip-communicator.org <mailto:
emcho@sip-communicator.org>>:

   Hey Mathieu,

   This might be because the package is not on the classpath.

   Every time you start SIP Communicator it dumps all its system
   properties
    to the log file and among them you have the system.class.path
   one. Have
   a look there and check whether the bundlerepository jar is in it.

   Hope this helps
   Emil

   Mathieu Plourde написа:
   > Hello devs,
   >
   > I'm playing around with SC and Apache Felix OSGi Bundle
   Repository. I
   > noticed that the jar file for the bundle repository was already
   in the
   > lib/bundle folder. I added it to the project to be able to use
   it. When
   > I run SC, I get errors. It says the packages
   org.osgi.service.obr is not
   > imported in the manifest. I then add it to the manifest file of the
   > bundle. After that, I get an error for
   org.apache.felix.bundlerepository
   > package stating that it's not imported by the bundle and that
   it's not
   > exported by any other bundle. From there I'm unsure of what to do in
   > order to solve the problem. The error "recommended" me to add the
   > package in the org.osgi.framework.system.packages property and
   import it
   > in the bundle's manifest. I did all that, but now I get the
   > BundleException: Unresolved package in bundle 34: package;
   > (&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))
   >
   > Anyone can help me with that?
   >
   > Thanks!

   ---------------------------------------------------------------------
   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

Mathieu Plourde wrote:

I don't think it's loaded as a bundle. It's just a jar file I added to the classpath. I don't see how it could be loaded as a bundle as it's just a library of classes. The only place I import the package is in the pluginmanager activator. I don't understand how there could be a conflict in the class loader...

Well, when I run SIP Comm and look in the "plugins" list under settings, I see the OBR bundle installed and active...so, someone is installing already for me.

I admit that I might be confused about what you are asking.

-> richard

···

2008/5/15 Richard S. Hall <heavy@ungoverned.org <mailto:heavy@ungoverned.org>>:

    What is the setup here? Is the the OBR bundle being loaded as a
    bundle or is it on the class path? If it is being loaded as a
    bundle, then you shouldn't be putting anything on the system class
    path for it.

    -> richard

    Mathieu Plourde wrote:

        I found the problem...I forgot a semicolon in the
        felix.client.run.properties file. It almost works now...I have
        another problem about the class loaders.
         Here's what I did step by step:
        I added the package org.apache.felix.bundlerepository to the
        property org.osgi.framework.system.packages. Then I imported
        both org.osgi.service.obr and
        org.apache.felix.bundlerepository packages in the
        pluginmanager's manifest file.
        In the start method of the PluginManagerActivator, I added the
        following:

        RepositoryAdminImpl rai = *new* RepositoryAdminImpl(bc);
        Resolver res = rai.resolver();
        URL url = *null*;
        File f = *new* File("test.xml");
        url = f.toURI().toURL();
        rai.addRepository(url);
        Repository [] repArray = rai.listRepositories();
        System./out/.println(repArray[0].getURL().toString());
         This will NOT work. I'm getting this error:
        ERROR: Error starting
        reference:file:sc-bundles/pluginmanager.jar
        (org.osgi.framework.BundleException: Activator start error.)
        java.lang.LinkageError: loader constraint violation: loader
        (instance of
        org/apache/felix/framework/searchpolicy/ContentClassLoader)
        previously initiated loading for a different type with name
        "org/osgi/service/obr/Repository"
         I can't call any methods of the class Repository, even though
        I can use their obj.
         Replacing the last line with the following works:
        System./out/.println(((RepositoryImpl)repArray[0]).getURL().toString());
         I also can't use RepositoryAdmin methods. I HAVE to use
        RepositoryAdminImpl. If I replace the first two lines of the
        code above with this:
        RepositoryAdmin rai = *new* RepositoryAdminImpl(bc);
        Resolver res = _rai_.resolver();
        I get this error:
        ERROR: Error starting
        reference:file:sc-bundles/pluginmanager.jar
        (_org.osgi.framework.BundleException_: Activator start
        error.)java.lang.IncompatibleClassChangeError: Class
        org.apache.felix.bundlerepository.RepositoryAdminImpl does not
        implement the requested interface
        org.osgi.service.obr.RepositoryAdmin
         I googled it and tried to find a solution, but I found
        nothing that could help me. I suppose you guys that have
        played with OSGi / SC for a while can help me with this issue.
         Thanks again!
          2008/5/14 Emil Ivov <emcho@sip-communicator.org
        <mailto:emcho@sip-communicator.org>
        <mailto:emcho@sip-communicator.org
        <mailto:emcho@sip-communicator.org>>>:

           Hey Mathieu,

           This might be because the package is not on the classpath.

           Every time you start SIP Communicator it dumps all its system
           properties
            to the log file and among them you have the system.class.path
           one. Have
           a look there and check whether the bundlerepository jar is
        in it.

           Hope this helps
           Emil

           Mathieu Plourde ������:
           > Hello devs,
           >
           > I'm playing around with SC and Apache Felix OSGi Bundle
           Repository. I
           > noticed that the jar file for the bundle repository was
        already
           in the
           > lib/bundle folder. I added it to the project to be able
        to use
           it. When
           > I run SC, I get errors. It says the packages
           org.osgi.service.obr is not
           > imported in the manifest. I then add it to the manifest
        file of the
           > bundle. After that, I get an error for
           org.apache.felix.bundlerepository
           > package stating that it's not imported by the bundle and that
           it's not
           > exported by any other bundle. From there I'm unsure of
        what to do in
           > order to solve the problem. The error "recommended" me to
        add the
           > package in the org.osgi.framework.system.packages
        property and
           import it
           > in the bundle's manifest. I did all that, but now I get the
           > BundleException: Unresolved package in bundle 34: package;
           >
        (&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))
           >
           > Anyone can help me with that?
           >
           > Thanks!

                  ---------------------------------------------------------------------
           To unsubscribe, e-mail:
           dev-unsubscribe@sip-communicator.dev.java.net
        <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
           <mailto: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>
           <mailto: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
    <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


#7

I'm going to investigate about this issue...I'll come back with the solution
hopefully.

···

2008/5/15 Richard S. Hall <heavy@ungoverned.org>:

Mathieu Plourde wrote:

I don't think it's loaded as a bundle. It's just a jar file I added to the
classpath. I don't see how it could be loaded as a bundle as it's just a
library of classes. The only place I import the package is in the
pluginmanager activator. I don't understand how there could be a conflict in
the class loader...

Well, when I run SIP Comm and look in the "plugins" list under settings, I
see the OBR bundle installed and active...so, someone is installing already
for me.

I admit that I might be confused about what you are asking.

-> richard

2008/5/15 Richard S. Hall <heavy@ungoverned.org <mailto:
heavy@ungoverned.org>>:

   What is the setup here? Is the the OBR bundle being loaded as a
   bundle or is it on the class path? If it is being loaded as a
   bundle, then you shouldn't be putting anything on the system class
   path for it.

   -> richard

   Mathieu Plourde wrote:

       I found the problem...I forgot a semicolon in the
       felix.client.run.properties file. It almost works now...I have
       another problem about the class loaders.
        Here's what I did step by step:
       I added the package org.apache.felix.bundlerepository to the
       property org.osgi.framework.system.packages. Then I imported
       both org.osgi.service.obr and
       org.apache.felix.bundlerepository packages in the
       pluginmanager's manifest file.
       In the start method of the PluginManagerActivator, I added the
       following:

       RepositoryAdminImpl rai = *new* RepositoryAdminImpl(bc);
       Resolver res = rai.resolver();
       URL url = *null*;
       File f = *new* File("test.xml");
       url = f.toURI().toURL();
       rai.addRepository(url);
       Repository [] repArray = rai.listRepositories();
       System./out/.println(repArray[0].getURL().toString());
        This will NOT work. I'm getting this error:
       ERROR: Error starting
       reference:file:sc-bundles/pluginmanager.jar
       (org.osgi.framework.BundleException: Activator start error.)
       java.lang.LinkageError: loader constraint violation: loader
       (instance of
       org/apache/felix/framework/searchpolicy/ContentClassLoader)
       previously initiated loading for a different type with name
       "org/osgi/service/obr/Repository"
        I can't call any methods of the class Repository, even though
       I can use their obj.
        Replacing the last line with the following works:

System./out/.println(((RepositoryImpl)repArray[0]).getURL().toString());
        I also can't use RepositoryAdmin methods. I HAVE to use
       RepositoryAdminImpl. If I replace the first two lines of the
       code above with this:
       RepositoryAdmin rai = *new* RepositoryAdminImpl(bc);
       Resolver res = _rai_.resolver();
       I get this error:
       ERROR: Error starting
       reference:file:sc-bundles/pluginmanager.jar
       (_org.osgi.framework.BundleException_: Activator start
       error.)java.lang.IncompatibleClassChangeError: Class
       org.apache.felix.bundlerepository.RepositoryAdminImpl does not
       implement the requested interface
       org.osgi.service.obr.RepositoryAdmin
        I googled it and tried to find a solution, but I found
       nothing that could help me. I suppose you guys that have
       played with OSGi / SC for a while can help me with this issue.
        Thanks again!
         2008/5/14 Emil Ivov <emcho@sip-communicator.org
       <mailto:emcho@sip-communicator.org>
       <mailto:emcho@sip-communicator.org
       <mailto:emcho@sip-communicator.org>>>:

          Hey Mathieu,

          This might be because the package is not on the classpath.

          Every time you start SIP Communicator it dumps all its system
          properties
           to the log file and among them you have the system.class.path
          one. Have
          a look there and check whether the bundlerepository jar is
       in it.

          Hope this helps
          Emil

          Mathieu Plourde написа:
          > Hello devs,
          >
          > I'm playing around with SC and Apache Felix OSGi Bundle
          Repository. I
          > noticed that the jar file for the bundle repository was
       already
          in the
          > lib/bundle folder. I added it to the project to be able
       to use
          it. When
          > I run SC, I get errors. It says the packages
          org.osgi.service.obr is not
          > imported in the manifest. I then add it to the manifest
       file of the
          > bundle. After that, I get an error for
          org.apache.felix.bundlerepository
          > package stating that it's not imported by the bundle and that
          it's not
          > exported by any other bundle. From there I'm unsure of
       what to do in
          > order to solve the problem. The error "recommended" me to
       add the
          > package in the org.osgi.framework.system.packages
       property and
          import it
          > in the bundle's manifest. I did all that, but now I get the
          > BundleException: Unresolved package in bundle 34: package;
          >
       (&(package=org.apache.felix.bundlerepository)(version>=0.0.0)))
          >
          > Anyone can help me with that?
          >
          > Thanks!

---------------------------------------------------------------------
          To unsubscribe, e-mail:
          dev-unsubscribe@sip-communicator.dev.java.net
       <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
          <mailto: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>
          <mailto: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
   <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