> > 
> > Why don't you simply implement check? The UserContext is an argument

> > then? I mean, why are you calling the security methods yourself in
the 
> > first place? Perhaps I don't quite understand your problem....
> 
> I do implement check(), but it's impossible to call it from 
> any other place than the classes inside the 
> org.mmbase.bridge.implementation package. These classes are 
> the only ones that have access to the package-protected 
> method BasicUser.getUserContext.

Is it an idea to make BasicUser.getUserContext() public? Why is it
package-protected in the first place?


Regards,
Ronald.



-----------------------Disclaimer-------------------------
Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor mogelijke 
onjuistheid en/of onvolledigheid van de hierin verstrekte informatie kan Kennisnet 
geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud van dit bericht (met 
bijlagen) rechten worden ontleend. De inhoud van dit bericht (met bijlagen) kan 
vertrouwelijke informatie bevatten en is uitsluitend bestemd voor de geadresseerde van 
dit bericht. Indien u niet de beoogde ontvanger van dit bericht bent, verzoekt 
Kennisnet u dit bericht te verwijderen, eventuele bijlagen niet te openen en wijst 
Kennisnet u op de onrechtmatigheid van het gebruiken, kopiëren of verspreiden van de 
inhoud van dit bericht (met bijlagen).

This message (with attachments) is given in good faith. Kennisnet cannot assume any 
responsibility for the accuracy or reliability of the information contained in this 
message (with attachments), nor shall the information be construed as constituting any 
obligation on the part of Kennisnet. The information contained in this message (with 
attachments) may be confidential or privileged and is only intended for the use of the 
named addressee. If you are not the intended recipient, you are requested by Kennisnet 
to delete this message (with attachments) without opening it and you are notified by 
Kennisnet that any disclosure, copying or distribution of the information contained in 
this message (with attachments) is strictly prohibited and unlawful.
----------------------------------------------------------


Reply via email to