[sip-comm-dev] eclipse documentation hidden files .project and .classpath


#1

Hi Yana,

I remember sometimes ago, there where a guy complaining about the fact that he didn't found the .project and .classpath referred here in the eclipse configuration documentation for SC

  Setting up Eclipse for SIP Communicator

     * Copy the files .project and .classpath from PROJECT_DIR/ide/eclipse to PROJECT_DIR
     * Right button click on the project in the Package explorer and select Refresh.
     * Done.

The problem is that those files are "hidden" for unix/linux user and thus doesn't appears by default in an explorer or when someone type "ls" in a console. It can be a little awkward for certain peoples. So, it could be usefull to highligth the fact that those files can be hidden.

   ++ Sympho

···

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


#2

Hi Sympho,

Sympho wrote:

Hi Yana,

I remember sometimes ago, there where a guy complaining about the fact that he didn't found the .project and .classpath referred here in the eclipse configuration documentation for SC

Setting up Eclipse for SIP Communicator

    * Copy the files .project and .classpath from PROJECT_DIR/ide/eclipse to PROJECT_DIR
    * Right button click on the project in the Package explorer and select Refresh.
    * Done.

The problem is that those files are "hidden" for unix/linux user and thus doesn't appears by default in an explorer or when someone type "ls" in a console. It can be a little awkward for certain peoples. So, it could be usefull to highligth the fact that those files can be hidden.

Oh, you're right! I didn't thought of that. Very good idea! Would you like to update the documentation and add this information ? If you don't have already an account for the wiki, tell me and I'll create a one for you.

Yana

···

  ++ Sympho

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


#3

Yana Stamcheva <yana@sip-communicator.org> a écrit :

Hi Sympho,

Sympho wrote:

Hi Yana,

I remember sometimes ago, there where a guy complaining about the fact that he didn't found the .project and .classpath referred here in the eclipse configuration documentation for SC

Setting up Eclipse for SIP Communicator

   * Copy the files .project and .classpath from PROJECT_DIR/ide/eclipse to PROJECT_DIR
   * Right button click on the project in the Package explorer and select Refresh.
   * Done.

The problem is that those files are "hidden" for unix/linux user and thus doesn't appears by default in an explorer or when someone type "ls" in a console. It can be a little awkward for certain peoples. So, it could be usefull to highligth the fact that those files can be hidden.

Oh, you're right! I didn't thought of that. Very good idea! Would you
like to update the documentation and add this information ? If you
don't have already an account for the wiki, tell me and I'll create a
one for you.

Yana

I am waiting for the wiki account :slight_smile:

···

++ Sympho

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

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


#4

Hi!

I'm just debugging the shutdown sequence, as my sip-accounts do not
unregister when closing the SC. Therefore I found following code in
ProtocolProviderServiceSipImpl:

    /**
     * Makes the service implementation close all open sockets and release
     * any resources that it might have taken and prepare for
shutdown/garbage
     * collection.
     */
    public void shutdown()
    {
        if(!isInitialized)
        {
            return;
        }
        
        // launch the shutdown process in a thread to free the GUI as soon
        // as possible even if the SIP unregistration process may take time
        // especially for ending SIMPLE
        Thread t = new Thread(new ShutdownThread());
        t.setDaemon(false);
------> t.run(); <-------
    }

Is it really intended to call "run" on a thread?

Moreover, the VM exits (also when calling t.start) before all my connections
are unregistered, I'm just having a look, why.

···

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


#5

Hi Sympho,

Thanks! I've sent you the account information in a personal email.

Yana

Sympho wrote:

···

Yana Stamcheva <yana@sip-communicator.org> a �crit :

Hi Sympho,

Sympho wrote:

Hi Yana,

I remember sometimes ago, there where a guy complaining about the fact that he didn't found the .project and .classpath referred here in the eclipse configuration documentation for SC

Setting up Eclipse for SIP Communicator

   * Copy the files .project and .classpath from PROJECT_DIR/ide/eclipse to PROJECT_DIR
   * Right button click on the project in the Package explorer and select Refresh.
   * Done.

The problem is that those files are "hidden" for unix/linux user and thus doesn't appears by default in an explorer or when someone type "ls" in a console. It can be a little awkward for certain peoples. So, it could be usefull to highligth the fact that those files can be hidden.

Oh, you're right! I didn't thought of that. Very good idea! Would you
like to update the documentation and add this information ? If you
don't have already an account for the wiki, tell me and I'll create a
one for you.

Yana

I am waiting for the wiki account :slight_smile:

++ Sympho

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

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

In ProtocolProviderServiceSipImpl - ShutdownThread.run (line 1323)

*** Package 'net.java.sip.communicator.impl.protocol.sip' is not imported by
bundle 13, nor is there any bundle that exports package
'net.java.sip.communicator.impl.protocol.sip'. However, the class
'net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl$
ShutdownUnregistrationBlockListener' is available from the system class
loader. There are two fixes: 1) Add package
'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.system.packages' property and modify bundle 13 to import
this package; this causes the system bundle to export class path packages.
2) Add package 'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.bootdelegation' property; a library or VM bug can cause
classes to be loaded by the wrong class loader. The first approach is
preferable for preserving modularity. ***

Cheers, thomas

···

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


#7

Hi! I found one issue when unregistering from a sipserver.

1. it does work, when setting the status to offline

2. it does not work, when just quitting SC, which is online.

unregisterTransaction.sendRequest(); (in SipRegistrarConnection)
is called in both ways, but (in my case) a " Proxy Authentication Required"
from the sip-server comes back. And the VM exits, before this is answered by
the Jain-Sip-Stack.

Can anybody reproduce this issue and is there an idea for a workaround?

Regards, thomas

···

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


#8

I wrote a workaround for the issue. I just wait for 1 second at the maximum
to complete the unregisterTransaction.

            unregisterTransaction.sendRequest();
            
            //workaround/bugfix for unregistering-bug. wait here, until the
transaction
            //has been completed to be sure, that unregistering was
successful.
            int i = 0;;
            while(unregisterTransaction.getState() !=
TransactionState.COMPLETED && i < 10) {
                try {
                    Thread.sleep(100);
                } catch (InterruptedException e) {
                }
                i++;
            }

Cheers, thomas

···

-----Ursprüngliche Nachricht-----
Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Dienstag, 09. Oktober 2007 11:53
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] Shutdown - does not unregister from sip-server

Hi! I found one issue when unregistering from a sipserver.

1. it does work, when setting the status to offline

2. it does not work, when just quitting SC, which is online.

unregisterTransaction.sendRequest(); (in SipRegistrarConnection)
is called in both ways, but (in my case) a " Proxy Authentication
Required"
>from the sip-server comes back. And the VM exits, before this is
answered by
the Jain-Sip-Stack.

Can anybody reproduce this issue and is there an idea for a workaround?

Regards, thomas

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


#9

Hi Thomas,

I was looking at the shutdown problem you have. I'm not sure I understand this one though. As I had a look in the ProtocolProviderServiceSipImpl the ShutdownUnregistrationBlockListener is an inner class used only inside the protocol provider service SIP implementation. It's strange this NoClassDefFoundException.

Otherwise, I don't think that it is a good idea to add an "impl" package in the osgi system packages, because impl packages are contained in bundles and are not meant to be exported and be used from outside the bundle.

May be I didn't understand well what you mean.

Yana

Thomas Hofer wrote:

···

In ProtocolProviderServiceSipImpl - ShutdownThread.run (line 1323)

*** Package 'net.java.sip.communicator.impl.protocol.sip' is not imported by
bundle 13, nor is there any bundle that exports package
'net.java.sip.communicator.impl.protocol.sip'. However, the class
'net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl$
ShutdownUnregistrationBlockListener' is available from the system class
loader. There are two fixes: 1) Add package
'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.system.packages' property and modify bundle 13 to import
this package; this causes the system bundle to export class path packages.
2) Add package 'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.bootdelegation' property; a library or VM bug can cause
classes to be loaded by the wrong class loader. The first approach is
preferable for preserving modularity. ***

Cheers, thomas

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


#10

I meant, that I had a CNFE. Nothing more :wink: The 1) and 2) proposals are not
mine, but part of the default error message of the osgi-runtime.

But It probably raised, because I tested to replace the Thread.run (I posted
before) through a Thread.start. Probably this caused this problem.

I'll have another look at this issue.

···

-----Ursprüngliche Nachricht-----
Von: Yana Stamcheva [mailto:yana@sip-communicator.org]
Gesendet: Dienstag, 09. Oktober 2007 13:36
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] ClassNotFoundException on Shuftdown

Hi Thomas,

I was looking at the shutdown problem you have. I'm not sure I
understand this one though. As I had a look in the
ProtocolProviderServiceSipImpl the ShutdownUnregistrationBlockListener
is an inner class used only inside the protocol provider service SIP
implementation. It's strange this NoClassDefFoundException.

Otherwise, I don't think that it is a good idea to add an "impl"
package
in the osgi system packages, because impl packages are contained in
bundles and are not meant to be exported and be used from outside the
bundle.

May be I didn't understand well what you mean.

Yana

Thomas Hofer wrote:
> In ProtocolProviderServiceSipImpl - ShutdownThread.run (line 1323)
>
> *** Package 'net.java.sip.communicator.impl.protocol.sip' is not
imported by
> bundle 13, nor is there any bundle that exports package
> 'net.java.sip.communicator.impl.protocol.sip'. However, the class
>
'net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSip
Impl$
> ShutdownUnregistrationBlockListener' is available from the system
class
> loader. There are two fixes: 1) Add package
> 'net.java.sip.communicator.impl.protocol.sip' to the
> 'org.osgi.framework.system.packages' property and modify bundle 13 to
import
> this package; this causes the system bundle to export class path
packages.
> 2) Add package 'net.java.sip.communicator.impl.protocol.sip' to the
> 'org.osgi.framework.bootdelegation' property; a library or VM bug can
cause
> classes to be loaded by the wrong class loader. The first approach is
> preferable for preserving modularity. ***
>
>
> Cheers, thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
> For additional commands, e-mail: 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

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


#11

Hi,

Thomas Hofer wrote:

I meant, that I had a CNFE. Nothing more :wink: The 1) and 2) proposals are not
mine, but part of the default error message of the osgi-runtime.

Haha, I thought that the proposals are strange :wink:

But It probably raised, because I tested to replace the Thread.run (I posted
before) through a Thread.start. Probably this caused this problem.

Yes, it could be that.

I'll have another look at this issue.

Ok, great. Thanks!

Yana

···

-----Urspr�ngliche Nachricht-----
Von: Yana Stamcheva [mailto:yana@sip-communicator.org]
Gesendet: Dienstag, 09. Oktober 2007 13:36
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] ClassNotFoundException on Shuftdown

Hi Thomas,

I was looking at the shutdown problem you have. I'm not sure I
understand this one though. As I had a look in the
ProtocolProviderServiceSipImpl the ShutdownUnregistrationBlockListener
is an inner class used only inside the protocol provider service SIP
implementation. It's strange this NoClassDefFoundException.

Otherwise, I don't think that it is a good idea to add an "impl"
package
in the osgi system packages, because impl packages are contained in
bundles and are not meant to be exported and be used from outside the
bundle.

May be I didn't understand well what you mean.

Yana

Thomas Hofer wrote:

In ProtocolProviderServiceSipImpl - ShutdownThread.run (line 1323)

*** Package 'net.java.sip.communicator.impl.protocol.sip' is not

imported by

bundle 13, nor is there any bundle that exports package
'net.java.sip.communicator.impl.protocol.sip'. However, the class

'net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSip
Impl$

ShutdownUnregistrationBlockListener' is available from the system

class

loader. There are two fixes: 1) Add package
'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.system.packages' property and modify bundle 13 to

import

this package; this causes the system bundle to export class path

packages.

2) Add package 'net.java.sip.communicator.impl.protocol.sip' to the
'org.osgi.framework.bootdelegation' property; a library or VM bug can

cause

classes to be loaded by the wrong class loader. The first approach is
preferable for preserving modularity. ***

Cheers, thomas

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

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


#12

Hi!
Has anyone a configuration file for the sip-communicator-code-conventions
for eclipse? If so, it would be a great idea to add it to the Wiki (and sent
it to me).

Cheers, thomas

···

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


#13

Hi!

Has anyone a configuration file for the
sip-communicator-code-conventions
for eclipse?

Attached is the Java/Code Style/Formatter setting which I use. It is for
Eclipse 3.2 (don't know if it will work with older versions). It doesn't
cover all conventions, since some things seem to not be configurable (like
put each interface name of the implements clause on a separate line). Also,
the package import convention is configured separately (under Java/Code
Style/Organize Imports).

Regards
Michael Koch

sip-comm-eclipse-formatter.xml (27.8 KB)


#14

Hi Thomas, Michael,

here is also my configuration file, I have tried to configure as much things as possible. Michael is right that unfortunately this doesn't contain the whole configuration needed. Otherwise I think I found a way to configure each interface name on a separate line (but the indention still should be done manually).

Regards,
Yana

Koch Michael wrote:

sip-comm-convention-eclipse.xml (27.5 KB)

···

Hi!

Has anyone a configuration file for the sip-communicator-code-conventions
for eclipse?

Attached is the Java/Code Style/Formatter setting which I use. It is for
Eclipse 3.2 (don't know if it will work with older versions). It doesn't
cover all conventions, since some things seem to not be configurable (like
put each interface name of the implements clause on a separate line). Also,
the package import convention is configured separately (under Java/Code
Style/Organize Imports).

Regards
Michael Koch