Hi Dimitra, hard to say. Such things (wrong class names, compilation problems, ...) usually happen if you have naming conflicts in your XML schema, and Castor hence is not capable of resolving those automatically (read without your intervention, e.g. through a binding file).
Can you show us an example of some XML schema fragments where the code is being generated wrongly ? Werner Dimitra Giannakopoulou wrote: > When running org.exolab.castor.builder.SourceGeneratorMain, > > I get some instances where the class names are wrong in the generated > code, for example, > > I get "plexil.types.DirType" instead of "plexil.types.NodeDefDirType" > > > So I get compilation errors (because DirType does not exist, for > example). When I fix it by hand, everything works as intended. > However, since this is supposed to be an automated step, manually > fixing this is not an option. > > Is this a known problem? Is there something I am doing wrong? > > Thanks, > > Dimitra > > > > > > > --------------------------------------------------------------------- > 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
