Hi Bongjae
I am trying to understand your use case. Can you walk me through an
end-to-end example covering both sending and receiving side and covering
startup to shutdown scenarios?
Thanks
Shreedhar
Bongjae Chang wrote:
> Hi.
> I havesome questions about DSC and MemberDetails
> I am trying to apply Shoal to our WAS(Web Application Server)
> WAS has many components. ex) JMS, Security, JNDI, etc...
> Acomponet has own configuration. If many WAS are clustered, I want to
> share configurations betweensame components.
> I knowDSC is applied to this case. But because GroupManagementService
> interface providesusers with MemberDetails API, if MemberDetails API
> has component parameter, I can only use GroupManagementService
> interface without using DSC directly.
> Of course, I know MemberDetails API is not for components but because
> DSC supports memory repositoryfor components, I think it is not bad
> that MemberDetails API is usedforcomponents. Actually I wanted to use
> only GMS API without DSC's knowledge in this case.
> ex)
> pubic void updateMemberDetails( final String memberToken, final String
> componentName, final Serializable key, final Serializable value ) {
> if ( componentName == null )
> componentName = MEMBER_DETAILS;
> ctx.getDistributedStateCache().addToCache( componentName, memberToken,
> key, value );
> }
> AndAssuming components already shared all configuration, if a
> component's configuration is changed dynamically, the component will
> maybe call updateMemberDetails() or DSC.addToCache() for renewing own
> configuration. Then other component will receive the change and the
> change will be updated locally in other component finally.
> But other component can't beaware of the change at this point of time.
> Of course the change will be updated well, but I just want to know
> this point of time in order to execute some logic.
> Of course, I knowI can resolve this usecase if I use
> MessageActionFactory and GroupHandle's sendMessage(componentName,
> message) and own memory repository.
> But I think that if DSC provides some listeners like GMSMessage, this
> usecase can be resolved easily.
> ex)
> gms.addActionFactory( new DistributedStateCacheFactoryImpl( callBack)
> ), componentName );
> I am eager to knowyour opinions about this. Please advice me.
> Thanks.
> --
> Bongjae Chang