Hi,
here is the pull request, with pluggable GeoServerNodeInfo, docs and tests
https://github.com/geoserver/geoserver/pull/539
Cheers
Andrea
--
==
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
On Wed, Mar 12, 2014 at 8:43 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Looks pretty great to me Andrea. Nice work.
Thank you.
Talking internally in GeoSolutions, we found an extra need, an ability for
a plugin to setup
its own id and style (which might be coming up from custom
On Thu, Mar 13, 2014 at 3:55 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Wed, Mar 12, 2014 at 8:43 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Looks pretty great to me Andrea. Nice work.
Thank you.
Talking internally in GeoSolutions, we found an extra need, an
On Thu, Mar 13, 2014 at 4:33 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
On Thu, Mar 13, 2014 at 3:55 AM, Andrea Aime andrea.a...@geo-solutions.it
wrote:
On Wed, Mar 12, 2014 at 8:43 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Looks pretty great to me Andrea.
Hmmm... how about using the same terminology as the system properties:
interface GeoServerNodeInfo {
String getId();
MapString,String getOptions();
}
There was actually a reason, the style that sits behind the identifier
element is build
from this template:
position:absolute;
That would work for me. However perhaps if we want to give full control in
terms of layout perhaps we should do something like this.
GeoServerNodeInfo {
String getId();
WebMarkupContainer render(MarkupContainer parent);
}
And then with a subclass that creates a single element with a css stye
On Thu, Mar 13, 2014 at 4:49 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
That would work for me. However perhaps if we want to give full control in
terms of layout perhaps we should do something like this.
GeoServerNodeInfo {
String getId();
WebMarkupContainer
On Fri, Feb 28, 2014 at 7:06 PM, Ian Schneider
ischnei...@boundlessgeo.comwrote:
Great idea. What about by default
using java.net.InetAddress.getLocalHost() ?
Nice for anyone with multiple instances, clustered or not.
Hmm... not sure we want to have this visible in every page unless the
On Fri, Feb 28, 2014 at 8:20 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Like the idea too. But how about rather than adding a bunch of different
options for different aspect of the display we just add one, and it behaves
like format options. So something like:
I have not used nodes in a cluster before. My understanding is that nodes
are not used to configure the common data directory - as such would it be
appropriate to place this note in the login area?
Jody Garnett
On Tue, Mar 4, 2014 at 9:02 PM, Andrea Aime andrea.a...@geo-solutions.itwrote:
On
On Tue, Mar 4, 2014 at 12:10 PM, Jody Garnett jody.garn...@gmail.comwrote:
I have not used nodes in a cluster before. My understanding is that nodes
are not used to configure the common data directory - as such would it be
appropriate to place this note in the login area?
The screenshot
On Tue, Mar 4, 2014 at 3:02 AM, Andrea Aime andrea.a...@geo-solutions.itwrote:
On Fri, Feb 28, 2014 at 8:20 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Like the idea too. But how about rather than adding a bunch of different
options for different aspect of the display we just add
On Tue, Mar 4, 2014 at 5:11 PM, Justin Deoliveira jdeol...@boundlessgeo.com
wrote:
Yep, that would work also.
It may not mix too well with CQL expression/variable expansion parsing
though (e.g., we'd need escapes, or start/end markers).
Some bright ideas on how to approach this? Trying to
On Tue, Mar 4, 2014 at 9:14 AM, Andrea Aime andrea.a...@geo-solutions.itwrote:
On Tue, Mar 4, 2014 at 5:11 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Yep, that would work also.
It may not mix too well with CQL expression/variable expansion parsing
though (e.g., we'd need
On Tue, Mar 4, 2014 at 5:25 PM, Justin Deoliveira jdeol...@boundlessgeo.com
wrote:
On Tue, Mar 4, 2014 at 9:14 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Tue, Mar 4, 2014 at 5:11 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
Yep, that would work also.
It may not
On Tue, Mar 4, 2014 at 9:29 AM, Andrea Aime andrea.a...@geo-solutions.itwrote:
On Tue, Mar 4, 2014 at 5:25 PM, Justin Deoliveira
jdeol...@boundlessgeo.com wrote:
On Tue, Mar 4, 2014 at 9:14 AM, Andrea Aime andrea.a...@geo-solutions.it
wrote:
On Tue, Mar 4, 2014 at 5:11 PM, Justin
Hi,
I'm looking into this requirement of making GeoServer instances in a cluster
identifiable at a glance, mostly to help admins gets their bearings when
managing multiple nodes or multiple clusters.
The idea would be to have two new optional system variables that would make
a
node label appear
Great idea. What about by default using java.net.InetAddress.getLocalHost()
?
Nice for anyone with multiple instances, clustered or not.
On Fri, Feb 28, 2014 at 10:15 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
Hi,
I'm looking into this requirement of making GeoServer instances in a
Like the idea too. But how about rather than adding a bunch of different
options for different aspect of the display we just add one, and it behaves
like format options. So something like:
-DGEOSERVER_NODE_OPTS=id:wppgeog1;color:FF
This would also leave it open ended to be able to perhaps
19 matches
Mail list logo
