[Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration
Amila Silva
amilas at wso2.com
Tue Jun 21 03:54:55 EDT 2011
Hi,
[Progress Update]
=============
Focused on several tasks during last few days,
1 Notably, message mediation support.
~What I did was, modeling a separate component called "message mediator"
(which is not really a mediator)
to graphically represent message mediation.
~A single "message mediator" component can be added to the "ESB server", to
the left side, along with proxy services.
Similar to proxy services, "message mediator" has an input connector and
an output connector.
~When serializing, components connected on the input connector will belong
to "in" mediator of "main sequence" (similarly, "out")
~Had to give some thought and change the interface "EsbNodeTransformer",
because it was written focusing on just service mediation.
Created "TransformationInfo" to store related data to be passed to
separate transformers of components.
2 Experiments on how to add reusable sequences.
~Initially thought of having a single compartment, place a mediator snapped
to its left border (similar to proxy services in parent compartment),
another mediator to the right border (similar to endpoints) and enabling
to add any number of mediators in the middle.
(figure 1 below)
But faced a technical limitation on GMF. EditPart classes (controller
classes of MVC pattern) that can be placed on the border of a component
are extended from a different class than that of others.
(eg: ProxyServiceEditPart extends BorderedBorderItemEditPart vs
LogMediatorEditPart extends AbstractBorderedShapeEditPart)
~Tried another approach, which is, dividing graphical representation of
sequence to 3 parts. (3 border-less compartments) (figure 2)
Was able to get that working but the GMF generated code's readability is
poor.
for example,
after mapping Log Mediator to server figure and 3 compartments of sequence
figure, 4 EditPart classes are generated
(LogMediatorEditPart, LogMediator2EditPart, LogMediator3EditPart,
LogMediator4EditPart)
So if this is done for like 30 mediators, code would look messy (120 edit
part classes and 4x customizations).
[image: re-usable_sequences_ex.png]
~Or we can just add input/output connectors of its own to a sequence but
then the user will have to connect them to a mediator inside it, which is an
extra step.
Will see if there's a better way to do this.
3 Started working on switch mediator
~ Added model modifications, generated model, edit, diagram code.
~ Serialization part is almost done.
~ Added ability to add case branches after creating the switch mediator
~ Working on a method to automatically arrange user created case branch
graphical representation. (output connectors)
4 With help from Melan, Added and linked configuration dialogs for XSLT
mediator and switch mediator.
5 Did some UI improvements, including node size, background, automatically
switching to "WSO2 ESB Graphical" perspective.
On Fri, Jun 17, 2011 at 4:49 PM, Amila Silva <amilas at wso2.com> wrote:
>
>
> On Fri, Jun 17, 2011 at 4:17 PM, Paul Fremantle <paul at wso2.com> wrote:
>
>> Amila
>>
>> Is there a more recent build? How do I install? Do I need other prereqs?
>>
> Currently I'm middle of adding message mediation support, so it'll take a
> day or two to provide a new build.
>
> You don't need to install anything separately, eclipse will automatically
> install all necessary libraries.
>
> Installing (will take about 15min)
> =====================
> 1. Launch a new Eclipse and goto Help->Install New Software.
>
> 2. Point to the location of the zip file.
> 3. *Untick "group items by category"* and select EsbGraphicalEditor to
> install.
> 4. *Tick "Contact all update sites during install"*
> 5. Click Next and install as usual (while installing it'll download EMF,
> GMF and other required runtime libs)
> 6. Restart eclipse
>
> Trying out
> ========
> 1. Create a new project (for now any type of project, eg: java): Goto *
> File->New->Project*.
> 3. Create a new ESB Diagram: Goto *File->New->Other* . Select *ESB diagram
> * from the category Examples
> 2. Switch to WSO2 ESB Graphical Editor perspective. Goto *Window->Open
> Perspective->Other.. *and select *WSO2 ESB Graphical*
>
> 4. Create a new Server:
> a. Select the tool "EsbServer" from the palette and draw. or
>
> b. Drag and drop the tool "EsbServer"
> 5. Proxy services can be added of left side and endpoints can be added to
> right side of the server figure.
> Eg: To add a proxy service, select the relevant tool and click near the
> left border (just inside the server).
>
> 6. Proxy services, mediators and enpoints should be connected using the
> tool "*Esb Link*"
> Eg: To connect a proxy service to a log mediator, select the Esb Link
> tool, point the mouse on output connector of the proxy service (the
> arrowhead pointing outwards) and drag to the input connector of the log
> mediator)
> 7. Switch to source view as you edit the diagram, source will be
> automatically updated.
>
>
>>
>> Paul
>>
>>
>> On 8 June 2011 14:54, Amila Silva <amilas at wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Jun 8, 2011 at 1:44 PM, Samisa Abeysinghe <samisa at wso2.com>wrote:
>>>
>>>> Are the sequences "named"? How can I re-use a given sequence in another
>>>> proxy service?
>>>
>>> No. mediator sequences are added anonymously inside proxy services. So
>>> currently, you cannot re-use a sequence.
>>> How to represent sequences in a diagram should be further discussed.
>>>
>>>>
>>>> On Tue, Jun 7, 2011 at 10:40 PM, Amila Silva <amilas at wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Tue, Jun 7, 2011 at 10:07 PM, Paul Fremantle <paul at wso2.com> wrote:
>>>>>
>>>>>> Is there a new build I can install on Eclipse?
>>>>>
>>>>> Right now there isn't. Will provide a pack soon.
>>>>> Source is at [1].
>>>>>
>>>>>>
>>>>>> I'd love to play with this.
>>>>>>
>>>>> Please get the feature pack from [FP2]
>>>
>>>
>>> Installing the feature (will take about 15min):
>>> 1. Goto Help->Install New Software and point to the location of the zip
>>> file.
>>> 3. Untick "group items by category" and select EsbGraphicalEditor to
>>> install.
>>> 4. Tick "Contact all update sites during install"
>>> 5. Click Next and install as usual (while installing it'll download EMF,
>>> GMF and other required runtime libs)
>>>
>>> [FP2] -
>>> http://builder.wso2.org/~carbon/carbon-studio/scratch/EsbGraphicalEditor/0.1.0/feature/ESBGraphicalEditor_0.1.0.zip
>>>
>>>>
>>>>>> Paul
>>>>>>
>>>>>>
>>>>>> On 7 June 2011 17:36, Chathuri Wimalasena <chathuri at wso2.com> wrote:
>>>>>>
>>>>>>> Hi Amila,
>>>>>>>
>>>>>>> It will be better if we can highlight the names of the mediators.
>>>>>>> What is the usage of "Properties" tab in the editor ? Is it same as
>>>>>>> Properties view ?
>>>>>>>
>>>>>> Will do.
>>>>> "Properties" tab is just temporary (empty) as of now. I was thinking
>>>>> may be we can add some global settings (such as a registry, priority
>>>>> executor). Just a thought.
>>>>>
>>>>>>
>>>>>>> Regards,
>>>>>>> Chathuri
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jun 7, 2011 at 8:49 PM, Saminda Wijeratne <samindaw at wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jun 7, 2011 at 7:26 PM, Sumedha Rubasinghe <
>>>>>>>> sumedha at wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Amila,
>>>>>>>>> "Esb Diagram Editing" is a wrong term. what your editing is a
>>>>>>>>> Synapse Configuration.
>>>>>>>>>
>>>>>>>>> I would rather have it as "Synapse Configuration". That sort of
>>>>>>>>> goes hand in hand with "Diagram", "source" tabs as well.
>>>>>>>>>
>>>>>>>> In this case it should be the name of the file in workspace I guess.
>>>>>>>>
>>>>>>> Thanks for the feedback.
>>>>>
>>>>>>
>>>>>>>>
>>>>>>>>> BTW, "Diagram" should be "Design" as per Eclipse standards.
>>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>> Changed "Diagram" to "Design".
>>>>>
>>>>>>
>>>>>>>> Saminda
>>>>>>>>
>>>>>>>>>
>>>>>>>>> /sumedha
>>>>>>>>>
>>>>>>>>>
>>>>> [1] -
>>>>> https://svn.wso2.com/wso2/sites/intern/amilamanoj/esbGraphicalEditor
>>>>>
>>>>>>
>>>>>>>>> On Tue, Jun 7, 2011 at 6:24 PM, Amila Silva <amilas at wso2.com>wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> [Progress Update: Since last week]
>>>>>>>>>> ~ Added property grouping. Now the properties for proxy services,
>>>>>>>>>> mediators and endpoints are organized into categories (screenshots 1,2)
>>>>>>>>>> ~ Added XPath tooling support. Reused "NameSpacedPropertyEditor"
>>>>>>>>>> and "XPathSelector" dialog boxes from carbon studio for this. Now a user can
>>>>>>>>>> pick xpath from an XML file. (screenshot 3)
>>>>>>>>>> ~ Enhanced Enrich mediator support by linking xpath editor with
>>>>>>>>>> source and target xpath properties and by adding serialization support for
>>>>>>>>>> xpath.
>>>>>>>>>> ~ Enhanced Filter mediator support by linking xpath editor to
>>>>>>>>>> "filter source" and "xpath" properties.
>>>>>>>>>> ~ Added graphical representation for XSLT mediator.
>>>>>>>>>> ~ Minor bug fixes.
>>>>>>>>>> ~ UI improvements:
>>>>>>>>>> - Improved "WSO2 ESB Graphical Editor" eclipse perspective
>>>>>>>>>> by adding outline view to bottom-left. (screenshot 4)
>>>>>>>>>> Outline view allows:
>>>>>>>>>> Viewing overall ESB configuration.
>>>>>>>>>> Navigating when the diagram is larger than the
>>>>>>>>>> editor.
>>>>>>>>>> - Got a nice set of mediator icons from Chanaka. Now Log,
>>>>>>>>>> Drop and Enrich mediators look better.
>>>>>>>>>> ~ Added serializing support for XSLT mediator.
>>>>>>>>>>
>>>>>>>>>> [Tasks in progress...]
>>>>>>>>>> ~ Creating a custom configuration dialog box for XSLT mediator (to
>>>>>>>>>> specify properties, features, resources)
>>>>>>>>>> ~ Adding switch mediator
>>>>>>>>>> Graphical representation of switch mediator is somewhat
>>>>>>>>>> different than that of other mediators.
>>>>>>>>>> In switch mediator, users should be able to add any number
>>>>>>>>>> of output connectors (case branches) as they wish.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> [image: Enrich_Prop.png]
>>>>>>>>>>
>>>>>>>>>> [2]
>>>>>>>>>> [image: AddressEP_Prop.png]
>>>>>>>>>>
>>>>>>>>>> [3]
>>>>>>>>>> [image: Screenshot-XPath Navigator .png]
>>>>>>>>>>
>>>>>>>>>> [4]
>>>>>>>>>> [image: PerspectiveGE.png]
>>>>>>>>>>
>>>>>>>>>> On Fri, Jun 3, 2011 at 6:03 AM, Sanjiva Weerawarana <
>>>>>>>>>> sanjiva at wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Folks please don't copy private lists in public discussions.
>>>>>>>>>>> Replies by outsiders will bounce and second if the content is suitable for
>>>>>>>>>>> public lists no need to copy the private one and if not it cannot be copied.
>>>>>>>>>>
>>>>>>>>>> Sorry, my mistake.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> (I removed the private list from this email.)
>>>>>>>>>>>
>>>>>>>>>>> Sanjiva.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Jun 3, 2011 at 1:12 AM, Amila Silva <amilas at wso2.com>wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jun 2, 2011 at 4:02 PM, Samisa Abeysinghe <
>>>>>>>>>>>> samisa at wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Looks good!
>>>>>>>>>>>>
>>>>>>>>>>>> Glad to hear.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Does the Proxy and EPs depict the start and end of the
>>>>>>>>>>>>> sequence?
>>>>>>>>>>>>>
>>>>>>>>>>>> Yes.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Also, how many sequences do you have in this example case? One
>>>>>>>>>>>>> in/out, or two of them?
>>>>>>>>>>>>>
>>>>>>>>>>>> Two of them. One in-sequence and one out-sequence (anonymous)
>>>>>>>>>>>> per each proxy service.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Is the layout centered around the concept of proxy services? If
>>>>>>>>>>>>> so, how would we display man sequence?
>>>>>>>>>>>>>
>>>>>>>>>>>> As I mentioned in the previous post, this editor currently
>>>>>>>>>>>> supports only service mediation.
>>>>>>>>>>>> Message mediation is a TO-DO.
>>>>>>>>>>>> For message mediation, my suggestion is to add a "Message
>>>>>>>>>>>> Mediator" component along with proxy services.
>>>>>>>>>>>> There will be only one "Message Mediator" in a particular
>>>>>>>>>>>> configuration and that will be affixed to the left hand side of the server.
>>>>>>>>>>>> The set of components connected to "Message Mediator" can be considered as
>>>>>>>>>>>> the main sequence.
>>>>>>>>>>>>
>>>>>>>>>>>> Like this:
>>>>>>>>>>>> [image: synapse-flow.png]
>>>>>>>>>>>>
>>>>>>>>>>>> Currently, the sequences are anonymous for proxy services.
>>>>>>>>>>>> Set of components connected to input connector of a proxy
>>>>>>>>>>>> service is included in the in-sequence of that particular proxy service.
>>>>>>>>>>>> (similarly, the out-sequence.)
>>>>>>>>>>>> IMO, this approach may improve usability in some cases, as a
>>>>>>>>>>>> user would only have to concentrate on message flow.
>>>>>>>>>>>> It's a design decision to include or not to include reusable
>>>>>>>>>>>> sequences. If we decide to add them, we can represent them as rectangles and
>>>>>>>>>>>> mediators in that sequence can be included inside those.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> What is the drill down policy?
>>>>>>>>>>>>>
>>>>>>>>>>>> As of now, the editor does not provide any visual drilling down
>>>>>>>>>>>> support inside the diagram.
>>>>>>>>>>>> Almost every attribute of a component is displayed in property
>>>>>>>>>>>> view.
>>>>>>>>>>>> However, GMF does provide support to expand/contract components
>>>>>>>>>>>> (for compartments where
>>>>>>>>>>>> one element contains other elements).
>>>>>>>>>>>> We can use that functionality to display some of the information
>>>>>>>>>>>> of components.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> What is the traversal strategy?
>>>>>>>>>>>>>
>>>>>>>>>>>> ~ Iterating through visual components to locate a proxy service,
>>>>>>>>>>>>
>>>>>>>>>>>> ~ Creating a new org.apache.synapse.config.SynapseConfiguration
>>>>>>>>>>>> ~ Transforming the visual model of the proxy service to a
>>>>>>>>>>>> Synapse proxy service and adding it to the synapse config.
>>>>>>>>>>>> ~ Locating the component (a mediator) connected to the input
>>>>>>>>>>>> connector of proxy service, transforming it's visual model to synapse
>>>>>>>>>>>> component
>>>>>>>>>>>> ~ Continuing this process until an endpoint is found.
>>>>>>>>>>>> ~ Repeating above steps for all proxy services in the diagram.
>>>>>>>>>>>> If we include a "Message Mediator" component, that same
>>>>>>>>>>>> traversal strategy can be used there,
>>>>>>>>>>>> difference being, set of components connected to "Message
>>>>>>>>>>>> Mediator" will be considered as main sequence.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> What is the drag policy?
>>>>>>>>>>>>>
>>>>>>>>>>>> I assume that you are referring to how dragging of added
>>>>>>>>>>>> components are handled.
>>>>>>>>>>>> Generated code is customized to limit dragging ability of a
>>>>>>>>>>>> proxy service. They can be only dragged along the left border of the server.
>>>>>>>>>>>> Similarly, endpoints can only be dragged along the right border.
>>>>>>>>>>>> Input connectors and output connectors have fixed locations.
>>>>>>>>>>>> Mediators can be moved around inside the server rectangle.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> What is the drag-n-drop policy?
>>>>>>>>>>>>>
>>>>>>>>>>>> Mediators can be dragged and dropped into the server from the
>>>>>>>>>>>> tool palette.
>>>>>>>>>>>> Proxy services to the left border and endpoints to the right
>>>>>>>>>>>> border.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jun 2, 2011 at 8:44 AM, Amila Silva <amilas at wso2.com>wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Log Mediator Selected:
>>>>>>>>>>>>>> [image: LogM.png]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Property Mediator Selected:
>>>>>>>>>>>>>> [image: PropM.png]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Address Endpoint Selected:
>>>>>>>>>>>>>> [image: AddEP.png]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Jun 2, 2011 at 7:01 AM, Samisa Abeysinghe <
>>>>>>>>>>>>>> samisa at wso2.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Can you please send a screenshot with a mediator selected?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Thu, Jun 2, 2011 at 2:12 AM, Amila Silva <amilas at wso2.com
>>>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Here is an progress update on $subject.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [During early/mid last month]
>>>>>>>>>>>>>>>> ~Added drag and drop support for tool palette. Now the
>>>>>>>>>>>>>>>> components can be dragged and dropped from the palette to the diagram.
>>>>>>>>>>>>>>>> ~Added ability to automatically update which properties to
>>>>>>>>>>>>>>>> display based on which values are given to a particular property. For
>>>>>>>>>>>>>>>> example, when "none" is selected to "wsdl type", other properties to set
>>>>>>>>>>>>>>>> wsdl should be hidden.
>>>>>>>>>>>>>>>> ~Linked LogMediator property configuration dialog box into
>>>>>>>>>>>>>>>> property sheet
>>>>>>>>>>>>>>>> ~UI improvements:
>>>>>>>>>>>>>>>> -- Added new perspective: WSO2 ESB Graphical - This
>>>>>>>>>>>>>>>> consists of the main diagram editor, project explorer
>>>>>>>>>>>>>>>> and property sheet on vertically divided screen.
>>>>>>>>>>>>>>>> -- Added sample icons to the tool palette - An icon next
>>>>>>>>>>>>>>>> to each tool name.
>>>>>>>>>>>>>>>> -- Tool palette will be at the left hand side of the
>>>>>>>>>>>>>>>> diagram by default.
>>>>>>>>>>>>>>>> ~Added support for Property Mediator.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [During last week]
>>>>>>>>>>>>>>>> ~Embedded graphical editor to a multi-page editor. So that
>>>>>>>>>>>>>>>> we can provide design and source views on separate tabs
>>>>>>>>>>>>>>>> ~Now the source gets dynamically updated - If we edit
>>>>>>>>>>>>>>>> something in the diagram and switch to source view,
>>>>>>>>>>>>>>>> those changes will be automatically updated.
>>>>>>>>>>>>>>>> ~XML pretty printing for source view.
>>>>>>>>>>>>>>>> ~UI Improvements:
>>>>>>>>>>>>>>>> -- Gradient background.
>>>>>>>>>>>>>>>> -- Background images.
>>>>>>>>>>>>>>>> ~Added support for Enrich Mediator.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Adding support for a new mediator that has one input and one
>>>>>>>>>>>>>>>> output (Eg: Log, Enrich) includes following steps:
>>>>>>>>>>>>>>>> ~Adding the model class and its attribute to ecore model.
>>>>>>>>>>>>>>>> ~Reloading ecore genmodel
>>>>>>>>>>>>>>>> ~Generating model code
>>>>>>>>>>>>>>>> ~Generating edit code
>>>>>>>>>>>>>>>> ~Updating the graphical definition model using "reconcile
>>>>>>>>>>>>>>>> diagram wizard"
>>>>>>>>>>>>>>>> ~Customizing the updated graphical def model. (eg: Set
>>>>>>>>>>>>>>>> affixed parent side. customize figure)
>>>>>>>>>>>>>>>> ~Updating the tooling definition model
>>>>>>>>>>>>>>>> ~Customizing the updated tooling model (eg: Add newly added
>>>>>>>>>>>>>>>> too to a particular group)
>>>>>>>>>>>>>>>> ~Doing Model/Node/Tool mapping on newly added mediator
>>>>>>>>>>>>>>>> components in mapping model
>>>>>>>>>>>>>>>> ~Updating graphical gen model using the 3 updated models
>>>>>>>>>>>>>>>> ~Generating diagram code.
>>>>>>>>>>>>>>>> ~Performing code customizations on newly added mediator
>>>>>>>>>>>>>>>> classes: there are 3 main "edit part" classes, one provider class and one
>>>>>>>>>>>>>>>> model class need to be modified.
>>>>>>>>>>>>>>>> ~Writing transformer code to serialize.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A common difficulty we face is lack of documentation. In
>>>>>>>>>>>>>>>> many cases we have to go through eclipse news group discussions / blog posts
>>>>>>>>>>>>>>>> and in some cases trial-and-error approach!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What we do when we serialize code is obtaining the visual
>>>>>>>>>>>>>>>> (gmf) model from the diagram and iterate through it to create a synapse
>>>>>>>>>>>>>>>> configuration (org.apache.synapse.config.SynapseConfiguration)
>>>>>>>>>>>>>>>> Currently, only service mediation is serialized. i.e., we
>>>>>>>>>>>>>>>> find a proxy service in the visual model, add it to synapse config, find the
>>>>>>>>>>>>>>>> mediator to which its output is connected, add it, and so on until we meet
>>>>>>>>>>>>>>>> an endpoint, and back to the proxy service.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [Tasks to be done]
>>>>>>>>>>>>>>>> ~Importing a synapse configuration to create a diagram.
>>>>>>>>>>>>>>>> ~Automatically updating design view when source view is
>>>>>>>>>>>>>>>> changed
>>>>>>>>>>>>>>>> These two tasks are the reverse of obtaining source from
>>>>>>>>>>>>>>>> design view. I think this will take some effort.
>>>>>>>>>>>>>>>> ~Adding support for more mediators
>>>>>>>>>>>>>>>> - Some mediators have more than just one in flow and out
>>>>>>>>>>>>>>>> flow (Eg: Filter).
>>>>>>>>>>>>>>>> - Setting XPath: Rather than just entering an string,
>>>>>>>>>>>>>>>> user should be able to pick this from workspace,
>>>>>>>>>>>>>>>> registry or XML file. This functionality is available in
>>>>>>>>>>>>>>>> current ESB editor. Should be able to reuse some of that.
>>>>>>>>>>>>>>>> - Regarding Enqueue mediator: Even though this is
>>>>>>>>>>>>>>>> available in current (EMF) ESB editor, I couldn't find a way to
>>>>>>>>>>>>>>>> add a priority executor. Will have to think how to
>>>>>>>>>>>>>>>> represent this graphically.
>>>>>>>>>>>>>>>> ~Adding message mediation support
>>>>>>>>>>>>>>>> Should decide how to represent this graphically.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Here is an screen-shot of what we have as of now:
>>>>>>>>>>>>>>>> [image: ESBGraphicalEditor0.0.1.png]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, May 16, 2011 at 2:03 PM, Samisa Abeysinghe <
>>>>>>>>>>>>>>>> samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I would like to be there for this review. Please can we
>>>>>>>>>>>>>>>>> wait till I am back?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sat, May 14, 2011 at 12:49 PM, Senaka Fernando <
>>>>>>>>>>>>>>>>> senaka at wso2.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Milinda,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, May 13, 2011 at 10:16 PM, Milinda Pathirage <
>>>>>>>>>>>>>>>>>> milinda at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I had a look at that tool. Tool is still in very early
>>>>>>>>>>>>>>>>>>> stages and I communicate the errors to tooling team. I think we need to have
>>>>>>>>>>>>>>>>>>> a meeting to discuss the design of the tooling and milestone plan. I'll
>>>>>>>>>>>>>>>>>>> schedule meeting with tooling team and ESB team to discuss this in detail to
>>>>>>>>>>>>>>>>>>> come up with a plan.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> +1. I'd like to join too. I can add a few of my
>>>>>>>>>>>>>>>>>> experiences with regard to what we did at Suva, and some recent work I've
>>>>>>>>>>>>>>>>>> done with Buddhika on THR requirements.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Senaka.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>> Milinda
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Fri, May 13, 2011 at 6:52 PM, Samisa Abeysinghe <
>>>>>>>>>>>>>>>>>>> samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, May 11, 2011 at 10:46 PM, Amila Silva <
>>>>>>>>>>>>>>>>>>>> amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Tue, May 10, 2011 at 8:52 PM, Samisa Abeysinghe <
>>>>>>>>>>>>>>>>>>>>> samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> So between this new design and the old...
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I assume, by old design, you mean the existing ESB
>>>>>>>>>>>>>>>>>>>>> editor in CS.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> What is the plan to migrate/re-use the existing code?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Since both designs use the EMF model of the ESB, we can
>>>>>>>>>>>>>>>>>>>>> re-use most of the components from the existing ecore model.
>>>>>>>>>>>>>>>>>>>>> However we can't really migrate the code because code
>>>>>>>>>>>>>>>>>>>>> of the graphical representation obtained from GMF is different than that of
>>>>>>>>>>>>>>>>>>>>> EMF.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Sounds greek. Can you elaborate more please?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> When do we plan to switch from old to new design?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Since the new design is still in an early stage we
>>>>>>>>>>>>>>>>>>>>> cannot exactly say when it'll be ready to switch to.
>>>>>>>>>>>>>>>>>>>>> Need some feedback on the new design and have to make
>>>>>>>>>>>>>>>>>>>>> some decisions.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I did not have time to look into the build sent
>>>>>>>>>>>>>>>>>>>> yet...but I am not the only one around to give feedback ;)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I am trying to figure out how we go about making
>>>>>>>>>>>>>>>>>>>>>> usability improvements in ESB space.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, May 10, 2011 at 6:44 PM, Amila Silva <
>>>>>>>>>>>>>>>>>>>>>> amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Uploaded the packs to [1]
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Either use the eclipse distro with the feature
>>>>>>>>>>>>>>>>>>>>>>> installed. Or install the feature to a new eclipse.
>>>>>>>>>>>>>>>>>>>>>>> Currently, the editor supports service mediation with
>>>>>>>>>>>>>>>>>>>>>>> few mediators. Also added drag and drop support for tools.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Installing the feature (will take about 15min)
>>>>>>>>>>>>>>>>>>>>>>> ==================== ============
>>>>>>>>>>>>>>>>>>>>>>> 1. Goto Help->Install New Software.
>>>>>>>>>>>>>>>>>>>>>>> 2. Point to the location of the zip file.
>>>>>>>>>>>>>>>>>>>>>>> 3. Untick "group items by category" and select
>>>>>>>>>>>>>>>>>>>>>>> EsbGraphicalEditor to install.
>>>>>>>>>>>>>>>>>>>>>>> 4. Tick "Contact all update sites during install"
>>>>>>>>>>>>>>>>>>>>>>> 5. Click Next and install as usual (while installing
>>>>>>>>>>>>>>>>>>>>>>> it'll download EMF, GMF and other required runtime libs)
>>>>>>>>>>>>>>>>>>>>>>> 6.Restart eclipse
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Trying out
>>>>>>>>>>>>>>>>>>>>>>> ========
>>>>>>>>>>>>>>>>>>>>>>> 1. Create a new project (for now any type of project,
>>>>>>>>>>>>>>>>>>>>>>> eg: java): Goto File->New->Project.
>>>>>>>>>>>>>>>>>>>>>>> 2. Create a new ESB Diagram: Goto File->New->Other .
>>>>>>>>>>>>>>>>>>>>>>> Select ESB diagram from the category Examples
>>>>>>>>>>>>>>>>>>>>>>> 3. Create a new Server:
>>>>>>>>>>>>>>>>>>>>>>> a. Select the tool "EsbServer" and draw. or
>>>>>>>>>>>>>>>>>>>>>>> b. Drag and drop the tool "EsbServer"
>>>>>>>>>>>>>>>>>>>>>>> 4. Proxy services can be added of left side and
>>>>>>>>>>>>>>>>>>>>>>> endpoints can be added to right side of the server figure.
>>>>>>>>>>>>>>>>>>>>>>> Eg: To add a proxy service, select the relevant
>>>>>>>>>>>>>>>>>>>>>>> tool and click on the left border (just inside the server).
>>>>>>>>>>>>>>>>>>>>>>> 5. Proxy services, mediators and enpoints should be
>>>>>>>>>>>>>>>>>>>>>>> connected using the tool "Esb Link"
>>>>>>>>>>>>>>>>>>>>>>> Eg: To connect a proxy service to a log mediator,
>>>>>>>>>>>>>>>>>>>>>>> select the Esb Link tool, point the mouse on output connector of the proxy
>>>>>>>>>>>>>>>>>>>>>>> service (the arrowhead pointing outwards) and drag to the input connector of
>>>>>>>>>>>>>>>>>>>>>>> the log mediator)
>>>>>>>>>>>>>>>>>>>>>>> 7. Right click on the diagram and select Export to
>>>>>>>>>>>>>>>>>>>>>>> create the Synapse configuration XML.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> [1] -
>>>>>>>>>>>>>>>>>>>>>>> http://builder.wso2.org/~carbon/carbon-studio/poc/EsbGraphicalEditor/
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, May 10, 2011 at 12:03 AM, Amila Silva <
>>>>>>>>>>>>>>>>>>>>>>> amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 11:48 PM, Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>> <samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 11:17 PM, Amila Silva <
>>>>>>>>>>>>>>>>>>>>>>>>> amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 10:21 PM, Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>>>> <samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> I want to run it myself, not a demo
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> We can export and provide you the bundles of those
>>>>>>>>>>>>>>>>>>>>>>>>>> projects tomorrow. (As it's not included in the builds right now.)
>>>>>>>>>>>>>>>>>>>>>>>>>> If you want to try it now, I can provide the
>>>>>>>>>>>>>>>>>>>>>>>>>> instructions on importing the necessary projects and running them.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I cannot build on windows. Can you provide a
>>>>>>>>>>>>>>>>>>>>>>>>> snapshot pack?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Sure. We'll provide tomorrow.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 10:18 PM, Saminda
>>>>>>>>>>>>>>>>>>>>>>>>>>> Wijeratne <samindaw at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Amila/Melan,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Lets have a small demo on what we currently
>>>>>>>>>>>>>>>>>>>>>>>>>>>> have. Create a rough milestone plan for the tasks ahead.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Saminda
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 10:15 PM, Samisa
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Abeysinghe <samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> How can I try what we have as of now?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 10:14 PM, Amila Silva <
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yes, we started working on this.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Contacted the previous developer (Asiri) and
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> got some clarification on the existing ecore model. We decided to extend
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that model. Now we are adding mediator sequence support. And doing some UI
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> improvements (with gmf graphical definition model).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> In the following days, we hope to add support
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> for more mediators to the graph and work on the persistence part
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simultaneously.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, May 9, 2011 at 9:49 PM, Samisa
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Abeysinghe <samisa at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Are you guys working on this?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, Apr 27, 2011 at 3:29 PM, Amila Silva
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <amilas at wso2.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Me and Melan are going to resume developing
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> $subject after we complete bug-fixing on CS branch.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This editor, once finished, will enable
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> users to create ESB configurations with a UI similar to an architectural
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> diagram of mediation engine.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [image: synapse-flow.png]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ESB domain model (ecore) will be used as the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> starting point. and the editor uses Graphical Modeling Framework (GMF) for
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> code generation.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This editor has been started some time ago.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Currently it is a basic diagram editor with graphical representation of
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Server, Proxy Services, Endpoints and two types of mediators. We hope to
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> extend on this existing code.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Past few weeks we've been studying GMF and
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> working on getting a working prototype
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The basic steps will include the following,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. Expanding ecore, graphical definition,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> tooling definition models to support other artifacts: mediation sequences,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> other types of mediators, local entries, etc.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. Working on code customization to support
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> functionalities of various mediators.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3. Transformation and Persistence - Writing
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the model exporter to export the configuration on diagrams as Carbon Apps or
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> separate artifacts.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 4. Enhancing the GUI.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The GUI of existing projects with our few
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> modifications currently looks like this:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [image: esb_diagram_draft.png]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> We'll keep updated on progress and any
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problems that may arise. Suggestions are much appreciated.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Milinda Pathirage
>>>>>>>>>>>>>>>>>>> Technical Lead and Product Manager, Business Process
>>>>>>>>>>>>>>>>>>> Server - WSO2 Inc; http://wso2.com
>>>>>>>>>>>>>>>>>>> Blog: http://blog.mpathirage.com
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Lean Enterprise Middleware
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> *Senaka Fernando*
>>>>>>>>>>>>>>>>>> Product Manager - WSO2 Governance Registry;
>>>>>>>>>>>>>>>>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com*
>>>>>>>>>>>>>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> E-mail: senaka AT wso2.com
>>>>>>>>>>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>>>>>>>>>>>>>> Linked-In: http://www.linkedin.com/in/senakafernando
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> *Lean . Enterprise . Middleware
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Samisa...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>>>>> VP Engineering
>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>> http://wso2.com
>>>>>>>>>>>>> http://wso2.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>> Amila Manoj
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sanjiva Weerawarana, Ph.D.
>>>>>>>>>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>>>>>>>>>>> email: sanjiva at wso2.com; phone: +94 11 763 9614; cell: +94 77
>>>>>>>>>>> 787 6880 | +1 650 265 8311
>>>>>>>>>>> blog: http://sanjiva.weerawarana.org/
>>>>>>>>>>>
>>>>>>>>>>> Lean . Enterprise . Middleware
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Cheers,
>>>>>>>>>> Amila Manoj
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Carbon-dev mailing list
>>>>>>>>> Carbon-dev at wso2.org
>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Carbon-dev mailing list
>>>>>>>> Carbon-dev at wso2.org
>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Carbon-dev mailing list
>>>>>>> Carbon-dev at wso2.org
>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Paul Fremantle
>>>>>> CTO and Co-Founder, WSO2
>>>>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>>>>
>>>>>> Office: +44 844 484 8143
>>>>>> Cell: +44 798 447 4618
>>>>>>
>>>>>> blog: http://pzf.fremantle.org
>>>>>> twitter.com/pzfreo
>>>>>> paul at wso2.com
>>>>>>
>>>>>> wso2.com Lean Enterprise Middleware
>>>>>>
>>>>>> Disclaimer: This communication may contain privileged or other
>>>>>> confidential information and is intended exclusively for the addressee/s. If
>>>>>> you are not the intended recipient/s, or believe that you may have received
>>>>>> this communication in error, please reply to the sender indicating that fact
>>>>>> and delete the copy you received and in addition, you should not print,
>>>>>> copy, retransmit, disseminate, or otherwise use the information contained in
>>>>>> this communication. Internet communications cannot be guaranteed to be
>>>>>> timely, secure, error or virus-free. The sender does not accept liability
>>>>>> for any errors or omissions.
>>>>>>
>>>>>> _______________________________________________
>>>>>> Carbon-dev mailing list
>>>>>> Carbon-dev at wso2.org
>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks & Regards,
>>>>> Amila Manoj
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Carbon-dev mailing list
>>>>> Carbon-dev at wso2.org
>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>> Thanks,
>>>> Samisa...
>>>>
>>>> Samisa Abeysinghe
>>>> VP Engineering
>>>> WSO2 Inc.
>>>> http://wso2.com
>>>> http://wso2.org
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Carbon-dev mailing list
>>>> Carbon-dev at wso2.org
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>> --
>>> Regards,
>>> Amila Manoj
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> Carbon-dev at wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> paul at wso2.com
>>
>>
>> http://freo.me/wso2con11
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s. If
>> you are not the intended recipient/s, or believe that you may have received
>> this communication in error, please reply to the sender indicating that fact
>> and delete the copy you received and in addition, you should not print,
>> copy, retransmit, disseminate, or otherwise use the information contained in
>> this communication. Internet communications cannot be guaranteed to be
>> timely, secure, error or virus-free. The sender does not accept liability
>> for any errors or omissions.
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev at wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> --
> Thanks,
> Amila
>
>
--
Thanks & Regards,
Amila Manoj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/carbon-dev/attachments/20110621/23d608ba/attachment-0001.html>
More information about the Carbon-dev
mailing list