Hi all,
due to a mistake of mine we released rc2 and rc3 with an
oversized release directory that had quite a few
references to external wfs servers... this is not so nice.
I've hopefully fixed this on both 1.6.x and trunk: can you
test and confirm it works for you too?
Cheers
Andrea
well, I thought it was intentional and seemed like a nice idea to me. Yet I
have to recognize that even if I saw them I din't tried if they worked.
I've updated and tested the release config, it seems to be alright.
cheers,
Gabriel
On Friday 18 January 2008 03:26:43 pm Andrea Aime wrote:
Hi all,
due to a mistake of mine we released rc2 and rc3 with an
oversized release directory that had quite a few
references to external wfs servers... this is not so nice.
I've hopefully fixed this on both 1.6.x and trunk: can you
test and confirm it works for you too?Cheers
Andrea-------------------------------------------------------------------------
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/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4045,4790b73b8461439371379!
Gabriel Roldán ha scritto:
well, I thought it was intentional and seemed like a nice idea to me. Yet I have to recognize that even if I saw them I din't tried if they worked.
Yeah, I understand why you think it's nice from a demo point of view.
Unfortunately the wfs datastore is not really super, it might get
stuck if the remote server does not respond... which is very very
ugly (they did not use commons-httpclient which would have allowed
to set a timeout on requests...)
I've updated and tested the release config, it seems to be alright.
Nice
Cheers
Andrea
On Friday 18 January 2008 03:44:22 pm Andrea Aime wrote:
Gabriel Roldán ha scritto:
> well, I thought it was intentional and seemed like a nice idea to me. Yet
> I have to recognize that even if I saw them I din't tried if they worked.Yeah, I understand why you think it's nice from a demo point of view.
Unfortunately the wfs datastore is not really super, it might get
stuck if the remote server does not respond... which is very very
ugly (they did not use commons-httpclient which would have allowed
to set a timeout on requests...)
ok. We can set a read timeout as well as a connect timeout on trunk now that
we're on Java5. For 1.6 hacking wfs I guess is not worth it 
(or at least I
don't have the time right now)
Gabriel
> I've updated and tested the release config, it seems to be alright.
Nice
Cheers
Andrea!DSPAM:4045,4790bb4a15821439371379!