Keith Chapman wrote:
How do you generate the tables required by the user manager? Are you
using a separate user manager specific script for that.
It is recommended to use derby-complete.sql as now registry and user
manager are merged.
derby-complete.sql was meant for the complete database, thats registry
and UM as a whole (including authentication tables). derby-registry.sql
was meant for the ppl who do authentication from else where. What we
merged was Registry and UM authorization and not the complete UM.
So If we want to use a separate authenticating mechanism we should
use derby-registry.sql. Thats what we do.
Also note that irrelevant of what scripts we use its always better to do
the change across all scripts so that you dont miss one accidentally.
(Which was the case here)
+1. I forgot to update the derby-registry.sql.
Thanks,
Keith.
I think you are mistaken here.
No. Now we need to have UM authorization tables also in the
derby-registry.sql (may be with a more suitable name for the script).
Because it is not a good idea to use two scripts to create tables for
the same database.
Thanks,
Chathura
Registry assumes the existence of user manager
tables in its database, specially for the more user centric features we
are planning to add.
Thanks,
Chathura
I just committed the change to the Registry SVN.
Tyrell
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
