XMPP RA Activity ID
Right now the Activity ID created in XMPP Resource Adaptor is the event hashCode(). This means that each event, which is the XMPP packet received, creates a new Activity.
The XMPP Activity does not have any value for services right now, but the fact that 2 events related arrive at the RA and may be delivered in the wrong order is a real problem right now. Note that this is a real possibility because those 2 events do not belong to the same SLEE transaction because they will be fired to different ACs.
Ok, we need to change that Activity ID, that is mandatory, what I seek here is an agreement to what is the best solution for this key.
The XMPP packet recieved has the following common attributes:
Id: the packet identification
From: the entity that sent the packet
To: the entity that will receive the packet
Type: the subtype of the packet, since the packet type is the element name (Message,Presence,IQ)
In my opinion the ID should be a (From,To) key, this would fix the order of related events problem, the AC creation grain would be appropriated too (not too much, not too less).