You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Hiranya Jayathilaka <hi...@gmail.com> on 2010/10/05 23:44:39 UTC
Change ServerWorker to Use New UIDGenerator
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 using the new UIDGenerator (see [1] for details). The
IDs generated by the two are slightly different in structure:
UUIDGenerator (deprecated): urn:uuid:ADC550543A84B984B31286224511085
UIDGenerator: urn:uuid:68b32f40-70e0-4907-b053-7b6e694c6b02
In fact IDs generated by UUIDGenerator are not standard compliant and
it could cause interop issues. So shall we modify the ServerWorker to
use the new UIDGenerator?
Thanks,
Hiranya
[1] - https://issues.apache.org/jira/browse/AXIS2-4527
--
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Change ServerWorker to Use New UIDGenerator
Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Thu, Oct 7, 2010 at 12:03 PM, Andreas Veithen
<an...@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 the changes.
Thanks,
Hiranya
>
> Andreas
>
> On Wed, Oct 6, 2010 at 19:53, Hiranya Jayathilaka <hi...@gmail.com> wrote:
>> On Wed, Oct 6, 2010 at 5:42 AM, Ruwan Linton <ru...@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 Axiom UUIDGenerator to be used
>> until it is fixed in the next Axiom release"
>>
>> So I think now we can use the new UIDGenerator from Axiom and retire
>> the Synapse UUIDGenerator. Andreas, can you please verify this? Is it
>> ok to switch?
>>
>> Thanks,
>> Hiranya
>>
>>> Ruwan
>>>
>>> On Wed, Oct 6, 2010 at 3:14 AM, Hiranya Jayathilaka <hi...@gmail.com>
>>> wrote:
>>>>
>>>> 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 using the new UIDGenerator (see [1] for details). The
>>>> IDs generated by the two are slightly different in structure:
>>>>
>>>> UUIDGenerator (deprecated): urn:uuid:ADC550543A84B984B31286224511085
>>>> UIDGenerator: urn:uuid:68b32f40-70e0-4907-b053-7b6e694c6b02
>>>>
>>>> In fact IDs generated by UUIDGenerator are not standard compliant and
>>>> it could cause interop issues. So shall we modify the ServerWorker to
>>>> use the new UIDGenerator?
>>>>
>>>> Thanks,
>>>> Hiranya
>>>>
>>>> [1] - https://issues.apache.org/jira/browse/AXIS2-4527
>>>>
>>>> --
>>>> Hiranya Jayathilaka
>>>> Senior Software Engineer;
>>>> WSO2 Inc.; http://wso2.org
>>>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> google: http://www.google.com/profiles/ruwan.linton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.; http://wso2.org
>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Change ServerWorker to Use New UIDGenerator
Posted by Andreas Veithen <an...@gmail.com>.
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 <hi...@gmail.com> wrote:
> On Wed, Oct 6, 2010 at 5:42 AM, Ruwan Linton <ru...@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 Axiom UUIDGenerator to be used
> until it is fixed in the next Axiom release"
>
> So I think now we can use the new UIDGenerator from Axiom and retire
> the Synapse UUIDGenerator. Andreas, can you please verify this? Is it
> ok to switch?
>
> Thanks,
> Hiranya
>
>> Ruwan
>>
>> On Wed, Oct 6, 2010 at 3:14 AM, Hiranya Jayathilaka <hi...@gmail.com>
>> wrote:
>>>
>>> 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 using the new UIDGenerator (see [1] for details). The
>>> IDs generated by the two are slightly different in structure:
>>>
>>> UUIDGenerator (deprecated): urn:uuid:ADC550543A84B984B31286224511085
>>> UIDGenerator: urn:uuid:68b32f40-70e0-4907-b053-7b6e694c6b02
>>>
>>> In fact IDs generated by UUIDGenerator are not standard compliant and
>>> it could cause interop issues. So shall we modify the ServerWorker to
>>> use the new UIDGenerator?
>>>
>>> Thanks,
>>> Hiranya
>>>
>>> [1] - https://issues.apache.org/jira/browse/AXIS2-4527
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Senior Software Engineer;
>>> WSO2 Inc.; http://wso2.org
>>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.; http://wso2.org
> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Change ServerWorker to Use New UIDGenerator
Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Wed, Oct 6, 2010 at 5:42 AM, Ruwan Linton <ru...@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 Axiom UUIDGenerator to be used
until it is fixed in the next Axiom release"
So I think now we can use the new UIDGenerator from Axiom and retire
the Synapse UUIDGenerator. Andreas, can you please verify this? Is it
ok to switch?
Thanks,
Hiranya
> Ruwan
>
> On Wed, Oct 6, 2010 at 3:14 AM, Hiranya Jayathilaka <hi...@gmail.com>
> wrote:
>>
>> 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 using the new UIDGenerator (see [1] for details). The
>> IDs generated by the two are slightly different in structure:
>>
>> UUIDGenerator (deprecated): urn:uuid:ADC550543A84B984B31286224511085
>> UIDGenerator: urn:uuid:68b32f40-70e0-4907-b053-7b6e694c6b02
>>
>> In fact IDs generated by UUIDGenerator are not standard compliant and
>> it could cause interop issues. So shall we modify the ServerWorker to
>> use the new UIDGenerator?
>>
>> Thanks,
>> Hiranya
>>
>> [1] - https://issues.apache.org/jira/browse/AXIS2-4527
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.; http://wso2.org
>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
--
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Change ServerWorker to Use New UIDGenerator
Posted by Ruwan Linton <ru...@gmail.com>.
+1, please do this change into the branch as well.
Ruwan
On Wed, Oct 6, 2010 at 3:14 AM, Hiranya Jayathilaka <hi...@gmail.com>wrote:
> 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 using the new UIDGenerator (see [1] for details). The
> IDs generated by the two are slightly different in structure:
>
> UUIDGenerator (deprecated): urn:uuid:ADC550543A84B984B31286224511085
> UIDGenerator: urn:uuid:68b32f40-70e0-4907-b053-7b6e694c6b02
>
> In fact IDs generated by UUIDGenerator are not standard compliant and
> it could cause interop issues. So shall we modify the ServerWorker to
> use the new UIDGenerator?
>
> Thanks,
> Hiranya
>
> [1] - https://issues.apache.org/jira/browse/AXIS2-4527
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.; http://wso2.org
> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton