You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commons-dev@ws.apache.org by Senaka Fernando <se...@gmail.com> on 2008/10/16 11:34:44 UTC

[Transport] Branch for JMS MapMessage support addition

Hi all,

I'm looking forward to create a branch to work on the addition of MapMessage
support to the JMS Transport. Since adding MapMessage support is a bit
tricky there can be some un-stability of code, sometimes. So, instead of
making the trunk unstable, thought of creating a branch instead.

Best Regards,
Senaka

Re: [Transport] Branch for JMS MapMessage support addition

Posted by Senaka Fernando <se...@gmail.com>.

Hi all,

I have added the branch I requested at [1], in the scratch area created for
WS-Commons at [2]. The commit message is found at [3].

[1]
http://svn.apache.org/repos/asf/webservices/commons/trunk/scratch/senaka/sci-flex/transport
[2] http://svn.apache.org/repos/asf/webservices/commons/trunk/scratch/
[3] http://markmail.org/message/26us6dq3hv6pw5zt

Thanks,
Senaka

On Thu, Oct 16, 2008 at 5:01 PM, Asankha C. Perera <as...@wso2.com> wrote:

> Hi Senaka
>
>> The commons trunk does not as yet have a
>> scratch area, so am I good to go by creating the scratch area at [1], or
>> is
>> it better to have it somewhere else on the trunk?
>>
>>
> I think location [1] is fine.. as it follows the typical scratch location
> in trunk
>
> asankha
>

Re: [Transport] Branch for JMS MapMessage support addition

Posted by "Asankha C. Perera" <as...@wso2.com>.

Hi Senaka
> The commons trunk does not as yet have a
> scratch area, so am I good to go by creating the scratch area at [1], or is
> it better to have it somewhere else on the trunk?
>   
I think location [1] is fine.. as it follows the typical scratch 
location in trunk

asankha

Re: [Transport] Branch for JMS MapMessage support addition

Posted by Senaka Fernando <se...@gmail.com>.

Hi Asankha,

Thanks for the clarification. The commons trunk does not as yet have a
scratch area, so am I good to go by creating the scratch area at [1], or is
it better to have it somewhere else on the trunk?

[1] https://svn.apache.org/repos/asf/webservices/commons/trunk/scratch/

Thanks,
Senaka

On Thu, Oct 16, 2008 at 3:28 PM, Asankha C. Perera <as...@wso2.com> wrote:

> Senaka
>
> I do not think this warrants for a branch.. since a branch is typically
> created for a release etc where many people will work on or used for
> maintenance. You could however create private branch for yourself at [1]
> similar to the ones we have used for Synapse [2] in the past
>
> asankha
>
> [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/scratch/
> [2] https://svn.apache.org/repos/asf/synapse/trunk/scratch/
>
>
> Senaka Fernando wrote:
>
>> Hi all,
>>
>> I'm looking forward to create a branch to work on the addition of
>> MapMessage
>> support to the JMS Transport. Since adding MapMessage support is a bit
>> tricky there can be some un-stability of code, sometimes. So, instead of
>> making the trunk unstable, thought of creating a branch instead.
>>
>> Best Regards,
>> Senaka
>>
>>
>>
>

Re: [Transport] Branch for JMS MapMessage support addition

Posted by "Asankha C. Perera" <as...@wso2.com>.

Senaka

I do not think this warrants for a branch.. since a branch is typically 
created for a release etc where many people will work on or used for 
maintenance. You could however create private branch for yourself at [1] 
similar to the ones we have used for Synapse [2] in the past

asankha

[1] https://svn.apache.org/repos/asf/webservices/commons/trunk/scratch/
[2] https://svn.apache.org/repos/asf/synapse/trunk/scratch/

Senaka Fernando wrote:
> Hi all,
>
> I'm looking forward to create a branch to work on the addition of MapMessage
> support to the JMS Transport. Since adding MapMessage support is a bit
> tricky there can be some un-stability of code, sometimes. So, instead of
> making the trunk unstable, thought of creating a branch instead.
>
> Best Regards,
> Senaka
>
>