Mick Knutson wrote:
So that is not currently implemented?
The data migration features haven't been required yet, since 2.0 is the
first version. The data migration features will be provided in 2.1 to
help those migrating from one version to another. So it doesn't really
apply to your case
My biggest requirement for a portal server is the ability to customize the
user for a subscription based system.
I have Music artists, and listeners. Artists will buy and sell music, and
listeners will just be buying (not selling).
Take a look at the Portlet API's User Attributes feature
Its a pretty dynamic way to add customized attributes to users
Jetspeed supports the Portlet API, in fact we allow for multiple
providers of user attributes, so you could have user attributes coming
from say LDAP and a relational database, or provided under the portlet
api interfaces
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
