You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Gedin Frederic <fr...@jaluna.com> on 2003/05/22 05:49:24 UTC
Security database selection scheme does not seems to be appropriate
Hi
As I develop several internal applications using the Turbine framework,
I decided to modify them in order to have a common security database.
This revealed to me that Turbine 2.2 behavior is to map the security
database to the default application database.
Digging into Turbine code source, I saw that the map is made by
TurbineMapBuilder which uses TurbineDB which is a deprecated class. So
I assume that in the future releases, TurbineMapBuilder will be updated
in order to avoid using TurbineDB. In such a case, is it possible to
have a configuration parameter in TurbineResources.properties which
specifies where to map the security database. I think this would add
flexibility.
Regards
Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Security database selection scheme does not seems to be appropriate
Posted by Frederic Gedin <fr...@Jaluna.COM>.
Bill wrote:
>Maybe I dont understand your dilemma entirely, but couldnt you very
>simply accomplish this by allowing the default database to be the
>security database and defining your datastore in a second schema file?
>
Let's say that it seems more logical for me to say that the default
database is the database which has a functional meaning regarding the
application, the security database being only secondary.
In addition, by default Torque builds the default database (i.e the one
which is named "${torque.project}-data.xml"). If I followed this line,
I would rebuild the security database which is share by all applications.
I can take the system as it is and twist it to make it work properly for
me. However, I think that my problem can give some ideas for improving
Turbine's usability regarding the configuration of the security model.
Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Security database selection scheme does not seems to be
appropriate
Posted by Bill <bh...@collaborativefusion.com>.
Maybe I dont understand your dilemma entirely, but couldnt you very
simply accomplish this by allowing the default database to be the
security database and defining your datastore in a second schema file?
On Wed, 2003-05-21 at 23:49, Gedin Frederic wrote:
> Hi
>
>
> As I develop several internal applications using the Turbine framework,
> I decided to modify them in order to have a common security database.
> This revealed to me that Turbine 2.2 behavior is to map the security
> database to the default application database.
>
> Digging into Turbine code source, I saw that the map is made by
> TurbineMapBuilder which uses TurbineDB which is a deprecated class. So
> I assume that in the future releases, TurbineMapBuilder will be updated
> in order to avoid using TurbineDB. In such a case, is it possible to
> have a configuration parameter in TurbineResources.properties which
> specifies where to map the security database. I think this would add
> flexibility.
>
> Regards
>
>
> Frederic
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org