Hi Marc, > The idea is to modify the turbine_* tables manually.
Can I ask how you are planning on modifying these tables? If you are going to add new columns to these tables, I believe that you might have to also create new classes of the existing Turbine class (correct me if there are other solutions here). eg. If you add a new column to the turbine_group table, then you'll probably have to subclass TurbineGroup class and provide the extra column. You'll probably also have to subclass Turbine's GroupPeer as well (to add the extra column when retrive()/save() is invoked). In addition you'll also have to modify (or subclass) every class that invokes Turbine's GroupPeer, so that it will call your _updated_ GroupPeer class to do the persistance instead (at this stage I _think_ it is only the DBSecurityService that invokes the Peer classes) As you can see you'll have to do this for every turbine_* table that you add columns to. However if you are just using these tables for foreign key relationships then I think you should be ok. >>I have achieved this, but not without compromises. One of the >>compromise is that we are only using Turbine's security system for >>authentication and when we need to do authorisation we use our own >>security model. In addition the replacement Turbine security classes is >>read-only, so as soon as you try to do any modification to the >>underlying system via Turbine's bundled DBSecurityService an exception >>will be thrown. > > > I see. But it is possible to modify the turbine_* tables by just using its > corresponding Peers, isn't it? > If this is not possible, I am going to the wrong direction right now and > need to switch to another solution. Yes, I believe the existing *Peer classes in (org.apache.turbine.om.security.peer) will work in persisting the TurbineUser, TurbineGroup, etc. objects to the database correctly. > Q: Did you make efforts to switch to the decoupled Fulcrum Turbine-Service, > or do you use the old model? I am still using the old model, but only for our first internal release. Subsequent releases will use the Fulcrum model (pending its stability). At this stage I don't see any big differences between the two so porting it from Turbine to Fulcrum should be (relatively) painless. cheers, -- R E D S H E R I F F C.P. Lim - Software Engineer Level 1, 10 Queens Road +61 3 9864 0733 tel Melbourne VIC +61 3 9864 0778 fax Australia +61 413 781 846 mob This message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you have received this message in error please notify us immediately by return email or telephone +61 (3) 9659 0432, then delete this message. Any views expressed in this message are those of the individual sender and many not necessarily reflect the views of Red Sheriff. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
