On 8/17/10 9:28 AM, Hiranya Jayathilaka wrote:
Ruwan,
On Tue, Aug 17, 2010 at 8:30 AM, Ruwan Linton <ru...@wso2.com
<mailto:ru...@wso2.com>> wrote:
On 8/17/10 7:45 AM, Samisa Abeysinghe wrote:
On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe
<sam...@wso2.com <mailto:sam...@wso2.com>> wrote:
On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva
<su...@wso2.com <mailto:su...@wso2.com>> wrote:
There are two ways to implement this.
1. We can simply read the configuration from the file
system and them
override the current synapse configuration with the sample
configuration. This leads to the destruction of current
configuration.
2. The second approach is to build the synapse
configuration from the
beginning. This includes initializing the persistence
again to fit the
sample etc. This preserves the current ESB configuration.
In case of the test automation framework, what we are doing
is to use admin services and update the synapse config with
the admin service calls.
The rationale is that, we have the provision for users to
edit the synapse config with management console and update
that via admin service and get ESB to work on the new updated
config.
We already have the test automation team doing this.
I think we can re-use that code and build this sample
component based on that.
This is the reason I was repeatedly asking if we are using
test automation model, and it looks to me that not many are
familiar with the test automation framework's model.
And I think, we should try and reuse that model from test
framework for this component.
Also, the automation model fits option #2. So that we preserve
what we have already.
Tobe frank I was not aware of the design of the test automation
framework, but if you use the admin service to update the synapse
configuration then you are not preserving the configuration that
you had, the admin service will persist the configuration to the
disk as well as to the registry.
What I want to see is a model where we have multiple synapse
configurations loaded, and those can be editable separately, but
only one configuration is active at any given point in time.
I don't think we have implemented that, to do so we need some
changes to synapse configuration management core code, where I
didn't see any code going into synapse of that sort.
Another issue we might have to face is with the proxy service
persistence. When a proxy service is built, Carbon's service
persistence manager comes into play. But ideally we should not let any
of the sample services get persisted to the registry. It will be
tricky to handle this properly.
Yes, we might need to introduce a new parameter to the service
persistence to ignore these sample services.
Ruwan
Thanks,
Hiranya
I am not clear as to what the model of the test automation
framework is (sorry about that), to me it is just using the
existing admin services, what we are talking about here ideally is
a new admin service.
Thanks,
Ruwan
I prefer the second approach.
Thanks,
Supun..
On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe
<sam...@wso2.com <mailto:sam...@wso2.com>> wrote:
> It would be a good idea to try and make these samples
more real world. The
> current ESB samples are all related to stock quote. But
it might be a good
> idea to see what Shelan did and re-use some of those.
>
> On Mon, Aug 16, 2010 at 9:01 AM, Ruwan Linton
<ru...@wso2.com <mailto:ru...@wso2.com>> wrote:
>>
>> To add a bit of context this is going to be useful
for a person who
>> wants to try out the ESB samples on stratos.
>>
>> We will have a set of sample configurations listed as
the security
>> templates in the security wizard and users can load
those sample
>> configurations to test those.
>>
>> To make it work seamlessly we might need to add some
sample services to
>> the cloud application server as well. Hope that is OK. :-)
>>
>> Ruwan
>>
>> On 8/16/10 8:07 AM, Supun Kamburugamuva wrote:
>> > Hi All,
>> >
>> > I've started working on a new Carbon Component for
ESB to load the
>> > samples from the UI.
>> >
>> > For example user can start the ESB normally and then
load a sample
>> > configuration by choosing the samples number.
>> >
>> > Thanks,
>> > Supun...
>> >
>> > _______________________________________________
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>> >
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>>
>>
>> --
>> Ruwan Linton
>> Software Architect& Product Manager, WSO2 ESB;
http://wso2.org/esb
>> WSO2 Inc.; http://wso2.com
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com <mailto:ru...@wso2.com>; cell:
+94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> tweet: http://twitter.com/ruwanlinton
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
>> https://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 <mailto:Carbon-dev@wso2.org>
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Ruwan Linton
Software Architect& Product Manager, WSO2 ESB;http://wso2.org/esb
WSO2 Inc.;http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email:ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 3097
blog:http://blog.ruwan.org
linkedin:http://www.linkedin.com/in/ruwanlinton
tweet:http://twitter.com/ruwanlinton
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com <mailto:hira...@wso2.com>; Mobile: +94 77
633 3491
Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Ruwan Linton
Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
