I had thought the mappings were fixed in 1.0? If you use multiple instances, bear in mind your memory usage will be considerably higher than a single instance. In our case, we switched over to virtual when XWiki 1.0b1 was released; before that we had several instances running. As to workarounds, this depends on the reason you've got multiple xwiki instances - if it's just to separate projects; you could achieve the same by making careful use of usergroups on a single xwiki instance (if you use panels, you check group membership before rendering the panel then it won't show for non-members). Naturally if one instance is to run locally and the other to run publicly, then it's easier - put the signature on the public one, and firewall the private one. -----Original Message----- From: hanspeter.klapf(a)gmx.at [mailto:hanspeter.klapf@gmx.at] Sent: 01 June 2007 10:28 To: xwiki-users(a)objectweb.org Subject: [xwiki-users] must xwiki really be aware of its context? In the xwiki-documentation I read about virtual wikis and their installation-procedure. While this is a great idea for a big number of wikis, it has some disadvantages for a small number of instances: - I need a wildcard-certificate (quite expensive) or X certificates for X wikis - Updates always take affect to each instances - An additional DNS-entry must be made for each instance (usually not the expertise of the wiki-administrator) For me it would be gread to use different context-names: wiki.mycompany.com/projectx wiki.mycompany.com/projecty This way, only one (no wildcard-) certificate is needed and a few instances would work on the same hardware. Unfortunately, some links/redirects are absolute (/xwiki/..) and so this is not possible. Will this feature be available in future? Are there any workarounds available? Thanks, Hanspeter