PS. Was assuming you were using JDO, but the rule applies to the XML side of things too. One class definition per mapping.
-Nick On 7/15/05, Nick Stuart <[EMAIL PROTECTED]> wrote: > Can you explain your situation a bit more? If I'm reading it write you > are trying to have two or more <class> section with the same name > attribute. This isn't going to work and the mapping DTD is not going > to change to fix it. > > Now, the real question is what are you trying to accomplish, and what > you mean when you say "nested class mappings". A class can only show > up once for each Database instance you have. > > Again, just explain the situation a bit more and I'm sure we'll find > some way to resolve it. > > -Nick > > On 7/13/05, Stephen Bash <[EMAIL PROTECTED]> wrote: > > Everyone- > > > > So I finally got an XML plugin set up in Eclipse (wow I dragged my feet > > on that one), and one of the first things I did was go through and > > validate my mapping files against the Castor Mapping DTD. > > > > The one problem the validation step exposed was multiple occurrences of > > the same class name (name is an ID) due to my use of nested class > > mappings -- <class name="org.exolab.castor.mapping.MapItem"> shows up > > several times in a single mapping file. Does anyone have any ideas of > > how to work around this on my end? Or is this something that can be > > easily fixed in the mapping DTD? > > > > Thanks! > > > > Stephen > > > > ------------------------------------------------- > > If you wish to unsubscribe from this list, please > > send an empty message to the following address: > > > > [EMAIL PROTECTED] > > ------------------------------------------------- > > > > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
