Sorry I missed the original thread.
I agree that using the urls in the capabilities document is the best way
to go as that is the whole point of the capabilities document.
It's just the prompting the user every time a WMS layer is added that I
wasn't too keen on (my project has 4 WMS layers).
Maybe I can propose a slight change to the suggestion of prompting for
accepting the getmap URL change. Have a boolean parameter called
useCabailitiesUrls which if set to true would just use the capabilities
document URLS and if false would prompt the user. Then extend the WMS
connection panel to have a check box so that the user can select if they
wish to use the urls defined in the capabilities document or the
original one.
Paul
*Paul Austin*
/President/CEO/
Revolution Systems Inc.
+1 (604) 288-4304 x201
www.revolsys.com <http://www.revolsys.com>
Rahkonen Jukka wrote:
Paul Austin wrote:
I noticed that someone added some functionality to display a
confirmation dialog if the URL in the capabilities document
is different from the service request URL. I'm not sure if
this is the best thing to do as it requires a lot of extra
key presses when you automatically add WMS layers in a
plugi-in. I presume this is there to stop people being
redirected to different sites. A suggestion I may make is
that if you say yes for a combination of source and
redirected URL it prompts you to confirm and then saves that
in the persistent blackboard so you never see that message again.
This change was done by Andreas Schmitz because of my suggestion.
Discussion was held on this mailing list a few days ago.
The purpose of this change was to make it possible to connect at all to
such WMS servers which are using a different URL for GetMap requests
than for GetCapabilities. Without this change OpenJUMP WMS blindly sent
all GetMap requests to the same address than used for the first
connection for GetCapabilities.
In theory it would be correct to always use that GetMap URL that is
returned with the GetCapabilities document. In real life just few WMS
servers are really using separate GetMap URL, even they may advertise
so. Usually it does not harm anybody, because many, if not most clients
behave just like OpenJUMP and never read the GetMap URL or try to use
it. This solution was made to allow
- directing GetMap requests to GetMap URL if it really works
- directing GetMap requests to GetCapabilities URL if it works but
GetMap URL is wrong
I had a certain WMS service in my mind when asking about this feature.
Unfortunately that site has another speciality in configuration that
prevents me to use it even the GetMap URL is now read from the
GetCapabilities document.
-Jukka Rahkonen-
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
