Thanks Roman,

I'll mark that as PCDATA for now instead of ID.

--Keith



Roman Maeder wrote:
> 
> Hi
> 
> I am using the new nested class mapping feature to map key/value pairs to a
> Java HashMap. The XML mapping doc says that this can be used if more than
> one mapping for a particular class is needed. I am using the
> org.exolab.castor.mapping.MapItem class to map my XML data to.
> 
> <field name="paramTable"
>        collection="map"
>        container="false">
>       <bind-xml name="paramlist"
>                 node="element">
>             <class name="org.exolab.castor.mapping.MapItem">
>                   <field name="key"
>                          type="string">
>                         <bind-xml name="key"
>                                   node="attribute"
>                                   location="param"/>
>                   </field>
>                   <field name="value"
>                          type="string">
>                         <bind-xml name="value"
>                                   node="attribute"
>                                   location="param"/>
>                   </field>
>             </class>
>       </bind-xml>
> </field>
> 
> All works fine as long as only one such mapping is declared in the mapping
> file. But if several such declarations are used in the same mapping file,
> mapping still works, but the mapping XML file cannot be validated properly
> anymore. This is because the mapping.dtd file declares the name attribute
> of the class element as ID. This does not allow multiple for example
> MapItem classes to be defined in the same mapping file.
> 
> Kind regards
> Roman Mäder
> 
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
>         unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to