from:"Amila Silva"

Re: [Carbon-dev] wso2throttle and Neethi 3.0.x incompatibility

2011-08-22 Thread Amila Silva

Hi Thilina and Isuru,

On Mon, Aug 22, 2011 at 2:44 PM, Thilina Buddhika  wrote:

>
>
> On Mon, Aug 22, 2011 at 2:39 PM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Mon, Aug 22, 2011 at 10:17 AM, Thilina Buddhika wrote:
>>
>>> Hi Amila,
>>>
>>> 1_6 branches of Axis2, Rampart is still dependent on Neethi 2.0.x. There
>>> are some huge API changes for Neethi 3.0.x which are not backward
>>> compatible. So currently only Axis2 and Rampart trunks are depending on
>>> Neethi 3.0.x. This is a collective decision took sometime back both in WSO2
>>> and Axis2 community.
>>>
>> Thanks for the explanation.

>
>> Yes, but to fix the issue in trunk which is described by Amila, we have to
>> fix the throttle trunk. If both Axis2 and Synapse trunks depend on Neethi
>> 3.0.x, we have to make the Throttle trunk compatible with Neethi 3.0.x.
>>
>
> +1. It is not hard to migrate to Neethi 3.0.x. The only catch is we need to
> test it thoroughly. But making this migration in trunk now will give us
> enough time to test it.
>
+1. I'd like to contribute to this effort.

>
> Thanks,
> Thilina
>
>
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Thanks,
>>> Thilina
>>>
>>> On Mon, Aug 22, 2011 at 2:44 AM, Amila Silva  wrote:
>>>
>>>> Hi devs,
>>>>
>>>> I ran into this issue while working on synapse sample automation
>>>> framework.
>>>>
>>>> There has been (apparently) a typo in the class name
>>>> org.apache.neethi.builders.xml.XmlPrimtiveAssertion in Neethi 2.0.x
>>>> releases.
>>>> This has been fixed in Neethi 3.0.x to
>>>> org.apache.neethi.builders.xml.Xml*Primitive*Assertion.
>>>>
>>>> However org.wso2.throttle.ThrottleFactory (in trunk [1]) still uses
>>>> XmlPrimtiveAssertion.
>>>>
>>>> Synpase uses wso2throttle snapshot version for throttle mediator. Due to
>>>> above issue, Neethi 3.0.x cannot be used.
>>>>
>>>> According to [2], Axis2 version (1.7.0-SNAPSHOT) used by Synapse
>>>> requires Neethi 3.0.x.
>>>>
>>>> Therefore synapse's WS-Security and WS-RM samples (Sample100, Sample101
>>>> [3]) don't work when Neethi 2.0.x is used.
>>>> (java.lang.NoSuchMethodError:
>>>> org.apache.neethi.Policy.normalize(Z)Lorg/apache/neethi/Policy;)
>>>>
>>>> Changing Neethi version to 3.0.x breaks the throttling samples
>>>> (Sample370, Sample 371...)
>>>> (java.lang.NoClassDefFoundError:
>>>> org/apache/neethi/builders/xml/XmlPrimtiveAssertion)
>>>>
>>>> This should be solved from wso2throttle side, right?
>>>>
>>>> [1] - http://wso2.org/repos/wso2/trunk/commons/throttle
>>>> [2] - https://issues.apache.org/jira/browse/SYNAPSE-788
>>>> [3] - http://synapse.apache.org/Synapse_Samples.html#Sample100
>>>>
>>>> --
>>>> Regards,
>>>> Amila Manoj
>>>>
>>>>
>>>> ___
>>>> Carbon-dev mailing list
>>>> Carbon-dev@wso2.org
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Thilina Buddhika
>>> Associate Technical Lead
>>> WSO2 Inc. ; http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> phone : +94 77 44 88 727
>>> blog : http://blog.thilinamb.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead & Product Manager, WSO2 Application Server
>>
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thilina Buddhika
> Associate Technical Lead
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 77 44 88 727
> blog : http://blog.thilinamb.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
-- 
Regards,
Amila Manoj
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] wso2throttle and Neethi 3.0.x incompatibility

2011-08-21 Thread Amila Silva

Hi devs,

I ran into this issue while working on synapse sample automation framework.

There has been (apparently) a typo in the class name
org.apache.neethi.builders.xml.XmlPrimtiveAssertion in Neethi 2.0.x
releases.
This has been fixed in Neethi 3.0.x to org.apache.neethi.builders.xml.Xml*
Primitive*Assertion.

However org.wso2.throttle.ThrottleFactory (in trunk [1]) still uses
XmlPrimtiveAssertion.

Synpase uses wso2throttle snapshot version for throttle mediator. Due to
above issue, Neethi 3.0.x cannot be used.

According to [2], Axis2 version (1.7.0-SNAPSHOT) used by Synapse requires
Neethi 3.0.x.

Therefore synapse's WS-Security and WS-RM samples (Sample100, Sample101 [3])
don't work when Neethi 2.0.x is used.
(java.lang.NoSuchMethodError:
org.apache.neethi.Policy.normalize(Z)Lorg/apache/neethi/Policy;)

Changing Neethi version to 3.0.x breaks the throttling samples (Sample370,
Sample 371...)
(java.lang.NoClassDefFoundError:
org/apache/neethi/builders/xml/XmlPrimtiveAssertion)

This should be solved from wso2throttle side, right?

[1] - http://wso2.org/repos/wso2/trunk/commons/throttle
[2] - https://issues.apache.org/jira/browse/SYNAPSE-788
[3] - http://synapse.apache.org/Synapse_Samples.html#Sample100

-- 
Regards,
Amila Manoj
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Updating the current ESB Editor in CS

2011-07-27 Thread Amila Silva

Hi Paul,

On Mon, Jul 25, 2011 at 12:14 PM, Paul Fremantle  wrote:

> How soon will the new editor be ready?

It'll take some time to fully complete the graphical editor with support for
all the mediators, probably 2-3 months. Hope to get it fully working for a
selected scenario (with re-usable items) by the end of August.
This is the reason why we decided to update the current ESB editor for the
changes in new ESB release.

>
> Paul
>
>
> On 6 June 2011 12:11, Samisa Abeysinghe  wrote:
>
>> So does this mean that we will continue to bug fix the existing ESB
>> editor?
>>
>> On Mon, Jun 6, 2011 at 4:08 PM, Kasun Indrasiri  wrote:
>>
>>>
>>>
>>> On Mon, Jun 6, 2011 at 3:37 PM, Malith Dhanushka 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 - element

 Also please include
>>> - enrich mediator modifications. (Enriching from a registry resource)
>>> - endpoint properties
>>> - Descriptions for mediators, sequences and endpoints in synapse config.
>>>
>>> Thanks.
>>>
 Mediator modification is already finished & developing new
 mediators,features is now in progress.

 Thanks,
 Malith

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Associate Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@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@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
> p...@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@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
-- 
Thanks,
Amila
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] WSO2 Committers += Amila Silva + Malith Dhanushak

2011-07-07 Thread Amila Silva

Hi,

Thank you all for the faith you have put in me and making me a committer.
Hope to contribute more in the days to come.

On Thu, Jul 7, 2011 at 1:19 PM, Saminda Wijeratne  wrote:

>
>
> On Thu, Jul 7, 2011 at 1:09 PM, Saminda Wijeratne wrote:
>
>> It's my great pleasure to welcome AmilaS & Malith as our
>> newest WSO2 commiters.
>>
>> They have being working close to 4 months in the tooling team and during
>> that time had performed well on the tasks assigned to them.
>>
>> Malith has worked on multiple areas. He had worked hard to improve his
>> output in all those areas. Following are the areas which he worked on,
>>
>>- Providing patches covering most of CS [1]
>>- Working on the data mapping tool
>>   - has being working on the Smooks editor looking at code,
>>   functionality & limitations.
>>   - has gone the extra mile to have a better understanding on the
>>   framework & tool by opening chanels with Tom Fennely from JBoss to get 
>> their
>>   help
>>   - has done a performance bench mark on smooks vs xslt mediators
>>   - currently preparing a screencast on this.
>>- He has & is working on updating the current ESB editor to get it up
>>to date with the new features & modifications corresponding to ESB 4.0.0
>>
>> AmilaS has also worked on many areas. He relatively communicates well in
>> mailing lists. Being a relatively fast learner & good communicator he has
>> shown great commitment as a individual & a team member.
>>
>>- Providing patches covering most of CS [2]
>>- Leading the work on the new ESB Graphical editor (refer the progress
>>mails sent by him in this regard) with Melan
>>   - Has done so far the most amount of work in the editor
>>- Actively participating on discussions & putting forward ideas (but
>>not on mailing lists, that needs to be improved)
>>
>> Congratulations & welcome aboard AmilaS & Melan
>>
> Small typo.
> It should be AmilaS & Malith :)
>
> Saminda
>
>>
>> Thank you,
>> Saminda
>>
>> 1.
>> https://wso2.org/jira/browse/TOOLS-444
>> https://wso2.org/jira/browse/TOOLS-458
>> https://wso2.org/jira/browse/TOOLS-462
>> https://wso2.org/jira/browse/TOOLS-476
>> https://wso2.org/jira/browse/TOOLS-514
>> https://wso2.org/jira/browse/TOOLS-454
>> https://wso2.org/jira/browse/TOOLS-688
>> https://wso2.org/jira/browse/TOOLS-666
>> https://wso2.org/jira/browse/TOOLS-668
>> https://wso2.org/jira/browse/TOOLS-675
>> https://wso2.org/jira/browse/TOOLS-676
>> https://wso2.org/jira/browse/TOOLS-677
>> https://wso2.org/jira/browse/TOOLS-678
>> https://wso2.org/jira/browse/TOOLS-679
>> https://wso2.org/jira/browse/TOOLS-680
>> https://wso2.org/jira/browse/TOOLS-681
>> https://wso2.org/jira/browse/TOOLS-687
>>
>> 2.
>> https://wso2.org/jira/browse/TOOLS-439
>> https://wso2.org/jira/browse/TOOLS-441
>> https://wso2.org/jira/browse/TOOLS-445
>> https://wso2.org/jira/browse/TOOLS-457
>> https://wso2.org/jira/browse/TOOLS-470
>> https://wso2.org/jira/browse/TOOLS-483
>> https://wso2.org/jira/browse/TOOLS-487
>> https://wso2.org/jira/browse/TOOLS-497
>> https://wso2.org/jira/browse/TOOLS-636
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

Cheers & Regards,
Amila
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

2011-05-13 Thread Amila Silva

On Fri, May 13, 2011 at 10:16 PM, Milinda Pathirage 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.

Thanks for taking a look and +1 for the meeting.

>
> Thanks
> Milinda
>
> On Fri, May 13, 2011 at 6:52 PM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Wed, May 11, 2011 at 10:46 PM, Amila Silva  wrote:
>>
>>>
>>>
>>> On Tue, May 10, 2011 at 8:52 PM, Samisa Abeysinghe 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  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  wr

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

2011-05-13 Thread Amila Silva

On Fri, May 13, 2011 at 6:52 PM, Samisa Abeysinghe  wrote:

>
>
> On Wed, May 11, 2011 at 10:46 PM, Amila Silva  wrote:
>
>>
>>
>> On Tue, May 10, 2011 at 8:52 PM, Samisa Abeysinghe 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?
>

Sure. I think it'll be clear if I briefly explain the technologies involved.
(according to my understanding :) )

EMF(Eclipse Modelling Framework) is used to model a particular domain (such
as ESB). It is somewhat similar to UML. But unlike UML, EMF has a single
representation of the domain model which is called the ecore model. This
model can be used to generate code to edit the components and their
relationships modelled in the ecore model. This is what is used in the
current design of ESB editor.
There's a separate framework called GEF(Graphical Editing Framework) in
Eclipse which enables drawing of graphical components (eg: geometrical
shapes)

GMF(Graphical Modelling Framework) combines above two frameworks. So we can
use the relationships/logic from the ecore model and generate code for a
graphical editor. (lots of customizations are needed, of course)
GMF basically uses 4 models to generate code: ecore model, graphical
definition model, tooling definition model and mapping model
In graphical definition model, we specify what are the graphical components
and how they should be represented in our editor. Tooling model specifies
creation tools (of the palette), context menus, etc. Mapping model creates
the relationships between real domain model (ecore), graphical components
and tools.

Therefore, many of the components (specially, mediators and various enums)
from the ecore model of existing design can be re-used in the new design.
I found customized code in few places which we can re-use (such as logic for
property sheets).
Other than that, old code cannot be migrated as the code obtained from two
methods (EMF and GMF) differ.

>
>
>>
>>
>>> 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  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 (ju

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

2011-05-11 Thread Amila Silva

On Tue, May 10, 2011 at 8:52 PM, Samisa Abeysinghe  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.


> 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 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  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  wrote:
>>
>>>
>>>
>>> On Mon, May 9, 2011 at 11:48 PM, Samisa Abeysinghe wrote:
>>>
>>>>
>>>>
>>>> On Mon, May 9, 2011 at 11:17 PM, Amila Silva  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, May 9, 2011 at 10:21 PM, Samisa Abeysinghe 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 >>>>> > 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 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> How can I try what we have as of now?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon,

Re: [Carbon-dev] Carbon Studio 1.0.5 Released

2011-04-12 Thread Amila Silva

On Tue, Apr 12, 2011 at 8:50 AM, Saminda Wijeratne wrote:

>  WSO2 Carbon Studio 1.0.5 Release Notes 6th April 2011
>
> We introduce WSO2 Carbon Studio, is a fully functioned tooling environment
> which facilitate you to develop, test, deploy and test WSO2 Carbon
> Artifacts. The tool is created as a plug-in for the popular IDE Eclipse.
>
> These tools are available under the Apache Software License (v2.0) 
> .
> This includes all of the extra integration and management functionality as
> well.
>  New Features
>
>- Carbon Application Tools
>   - Ability to create Registry Aspect class
>   - Allow creating the library artifact as a fragment bundle
>   - Create sequences and endpoints as registry resources
>   - Creating registry resources through templates
>- General
>   - Adding WSO2 related libraries when developing applications
>   - Other usability improvements
>- ESB tools
>   - Ability to specify references of ESB artifacts from a filtered
>   list of resources in the workspace
>   - Ability to create registry resource references on the fly for ESB
>   artifacts
>   - JBoss Smooks tools integration
>- Governance Registry Tools
>   - Enable/disable actions and update icons based on permissions for
>   registry resources for the specified user
>
> Write permission can be set for individual registry resources. Actions that
a logged user can perform (eg. Add new resource, Modify permissions) depend
on these permissions. Now, WSO2 Registry Browser will not allow users that
don't have permission to perform those actions by disabling them in context
menu and toolbar. JIRA issue: [1]

Registry Browser will now indicate which registry resources are read-only to
the logged user by displaying a padlock icon with the particular resource
icon. Screenshot: [2]

[1] - https://wso2.org/jira/browse/TOOLS-524
[2] - https://wso2.org/jira/secure/attachment/15668/padlock1_preview.png

>
> - Upload wsdl resources to the registry as governance archives (GAR
>   support)
>- Introduced Carbon Studio contribution features [Documentation
>pending]
>   - Extensions to add custom proxy service templates
>   - Extensions to add registry resource templates
>   - Extensions to allow adding mediatype resolvers
>   - Extensions to specify new 3rd party libraries
>   - Extensions to specify resource providers for
>  - Registry Resources
>  - ESB Sequences
>  - ESB Endpoints
>  - ESB Local Entries
>
> Key Features
>
>- Application Server Tools
>   - Create and Edit Apache Axis2 Web Service
>   - Create WSDL for Apache Axis2 Web Service archive (aar file)
>   - Generate Web Service client
>   - Web Applications
>   - JAX-WS services
>- Enterprise Service Bus Tools
>   - Sequences
>   - Endpoints
>   - Proxy Services
>   - Local Entries
>   - Create custom mediators
>   - Registry Referencing
>- Governance Registry Tools
>   - Create and deploy registry resources
>   - Create, edit, debug and deploy registry handlers, filters and
>   registry aspects
>   - Manage your remote registry instance
>- Business Process Server Tools
>   - View, create and edit BPEL projects
>- Gadget Server Tools
>   - Create and edit gadgets
>- Data Services Server Tools
>   - Create and edit data services (XML configurations)
>   - Create and edit data services validators
>- Carbon Tools
>   - Create, edit, debug and deploy Carbon UI bundles
>   - Deploy third party libraries as bundles
>- Testing, Deploying and Redeploying
>
> You can find a more detailed version of all the features available in
> Carbon Studio from WSO2 Carbon Studio 
> Features
>  page. Project Resources
>
>1. *Home page :* WSO2 Carbon Studio
>2. *JIRA-Issue Tracker :* WSO2 Carbon Studio - JIRA 
> Issues
>
> Reporting ProblemsIssues can be reported using the public JIRA available
> at https://wso2.org/jira/browse/TOOLS Contact usWSO2 Tools developers can
> be contacted via the mailing lists:
>
> *For Users:* tools-u...@wso2.org
>
> *For Developers:* carbon-dev@wso2.org
>
> For details on subscriptions see http://wso2.org/projects/tools#mail
>
> Alternatively, questions can also be raised in the WSO2 Tools forum:
>
> *Forum* http://www.wso2.org/forum/194 
>
> SupportWe are committed to ensuring that your enterprise middleware
> deployment is completely supported from evaluation to production. Our unique
> approach ensures that all support leverages our open development methodology
> and is provided by the very same engineers who build the technology.
>
> For more details and to take advantage of this unique opportunity

Re: [Carbon-dev] stratos/org.wso2.carbon.ui.menu commented out

2011-03-14 Thread Amila Silva

Hi,

It was commented out because there was a compilation error. Please take a
look here,
http://wso2.markmail.org/search/list:org.wso2.stratos-dev#query:list%3Aorg.wso2.stratos-dev+page:1+mid:ud2je6fvx7tsdvc6+state:results
It's working now :)

On Mon, Mar 14, 2011 at 10:05 PM, Isuru Suriarachchi  wrote:

> Anyone who knows about this??
>
> On Mon, Mar 14, 2011 at 5:58 PM, Isuru Suriarachchi wrote:
>
>> In the components/stratos/pom.xml, org.wso2.carbon.ui.menu module is
>> commented out. But the Stratos AppServer needs it. When I uncomment and
>> build it, there's a compilation failure. Is this no longer used? In that
>> case, how can I get the AppServer build fixed?
>>
>> Thanks,
>> ~Isuru
>>
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead & Product Manager, WSO2 Application Server
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks & Regards,
Amila Manoj
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] wso2throttle and Neethi 3.0.x incompatibility

[Carbon-dev] wso2throttle and Neethi 3.0.x incompatibility

Re: [Carbon-dev] Updating the current ESB Editor in CS

Re: [Carbon-dev] WSO2 Committers += Amila Silva + Malith Dhanushak

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

Re: [Carbon-dev] [Carbon Studio] Graphical editor for ESB Configuration

Re: [Carbon-dev] Carbon Studio 1.0.5 Released

Re: [Carbon-dev] stratos/org.wso2.carbon.ui.menu commented out

9 matches

Site Navigation

Mail list logo

Footer information