Neeme Praks wrote:
>
> Also, I was thinking along the other meaning of the word "profile": we
> need some sort of profiles with a set of pre-configured portlets. On one
> hand, we need them for users, to the user can get some set of default
> portlets (or he can choose a possible profile: student, business, etc.
> that have most common use-cases covered) when he signs up. Also, we
> would need portlet profiles for services (see my other post about the
> services), so the user gets some preconfigured set of portlets and pages
> when signing up for some service.
>
> Actually, these user profiles could have two levels: one level defines
> the default set of services that are activated for him when signing up
> (kind of use-case for the whole portal: what does the user want to do on
> the portal). And the other level is service specific: the service can
> offer more than one preconfigured set of portlets, depending on service
> level user profile selected (kind of use-case for the specific service:
> how / for what does the user want to use this service).
>
Yes, user profiles stored in PSML files and registered in the registry were
part of my initial specification for PSML, I just never had time to implement it.
I like the idea of portlets as views to an existing service. This already exists
in the registry since this exactly what we do when we create "ref" entries.
Maybe we should specify some kind of portlet grouping...
> >
> > I still include the portlet contents as is, so it needs to be
> > XML compliant
> > (I've have a modified ECS jar available for outputting XHTML code).
>
> excellent! is it in the CVS already? Should check it out ASAP.
>
Nope not yet, it'll be coming in small steps this week...
>
> > So we need quickly to implement an ID for portlets that can
> > be used to quickly
> > reference and instanciate any portlet described in a user-PSML file.
> >
> > This reference must be:
> > - simple to compute
> > - persistent across server reboot and registry changes and
> > PSML file changes
> > - usable for locating uniquely a portlet description in a PSML file
> >
> > Any ideas about such scheme implementation would be greatly
> > appreciated.
>
> Maybe adding auto-incrementing IDs to all portlets in a file?
>
Do you feel like manually entering ids in your PSML files ? I don't. ;)
> > 5 - Currently working on
> > ------------------------
> >
> > Adding basic multi-access capability, see my response to
> > kevin WAP proposal.
>
> Looks really nice, should checkout from CVS as soon as possible...
>
Let me check in first...
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
