needs to handle all initial events from all of the bound RA entities, but the
logic might depend on which particular entity an event came from.
--
Vilius Panevėžys
Elitnet
On 2011-03-28 19:17, Eduardo Martins wrote:
> Well, I think there would be no harm to have an additional attribute
> in the event type definition (sbb descriptor), to define a ra entity
> name, and if such definition was done, only events form that ra entity
> would create new service instances.
>
> We can define such extension, as we did before, what do you guys think
> about that?
>
> -- Eduardo
> ..............................................
> http://emmartins.blogspot.com
> http://redhat.com/solutions/telco
>
>
>
> 2011/3/28 fab.<fabien.markart@gmail.com>:
>> In case of an InitialEvent, if there're multiple entities of the same
>> RA Type, the SBB should know if the InitialEvent has been triggered by
>> its ra entity.
>>
>> From my point of view I'll be glad to see the specs suggesting an
>> entity ID in the activity (or the event) to make the link between the
>> potential InitialEvent, and the RA Entity my SBB is linked to, that
>> way if the event is not from my entity I will ignore it in the
>> InitialEventSelector.
>>
>> At least as workaround it the solution I've implemented in my homemade RAs.
>>
>> --
>> (\ /) | fab.
>> ( . .) | facile, rentable, légal mais jamais les trois à la fois
>> c(")(") | http://www.linkedin.com/in/fabienmarkart
>>
>>
>>
>> 2011/3/28 Eduardo Martins<emmartins@gmail.com>:
>>> By the way, just to correct some of your reasoning, the ACI Factory is
>>> not bound to a particular RA Entity, it is bound to the RA Type (see
>>> the sbb descriptor). This means the factory will interact with all RA
>>> entities of the RA Type, no matter if you are bound to just a
>>> particular entity link for the SBB Interface. The factory will only
>>> return null if the activity does not belongs to any of the existent RA
>>> entities.
>>>
>>> -- Eduardo
>>> ..............................................
>>> http://emmartins.blogspot.com
>>> http://redhat.com/solutions/telco
>>>
>>> 2011/3/28 Vilius Panevėžys<vilius@elitnet.lt>:
>>>> When a service has multiple resource adaptor entity bindings, sometimes
>>>> there's the need to distinguish the particular entity that delivered an
>>>> event.
>>>>
>>>> There are a couple of RA-implementation-specific methods for that in our
>>>> case one of which involves exposing implementation classes to SBB, which is
>>>> not clean and I always prefer doing things the standard and recommended way.
>>>>
>>>> One method that should work according to JSLEE is to get the activity from
>>>> event, then iterate through ACIFs of all bound RA entities invoking
>>>> getActivityContextInterface(activity). The activity belongs to the entity,
>>>> which returned non-null ACI. Is this good performance-wise? Are there any
>>>> superior methods?
>>>>
>>>>
>>>> TIA,
>>>> --
>>>> Vilius Panevėžys
>>>> Elitnet
>>>>
>>>
>>
>
>