[Registry-dev] Needing a context for Registry

[Chathura C. Ekanayake]

Hi Paul,

AuthorizingRealm for each user is stored in  the user's SecureRegistry 
instance. But we also need access to the DefaultRealm, which is used to 
create
SecureRegistry instances (AuthorizingRealms are created inside the 
SecureRegistry constructor).

We are also keeping a SecureRegistry instance created using the "system" 
user for performing background tasks (adding initial users, roles, 
creating queries for advance search operations, etc.).

Therefore, we need to access those three classes from many places of the 
code. Keeping them as three servlet context properties is also an 
option. But then we have to pass servlet context (or the request) object 
to all places that need to access them. I think there are some parts in 
APP impl, where the servlet context is not available.

So I think that having a RegistryContext as a system property would 
solve these problems.

Thanks,
Chathura

Paul Fremantle wrote:
> Can you explain why we are storing these in the system.properties?
>
> I thought the realm was stored in the secureRegistry instance. I would 
> have thought that the Registry instance was stored in the Servlet 
> instance.
>
> Paul
>
> Deepal Jayasinghe wrote:
>> At the beginning  we had to throw away the RegistryContext (runtime
>> object of the registry) since we did not find real  use of having that.
>> But now we are storing three separate properties in System.properties so
>> how about introduce a new class to keep all of them and store only that
>> in the System.property (In the future we may have some more). We are
>> storing following in the servlet and system.properties
>>
>>  - Registry instance
>>  - systemRegistry
>>  - RegistryRealm
>>
>> Thoughts ...
>>
>> -Deepal
>>
>>
>> _______________________________________________
>> Registry-dev mailing list
>> Registry-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
>>
>