I have implemented a new feature in the PageManager to leverage use of the "navigation" profiling rule to provide subsite isolation/partitioning. I have also extended the J2 demo site to add a subsite. While not related to subsites per se, this example also has two users associated with it to demonstrate a handy profiling technique that can be used to specify default pages for users with multiple roles.
Login and subsite/subsite or subsite2/subsite2 to navigate to the subsite. Note that you will be deposited in different default pages depending on the user's profiling rule and that the global navigation elements from the root directory are not included in the subsite. The content for this subsite is located in ../WEB-INF/pages/__subsite-root, (note that subsites will always be denoted by the "__" prefix). See the remaining configuration details in populate-userinfo-for-default-psml.sql. Security configuration is not partitioned and is still controlled globally by the principal configurations in the security DB tables and the /page.security file. Consequently, a principle will have to have view permissions on "/" in order to view the subsite. We can consider partitioning the security infomation per site if it seems appropriate in the future... I did not see the immediate value in attempting this at this point without input from others. No doubt the subsite profiling and related security issues may need tuning as they are used. Feedback is always welcome! Randy