At 12:29 AM 9/6/01 -0700, you wrote:
>on 9/5/01 3:09 PM, "Atul Dambalkar" <[EMAIL PROTECTED]> wrote:
>
> > Yes, but this syntax will be valid only if you have the entire schema
> > defined in one single file. So we need to modify, turbine-schema.xml file,
> > with all the Jetspeed tables added, right?.
> >
> > -Atul
>
>Not if you do it right.
>
>Look at Scarab and also read:
>
>     extend-user-howto.xml
>
>In the jakarta-turbine-2/xdocs/howto directory.

Jon,

This seems great!  I also looked at the Scarab docs, I guess, this is 
definitely one approach to the problem, but with one issue. If we use 
TurbineUser's User_Id, as a foreign key reference in Database-PSML schema, 
will that be doing cascading deletes to the referencing tables? If that is 
the case, then we DON'T want that to happen. Reason being:

The deletes in the TurbineUser table as well as related PSML  documents are 
anyway handled by JetspeedSecurityService. So, the JetspeedSecurityService 
invokes, PsmlManager service interface to remove user/role/group specific 
PSML documents, when a Turbine user/role/group has to be deleted (which it 
is already doing). So, it can happen that, if, cascading deletes are 
handled by TubineUser class, then the PSML documents in the Database will 
get deleted automatically, when JetspeedSecurityService deletes 
TurbineUser. On top of that JetspeedSecurityService also HAS-TO invoke 
PsmlManager service interface to remove PSML documents, because in case of 
File System implementation, it has to delete the file. Also in case of 
LDAPPsmlManager implementation, it has to delete a record in LDAP, as there 
is no question of cascading deletes in both these cases. Do we have a 
Tx-Mgr across DB-File system and DB-LDAP????

-Atul


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

Reply via email to