quick - pre-dawn jet-lagged response - I'll re-read after breakfast
and coffee ..
Thanks Justin - this sounds great - well done. How can we get a look
at the solution so far?
Once we have an approach to maintaining the code the AusScope team can
kick in to worry about handling the wierd cases.
I
On 05/09/2009, at 3:56 AM, Justin Deoliveira wrote:
> 2) How should complex types with simple content be represented? Jody
> has
> said/suggested that this be a property with the name "value", which is
> marked as inline. I think that can work... there will just have to
> be a
> another speci
>> However the feature model is incomplete in this regard.
>> ComplexAttribute.isInline() is never set (there is no way to set
>> it) and
>> it always returns false.
Yeah I am aware of the limitations; and that is why I am wanting
feedback and a review
as we roll this one out.
>
> The approach
That's looking good, I know it's being hard so congrats on the
achievements..
>
> 2) How should complex types with simple content be represented? Jody has
> said/suggested that this be a property with the name "value", which is
> marked as inline. I think that can work... there will just have t
I have made some progress toward getting the encoder to consume generic
ComplexAttribute instances (http://jira.codehaus.org/browse/GEOT-2505).
I have modified the code generator so that it can actually handle the
madness which is gml3, and spit out a Schema object which has all the
types from
