Actually, maybe the answer is simpler. Did you remove all the old generated files before regenerating? The problematic file may just be an old generated file which is no longer needed/generated (but it won't be deleted automatically).
Frank. Frank Budinsky/Toronto/[EMAIL PROTECTED] wrote on 03/20/2008 03:47:19 PM: > It definitely sounds like a bug. The Java code generator went through a > major redesign to disconnect it from EMF. It looks like your XSD is > invoking a pattern that wasn't converted properly. Maybe you can narrow > down which XSD feature is causing this to happend and open a JIRA. > > Thanks, > Frank > > > > > "Stanislaw T. Findeisen" <[EMAIL PROTECTED]> > 03/20/2008 03:15 PM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > nonexistent import - XSD2JavaGenerator problem (import > org.apache.tuscany.sdo.model.impl.ModelPackageImpl) > > > > > > > Hello > > In short: this statement: > > import org.apache.tuscany.sdo.model.impl.ModelPackageImpl > > is being generated by org.apache.tuscany.sdo.generate.XSD2JavaGenerator, > but there is no such class in the current release. > > This used to work OK with SDO Java Incubating-M2, but now I am upgrading > to the current release and this breaks my build. > > I am trying to generate Java classes corresponding to elements defined > in an XSD file. > > Generated class declaration is this: > > public class ConfigPackageImpl extends EPackageImpl > > Am I doing anything wrong, or is this a bug? > > Thanks! > STF > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
