On Apr 16, 2007, at 9:43 PM, Melchior, Joris wrote:

Given the following snippet:

<fragment id="experiment-562" type="portlet" name="DCLPortlet::DCLTest">
        <preference name="context" readOnly="false">
                <value>defaultCommon</value>
        </preference>
        <preference name="subContext" readOnly="false">
                <value>header</value>
        </preference>
</fragment>

Does Jetspeed store the preference information in its database? If so,
where does that information go?


Yes, it goes in two tables (XML DDL defs):

<database name="j2">

    <!--
       prefs_property_value
    -->
    <table name="PREFS_PROPERTY_VALUE">
<column name="PROPERTY_VALUE_ID" primaryKey="true" required="true" type="INTEGER"/>
        <column name="NODE_ID" type="INTEGER"/>
        <column name="PROPERTY_NAME" size="100" type="VARCHAR"/>
        <column name="PROPERTY_VALUE" size="254" type="VARCHAR"/>
        <column name="CREATION_DATE" type="TIMESTAMP"/>
        <column name="MODIFIED_DATE" type="TIMESTAMP"/>
<!-- Still an issue with OJB 1.0.3 when deleting M-N. Foreign Key Violation.
        <foreign-key foreignTable="PREFS_NODE">
            <reference foreign="NODE_ID" local="NODE_ID"/>
        </foreign-key>
        -->
    </table>

    <!--
       pref_node
    -->
    <table name="PREFS_NODE">
<column name="NODE_ID" primaryKey="true" required="true" type="INTEGER"/>
        <column name="PARENT_NODE_ID" type="INTEGER"/>
        <column name="NODE_NAME" size="100" type="VARCHAR"/>
        <column name="NODE_TYPE" type="SMALLINT"/>
        <column name="FULL_PATH" size="254" type="VARCHAR"/>
        <column name="CREATION_DATE" type="TIMESTAMP"/>
        <column name="MODIFIED_DATE" type="TIMESTAMP"/>
        <foreign-key foreignTable="PREFS_NODE" name="FK_PREFS_NODE_1">
            <reference foreign="NODE_ID" local="PARENT_NODE_ID"/>
        </foreign-key>
    </table>

</database>



Some Documentation here:

http://portals.apache.org/jetspeed-2/multiproject/jetspeed-prefs/ jetspeed-prefs.pdf


Reply via email to