Apart from bugs (did you report them?) - there are fundamental differences
between the data models of XML and Java, and the general idea of mapping
between Java objects and XML data "agglomerations" (I would not use the
term data *type *here) is hampered at many places. Generally, I have found
things to be less restrictive when you use annotated Java classes, or when
you can design an XML schema with JAXB in mind; also an architecture where
Java classes for XML data aren't the same ones you use in your application
has been advantageous at times.
I'd very much like to learn about alternatives that suit you better, and
why.
-W
On 11 December 2011 16:06, John G. Lussmyer <Cougar_at_casadelgato.com> wrote:
> More likely we'll just give up on using jaxb to generate java files.
> This is the straw that broke the camels back. We've run into too many
> restrictions and bugs to make it worth the effort needed.
>
>
>
> On 12/11/2011 6:59 AM, Tinnefeld, Karsten wrote:
>
>> Let me suggest you build an indexed version of SortedSet (sorted in order
>> to have some sense in indexing), and give it that implementation. This
>> should work, shouldn't it?
>>
>> Karsten
>>
>
>
> --
> --
> John G. Lussmyer mailto:Cougar_at_CasaDelGato.Com
> Electric Vehicle Battery Monitoring Systems, http://www.CasaDelGato.com
>
>
>