Hi Doug,
If both elements refer to the same complexType then you can probably ignore the warning. One way to prevent the warning is to use an element reference to a shared top-level element declaration instead of two nested element declarations.
But since you didn't write the schema, I think in your case you can just ignore the warning.
--Keith
Doug Porter wrote:
I am working on generating a set of objects from the Open Financial Exchange (OFX) schema.
(Available here: http://www.ofx.net/ofx/de_spec.asp).
I am receiving the following naming conflict error message when using the SourceGenerator:
---------
Warning: A class name generation conflict has occurred between element 'complexType:ChangeUserInfoSyncRequest/CHGUSERINFOTRNRQ' and element 'complexType:SignupRequestMessageSetV1/CHGUSERINFOTRNRQ'. Please use a Binding file to solve this problem.
---------
These two complex types contain an element that has the same name and type. I know I can set up a binding file to give each of these two elements a different generated class name, but the underlying object in both of the complex types is exactly the same.
Must I generate two separate classes even though they will differ only in name or am I missing something? It would seem like both of the complex type element objects should just reference a single shared object.
New to Castor and XML binding so any ideas would be greatly appreciated.
Thanks, Doug Porter
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
