>> > >> > I know that it has something to do with types defined before this >> > schema because ... >> Sorry, I don't really understand what you are trying to say >> here. Can you please elaborate ?
Sorry for the confusion, I was trying to say that other schemas affect the generation of this particular one. I have several schemas that ant generated before the one that causes problem. Ant generates source for schema: A, B and B A and B schemas went through ok and C is where I encountered an error. I run schema C in the command line separately and it went successfully. By the way, I have the org.exolab.castor.builder.forceJava4Enums property set to true. Thanks, Alex >> >> > ... when I manually do it through the command line, this >> particular >> > schema goes through successfully. It does not look like the above >> > type is causing a problem, I can eliminate it and it still >> shows the error. >> > Is there a way I can see which type is causing other than >> eliminating >> > them one by one? >> > >> > Let me know and thanks in advance. >> > >> > Alex >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe from this list, please visit: >> > >> > http://xircles.codehaus.org/manage_email >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
