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> wrote:
> 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<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
>> (app-schema-test SecondaryNamespaceExceptionTes**t). Looks like a side
>> effect of your dexercesification is that undefined namespace prefixes
>> (null:) are now passed through the GML32OutputFormat XSLT rather that
>> causing an ows:ExceptionReport. Not sure why. I also needed to remove
>> the xerces dependencies in the release module.
>>
>> Nice work! You are pretty close.
>>
>> Now just that pesky Xalan (app-schema GeoServer plugin, so off-topic).
>> Any XSLT gurus willing to help backport to Xalan 2.6 (in the JDK)?
>> https://jira.codehaus.org/**browse/GEOS-5352<https://jira.codehaus.org/browse/GEOS-5352>
>>
>> Kind regards,
>> Ben.
>>
>> On 23/10/12 08:29, Justin Deoliveira wrote:
>>
>>> 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 class uses an implementation of what
>>> was XMLEntityResolver directly in xerces. I tried porting this to the
>>> jaxp EntityResolver interface which is included in the JDK, but couldn't
>>> make it work. So I think i will need some help there. Or we can simply
>>> keep xerces as a dependency of just app-schema.
>>>
>>> Here is the branch I am currently working on.
>>>
>>> https://github.com/jdeolive/**geotools/tree/noxmldeps<https://github.com/jdeolive/geotools/tree/noxmldeps>
>>> And the corresponding geoserver branch:
>>>
>>> https://github.com/jdeolive/**geoserver/tree/noxmldeps<https://github.com/jdeolive/geoserver/tree/noxmldeps>
>>>
>>> WIth these changes all unit tests pass in both code bases, and so do the
>>> GeoServer cite tests.
>>>
>>> -Justin
>>>
>>> --
>>> Justin Deoliveira
>>> OpenGeo - http://opengeo.org
>>> Enterprise support for open source geospatial.
>>>
>>>
>>
> --
> Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
> Software Engineer
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
