[jitsi-dev] ${resX} ${resY} provisioning parameter


#1

Dear dev team,

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Best regards,
Patrick


#2

Hey Patrick,

На 04.10.11 14:17, Patrick написа:

Dear dev team,

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Emil


#3

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example regularly use a multi-monitor setup, sometimes with different resolution on the two monitors (the Laptop's built-in display and an external 24" screen). In addition the primary monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in general: allow the ${x} replacement to accept any of the Java properties available through System.getProperty(x)

Ingo


#4

Hello Ingo,

The way I saw it was to use the default screen (using
http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

···

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo <ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example regularly use a multi-monitor setup, sometimes with different resolution on the two monitors (the Laptop's built-in display and an external 24" screen). In addition the primary monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in general: allow the ${x} replacement to accept any of the Java properties available through System.getProperty(x)

Ingo


#5

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using
http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters someone.

Emil

···

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo <ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example regularly use a multi-monitor setup, sometimes with different resolution on the two monitors (the Laptop's built-in display and an external 24" screen). In addition the primary monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in general: allow the ${x} replacement to accept any of the Java properties available through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#6

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Best regards,
Patrick

···

On Wed, Oct 5, 2011 at 12:23, Emil Ivov <emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using
http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo <ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example regularly use a multi-monitor setup, sometimes with different resolution on the two monitors (the Laptop's built-in display and an external 24" screen). In addition the primary monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in general: allow the ${x} replacement to accept any of the Java properties available through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#7

Hi Patrick,

···

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using
http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example regularly use a multi-monitor setup, sometimes with different resolution on the two monitors (the Laptop's built-in display and an external 24" screen). In addition the primary monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in general: allow the ${x} replacement to accept any of the Java properties available through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#8

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
     [java] java.lang.IllegalArgumentException: null owner window
     [java] at java.awt.Window.ownedInit(Window.java:415)
     [java] at java.awt.Window.<init>(Window.java:375)
     [java] at java.awt.Dialog.<init>(Dialog.java:310)
     [java] at javax.swing.JDialog.<init>(JDialog.java:329)
     [java] at javax.swing.JDialog.<init>(JDialog.java:288)
     [java] at javax.swing.JDialog.<init>(JDialog.java:269)
     [java] at
net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:63)
     [java] at
net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:104)
     [java] at
net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:124)
     [java] at
net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:108)
     [java] at
net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvider.getCredentials(HttpUtils.java:662)
     [java] at
net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:458)
     [java] at
net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:377)
     [java] at
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(ProvisioningActivator.java:507)
     [java] at
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(ProvisioningActivator.java:203)
     [java] at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
     [java] at org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
     [java] at org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
     [java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
     [java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
     [java] at java.lang.Thread.run(Thread.java:595)
     [java] IOException in readRegistry: java.io.EOFException
     [java] stream:error (host-unknown)
     [java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
     [java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
     [java] at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

Best regards,
Patrick

···

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> >>>> wrote:

Other parameters that could be interesting to have in the
provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width
for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example
regularly use a multi-monitor setup, sometimes with different resolution on
the two monitors (the Laptop's built-in display and an external 24" screen).
In addition the primary monitor can be on the right. We'd need a solution to
handle that.

I already thought about extending the provisioning service in general:
allow the ${x} replacement to accept any of the Java properties available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#9

Hi Patrick,

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
      [java] java.lang.IllegalArgumentException: null owner window
      [java] at java.awt.Window.ownedInit(Window.java:415)
      [java] at java.awt.Window.<init>(Window.java:375)
      [java] at java.awt.Dialog.<init>(Dialog.java:310)
      [java] at javax.swing.JDialog.<init>(JDialog.java:329)
      [java] at javax.swing.JDialog.<init>(JDialog.java:288)
      [java] at javax.swing.JDialog.<init>(JDialog.java:269)
      [java] at
net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:63)
      [java] at
net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:104)
      [java] at
net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:124)
      [java] at
net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:108)
      [java] at
net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvider.getCredentials(HttpUtils.java:662)
      [java] at
net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:458)
      [java] at
net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:377)
      [java] at
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(ProvisioningActivator.java:507)
      [java] at
net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(ProvisioningActivator.java:203)
      [java] at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
      [java] at org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
      [java] at org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
      [java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
      [java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
      [java] at java.lang.Thread.run(Thread.java:595)
      [java] IOException in readRegistry: java.io.EOFException
      [java] stream:error (host-unknown)
      [java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
      [java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
      [java] at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the authentication popup for ${username} and ${password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem compiling. What is your OS ? Are you sure SVN update has correctly finished ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,

···

Le 06/10/11 09:32, Patrick a écrit :
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> >>>>> wrote:

Other parameters that could be interesting to have in the
provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width
for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for example
regularly use a multi-monitor setup, sometimes with different resolution on
the two monitors (the Laptop's built-in display and an external 24" screen).
In addition the primary monitor can be on the right. We'd need a solution to
handle that.

I already thought about extending the provisioning service in general:
allow the ${x} replacement to accept any of the Java properties available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#10

Hey

I've started the 'rebuild' and 'run' targets to test my new code but, I
never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
     [java] java.lang.IllegalArgumentException: null owner window
[...]
Any idea how I should fix it and show the authentication popup ?

On which OS and JDK are you encountering this?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

You probably don't have sdes4j.jar on your Classpath. If you copied the files from ide/eclipse or ide/nbproject before the SDES introduction, you need to either copy them again (while the IDE is closed), or just add lib/installer-exclude/sdes4j.jar to the build Classpath (in Eclipse you can do this by right clicking on it, select Build Path->Add to Build Path)

You shouldn't get any errors when building with Ant however.

Ingo


#11

Patrick, how is the compilation being performed when the errors
appear: with Ant on the command line or inside Eclipse SDK/NetBeans?
If the compilation errors appear inside Eclipse SDK and not when
building with Ant on the command line, you may have to copy
ide/eclipse/.classpath to .classpath to reflect the dependency on the
sdes4j.jar library.

···

On Thu, Oct 6, 2011 at 10:32 AM, Patrick <java@ict-synergy.be> wrote:

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?


#12

Hi,

···

On Thu, Oct 6, 2011 at 10:32 AM, Patrick <java@ict-synergy.be> wrote:

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

How do you compile? Running ant rebuild from terminal works ok at my side.

Regards
damencho


#13

Thanks to all for the feedback.

The issue is that the ${username} ${password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

···

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
[java] java.lang.IllegalArgumentException: null owner window
[java] at java.awt.Window.ownedInit(Window.java:415)
[java] at java.awt.Window.<init>(Window.java:375)
[java] at java.awt.Dialog.<init>(Dialog.java:310)
[java] at javax.swing.JDialog.<init>(JDialog.java:329)
[java] at javax.swing.JDialog.<init>(JDialog.java:288)
[java] at javax.swing.JDialog.<init>(JDialog.java:269)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:63)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:104)
[java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:124)
[java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:108)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvider.getCredentials(HttpUtils.java:662)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:458)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:377)
[java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(ProvisioningActivator.java:507)
[java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(ProvisioningActivator.java:203)
[java] at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
[java] at
org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
[java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
[java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
[java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
[java] at java.lang.Thread.run(Thread.java:595)
[java] IOException in readRegistry: java.io.EOFException
[java] stream:error (host-unknown)
[java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
[java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
[java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the authentication
popup for ${username} and ${password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly finished
?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> >>>>>> wrote:

Other parameters that could be interesting to have in the
provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width
for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example
regularly use a multi-monitor setup, sometimes with different
resolution on
the two monitors (the Laptop's built-in display and an external 24"
screen).
In addition the primary monitor can be on the right. We'd need a
solution to
handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#14

Dear,

I had the time to dig into the code source and I found that the line
108 of the AuthenticationWindows is the following:

this(null, server, isUserNameEditable, icon);

This line calls finally the constructor of a JDialog that cannot a
support a null owner => java.lang.IllegalArgumentException: null owner
window

So, the error looks "normal" to me

I've checked the javadoc of more recent JDK and it's still the case,
JDialog cannot accept a null owner

I'm confused how it's working on your side. Am I in a special
condition where I don't use the same contructor than yours ?

Best regards,
Patrick

···

On Thu, Oct 6, 2011 at 16:07, Patrick <java@ict-synergy.be> wrote:

Thanks to all for the feedback.

The issue is that the ${username} ${password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
[java] java.lang.IllegalArgumentException: null owner window
[java] at java.awt.Window.ownedInit(Window.java:415)
[java] at java.awt.Window.<init>(Window.java:375)
[java] at java.awt.Dialog.<init>(Dialog.java:310)
[java] at javax.swing.JDialog.<init>(JDialog.java:329)
[java] at javax.swing.JDialog.<init>(JDialog.java:288)
[java] at javax.swing.JDialog.<init>(JDialog.java:269)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:63)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.java:104)
[java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:124)
[java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(AuthenticationWindow.java:108)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvider.getCredentials(HttpUtils.java:662)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:458)
[java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.java:377)
[java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(ProvisioningActivator.java:507)
[java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(ProvisioningActivator.java:203)
[java] at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
[java] at
org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
[java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
[java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
[java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
[java] at java.lang.Thread.run(Thread.java:595)
[java] IOException in readRegistry: java.io.EOFException
[java] stream:error (host-unknown)
[java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
[java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
[java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the authentication
popup for ${username} and ${password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly finished
?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if I
put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrieveConfigurationFile(String
url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.html#getDefaultScreenDevice()
)
After that, snap the windows to the right at the first provisioning
request. After, remove the positioning data from provisioning, so the
windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going to
feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> >>>>>>> wrote:

Other parameters that could be interesting to have in the
provisioning
URL is the resolution of the screen. This way, it would be easy to
snap Jitsy on the right side of the screen with a convenient width
for
the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example
regularly use a multi-monitor setup, sometimes with different
resolution on
the two monitors (the Laptop's built-in display and an external 24"
screen).
In addition the primary monitor can be on the right. We'd need a
solution to
handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#15

Well, although we still want to be compatible with JDK1.5 we obviously aren't :slight_smile:
For the time being, use the JDK1.6.0_27 and set compiler compliance level in Eclipse to 1.5 (right click on the project -> Properties -> Java Compiler).

Emil: as nobody noticed up until now, drop it finally? See the discussion on the JSIP list well.

Ingo

···

-----Original Message-----
From: nollet.patrick@gmail.com [mailto:nollet.patrick@gmail.com] On Behalf
Of Patrick
Sent: Donnerstag, 6. Oktober 2011 16:08
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: \{resX\} {resY} provisioning parameter
Thanks to all for the feedback.

The issue is that the \{username\} {password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
[java] java.lang.IllegalArgumentException: null owner window
[java] at java.awt.Window.ownedInit(Window.java:415)
[java] at java.awt.Window.<init>(Window.java:375)
[java] at java.awt.Dialog.<init>(Dialog.java:310)
[java] at javax.swing.JDialog.<init>(JDialog.java:329)
[java] at javax.swing.JDialog.<init>(JDialog.java:288)
[java] at javax.swing.JDialog.<init>(JDialog.java:269)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:63)

 \[java\]    at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:104)

 \[java\]    at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:124)

 \[java\]    at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:108)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvid
er.getCredentials(HttpUtils.java:662)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:458)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:377)

 \[java\]    at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(ProvisioningActivator.java:507)

 \[java\]    at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(
ProvisioningActivator.java:203)

 \[java\]    at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.j
ava:629)

 \[java\]    at

org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
[java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
[java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
[java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
[java] at java.lang.Thread.run(Thread.java:595)
[java] IOException in readRegistry: java.io.EOFException
[java] stream:error (host-unknown)
[java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
[java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
[java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the
authentication popup for \{username\} and {password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly
finished ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if
I put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(String

url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.
html#getDefaultScreenDevice()

) After that, snap the windows to the right at the first
provisioning request. After, remove the positioning data from
provisioning, so the windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going
to feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs >>>>>>> Ingo<ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the
provisioning URL is the resolution of the screen. This way, it
would be easy to snap Jitsy on the right side of the screen
with a convenient width for the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example regularly use a multi-monitor setup, sometimes with
different resolution on the two monitors (the Laptop's built-in
display and an external 24" screen). In addition the primary
monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#16

Hey Ingo,

На 08.10.11 14:58, Bauersachs Ingo написа:

Well, although we still want to be compatible with JDK1.5 we obviously aren't :slight_smile:

Eeer ... not sure why you say this. All our builds go through a mac that
creates the DMGs on a 1.5 java.

For the time being, use the JDK1.6.0_27 and set compiler compliance level in Eclipse to 1.5 (right click on the project -> Properties -> Java Compiler).

I just did a successful build with 1.5's javac. Not sure what you are
seeing in Eclipse but it's obviously being overly cautions.

Emil: as nobody noticed up until now, drop it finally? See the discussion on the JSIP list well.

Is there anything in J6 that you think we'd benefit from and that breaks
backward compatibility?

Emil

···

Ingo

-----Original Message-----
From: nollet.patrick@gmail.com [mailto:nollet.patrick@gmail.com] On Behalf
Of Patrick
Sent: Donnerstag, 6. Oktober 2011 16:08
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: \{resX\} {resY} provisioning parameter
Thanks to all for the feedback.

The issue is that the \{username\} {password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
     [java] java.lang.IllegalArgumentException: null owner window
     [java] at java.awt.Window.ownedInit(Window.java:415)
     [java] at java.awt.Window.<init>(Window.java:375)
     [java] at java.awt.Dialog.<init>(Dialog.java:310)
     [java] at javax.swing.JDialog.<init>(JDialog.java:329)
     [java] at javax.swing.JDialog.<init>(JDialog.java:288)
     [java] at javax.swing.JDialog.<init>(JDialog.java:269)
     [java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:63)

     [java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:104)

     [java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:124)

     [java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:108)

     [java] at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvid
er.getCredentials(HttpUtils.java:662)

     [java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:458)

     [java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:377)

     [java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(ProvisioningActivator.java:507)

     [java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(
ProvisioningActivator.java:203)

     [java] at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.j
ava:629)

     [java] at
org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
     [java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
     [java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
     [java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
     [java] at java.lang.Thread.run(Thread.java:595)
     [java] IOException in readRegistry: java.io.EOFException
     [java] stream:error (host-unknown)
     [java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
     [java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
     [java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the
authentication popup for \{username\} and {password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly
finished ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if
I put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(String

url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.
html#getDefaultScreenDevice()

) After that, snap the windows to the right at the first
provisioning request. After, remove the positioning data from
provisioning, so the windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going
to feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs >>>>>>>> Ingo<ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the
provisioning URL is the resolution of the screen. This way, it
would be easy to snap Jitsy on the right side of the screen
with a convenient width for the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example regularly use a multi-monitor setup, sometimes with
different resolution on the two monitors (the Laptop's built-in
display and an external 24" screen). In addition the primary
monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#17

Dear Dev team,

Please find attached my first (tiny) contribution to Jitsi.

Feel free to rename resx and resy with the name you want if more
meaningful for the community

I'm already looking for my next contrib :wink:

Best regards,
Patrick

Index_ src_net_java_sip_communicator_plugin_provisioning_ProvisioningActivator.java.txt (1.47 KB)

···

On Sat, Oct 8, 2011 at 14:58, Bauersachs Ingo <ingo.bauersachs@fhnw.ch> wrote:

Well, although we still want to be compatible with JDK1.5 we obviously aren't :slight_smile:
For the time being, use the JDK1.6.0_27 and set compiler compliance level in Eclipse to 1.5 (right click on the project -> Properties -> Java Compiler).

Emil: as nobody noticed up until now, drop it finally? See the discussion on the JSIP list well.

Ingo

-----Original Message-----
From: nollet.patrick@gmail.com [mailto:nollet.patrick@gmail.com] On Behalf
Of Patrick
Sent: Donnerstag, 6. Oktober 2011 16:08
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: ${resX} ${resY} provisioning parameter
Thanks to all for the feedback.

The issue is that the ${username} ${password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent <seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
[java] java.lang.IllegalArgumentException: null owner window
[java] at java.awt.Window.ownedInit(Window.java:415)
[java] at java.awt.Window.<init>(Window.java:375)
[java] at java.awt.Dialog.<init>(Dialog.java:310)
[java] at javax.swing.JDialog.<init>(JDialog.java:329)
[java] at javax.swing.JDialog.<init>(JDialog.java:288)
[java] at javax.swing.JDialog.<init>(JDialog.java:269)
[java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:63)

 \[java\]    at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:104)

 \[java\]    at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:124)

 \[java\]    at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:108)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvid
er.getCredentials(HttpUtils.java:662)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:458)

 \[java\]    at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:377)

 \[java\]    at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(ProvisioningActivator.java:507)

 \[java\]    at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(
ProvisioningActivator.java:203)

 \[java\]    at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.j
ava:629)

 \[java\]    at

org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
[java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
[java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
[java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
[java] at java.lang.Thread.run(Thread.java:595)
[java] IOException in readRegistry: java.io.EOFException
[java] stream:error (host-unknown)
[java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
[java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
[java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the
authentication popup for ${username} and ${password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly
finished ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if
I put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(String

url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.
html#getDefaultScreenDevice()

) After that, snap the windows to the right at the first
provisioning request. After, remove the positioning data from
provisioning, so the windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going
to feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs >>>>>>>> Ingo<ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the
provisioning URL is the resolution of the screen. This way, it
would be easy to snap Jitsy on the right side of the screen
with a convenient width for the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example regularly use a multi-monitor setup, sometimes with
different resolution on the two monitors (the Laptop's built-in
display and an external 24" screen). In addition the primary
monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#18

Hey

Well, although we still want to be compatible with JDK1.5 we obviously
aren't :slight_smile:

Eeer ... not sure why you say this. All our builds go through a mac that
creates the DMGs on a 1.5 java.

Ahm, yes the build, but maybe not at runtime?

For the time being, use the JDK1.6.0_27 and set compiler compliance
level in Eclipse to 1.5 (right click on the project -> Properties ->
Java Compiler).

I just did a successful build with 1.5's javac. Not sure what you are
seeing in Eclipse but it's obviously being overly cautions.

The point of that was to get it to run under Windows. At least Patrick sees an exception with JDK5 on Windows. So the obvious setup is to use JDK6 and set the compiler compliance to 1.5. That catches at least the @Override annotations of interfaces.

Emil: as nobody noticed up until now, drop it finally? See the
discussion on the JSIP list well.

Is there anything in J6 that you think we'd benefit from and that breaks
backward compatibility?

For example there's the IOException constructor that takes a nested exception. @Override for interfaces (makes the code a little bit safer). Some crypto stuff (e.g. the Windows CA root store access) is only available from JRE6 on (and JRE7 for 64bit). Kerberos (which I have on my personal roadmap). NetworkInterface.isX/getX native instead of through reflection. Native SystemTray/TrayIcon. Java 5 is EOL. Java 7 has its foot in the door.

Are we actually running (not building) on Java 5 _anywhere_? I once tried to run on JDK5 on Windows and it didn't work (can't remember the issues, but there were several and something different than the authentication window). I do see the argument Android, but that has to be handled differently than just relying on the JRE.

Ingo


#19

Hi Patrick,

Thank you.

Just for your information, in Jitsi project we try to follow coding style convention as specified at http://jitsi.org/index.php/Documentation/CodeConvention in order to keep code consistent.

So in your future patch, try to follow the convetion ;).

To summarize what needs to be done in your patch: no tabs (4 spaces indent as replacement), bracket on its own line, no indent for brackets, always use package import (import java.awt.* instead of import java.awt.Window).

Regards,

···

--
Seb

Le 13/10/11 22:06, Patrick a écrit :

Dear Dev team,

Please find attached my first (tiny) contribution to Jitsi.

Feel free to rename resx and resy with the name you want if more
meaningful for the community

I'm already looking for my next contrib :wink:

Best regards,
Patrick

On Sat, Oct 8, 2011 at 14:58, Bauersachs Ingo<ingo.bauersachs@fhnw.ch> wrote:

Well, although we still want to be compatible with JDK1.5 we obviously aren't :slight_smile:
For the time being, use the JDK1.6.0_27 and set compiler compliance level in Eclipse to 1.5 (right click on the project -> Properties -> Java Compiler).

Emil: as nobody noticed up until now, drop it finally? See the discussion on the JSIP list well.

Ingo

-----Original Message-----
From: nollet.patrick@gmail.com [mailto:nollet.patrick@gmail.com] On Behalf
Of Patrick
Sent: Donnerstag, 6. Oktober 2011 16:08
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: ${resX} ${resY} provisioning parameter
Thanks to all for the feedback.

The issue is that the ${username} ${password} popup not showing up. I
receive the provided error in place of the popup and Jitsi continues
without provisioning. It occurs on windows 7 with JDK 1.5.
Any idea ?

For the comilation error, thank you for the missing library. I didn't
know which one was missing

Best regards,
Patrick

On Thu, Oct 6, 2011 at 10:49, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 06/10/11 09:32, Patrick a écrit :

Dear dev team,

I've started my first contribution to Jitsy with the availability of
screen resolution in the provisioning. I don't have questions about
the code but about testing.

I've started the 'rebuild' and 'run' targets to test my new code but,
I never see the authentication screen poping up. Jitsi is starting
ingnoring the provisioning request after throwing the following
stacktrace:

[java] 09:18:07.748 GRAVE: service.httputil.HttpUtils.postForm().405
Error posting form
      [java] java.lang.IllegalArgumentException: null owner window
      [java] at java.awt.Window.ownedInit(Window.java:415)
      [java] at java.awt.Window.<init>(Window.java:375)
      [java] at java.awt.Dialog.<init>(Dialog.java:310)
      [java] at javax.swing.JDialog.<init>(JDialog.java:329)
      [java] at javax.swing.JDialog.<init>(JDialog.java:288)
      [java] at javax.swing.JDialog.<init>(JDialog.java:269)
      [java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:63)

      [java] at

net.java.sip.communicator.util.swing.SIPCommDialog.<init>(SIPCommDialog.ja
va:104)

      [java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:124)

      [java] at

net.java.sip.communicator.util.swing.AuthenticationWindow.<init>(Authentic
ationWindow.java:108)

      [java] at

net.java.sip.communicator.service.httputil.HttpUtils$HTTPCredentialsProvid
er.getCredentials(HttpUtils.java:662)

      [java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:458)

      [java] at

net.java.sip.communicator.service.httputil.HttpUtils.postForm(HttpUtils.ja
va:377)

      [java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(ProvisioningActivator.java:507)

      [java] at

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.start(
ProvisioningActivator.java:203)

      [java] at

org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.j
ava:629)

      [java] at
org.apache.felix.framework.Felix.activateBundle(Felix.java:1827)
      [java] at
org.apache.felix.framework.Felix.startBundle(Felix.java:1744)
      [java] at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
      [java] at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
      [java] at java.lang.Thread.run(Thread.java:595)
      [java] IOException in readRegistry: java.io.EOFException
      [java] stream:error (host-unknown)
      [java] at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:260)
      [java] at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)
      [java] at
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)

Any idea how I should fix it and show the authentication popup ?

By authentication you mean htaccess like ? Or more just the
authentication popup for ${username} and ${password} parameters ?

Another think is that I've updated the project with repository's HEAD
and I've now compilation errors with SDES classes (classes that
couldn't be resolved). Do you also ave the same issue ?

On Mac OS X Leopard/Snow Leopard and Linux x86_64 I have no problem
compiling. What is your OS ? Are you sure SVN update has correctly
finished ?

@Vincent: In fact my question was more 'where should you want me to
put the screen size detection code; but after some researches I've
seen that the code was already existing in the ScreenInformation
class, so I've reused it :wink:

OK.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 15:47, Sebastien Vincent<seb@jitsi.org> wrote:

Hi Patrick,

Le 05/10/11 13:58, Patrick a écrit :

Hello Emil,

Of course, it's up to the provisioning server to take the "first prov
request" logic into account :slight_smile:

BTW, I'm new to Jitsi project so I'm wondering if you would be OK if
I put the resolution discovery snippet directly in the

net.java.sip.communicator.plugin.provisioning.ProvisioningActivator.retrie
veConfigurationFile(String

url) method
Or, you prefer another place ?

Yes it is the place to modify for new provisioning parameters.

Regards,
--
Seb

Best regards,
Patrick

On Wed, Oct 5, 2011 at 12:23, Emil Ivov<emcho@jitsi.org> wrote:

На 05.10.11 10:56, Patrick написа:

Hello Ingo,

The way I saw it was to use the default screen (using

http://download.oracle.com/javase/6/docs/api/java/awt/GraphicsEnvironment.
html#getDefaultScreenDevice()

) After that, snap the windows to the right at the first
provisioning request. After, remove the positioning data from
provisioning, so the windows will stay where the user has left it

Provisioning is happening every time Jitsi starts. If you are going
to feed positioning information you need to make sure that your
provisioning server would only do so the first time it encounters
someone.

Emil

What do you think ? Would it be convenient for everyone ?

Having system properties available from a generic mechanism is a
brilliant idea !

Best regards,
Patrick

On Wed, Oct 5, 2011 at 00:48, Bauersachs >>>>>>>>> Ingo<ingo.bauersachs@fhnw.ch> wrote:

Other parameters that could be interesting to have in the
provisioning URL is the resolution of the screen. This way, it
would be easy to snap Jitsy on the right side of the screen
with a convenient width for the resolution.

Sounds reasonable indeed. Feel free to log a feature request.

Just for reference: This is not as simple as it may seem. I for
example regularly use a multi-monitor setup, sometimes with
different resolution on the two monitors (the Laptop's built-in
display and an external 24" screen). In addition the primary
monitor can be on the right. We'd need a solution to handle that.

I already thought about extending the provisioning service in
general:
allow the ${x} replacement to accept any of the Java properties
available
through System.getProperty(x)

Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#20

For the time being, use the JDK1.6.0_27 and set compiler compliance
level in Eclipse to 1.5 (right click on the project -> Properties ->
Java Compiler).

I just did a successful build with 1.5's javac. Not sure what you are
seeing in Eclipse but it's obviously being overly cautions.

The point of that was to get it to run under Windows. At least Patrick sees an exception with JDK5 on Windows. So the obvious setup is to use JDK6 and set the compiler compliance to 1.5. That catches at least the @Override annotations of interfaces.

Jitsi's Windows setup deploys a private Java 1.6 so the Eclipse SDK
setup to use would be Java 1.5 at compile time to satisfy Jitsi's Java
1.5 compliance and Java 1.6 at runtime - Eclipse SDK easily supports
such a configuration.

Are we actually running (not building) on Java 5 _anywhere_? I once tried to run on JDK5 on Windows and it didn't work (can't remember the issues, but there were several and something different than the authentication window). I do see the argument Android, but that has to be handled differently than just relying on the JRE.

We need Java 1.5 for Mac OS X 10.5 at least. As stated above Jitsi on
Windows is deployed with Java 1.6 so there's no point in using Java
1.5 at runtime.

···

2011/10/10 Bauersachs Ingo <ingo.bauersachs@fhnw.ch>: