Trace: • Compiling JVx
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jvx:server:storage:metadata [2020/06/15 11:50] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:storage:metadata [2020/06/26 13:21] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 63: | Line 63: | ||
| As can be seen already, both classes are linked. The class ColumnMetaData creates a new instance of ColumnDefinition. | As can be seen already, both classes are linked. The class ColumnMetaData creates a new instance of ColumnDefinition. | ||
| - | In **2. step**, we're going to configure a DBAccess object. It should use our new classes: | + | In **Step 2*, we're going to configure a DBAccess object. It should use our new classes: |
| <file java> | <file java> | ||
| Line 89: | Line 89: | ||
| We have to implement the interface IColumnMetaDataCreator and simply return our own class. We set the new ColumnInfo before we return the object. | We have to implement the interface IColumnMetaDataCreator and simply return our own class. We set the new ColumnInfo before we return the object. | ||
| - | From now on, all metadata instance are created using the ''ColumnMetaDataCreator''. | + | From now on all metadata instance are created using the ''ColumnMetaDataCreator''. |
| The newly created MyColumnMetaData instance is transferred to the client as usual. The model continues to generate automatically our MyColumnDefinition instance via createColumnDefinition. No further action needed. | The newly created MyColumnMetaData instance is transferred to the client as usual. The model continues to generate automatically our MyColumnDefinition instance via createColumnDefinition. No further action needed. | ||