Yes, UIDGenerator.generateURNString() is the right method to use for
message IDs. The Synapse UUIDGenerator should indeed be
removed/deprecated for the same reasons as the UUIDGenerator in Axiom.
Andreas
On Wed, Oct 6, 2010 at 19:53, Hiranya Jayathilaka hiranya...@gmail.com wrote:
On Wed, Oct
On Thu, Oct 7, 2010 at 12:03 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Yes, UIDGenerator.generateURNString() is the right method to use for
message IDs. The Synapse UUIDGenerator should indeed be
removed/deprecated for the same reasons as the UUIDGenerator in Axiom.
Great. I'll do
On Wed, Oct 6, 2010 at 5:42 AM, Ruwan Linton ruwan.lin...@gmail.com wrote:
+1, please do this change into the branch as well.
Will do.
I also noticed that in certain places we use a UUIDGenerator
implementation in Synapse. The javadocs of this class says:
This is a thread-safe version of the
+1, please do this change into the branch as well.
Ruwan
On Wed, Oct 6, 2010 at 3:14 AM, Hiranya Jayathilaka hiranya...@gmail.comwrote:
Hi,
The ServerWorker impl of the NHTTP transport uses the deprecated
UUIDGenerator from Axiom to generate message IDs. The proper way of
doing this is by
