I tried the binding file approach, but had no luck. I did have luck with changing the mapping from element to types, but was not able to get my binding file to work. I've attached them in case someone sees my goof:
This is more research I am doing for the ACORD standards body. We are
trying to figure out how best to support code generation in our next
standard.
Jim Brain, [EMAIL PROTECTED]
"Researching tomorrow's solutions today."
(319) 369-2070 (work)
APPLICATIONS ARCHITECT, AFP-IT
-----Original Message-----
From: Keith Visco [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 4:15 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] Local defined elements with unique types
> "Brain, Jim" wrote:
>
> Notice that each type has an element named Extension, but each has a
> different type. When I run it through Castor, it creates the first
> Extension class and names it Extension, but then when it gets to the
> second one, it creates a new Extension class and overwrites the first
> one.
>
> Is there a way to prevent that from occurring?
As Rhett suggested, a binding file is the best approach. You'll be happy
to know however, that the CVS version of Castor will warn you about the
problem instead of clobbering the first Extension Class.
--Keith
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
binding.xml
Description: Binary data
ACORDAddr_Any2.xsd
Description: Binary data
