I'm -1 for creating new artifacts at this stage.

   1. Work involved in introducing a new artifact
      - creating relevant wizards
      - this particular artifact requires update on the existing ESB editor.
   2. the plan is to freeze the branch at 1.0.13. Thus new artifacts should
   be attempted at trunk. not at the branch.
   3. a fix need to go at the carbon end to support deploying this new
   artifact type

Saminda

On Tue, Aug 2, 2011 at 12:43 PM, Malith Dhanushka <[email protected]> wrote:

> Hi all,
> I am in the process of adding Message Store feature to the Carbon Studio.So
> are we going to introduce it as a new artifact?
> WDYT.
>
> On Mon, Jun 6, 2011 at 3:37 PM, Malith Dhanushka <[email protected]> wrote:
>
>> Hi all,
>> We have identified following areas need to be modified in the
>> current CS ESB Editor to sync properly with the upcoming release of ESB.
>>
>>    - New mediators
>>       - store mediator
>>       - url re-writer
>>       - call-template
>>       - conditional-router
>>    - New features
>>       - message store
>>       - message process
>>       - sequence template
>>       - endpoint template
>>    - Modified mediators
>>       - Send
>>       - XSLT
>>       - XQuery
>>       - Validate
>>       - Clone
>>       - Aggregate
>>       - Iterate
>>       - Sequence
>>       - Event
>>       - Sequence -<description> element
>>
>>
>> Mediator modification is already finished & developing new
>> mediators,features is now in progress.
>>
>> Thanks,
>> Malith
>>
>
> Thanks,
> Malith
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to