Here's an excerpt from my mapping file:

<mapping>
    <class name="ourcommunity.org.dao.NFPOrgDO" identity="id" 
            key-generator="IDENTITY"> 
        <cache-type type="unlimited" />    
        <map-to table="ORG" />
    
        <field name="id" type="integer">
            <sql name="ID" type="integer"/>
        </field>

...

it works fine for me. Perhaps if you include a bit more detail with your
post people will have a closer look at it. It would help if you would
include the stack trace for the mapping exception you get and also code
for the com.quigley.dashboard.Account object would be good too.

-----Original Message-----
From: Michael Quigley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 12 December 2001 3:00 PM
To: [EMAIL PROTECTED]
Subject: [castor-dev] key-generator="IDENTITY"


Can anyone even get the following mapping.xml to be recognized as a
valid
class by Castor 0.9.3?

<mapping>
  <class name="com.quigley.dashboard.Account" identity="id"
key-generator="IDENTITY">
    <map-to table="ACCOUNT" />
    <field name="id" type="string">
      <sql name="ID" type="char" />
    </field>
  </class>
</mapping>

Is everyone on this list on vacation? Hasn't anyone run across any
mapping.xml problems like this in their Castor work? Everything is
working
great for me, until I add a "key-generator" attribute to the <class>
element
of my mapping.xml. Once I add the attribute, something gets messed up
and
Castor no longer thinks it has a mapping for my class!

How are people creating new keys when using Castor JDO?

Anyone?

Thanks,
Michael

----------------------------------------------------------- 
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