Andreas Schmitz wrote: >Rahkonen Jukka wrote:
Hi, >> >> One quick question: Does anybody know directly if OpenJUMP is parsing >> >> the WMS >> >> GetCapabilities document and using the GetMap onlineresource that is >> >> advertised there? ... >> >no, unfortunately that does not work at the moment (the capabilities are >> >only >> >used to extract the layer tree IIRC). > >> Sad, but not surprising. Would it be very hard to implement? I know that >> many other clients do not support this either, and this information is also >> wrong in many WMS services. So the most robust WMS client should perhaps > >> - first take GetMap URL from the GetCapabilities document >> - if that fails, try next the same URL as used for GetCapabilities (the way >> it is now in OpenJUMP) >> - if even that fails let the user write any URL he wants > > yes, that's true, it's sad. I think it's not really worth the effort to change > the behaviour, as I cannot think of a scenario where it might be useful. I can > think of the following (all not applicable to WMS): > * a service can optionally be used via SOAP, so the SOAP URL will be different from the rest > * a service can be used transactionally, and for security reasons this uses a different URL > The problem is that one cannot determine the failure in the first step > properly. Does a connect error mean that the network is down or that the > server > is misconfigured? So in essence, changing the behaviour to the one you > suggested > means to obscure errors, making it possibly more difficult to debug networking > problems. Changing the behaviour to just use the capabilities' URLs breaks > "working" setups. So not changing the behaviour seems like a better option the > more one thinks about it... The service provider is much bigger authority than I. They say this way gives them a possibility to separate the requests on different servers for sharing the load in the future. I don't believe really that sending GetCapabilities is so extra heavy computitional task that it would ever deserve a dedicated server but this is the way they have decided to use and that's it. I will try to cascade the service through Mapserver, it should lead to a normal looking WMS service that could be accessed with OpenJUMP. -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
