Removing engineering@ and adding architecture@.

Thanks and Regards,
AsankaS.


On Fri, Jan 17, 2014 at 4:52 PM, Selvaratnam Uthaiyashankar <
[email protected]> wrote:

> Why this is private (in engineering@)? It sounds like architecture@ for
> me.
>
> Regards,
> Shankar
>
>
> On Fri, Jan 17, 2014 at 9:03 AM, Asanka Sanjeewa <[email protected]> wrote:
>
>> Hi All
>>
>> From Developer Studio end it should provide functionality to test a ESB
>> config project with the minimal set of steps. For example if user may right
>> click on a particular ESB config project and select 'Test' it should create
>> necessary sample proxies, sequences, etc. and deploy them on a particular
>> ESB server (if already added to the developer studio servers, else it
>> should ask user to point CARBON_HOME of the ESB server and the server will
>> be started and the artifacts will be deployed).
>>
>> In debugging state developer studio should depict the graphical flow of
>> mediation and it should display the information of the particular state of
>> the mediation flow where the debug point has been hit. Those information
>> should be displayed in human readable manner. Developer studio will
>> communicate with ESB or the activity monitoring tool in retrieving
>> information of the particular debug point.
>>
>> Please feel free to add anything I have missed.
>>
>> Thanks and Regards,
>> AsankaS.
>>
>>
>> On Thu, Jan 16, 2014 at 7:43 PM, Jeewantha Dharmaparakrama <
>> [email protected]> wrote:
>>
>>> Hi All,
>>>
>>> In this meeting we identified the following areas which need to be done
>>> for Milestone 1.
>>>
>>> Firstly, the flow debugger does Not stop the execution flow of the ESB
>>> but simply persist the data so that it can be properly presented via a Web
>>> console, DevS or BAM. The data can include transport level properties,
>>> payloads, headers etc.
>>>
>>> The debugger should be able to be turned on and off from proxy level,
>>> api level or sequence level such that turning debugging on in one, would
>>> not affect the others.
>>>
>>> Once debugging is on, the information should be shown before and after
>>> the message hit the logical block of execution. For example, If debugging
>>> is turned on for *Sequence1*, the user should be able to analyse the
>>> messages came into and went out of *Sequence1*.
>>>
>>> To extend the usability of this feature, the ESB should be able to
>>> filter out the messages which hit the debugger. For example, if the user
>>> needs debug information of messages coming from a particular client, the
>>> debugger should be able to pick the right messages by looking at its source
>>> address.
>>>
>>> Please feel free to add anything I missed.
>>>
>>> Thanks,
>>> Jeewantha
>>>
>>>
>>>
>>> --
>>> Jeewantha Dharmaparakrama
>>> Software Engineer; WSO2, Inc.; http://wso2.com/
>>> Phone : (+94) 774726790
>>> Skype : prasad.jeewantha
>>> LinkedIn : http://www.linkedin.com/in/jeewanthad
>>> Twitter: https://twitter.com/jeewamp
>>> Blog: http://jeewanthad.blogspot.com/
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 Engineering Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit
>>> https://groups.google.com/a/wso2.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>> *Asanka Sanjeewa*
>> Senior Software Engineer
>> Mobile: +94772532924
>> WSO2 Inc. http://wso2.com/
>> Blog: http://asanka-tech-blog.blogspot.com/
>>
>>   --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Engineering Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit
>> https://groups.google.com/a/wso2.com/groups/opt_out.
>>
>
>
>
> --
> S.Uthaiyashankar
> VP Engineering
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591
>



-- 
*Asanka Sanjeewa*
Senior Software Engineer
Mobile: +94772532924
WSO2 Inc. http://wso2.com/
Blog: http://asanka-tech-blog.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to