On Fri, Sep 28, 2012 at 9:40 AM, Ben Caradoc-Davies <
ben.caradoc-dav...@csiro.au> wrote:
> On 18/09/12 16:54, Andrea Aime wrote:
>
>> Ha, good question, have no idea, have you tried setting a breakpoint in
>> that portion of the dispatcher and see
>> what's going on?
>> Also put a breakpoint in s
It sounds as though you are running into the Same-Origin Policy enforced by
all modern browsers: http://en.wikipedia.org/wiki/Same_origin_policy
The usual technique for dealing with this is to use Apache to proxy
GeoServer so that it appears on the same port as your OpenLayers
application. You ca
Hello,
I am facing one problem while working on GeoServer. I am working on
getfeatureinfo. I have written a Java script for my application where I am
trying to send the request using URL on Geoserver (i.e localhost:8080) which
I want it to reflect on Apache Server. But unfortunately it is reflecti
Clarification: *without* -nsu, snapshots are always checked for updates,
and releases are not. *With* -nsu, they are treated the same and only
downloaded if missing. So with -nsu you can have the benefit of being
online to download missing dependencies without unexpected snapshot
checks or snap
I build using "-nsu" (no snapshot updates), a new flag present in Maven
3.0.4 or later. This is a great way (IMHO) to build GeoServer against
known-version local builds of GeoTools and GeoWebcache (its only
snapshot dependencies) without risking an unintended download of remote
snapshots. It al
On 18/09/12 16:54, Andrea Aime wrote:
> Ha, good question, have no idea, have you tried setting a breakpoint in
> that portion of the dispatcher and see
> what's going on?
> Also put a breakpoint in setCiteCompliant, the dispatcher has to
> manually be set that way by a
> interceptor, normally the
Bart van
Hey folks, just a quick tip Andrea thought I should send to the list since
it might be useful for others.
Anyone who builds a maven project that depends on geotools snapshot
dependencies has felt the following pain.
1. You update
2. Do an offline build, which fails because someone added a new lib
