Re: [Geotools-devel] Include app-schema in build

[Justin D. <jde...@op...>]

Ben Caradoc-Davies wrote:
> Andrea Aime wrote:
>>>> Another option could be to have the build server build with
>>>> -Pextensive (shall we rename this to -Pexpensive ;-) ?)
>>> +1 for the rename.
>>
>> I was just joking :)
> 
> I know, but it was a good suggestion.
> 
>> This Eclipse XSD issue seem relevant as well and it's being discussed
>> these days too:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=278853
> 
> Could be relevant.
> 
>> Also, an old thread on the eclipse ml suggests to use xerces-j schema
>> api instead of XSD if one does not have schema manipulation needs:
>> http://dev.eclipse.org/newslists/news.eclipse.technology.xsd/msg01221.html 
>>
>> This does not mean we have to jump on xerces-j api right away, just
>> that we keep it in mind for the future (this is the same API DeeGree is
>> using for its schema handling needs, too).
> 
> Mmm, we only consume schemas, so xerces-j may be an option. We do need 
> to walk the schemas to find things like substitution groups, and I am 
> not sure the xerces API allows this. Justin?

Correct, we do inspect the schema contents quite closely, so any tech 
needs to model every part of the schema down to small detail, this 
includes particle information, and substitution group info.

We also do need the ability to build up schemas from scratch, this is 
how the application schema stuff works, at least in geoserver. But I 
agree, xerces-j is definition worth a look at.
> 


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.