roller-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shervin Asgari <>
Subject New version of multidomain in roller
Date Fri, 14 Jul 2006 09:04:41 GMT
Hello developers.
We have developed a new version of the multidomain with some new 
changes. We have added a new role called domainadministrator. The 
domainadministrator can now administer his own domain. We have also 
added some editor functionality.

The new patch can be downloaded here. If you just want to quickly check 
out what we have made, then I have the whole roller 2.1 + multidomain 
sourcecode present. Just use your exisiting web server and run build 
after changing and the other necessary changes, and it 
should be ready for reviewing.

This will be the last version we commit this summer. Hope for some 
feedback during summer.

Below is the CAVEATS from the previous text in an updated form.


This solution is now considered to be in a production ready state. But there
are still things that could be improved.

The most urgent need for improvement is to add a new administration 
level for
domain administrators. This could be done by adding a new userrole called
"domainadmin". A domain administrator would then be associated with his 
through domainuser, and with the role through userrole. A user with these
associations whould then be able to administer what blogs are available 
in his
domain. This job is now left to a central administrator.

The procedure to create a new domain with a set of blogs is now to 
create the
users as the administrator user, create blogs for these users, create 
the new
domain and associate the blogs with the domain. This is quite time 
as the administrator needs to go through many different web forms. And login
as the created users to create the blogs for them. This procedure needs 
to be
simplified so the administrator can just create the domain and a domain
administrator. The domain administrator must then be able to create new 
with a new user as owner in one simplified form, where all the administrator
needs to enter is User full name, email-address (used as username), 
Name of blog and handle. The rest will get default values which can be 
by the users at a later time.

There is also a need for a domain editor. The news papers have legal
responsibility for the content they publish. The editor for the news paper
must therefore be able to remove or edit entries in any blog under his
domain in case a blog contains material that could result in legal issues.


Patches that enable URLs to be rewritten:

(Add context to be used later for URL rewrite)

(Rewrite URLs)

(Rewrite URLs and make description translatable:)

Patches that add new tables and a domain manager (DB stuff):

(Add the new database tables:)

(Add DomainManager:)

Patches that enable the use of the domain model (ie. filter incoming 
under /domain/ and rewrite URLs on the way out:

(A servlet filter to filter incoming domain requests, with helper classes:)

(Rewrite outgoing URLs:)

Patches that add a configuration interface that lets the administrator
administer the domain model:


(Add some constants:)

(Add menu items and bind JSPs to actions:)

(New properties used by domain administration interface:)

General patches used to fix problems we encountered:

(Add norsk and nynorsk as available languages:)

(Use language from current blog as default:)

(Use Asynchronous GET when gettin list of users, fixes Firefox bug:)

(Allow 255 character usernames to handle long email addresses:)

Shervin Asgari - System Consultant
M: +47 918 64 148, @:
Linpro AS - Leading on Linux	Tel: +47 21 54 41 00/02
Vitaminveien 1A        Fax: +47 21 54 41 01
PB 4 Grefsen, 0409 Oslo    WWW:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message