Hi all,
Recently it was required that GeoServer have the ability to disable wfs
1.1. So what I did was moved wfs 1.1 to a new module so that to disable
wfs 1.1 all one must do is delete the jar for that (new) module. There
should be no difference for the normal user.
However this solution is f
If possible yes... although what we really need to do is have the
deprecated reflector delegate to the new reflector. Which should be
doable... just have to find the time :). So i leave it to you. If its
easy, sure, if not dont worry about it.
-Justin
Wayne Fang wrote:
> Hi Justin,
>
> Thank
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/324/changes
Changes:
[aaime] Fixing class names (this is an edit/remove component, not an add/remove
one)
--
[...truncated 5940 lines...]
at junit.framework.TestCase.runBare(TestCas
The links available in the mini-map preview of the featuretypes are not correct
---
Key: GEOS-2008
URL: http://jira.codehaus.org/browse/GEOS-2008
Project: GeoServer
Hi Justin,
Thanks for the response. So should I make my changes to the
wms.servlets.KMLReflector as well, knowing that it is deprecated but
still in use?
Thanks,
Wayne
Justin Deoliveira wrote:
> Hi Wayne,
>
> While deprecated, the wms.servlets.KMLReflector is still used
> unfortunatly. Its a
Andrea Aime wrote:
> I'm ok with that. As an alternative, I'm open to take what you
> cooked up so far and try to take it to a completion so that
> we can release following the usual rules.
>
> What about the other PMC members. Anyone interested in expressing
> his thoughts? Do we have a GeoServer
Thanks for the review Andrea.
>>
>> I have found xstream to be very flexible and straight forward.
>> Tweaking the default settings and adding in some custom stuff I have
>> been able to output xml which looks pretty close to what we actually
>> output today.
>>
>> Comments/concerns/feedback we
Yeah, I think undo/redo is a cool idea, but in the desire to cut scope
I'm inclined to go with David's suggestion in the short term - just have
an 'export' or 'save as' button, so that an admin can save it at a point
that he wants. In 2.1 or something we could try out the undo/redo,
which I ag
Alessio Fabiani wrote:
Just two quick things:
1. Yes we definitely need a smart full layer preview list, which is
usually the page that the scientists use to have a quick review of their
products ingested in GeoServer
Yeah, I think the thought was to eventually have the full layer previe
> Ouch, merge them? Last time I checked the xml schemas of the two specs
> where so different that a single module trying to address them seemed
> very hard to achieve. Do you have a plan on how to deal with that?
>
> Don't get me wrong, having a single wcs module able to handle
> both wcs 1.0
Oops, one of those 'CoverageStore Management' entries should have been
just 'Coverage Management.' Thanks for catching this.
-David
Alessio Fabiani wrote:
> Just two quick things:
>
> 1. Yes we definitely need a smart full layer preview list, which is
> usually the page that the scientists use
Justin Deoliveira ha scritto:
> Hi all,
>
> I just added a class called "org.geoserver.config.util.XStreamPersister"
> which I hope will become the base of taking config objects back to xml
> land and back. I am hoping it will also be of use to David's REST stuff.
>
> I have found xstream to be
Alessio Fabiani ha scritto:
> On GeoTools side yes, my intention would be to create a new module under
> the xsd parser and on GeoServer side to merge WCS 1.0.0 and 1.1.1 models.
Ouch, merge them? Last time I checked the xml schemas of the two specs
where so different that a single module trying
On GeoTools side yes, my intention would be to create a new module under the
xsd parser and on GeoServer side to merge WCS 1.0.0 and 1.1.1 models.
On Thu, Jun 26, 2008 at 11:02 AM, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Alessio Fabiani ha scritto:
>
>> It is almost the same for me, just want to
Alessio Fabiani ha scritto:
> It is almost the same for me, just want to remember that I'm working
> right now on the WCS 1.0.0 EMF refactoring that would introduce several
> changes on geotools side also.
Several changes as in? A new module under the xsd parser? Or
you're talking about changes
Just two quick things:
1. Yes we definitely need a smart full layer preview list, which is usually
the page that the scientists use to have a quick review of their products
ingested in GeoServer
2. In the Wicket UI TODO list the statement "CoverageStore Management" is
repeated two times
On Thu,
It is almost the same for me, just want to remember that I'm working right
now on the WCS 1.0.0 EMF refactoring that would introduce several changes on
geotools side also.
On Wed, Jun 25, 2008 at 9:39 PM, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Justin Deoliveira ha scritto:
> > I have not had mu
Alessio Fabiani ha scritto:
> Hi guys,
>
> I almost agree with you David, and also I think RESTConfig should not be
> included into 1.7.x release at least in this very incomplete state, but
> anyway it is a valid alternative to interact with GS catalog
> configuration ... so what I'm thinking i
John Preston ha scritto:
> I have some shape files that I want to use in geoserver (read only), but
> they are stored within zip files, and I don't want to have to unzip them
> to other directories. I was thinking of writing my own datastore based
> on the existing one for shape files, and just
Hi guys,
I almost agree with you David, and also I think RESTConfig should not be
included into 1.7.x release at least in this very incomplete state, but
anyway it is a valid alternative to interact with GS catalog configuration
... so what I'm thinking is that maybe we can distribute it as a GeoS
http://java.dzone.com/news/wicket-creating-restful-urls
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/inde
21 matches
Mail list logo
