Dave wrote:
>
> Josh,
>
> >After all of this, I now have a question. The current architecture that
> I'm
> >working with has user information in XML files as opposed to a database and
> >authentication against a server instead of a database. I realize that the
> >out-of-the-box Turbine does not support this but I was wondering if anyone
> >had any suggestions as to where to start looking to modify the necessary
> >code in order to work with this architecture.
> >
> >Any help would be greatly appreciated.
>
> I was thinking about an XML alternative myself. We currently use an XML
> store for document managment
> and I would like to move user profiles into XML.
>
> I would start by having a look at org.apache.turbine.util.User. According
> to the docs:
No, no... the user object should _not_ change. What changes is how that
object is created, i.e. where the data that populates the User object
comes from, in your case an XML store. You are using XML here just like
a database, or LDAP. Don't change the data structure, change the data
retrieval.
-Brett
>
> /**
> * This interface represents functionality that all users of
> * the Turbine system require.
> */
>
> Then look at TurbineUser and TurbineUserPeer.
>
> Hope this helps,
> Dave
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
