If I remember well, in the mentioned example, there's a thread that
periodically is creating a resource member. The service group will qualify
that resource as a group member.
There's no a direct / explicit link between the resource and the group...the
membership rules are defined at RMD level.
For example, the following is an extract of my service group resource RMD :
<Property name="wsrf-sg:MembershipContentRule"
modifiability="read-only" mutability="mutable">
<StaticValues>
<wsrf-sg:MembershipContentRule
MemberInterface="qman:QManWsResourcePortType"/>
</StaticValues>
</Property>
That property states that all resources that will be created will be part of
this service group only if they have the mentioned interface (port type).
Obviously there are a lot of things that you can use in order to specify
membership rules... you can find a better explanation about that here:
http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.pdf
Note that I'm not part of Muse developemnt team so what I'm writing is what
I understood browsing / using the module.
As I see this is what happens
1) a resource is created using *
Resource resource = resourceManager.createResource(<resource name>);
...
...
...
**resourceManager.addResource(resource.getEndpointReference(), resource);*
2) ResourceManager informs all resource manager listeners about this event
using *ResourceManagerListener.resourceAdded
*3) One of the register listeners is the *SimpleServiceGroup *that is doing
what I described above...
*
*Hope it helps...*
*Andrea
*
* 2009/3/12 SARA1232007 <[email protected]>
>
> Hi,
>
> In wsrf example, it seems that WSResource instances are assembled into
> ServiceGroup automatically. Can anyone tell me how this is done and which
> java class is reponsible for this?
>
> Thanks.
>
> SARA
> --
> View this message in context:
> http://www.nabble.com/Questions-about-wsrf-example-tp22471234p22471234.html
> Sent from the Muse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
