Cc: Geotools-Devel list; Tey, Victor (CESRE, Kensington); Angreani, Rini
(CESRE, Kensington)
Subject: Re: [Geotools-devel] removing xerces dependency
Thanks, Justin. My patch was not expected to fix the
SecondaryNamespaceExceptionTest failure.
I recall that SecondaryNamespaceExceptionTest tests
] removing xerces dependency
Thanks, Justin. My patch was not expected to fix the
SecondaryNamespaceExceptionTest failure.
I recall that SecondaryNamespaceExceptionTest tests that an exception is
thrown if secondary namespaces are not defined (null). Once the external
xerces 2.7 is removed
Hey Ben,
So I rebased the xmlnodeps branch against the latest on master and i am
still having the same failure with the SecondaryNamespaceExceptionTest.
I pushed up newly rebased branches to my repos.
https://github.com/jdeolive/geoserver/tree/noxmldeps2
Thanks, Justin. My patch was not expected to fix the
SecondaryNamespaceExceptionTest failure.
I recall that SecondaryNamespaceExceptionTest tests that an exception is
thrown if secondary namespaces are not defined (null). Once the external
xerces 2.7 is removed (in favour of the internal
Hey Ben,
Wasn't waiting explicitly, this sort of just fell off in light of other
things to do. I will try this week to resurrect this. As I understand it
the app-schema issues have been resolved now?
-Justin
On Mon, Jan 21, 2013 at 7:03 PM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au
Thanks, Justin.
The gt-app-schema-resolver Xerces dependency you found is resolved in
the pull request linked below. This patch is against your noxmldeps
branch; everything works when it is applied, except that xmlcodegen does
not build (I commented it out while testing), and one unit test
Justin,
at Monday's meeting we were wondering if you have had time to progress
the removal of (external) Xerces dependencies. My understanding is that
you were pretty close. Or are you waiting until after this release cycle?
Kind regards,
Ben.
On 02/11/12 15:43, Ben Caradoc-Davies wrote:
Justin,
I ported AppSchemaValidator to use EntityResolver2, required for
relative schema locations:
https://github.com/jdeolive/geotools/pull/1
Note that xmlcodegen still fails to build (I commented it out for testing).
With noxmldeps GeoTools, there is a unit test failure in GeoServer
Nice. Thanks Ben!
On Fri, Nov 2, 2012 at 1:43 AM, Ben Caradoc-Davies
ben.caradoc-dav...@csiro.au wrote:
Justin,
I ported AppSchemaValidator to use EntityResolver2, required for relative
schema locations:
On Thu, Oct 25, 2012 at 9:24 PM, Gabriel Roldan grol...@opengeo.org wrote:
re xerces, we'd also need to exclude it from the JTS dependency:
[INFO] | +- com.vividsolutions:jts:jar:1.12:compile
[INFO] | | \- xerces:xercesImpl:jar:2.7.1:compile (version managed from
2.4.0)
I'm in favor of
re xerces, we'd also need to exclude it from the JTS dependency:
[INFO] | +- com.vividsolutions:jts:jar:1.12:compile
[INFO] | | \- xerces:xercesImpl:jar:2.7.1:compile (version managed from 2.4.0)
I'm in favor of reducing the number of embedded databases, but taking
bdb je off might be good
On 26 October 2012 06:24, Gabriel Roldan grol...@opengeo.org wrote:
re xerces, we'd also need to exclude it from the JTS dependency:
[INFO] | +- com.vividsolutions:jts:jar:1.12:compile
[INFO] | | \- xerces:xercesImpl:jar:2.7.1:compile (version managed from
2.4.0)
The JTS jars from Maven
On Thu, Oct 25, 2012 at 5:48 PM, Michael Bedward
michael.bedw...@gmail.comwrote:
On 26 October 2012 06:24, Gabriel Roldan grol...@opengeo.org wrote:
re xerces, we'd also need to exclude it from the JTS dependency:
[INFO] | +- com.vividsolutions:jts:jar:1.12:compile
[INFO] | | \-
Thanks for that explanation Justin.
I know Martin still tries to cater for Java 1.5 but xerces is not
used in any of the core classes that make up the JTS maven artifacts.
Michael
On 26 October 2012 10:40, Justin Deoliveira jdeol...@opengeo.org wrote:
Btw, i did this on the branch i pushed
On Tue, Oct 23, 2012 at 7:49 PM, Chris Holmes chol...@opengeo.org wrote:
However, it does not make sense to duplicate what we already have for
free, either.
If it's not too much trouble, why not remove those as well?
+1 - seems like removing them could help more with like our weird memory
On Wed, Oct 24, 2012 at 2:45 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Tue, Oct 23, 2012 at 7:49 PM, Chris Holmes chol...@opengeo.org wrote:
However, it does not make sense to duplicate what we already have for
free, either.
If it's not too much trouble, why not remove those
On Tue, Oct 23, 2012 at 1:49 PM, Chris Holmes chol...@opengeo.org wrote:
On Tue, Oct 23, 2012 at 9:08 AM, Andrea Aime andrea.a...@geo-solutions.it
wrote:
On Tue, Oct 23, 2012 at 2:59 PM, Justin Deoliveira jdeol...@opengeo.org
wrote:
Indeed. And also while we are at it i will pose the
Having poked around with MAT (http://www.eclipse.org/mat/) a few weeks
back, I think we'll get a decent win by avoiding the use of two embedded
database solutions. Both H2 and BerkeleyDB had disk caches taking up
around 4MB in my minimally configured GeoServer test instance.
--
David Winslow
So what do we have let for embedded database solution? hsql for gt-epsg-hsql
...
--
Jody Garnett
On Thursday, 25 October 2012 at 12:02 AM, David Winslow wrote:
Having poked around with MAT (http://www.eclipse.org/mat/) a few weeks back,
I think we'll get a decent win by avoiding the use
However, it does not make sense to duplicate what we already have for
free, either.
If it's not too much trouble, why not remove those as well?
+1 - seems like removing them could help more with like our weird memory
bloat more than the actual download size no?
Just so everyone is clear
On Tue, Oct 23, 2012 at 2:29 AM, Justin Deoliveira jdeol...@opengeo.orgwrote:
Hi all,
So I recently I took a crack at removing the xerces dependency as we
discussed in our last skype meeting. For the most part this was relatively
straight forward. Unfortunately one thing i wasn't quite able
On Tue, Oct 23, 2012 at 3:02 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Tue, Oct 23, 2012 at 2:29 AM, Justin Deoliveira
jdeol...@opengeo.orgwrote:
Hi all,
So I recently I took a crack at removing the xerces dependency as we
discussed in our last skype meeting. For the most part
On Tue, Oct 23, 2012 at 2:59 PM, Justin Deoliveira jdeol...@opengeo.org wrote:
Indeed. And also while we are at it i will pose the question. There is also
the opportunity to prune out some other xml dependencies as well. Namely
jdom, xpp and stax from what i can tell. All seem to have
On Tue, Oct 23, 2012 at 9:08 AM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Tue, Oct 23, 2012 at 2:59 PM, Justin Deoliveira jdeol...@opengeo.org
wrote:
Indeed. And also while we are at it i will pose the question. There is
also
the opportunity to prune out some other xml
Hi all,
So I recently I took a crack at removing the xerces dependency as we
discussed in our last skype meeting. For the most part this was relatively
straight forward. Unfortunately one thing i wasn't quite able to figure out
was some stuff in app-schema-resolver module. The AppSchemaValidator
25 matches
Mail list logo
