A profile locator param in the saveDocument method would solve a
significant part of my problem. Would you be interested in diff -u
patches for this?
The rest of my problem probably has more to do with the Turbine security
service than with Jetspeed. Thanks for your help -- I am setting the
LDAP issues aside for now.
-mark
> -----Original Message-----
> From: Raphaël Luta [mailto:raphael.luta@networks.groupvu.com]
> Sent: Tuesday, August 14, 2001 12:34 PM
> To: jetspeed-dev@jakarta.apache.org
> Subject: Re: Change to PSMLManagerService interface
>
>
> McClelland, Mark wrote:
>
> >>There aren't a lot of methods left after we complete the
> deprecation:
> >>
> >> public PSMLDocument getDocument( ProfileLocator locator );
> >> public boolean saveDocument(PSMLDocument doc);
> >> public PSMLDocument createDocument( ProfileLocator locator );
> >> public Iterator list( ProfileLocator locator );
> >>
> >
> > Why doesn't saveDocument also take a ProfileLocator? In
> order to write
> > the document to a database or to LDAP, user information is
> needed. Am I
> > missing something obvious here?
> >
>
>
> The legacy PSMLDocument implementation is storing it's file
> path within the
> object so can save itself but I agree that'll also need a
>
> public boolean saveDocument(ProfileLocator locator, PSMLDocument doc);
>
> to address the general need.
>
>
> --
> Raphael Luta - raphael.luta@networks.groupvu.com
> Vivendi Universal Networks - Paris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
|