I don't really see the point of two distinct User implementations, where one will wrap and return the other, so I would not mind changing all this, but it will give compatibility issues.
Persinally I oprefer making getUserContext(0 a part of the interface.
this way, when people use the UserContext, they are _explicitly_ making use of the MMBase security framework. And breaking backward compatibility in the bridge doesn't sound like a good idea.
Otoh, implementing bridge methods in the security layer doesn't seem too hard.
I suggest you simply call a vote on this.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
