Hi Werner,

indeed, I got the following warnings while I was running Castor but told it to 
continue anyway.

----
Warning: A class name generation conflict has occured between element '/Name' 
and element '/ArrayElement/Name'. Please use a Binding file to solve this 
problem.Continue anyway [not recommended] (y|n|?)y


Warning: A class name generation conflict has occured between element 
'/DeclareVariable/InitialValue' and element '/DeclareArray/InitialValue'. 
Please use a Binding file to solve this problem.Continue anyway [not 
recommended] (y|n|?)y
----

Could you send me some pointer / information or examples on creating binding 
files to solve such problems? (I just have no experience with XML - I am just 
using Castor to translate a schema produced by another team).

I will see if I can also send you portions of the schema.

Thanks,

Dimitra




--- On Fri, 6/20/08, Werner Guttmann <[EMAIL PROTECTED]> wrote:

> From: Werner Guttmann <[EMAIL PROTECTED]>
> Subject: Re: [castor-user] Wrong class names in generated code
> To: [email protected]
> Cc: [EMAIL PROTECTED]
> Date: Friday, June 20, 2008, 3:27 AM
> 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


      

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to