In fact, JAXB reacts like that because :
PhoneType is defined in audio-2001.xsd
phoneticAlphabetType is defined in audio-2001.xsd
WordType is defined in audio-2001.xsd
RegionLocatorType is defined in visual-2001.xsd
....
so it's not really possible to parse mds-2001.xsd separately... :-(
Christelle.
On Fri, 16 May 2003 14:03:03 -0400, David F. Wall <dwall_at_foliage.com> wrote:
>Well, I gave it a quick whirl, and it failed.
>
>HOWEVER
>
>Seeing the mds-2001.xsd is 249KB and it does only one small include, I tried
>doing that separately, and got a whole bunch of errors:
>
>[ERROR] src-resolve: Cannot resolve the name 'mpeg7:PhoneType' to a(n) type
>definition component.
> line 1188 of mds-2001.xsd
>
>[ERROR] src-resolve: Cannot resolve the name 'mpeg7:phoneticAlphabetType' to
>a(n) type definition component.
> line 1191 of mds-2001.xsd
...
...
>
>Failed to parse a schema.
>
>But no OutOfMemoryError.
>
>I am not an XML expert, a schema expert, or an MPEG expert, but if I were in
>your position, I'd start by finding out why mds-2001.xsd provokes this
>behavior out of JAXB. It might be
>that going down error paths is resulting in a lot of memory consumption that
>wouldn't
>occur if this parsed cleanly.