Table mapping (KODO 3.4) using XDoclet

Question

Hi,
I need to map an Object to a differntly named table via XDoclet. That is described in the [url http://edocs.bea.com/kodo/docs303/ref_guide_integration_xdoclet.html]Docs here.
When I use the foloowing class it will produce a different looking JDO file and KODO simply ignores it. Can you tell me, what I'm doing wrong?
Java Code:
* @jdo.persistence-capable
* identity-type="application"
* objectid-class="MyClassId"
* @jdo.class-vendor-extension
* vendor-name="kodo" key="detachable" value="true"
* @jdo.class-vendor-extension
* vendor-name="kodo" key="jdbc-class-map" value="base"
* @jdo.class-vendor-extension
* vendor-name="kodo" key="jdbc-class-map/table" value="MyTableName"
public class MyClass {...}
JDO file:
<class name="MyClass" identity-type="application" objectid-class="MyClassId" requires-extent="true">
<extension vendor-name="kodo" key="detachable" value="true">
</extension>
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
</extension>
<extension vendor-name="kodo" key="jdbc-class-map/table" value="MyTableName">
</extension>
<field name="xxx" persistence-modifier="persistent" primary-key="false" null-value="none">
</field>
Update:
I also tried:
* @jdo.persistence-capable
* identity-type="application"
* objectid-class="MyClassId"
* table="MyTable"
public class MyClass {...}
But it seems, Kodo does not support the table attribute!
Update 2:
The upper solution should be the right one. It seems in the kodo.properties must be set the attribute "kodo.jdbc.MappingFactory: metadata"
Is anyone using such a table mapping that is working? I'm still struggeling to get this working!
Edited by jdeluxe at 05/16/2008 4:32 AM

Answer 1

Wow, I didn't expect almost 100 people watching this thread without any hint!
Here it is:
Ant Task
          <jdomappingtool action="refresh" sqlfile="XXX">
               <fileset dir="YYY" >
                    <include name="**/*.jdo" />
               </fileset>
               <config propertiesFile="D:/kodo-jdo-3.4.1/kodo.properties" />
EntityClass:
* @jdo.persistence-capable
*           identity-type="application"
*      objectid-class="foo.MyClassId"
*      name="myClass"
* @jdo.class-vendor-extension
*           vendor-name="kodo" key="jdbc-class-map" value="base"
* @jdo.class-vendor-extension
*           vendor-name="kodo" key="jdbc-class-map/table" value="MYTABLENAME"
* @jdo.class-vendor-extension
*           vendor-name="kodo" key="jdbc-class-map/pk-column" value="ID"
public class MyClass {
* description
* @jdo.field persistence-modifier="persistent"
* @jdo.field-vendor-extension vendor-name="kodo"
* key="jdbc-field-map" value="value"
* @jdo.field-vendor-extension vendor-name="kodo"
* key="jdbc-field-map/column" value="description"
private String description;
Note that when not using the explicit column mapping I experienced a strange behaviour: Kodo did not map to the existing table column, but wanted to add new fields postfixed with "1" (e.g. ALTER TABLE MYTABLENAME ADD COLUMN "description1").
Also the setting
kodo.jdbc.MappingFactory: metadata
in the kodo.properties file is mandatory !!!!!