on 11/7/2000 7:59 AM, "Gerd Mueller" <[EMAIL PROTECTED]> wrote:

> 
> Hi all,
> 
> I'd like to integrate Prowler
> (http://www.infozone-group.org/projects_main.html)
> with Turbine/Jetspeed. Prowler is an XML-based transaction-safe content
> managment framework. At the moment we use only Cocoon for the web-frontend.
> But we'd like to have Turbine/Jetspeed to build a personalized web-protal.

Wow...this seems to be the big thing to do for 2000.

> The overall goal of Infozone is to create an EIP based on open source
> technolgies. The raw picture might be as follows:
> 
> +---------+ +----------+ +---------+
> | Cocoon  | | Jetspeed | | Turbine |
> |         | +----------+ |         |
> |         +-----+  +-----+         |
> |               |  |               |
> +---------------+  +---------------+
> +----------------------------------+
> |              Prowler             |
> +----------------------------------+
> +----------------------------------+
> |    data source (databases, app   |
> |     servers, mail boxes, etc.)   |
> +----------------------------------+

I don't think your picture is entirely accurate, but whatever.

> One important point is the user management (UM). The UM of Prowler is
> pluggable
> but the interface is very simple (only users and groups). I'd like to have
> only 
> one user manager for all parties - Jetspeed, Turbine and Prowler. As a common
> interface I thought of JAAS (published by Sun), also because of the tight
> integration with the Java security mechanims. How much differs the UM of
> Turbine from this specification ?

Turbine's implementation is its own. It is all interface based and can be
implemented however you wish. By default, Turbine will have an
implementation for a database back end as well as a LDAP back end. This is
being completely re-done right now.

<http://java.apache.org/turbine/branches.html>

Personally, I see absolutely no need to tie myself to JAAS.

> Also I saw that Turbine's UM heavly depends on SQL but I'd like to use ozone
> (http://www.ozone-db.org) - an OODBMS - to store the UM informations. As far
> as
> I could see from the API docs this is not possible yet - or am I wrong?

You are wrong. It is entirely interface based and you can provide any
implementation you want on the back end.

> Is there any way to separate the UM interface of Turbine clearly from the
> underlying database ?

Of course.

> I have to admit that I'm not yet very familar with Turbine. What I've written
> here is based on my first impressions that I've got while reading the docs.
> I would be grateful for any hints.

Read the source code.

-jon

-- 
http://scarab.tigris.org/    | http://noodle.tigris.org/
http://java.apache.org/      | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/       | http://www.sourcexchange.com/




------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to