Title: Message Title
alexandr bobrov created an issue
See http://ares.opengeo.org/jenkins/job/geoserver-master/1413/changes
Changes:
[tbarsballe] [GEOS-7038] Added support for prettyPrint to REST GET Style
--
[...truncated 26019 lines...]
[INFO] [GitCommitIdMojo] build.build.time = 22.05.2015 @ 20:07:49 UTC
See http://ares.opengeo.org/jenkins/job/geoserver-master/1414/
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance
On Thu, May 21, 2015 at 11:10 PM, Sen, Marcus A. m...@bgs.ac.uk wrote:
-Original Message-
From: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Sent: 20 May 2015 15:34
...
Normally we prefer to point to local hosted schemas, as opposed to remote
ones, because in some
Title: Message Title
Per Reinholdt created an issue
Hi Jody,
I think discussions have been resolved. For the time being we do not
plan any move away from restful in geoserver and we will keep the
user/role stuff as a bonus feature of geofence-server for now until it
is reimplemented in restful.
Just the spring bean issue (see other email)
On 22-05-15 12:28, Andrea Aime wrote:
Before I spend a lot of more time on this I wanted to check if you
guys had an easy solution. I noticed the commit adds a lot of
'lazy-init=false' to the bean definitions. Now the problem is
that this regards beans defined in the geofence
Hi,
thanks for the explanation.
Maybe Harrison - as the professional for the migration - could also fix the bad
display of any comment. Instead of showing the html tags they should be
interpreted. It would be a pity if we lose them.
Yours sincerely.
M.Sc. Robin Pradel
Senior Software
Hello Andrea and Jody,
There are two tests in geofence-server that are based on
GeoServerTestSupport to initialize the spring context.
They used to work fine but only since recently they started breaking,
and I traced it back to this commit you guys did:
On Fri, May 22, 2015 at 12:17 PM, Niels Charlier ni...@scitus.be wrote:
Hello Andrea and Jody,
There are two tests in geofence-server that are based on
GeoServerTestSupport to initialize the spring context.
They used to work fine but only since recently they started breaking, and
I traced
On Fri, May 22, 2015 at 1:23 PM, Niels Charlier ni...@scitus.be wrote:
For all clarity, with geofence modules I was talking about the actual
*geofence* backend modules themselves, not the community modules in
geoserver. Because the problem concerns beans declared in geofence itself,
not the
Okay, I found nothing on google but I have further debugged, as I had
expected it appears the problems are not caused by lazy initialization,
but by the following single line
On Fri, May 22, 2015 at 4:26 PM, Niels Charlier ni...@scitus.be wrote:
I would recommend removing that line altogether since it seems a
malfunction to me. Otherwise it must at least be made optional somehow
because at this point it is already too late to change when oneTimeSetUp is
run in my
On 22-05-15 16:28, Andrea Aime wrote:
On Fri, May 22, 2015 at 4:26 PM, Niels Charlier ni...@scitus.be
mailto:ni...@scitus.be wrote:
I would recommend removing that line altogether since it seems a
malfunction to me. Otherwise it must at least be made optional
somehow because at
Andrea,
Sorry I dropped off for awhile on this shapefile conversation. I was
wanting to add some unit tests, but wondered if I could get a pointer as to
how I'd test the shapefile with data including time. I looked through where
I understood all the test data to come from
Title: Message Title
Torben Barsballe created an issue
I just stumbled into this: https://osgeo-org.atlassian.net/browse/GEOS-7046
while using geoserver.
It turns out org.geoserver.catalog.impl.ResolvingProxy.handleOther()
overrides ProxyBase.handleOther() to always return null instead of excecute
the method. Does anyone have any idea why this is?
17 matches
Mail list logo
