deserves a larger audience than that, so I'm repeating it here.
I'm using the 4.5 beta release from CVS as of about 1 week ago.
This problem is observed when I create two subfolders of the main
site, say foo1 and foo2, and then mount an instance of Subsite at each
folder (using the "New Application" option).
When the first instance is mounted, OACS appropriately creates an
application group for the subsite and an apm_package instance of
acs-subsite. However, when the second instance is mounted (foo2),
OACS does all of the above PLUS creates a composition relation between
the foo1 and foo2 application groups.
This seems incorrect to me. These subsites are at the same "level."
Why should one be "composed" of the other just because one was mounted
before the other? (Note: I specified the "New Application" mounting
method both times)
Additonally, I notice that if I visit the group admin pages for the
site and subsites I can only "see" the following groups defined:
At Main Site Group Admin: No Groups Defined
At Foo1 Group Admin: Main Site Parties, Foo2 Subsite Parties
At Foo2 Group Admin: No Groups Defined
I would have thought that ALL groups would have been visible from the
Main Site admin pages.
It looks to me like maybe the subsite code is assigning the "reverse"
of the relations that it should be but I hope that someone who is up
on this will comment...