Atul,
A am concerned with the key structure. My experience with the PSML
files is the "key", more correctly the directory structure, always
includes media_type, language, and country. Thus the role
'Payroll_Manager" would accommodate a French cell phone, a French
Canadian Web Browser, and a German Web Browser. In all cases the role
is the same, but portlet defined in the associated PSML file may be
different. Similar example can be made for user and groups.
Are Language and Country codes defined as 2 characters each ?
Paul Spencer
Atul Dambalkar wrote:
>
> Hi Jon, David,
>
> Here is the XML Database schema for putting PSML information along with
> user/role/group profile. Please review it.
> =======================================================
> <app-data>
>
> <database defaultIdMethod="idbroker"
> basePeer="org.apache.turbine.om.peer.BasePeer" >
>
> <table name="JETSPEED_USER_PROFILE" idMethod="idbroker">
>
> <column name="USER_ID" required="true" autoIncrement="true"
> primaryKey="true" type="INTEGER"/>
> <column name="LOGIN_NAME" required="true" size="32" type="VARCHAR"/>
> <column name="MEDIA_TYPE" size="99" type="VARCHAR"/>
> <column name="LANGUAGE" size="99" type="VARCHAR"/>
> <column name="COUNTRY" size="99" type="VARCHAR"/>
> <column name="PAGE" size="99" type="VARCHAR"/>
> <column name="PROFILE" type="VARBINARY"/>
>
> <unique>
> <unique-column name="LOGIN_NAME" />
> </unique>
>
> </table>
>
> <table name="JETSPEED_GROUP_PROFILE" idMethod="idbroker">
>
> <column name="GROUP_ID" required="true" autoIncrement="true"
> primaryKey="true" type="INTEGER"/>
> <column name="GROUP_NAME" required="true" size="99" type="VARCHAR"/>
> <column name="MEDIA_TYPE" size="99" type="VARCHAR"/>
> <column name="LANGUAGE" size="99" type="VARCHAR"/>
> <column name="COUNTRY" size="99" type="VARCHAR"/>
> <column name="PAGE" size="99" type="VARCHAR"/>
> <column name="PROFILE" type="VARBINARY"/>
> <unique>
> <unique-column name="GROUP_NAME" />
> </unique>
>
> </table>
>
> <table name="JETSPEED_ROLE_PROFILE" idMethod="idbroker">
>
> <column name="ROLE_ID" required="true" autoIncrement="true"
> primaryKey="true" type="INTEGER"/>
> <column name="ROLE_NAME" required="true" size="99" type="VARCHAR"/>
> <column name="MEDIA_TYPE" size="99" type="VARCHAR"/>
> <column name="LANGUAGE" size="99" type="VARCHAR"/>
> <column name="COUNTRY" size="99" type="VARCHAR"/>
> <column name="PAGE" size="99" type="VARCHAR"/>
> <column name="PROFILE" type="VARBINARY"/>
>
> <unique>
> <unique-column name="ROLE_NAME" />
> </unique>
>
> </table>
>
> </database>
> ===============================================================
>
> I could generate all the peer classes, but "torque" fails if I try to use
> "native" as idMethod. So I have to use "idbroker".
>
> Questions:
> 1. The generated package name, I decided as:
> "org.apache.jetspeed.om.dbpsml" Is that okay?
> 2. The basePeer for generated peer classes is
> org.apache.turbine.om.peer.BasePeer. Hope that's correct...
>
> Also, how could we automate the process of generating database specific
> peer classes, when some one decides to use it for let's say MSSQL? Right
> now I am trying it with Oracle.. Currently I have generated all the peer
> classes with stand-alone version of Torque and manually copied them under
> Jetspeed cources, and got all compiled.
>
> Christopher, now, you don't have to define a separate schema in MSSQL, the
> above Torque schema will handle all the different database cases.
>
> -Atul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
