TUSCANY-2055 has raised an issue where we need some spec clarity. Namely, in relation to the function ServiceReference.getConversationID(), the Java Annotations and API V1 spec says a few things.
521 1.6.6.2. Accessing Conversation IDs from Clients 522 Whether the conversation ID is chosen by the client or is generated by the system, the client may access 523 the conversation ID by calling ServiceReference.getConversationID(). 924 • getConversationID() - Returns the id supplied by the user that will be associated with 925 conversations initiated through this reference. 946 • getConversationID() - Returns the identifier for this conversation. If a user-defined identity had 947 been supplied for this reference then its value will be returned; otherwise the identity generated by 948 the system when the conversation was initiated will be returned. As I said in my JIRA comment my interpretation is that the Conversation object represents the current conversation so you should always go there to get the current conversationID. The get/setConversationId on the ServiceReference allows the user to provide a conversation ID that will subsequently be used for new conversations. Hence you won't get the current conversationID by calling getConversationId on ServiceReference you'll just get whatever you set there manually. Do one of the people here who are directly involved in the Java spec know what is intended. If not I'll mail the spec list with the question. Let me know. Simon
