Re: [JPP-Devel] [jump-pilot:bugs] #484 WMS Authentification fails

2019-02-23 Thread Stefan Steiniger
Hi Michael, As you said you may need another uncertified url to test: you can try with GeoNode demo, or my GeoNode instance: http://datos.cedeus.cl (both with GeoServer backend) Cheers, Stefan On Sat, Feb 23, 2019, 08:36 Michaël Michaud, wrote: > Ede, > > I moved the URLConnection strategy

Re: [JPP-Devel] [jump-pilot:bugs] #484 WMS Authentification fails

2019-02-23 Thread Michaël Michaud
Ede, I moved the URLConnection strategy into a separate class. It will be easier to share if another service (WFS?) needs it. I also added the persistance mechanism with PersistantBlackboard. I tried to set the authorization on a per URL basis rather than globally. In fact, I still use the

[JPP-Devel] SVN: [6136] core/trunk/src

2019-02-23 Thread jump-pilot-svn--- via Jump-pilot-devel
Revision: 6136 http://sourceforge.net/p/jump-pilot/code/6136 Author: michaudm Date: 2019-02-23 11:27:51 + (Sat, 23 Feb 2019) Log Message: --- Move the URLConnection strategy into a separate class (URLConnectionProvider) Modified Paths: --

Re: [JPP-Devel] SVN: [6134] core/trunk/src

2019-02-23 Thread Michaël Michaud
Hi, Stefan, I don't know how the server ensure backward compatibility, but I think that in OpenJUMP, the version always represent the version given in the request through the version parameter url?SERVICE=WMS&*VERSION*=1.3.0 This version is chosen by the user in URLWizardPanel and is used