I believe the answer to this is yes for anyone else that is interested. On Fri, Oct 3, 2008 at 8:56 AM, Jamie Johnson <[EMAIL PROTECTED]> wrote:
> I am attempting to build a set of schemas that uses substitution groups and > abstract types which works flawlessly if I compile all the schemas together > (i.e. one big jar) but if I build them all separately by first building the > abstract type then building all the types that extend the abstract type with > the abstracttype on the classpath XmlBeans substitution doesn't seem to > work. Do all objects that extend the AbstractType need to be available at > build time for XmlBeans to properly recognize the substitution groups? > > What is strange is when looking at a class that extends the AbstractType it > clearly indicates that the AbstractType is it's base, but if I try to do > (Extended)AbstractType.substitute(ExtendedDocument.impl.type, > Extended.type); I received a class cast exception. Any idea how to address > this without having to recompile the Abstract Schema everytime I want to add > a type that extends the AbstractType? > > Jamie > >
