In GeoServer 1.7 it was possible to reload (Load/Apply) the configuration via the web user interface. Is this possible in the new Wicket UI in GeoServer trunk / 2.0 beta?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies wrote:
In GeoServer 1.7 it was possible to reload (Load/Apply) the configuration via the web user interface. Is this possible in the new Wicket UI in GeoServer trunk / 2.0 beta
This may get retracted when the other side of the globe wakes up:
I believe that disappeared when Submit + Apply + Save was merged into "Ok". Mangling the UI configuration files outside the UI has never been supported, so I'm not sure it was brought up when we discussed this on the dev list* about a year ago.
Can always reload the servlet, it has much of the same effect anyway.
-Arne
*: " New UI: The Persistence of Save (or The Saving of Persist)" , "Temp vs persistent"
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Ben Caradoc-Davies ha scritto:
In GeoServer 1.7 it was possible to reload (Load/Apply) the configuration via the web user interface. Is this possible in the new Wicket UI in GeoServer trunk / 2.0 beta?
If you want a full reload, as long as you're running in development
mode the "developer toolbar" shows up and has a button that does
that.
If you're running in deployment mode nope, no chance, thought I
believe we want one (think people fiddling manually with the
config files for... oh yeah, setting up app schema configurations
for example 
)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Arne Kepp wrote:
Can always reload the servlet, it has much of the same effect anyway.
OK. I'll need to enable and configure the manager servlet, though.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Andrea Aime wrote:
Ben Caradoc-Davies ha scritto:
In GeoServer 1.7 it was possible to reload (Load/Apply) the configuration via the web user interface. Is this possible in the new Wicket UI in GeoServer trunk / 2.0 beta?
If you want a full reload, as long as you're running in development
mode the "developer toolbar" shows up and has a button that does
that.
If you're running in deployment mode nope, no chance, thought I
believe we want one (think people fiddling manually with the
config files for... oh yeah, setting up app schema configurations
for example
I would not be against a "reload" feature, but I can see it quickly turning into a crutch. I foresee it not acting exactly like the old one with not everything actually getting reloaded. I fear us having to spend time reimplementing the the load/save functionality we have been working so hard to kill 
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Ben Caradoc-Davies ha scritto:
In GeoServer 1.7 it was possible to reload (Load/Apply) the configuration via the web user interface. Is this possible in the new Wicket UI in GeoServer trunk / 2.0 beta?
If you want a full reload, as long as you're running in development
mode the "developer toolbar" shows up and has a button that does
that.
If you're running in deployment mode nope, no chance, thought I
believe we want one (think people fiddling manually with the
config files for... oh yeah, setting up app schema configurations
for exampleI would not be against a "reload" feature, but I can see it quickly turning into a crutch. I foresee it not acting exactly like the old one with not everything actually getting reloaded. I fear us having to spend time reimplementing the the load/save functionality we have been working so hard to kill
Hmmm... I put it back in the dev toolbar because
restarting geoserver to get the same behaviour was too slow.
It helped in a number of occasion, particularly when debugging
geoserver or when dealing with the geoserver caps link being missing
upon data directory conversion.
I'd say to put it in some secondary page for users, like the status one.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.