Re: [Carbon-dev] Carbon trunk still use 3.0.0 snapshot

[Ruwan Linton]

 On 8/17/10 11:53 AM, Samisa Abeysinghe wrote:

Do we have a script to do this?
There was a single line find and replace command, which also require 
manual checking after execution, just to make sure that other deps of 
the same version didn't get changed. :-)


Ruwan


On Tue, Jul 27, 2010 at 12:53 PM, Ruwan Linton > wrote:


Samisa Abeysinghe wrote:
> It is time that we updated to 3.1.0?
+1

Ruwan
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>

>
> ___
> 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

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org



___
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

Re: [Carbon-dev] Carbon trunk still use 3.0.0 snapshot

[Samisa Abeysinghe]

Do we have a script to do this?

On Tue, Jul 27, 2010 at 12:53 PM, Ruwan Linton  wrote:

> Samisa Abeysinghe wrote:
> > It is time that we updated to 3.1.0?
> +1
>
> Ruwan
> >
> > Thanks,
> > Samisa...
> >
> > Samisa Abeysinghe
> > VP Engineering
> > WSO2 Inc.
> > http://wso2.com
> > http://wso2.org
> >
> >
> >
> > 
> >
> > ___
> > 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
>
Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Ruwan Linton]

  On 8/17/10 11:06 AM, Supun Kamburugamuva wrote:
> We can extend this concept to have versioning for Synapse
> Configurations as well. This is a basic user requirement. When user
> does a change to a synapse configuration and save it we can give a new
> version to the configuration and later user can decide which version
> should be active.
Exactly, you read my mind :-)

Further, in the future, when we have the configuration referencing 
mechanism and the mediation debugger, we should be able to play a 
message via a non active developing version of the configuration and 
debug it, while developing.

After it is done, you can make it the active one. Yes, I am talking 
about the ESB 4.0 :-)

Ruwan
> Thanks,
> Supun..
>
> On Tue, Aug 17, 2010 at 10:18 AM, Samisa Abeysinghe  wrote:
>>
>> On Tue, Aug 17, 2010 at 9:20 AM, Hiranya Jayathilaka
>> wrote:
>>>
>>> On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe
>>> wrote:

 On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva
 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.
>>> I don't think any of the existing admin services fit the task in hand. IMO
>>> we need a new admin service. All the existing services are built around a
>>> single Synapse config. But the samples component should be able to manage
>>> multiple configurations - the main configuration and many sample
>>> configurations. Switching to a sample config should not wipe out the main
>>> config.
>>>
 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.
>>> Well, I'm not aware of the latest status of the test framework. Do you
>>> mean it has the ability to create multiple configurations and switch among
>>> them if needed (without wiping out each other)? If that capability is there
>>> then we +1 for reusing it.
>> I do not think that is possible as of now. I think what we have is that, for
>> each sample, we create and add new config elements.
>> Automation folks, please chime in.
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
> ___
> 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

Re: [Carbon-dev] Build failure in carbon core :-(

[Ruwan Linton]

  I have fixed this, please do not commit without building from here 
onwards, this is a single core build not even a component :-(

Ruwan

On 8/17/10 11:00 AM, Ruwan Linton wrote:
>  [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[36,30]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: package org.wso2.carbon.queuing
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[475,19]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class org.wso2.carbon.utils.multitenancy.CarbonContextHolder
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[487,44]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class org.wso2.carbon.utils.multitenancy.CarbonContextHolder
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[517,23]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class 
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[530,61]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class 
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[521,26]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class 
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[525,26]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class 
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager
>
> /Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[534,26]
>  
> cannot find symbol
> symbol  : class QueuingException
> location: class 
> org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager
>
>


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

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

On Tuesday, August 17, 2010, Supun Kamburugamuva  wrote:
> We can extend this concept to have versioning for Synapse
> Configurations as well. This is a basic user requirement.

+1

When user
> does a change to a synapse configuration and save it we can give a new
> version to the configuration and later user can decide which version
> should be active.

I hope this solution will be registry based as well.

Samisa...
>
> Thanks,
> Supun..
>
> On Tue, Aug 17, 2010 at 10:18 AM, Samisa Abeysinghe  wrote:
>>
>>
>> On Tue, Aug 17, 2010 at 9:20 AM, Hiranya Jayathilaka 
>> wrote:
>>>
>>>
>>> On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe 
>>> wrote:


 On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 
 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.
>>>
>>> I don't think any of the existing admin services fit the task in hand. IMO
>>> we need a new admin service. All the existing services are built around a
>>> single Synapse config. But the samples component should be able to manage
>>> multiple configurations - the main configuration and many sample
>>> configurations. Switching to a sample config should not wipe out the main
>>> config.
>>>

 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.
>>>
>>> Well, I'm not aware of the latest status of the test framework. Do you
>>> mean it has the ability to create multiple configurations and switch among
>>> them if needed (without wiping out each other)? If that capability is there
>>> then we +1 for reusing it.
>>
>> I do not think that is possible as of now. I think what we have is that, for
>> each sample, we create and add new config elements.
>> Automation folks, please chime in.
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>

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

Re: [Carbon-dev] Samples carbon component for ESB

[Supun Kamburugamuva]

We can extend this concept to have versioning for Synapse
Configurations as well. This is a basic user requirement. When user
does a change to a synapse configuration and save it we can give a new
version to the configuration and later user can decide which version
should be active.

Thanks,
Supun..

On Tue, Aug 17, 2010 at 10:18 AM, Samisa Abeysinghe  wrote:
>
>
> On Tue, Aug 17, 2010 at 9:20 AM, Hiranya Jayathilaka 
> wrote:
>>
>>
>> On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe 
>> wrote:
>>>
>>>
>>> On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 
>>> 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.
>>
>> I don't think any of the existing admin services fit the task in hand. IMO
>> we need a new admin service. All the existing services are built around a
>> single Synapse config. But the samples component should be able to manage
>> multiple configurations - the main configuration and many sample
>> configurations. Switching to a sample config should not wipe out the main
>> config.
>>
>>>
>>> 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.
>>
>> Well, I'm not aware of the latest status of the test framework. Do you
>> mean it has the ability to create multiple configurations and switch among
>> them if needed (without wiping out each other)? If that capability is there
>> then we +1 for reusing it.
>
> I do not think that is possible as of now. I think what we have is that, for
> each sample, we create and add new config elements.
> Automation folks, please chime in.
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

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

[Carbon-dev] Build failure in carbon core :-(

[Ruwan Linton]

  [ERROR] BUILD FAILURE
[INFO] 

[INFO] Compilation failure

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[36,30]
 
cannot find symbol
symbol  : class QueuingException
location: package org.wso2.carbon.queuing

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[475,19]
 
cannot find symbol
symbol  : class QueuingException
location: class org.wso2.carbon.utils.multitenancy.CarbonContextHolder

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[487,44]
 
cannot find symbol
symbol  : class QueuingException
location: class org.wso2.carbon.utils.multitenancy.CarbonContextHolder

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[517,23]
 
cannot find symbol
symbol  : class QueuingException
location: class 
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[530,61]
 
cannot find symbol
symbol  : class QueuingException
location: class 
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[521,26]
 
cannot find symbol
symbol  : class QueuingException
location: class 
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[525,26]
 
cannot find symbol
symbol  : class QueuingException
location: class 
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager

/Users/ruwanlinton/Development/WSO2/carbon/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[534,26]
 
cannot find symbol
symbol  : class QueuingException
location: class 
org.wso2.carbon.utils.multitenancy.CarbonContextHolder.InternalCarbonQueueManager


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

Re: [Carbon-dev] Why does AuthenticationAdmin implement CarbonServerAuthenticator?

[Afkham Azeez]

Why can't you use a separate class which implements that interface, and then
from AuthenticationAdmin, delegate to that class?

Azeez

On Mon, Aug 16, 2010 at 8:09 PM, Prabath Siriwardana wrote:

>
>
> On Mon, Aug 16, 2010 at 5:26 PM, Senaka Fernando  wrote:
>
>> Hi Prabath,
>>
>> Just wondering what are the reasons to $subject? Due to this the
>> AuthenticationAdmin service exposes several public methods. Some of these
>> can't even be invoked (which I excluded in r72047), and also causes build
>> failures when generating code using the given WSDL. The Iridium based
>> releases have this issue as well.
>>
>
> CarbonServerAuthenticator needs to be implemented by any authenticator
> written to fit in to the carbon authentication architecture.
>
> AuthenticationAdmin is the default one - it should implement
> CarbonServerAuthenticator.
>
> Thanks & regards.
> -Prabath
>
>>
>> Thanks,
>> Senaka.
>>
>> --
>> Senaka Fernando
>> Associate Technical Lead
>> WSO2 Inc.
>> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>>
>> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath Siriwardena
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Afkham Azeez
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
Lean . Enterprise . Middleware
Member; Apache Software Foundation; http://www.apache.org/
email: az...@wso2.com cell: +94 77 3320919
blog: http://blog.afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

On Tue, Aug 17, 2010 at 9:20 AM, Hiranya Jayathilaka wrote:

>
>
> On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.
>>
>
> I don't think any of the existing admin services fit the task in hand. IMO
> we need a new admin service. All the existing services are built around a
> single Synapse config. But the samples component should be able to manage
> multiple configurations - the main configuration and many sample
> configurations. Switching to a sample config should not wipe out the main
> config.
>
>
>>
>> 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.
>>
>
> Well, I'm not aware of the latest status of the test framework. Do you mean
> it has the ability to create multiple configurations and switch among them
> if needed (without wiping out each other)? If that capability is there then
> we +1 for reusing it.
>

I do not think that is possible as of now. I think what we have is that, for
each sample, we create and add new config elements.

Automation folks, please chime in.

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] State of the health monitor component

[Hiranya Jayathilaka]

On Tue, Aug 17, 2010 at 7:54 AM, Samisa Abeysinghe  wrote:

> We need to re-visit what this component should be doing.


+1 for revising this. Jonathan and I also had a little chat about the scope
of this component. Will send a separate note  on that.

Thanks,
Hiranya


>
> I am still not really clear what the component will be capable of. What
> happens if the server is running behind a firewall? What happens if the
> machine running Carbon server is not connected to Internet? Would the
> component be useful at all?
>
>
> On Mon, Aug 16, 2010 at 9:28 PM, Afkham Azeez  wrote:
>
>> Shariq will take over this work from Heshan.
>>
>> Azeez
>>
>>
>> On Fri, Aug 13, 2010 at 6:47 PM, Heshan Suriyaarachchi 
>> wrote:
>>
>>> Hi Azeez,
>>>This was in experimental state. Initially this was done as
>>> a POC and I think there might be areas to improve.
>>>
>>> +1 for adding the Health Monitor to Stratos. I can help you to get this
>>> to work on Stratos.
>>>
>>> On Thu, Aug 12, 2010 at 1:06 PM, Afkham Azeez  wrote:
>>>
 Hi Heshan,
 Is this in a usable state? I'd like to have this running on all Stratos
 services. Can you help with getting this working on Stratos?

 Thanks
 --
 Afkham Azeez
 Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
 Lean . Enterprise . Middleware
 Member; Apache Software Foundation; http://www.apache.org/
 email: az...@wso2.com cell: +94 77 3320919
 blog: http://blog.afkham.org
 twitter: http://twitter.com/afkham_azeez
 linked-in: http://lk.linkedin.com/in/afkhamazeez

 ___
 Stratos-dev mailing list
 stratos-...@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev


>>>
>>>
>>> --
>>> Regards,
>>> Heshan Suriyaarachchi
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com/
>>>
>>> Blog: http://heshans.blogspot.com/
>>>
>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> Lean . Enterprise . Middleware
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: az...@wso2.com cell: +94 77 3320919
>> blog: http://blog.afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> ___
>> Stratos-dev mailing list
>> stratos-...@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>
> ___
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
>


-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: 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

Re: [Carbon-dev] Samples carbon component for ESB

[Ruwan Linton]

 On 8/17/10 9:28 AM, Hiranya Jayathilaka wrote:

Ruwan,

On Tue, Aug 17, 2010 at 8:30 AM, Ruwan Linton > wrote:


On 8/17/10 7:45 AM, Samisa Abeysinghe wrote:



On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe
mailto:sam...@wso2.com>> wrote:



On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva
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
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
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,
>> > 

Re: [Carbon-dev] Samples carbon component for ESB

[Hiranya Jayathilaka]

Ruwan,

On Tue, Aug 17, 2010 at 8:30 AM, Ruwan Linton  wrote:

>  On 8/17/10 7:45 AM, Samisa Abeysinghe wrote:
>
>
>
> On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe wrote:
>
>>
>>
>>  On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.

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

Re: [Carbon-dev] Build error in dashboard component

[Anjana Fernando]

On Tue, Aug 17, 2010 at 9:16 AM, Nuwan Bandara  wrote:
> Hi Anjana,
>
> Should be fine now. sorry for the trouble.

Great. Thanks.

Cheers,
Anjana.

>
> Regards
> /Nuwan
>
> On Tue, Aug 17, 2010 at 6:38 AM, Anjana Fernando  wrote:
>>
>> Hi,
>>
>> When building the dashboard component in the 3.0.0/3.0.1 branch .. I'm
>> getting the following build error [1]. Seems it's referring to some
>> components with version 3.0.2, which are not there.
>>
>> [1] http://pastebin.com/xnvK4RHU
>>
>> Cheers,
>> Anjana.
>>
>> --
>> Anjana Fernando
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> --
> Nuwan Bandara
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://www.nuwanbando.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
Anjana Fernando
Software Engineer
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Carbon-dev] Samples carbon component for ESB

[Hiranya Jayathilaka]

On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.
>

I don't think any of the existing admin services fit the task in hand. IMO
we need a new admin service. All the existing services are built around a
single Synapse config. But the samples component should be able to manage
multiple configurations - the main configuration and many sample
configurations. Switching to a sample config should not wipe out the main
config.


>
> 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.
>

Well, I'm not aware of the latest status of the test framework. Do you mean
it has the ability to create multiple configurations and switch among them
if needed (without wiping out each other)? If that capability is there then
we +1 for reusing it.

Thanks,
Hiranya


> 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.
>
>>
>> I prefer the second approach.
>>
>> Thanks,
>> Supun..
>>
>> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
>> 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  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
>> >> > 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
>> >
>> > Thanks,
>> > Samisa...
>> >
>> > Samisa Abeysinghe
>> > VP Engineering
>> >
>> > WSO2 Inc.
>> > http://wso2.com
>> > http://wso2.org
>> >
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>> ___
>> Carbon-dev mailing list
>> 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
> 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;  Mobile: +94 77 633 3491
Blog: h

Re: [Carbon-dev] Build error in dashboard component

[Nuwan Bandara]

Hi Anjana,

Should be fine now. sorry for the trouble.

Regards
/Nuwan

On Tue, Aug 17, 2010 at 6:38 AM, Anjana Fernando  wrote:

> Hi,
>
> When building the dashboard component in the 3.0.0/3.0.1 branch .. I'm
> getting the following build error [1]. Seems it's referring to some
> components with version 3.0.2, which are not there.
>
> [1] http://pastebin.com/xnvK4RHU
>
> Cheers,
> Anjana.
>
> --
> Anjana Fernando
> Software Engineer
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Nuwan Bandara
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

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

Re: [Carbon-dev] Samples carbon component for ESB

[Ruwan Linton]

 On 8/17/10 7:45 AM, Samisa Abeysinghe wrote:



On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe > wrote:




On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva
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.


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

Re: [Carbon-dev] [Stratos-dev] State of the health monitor component

[Samisa Abeysinghe]

We need to re-visit what this component should be doing.

I am still not really clear what the component will be capable of. What
happens if the server is running behind a firewall? What happens if the
machine running Carbon server is not connected to Internet? Would the
component be useful at all?

On Mon, Aug 16, 2010 at 9:28 PM, Afkham Azeez  wrote:

> Shariq will take over this work from Heshan.
>
> Azeez
>
>
> On Fri, Aug 13, 2010 at 6:47 PM, Heshan Suriyaarachchi wrote:
>
>> Hi Azeez,
>>This was in experimental state. Initially this was done as
>> a POC and I think there might be areas to improve.
>>
>> +1 for adding the Health Monitor to Stratos. I can help you to get this to
>> work on Stratos.
>>
>> On Thu, Aug 12, 2010 at 1:06 PM, Afkham Azeez  wrote:
>>
>>> Hi Heshan,
>>> Is this in a usable state? I'd like to have this running on all Stratos
>>> services. Can you help with getting this working on Stratos?
>>>
>>> Thanks
>>> --
>>> Afkham Azeez
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>> Lean . Enterprise . Middleware
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> email: az...@wso2.com cell: +94 77 3320919
>>> blog: http://blog.afkham.org
>>> twitter: http://twitter.com/afkham_azeez
>>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>>
>>> ___
>>> Stratos-dev mailing list
>>> stratos-...@wso2.org
>>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Heshan Suriyaarachchi
>> Software Engineer
>> WSO2 Inc.; http://wso2.com/
>>
>> Blog: http://heshans.blogspot.com/
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> Lean . Enterprise . Middleware
> Member; Apache Software Foundation; http://www.apache.org/
> email: az...@wso2.com cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> ___
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

On Tue, Aug 17, 2010 at 7:39 AM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.


>
>> I prefer the second approach.
>>
>> Thanks,
>> Supun..
>>
>> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
>> 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  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
>> >> > 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
>> >
>> > Thanks,
>> > Samisa...
>> >
>> > Samisa Abeysinghe
>> > VP Engineering
>> >
>> > WSO2 Inc.
>> > http://wso2.com
>> > http://wso2.org
>> >
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>> ___
>> Carbon-dev mailing list
>> 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
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.

>
> I prefer the second approach.
>
> Thanks,
> Supun..
>
> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
> 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  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
> >> > 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
> >
> > Thanks,
> > Samisa...
> >
> > Samisa Abeysinghe
> > VP Engineering
> >
> > WSO2 Inc.
> > http://wso2.com
> > http://wso2.org
> >
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> 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
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

Folks,
I have asked TWICE on this thread if this uses the model used by test
automation framework.

   The question can be DUMB, but you have to have some respect to answer
that question.

On Mon, Aug 16, 2010 at 9:25 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.
>>
>> I prefer the second approach.
>>
>
>
> Further to this, I believe we should keep some metadata about each sample
> in some meta descriptor file (XML or properties file). Things like sample
> name, description, prerequisites etc should go into this meta file and
> displayed on the UI. It would be great if we can automatically enforce
> certain prerequisites too. For instance for JMS samples we should verify
> that jms transport is enabled and if not we should show an error. I think
> this is doable through some kind of an interface (SamplePrerequisite ?).
>
> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> Supun..
>>
>> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
>> 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  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
>> >> > 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
>> >
>> > Thanks,
>> > Samisa...
>> >
>> > Samisa Abeysinghe
>> > VP Engineering
>> >
>> > WSO2 Inc.
>> > http://wso2.com
>> > http://wso2.org
>> >
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>>
>> ___
>> Carbon-dev mailing list
>> 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;  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
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Build error in dashboard component

[Anjana Fernando]

Hi,

When building the dashboard component in the 3.0.0/3.0.1 branch .. I'm
getting the following build error [1]. Seems it's referring to some
components with version 3.0.2, which are not there.

[1] http://pastebin.com/xnvK4RHU

Cheers,
Anjana.

-- 
Anjana Fernando
Software Engineer
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Carbon-dev] Why does AuthenticationAdmin implement CarbonServerAuthenticator?

[Prabath Siriwardana]

On Mon, Aug 16, 2010 at 11:20 PM, Senaka Fernando  wrote:

>
>
>  On Mon, Aug 16, 2010 at 8:09 PM, Prabath Siriwardana wrote:
>
>>
>>
>>  On Mon, Aug 16, 2010 at 5:26 PM, Senaka Fernando wrote:
>>
>>> Hi Prabath,
>>>
>>> Just wondering what are the reasons to $subject? Due to this the
>>> AuthenticationAdmin service exposes several public methods. Some of these
>>> can't even be invoked (which I excluded in r72047), and also causes build
>>> failures when generating code using the given WSDL. The Iridium based
>>> releases have this issue as well.
>>>
>>
>> CarbonServerAuthenticator needs to be implemented by any authenticator
>> written to fit in to the carbon authentication architecture.
>>
>> AuthenticationAdmin is the default one - it should implement
>> CarbonServerAuthenticator.
>>
>
> Ok I see. But, AuthenticationAdmin is also an admin service. Now, are these
> methods supposed to be invoked using a client? If not, Azeez was suggesting
> that it might be better to have a separate class. WDYT?
>


Only the login/logout methods are supposed to be invoked by a web service
client. [The rest used by the AuthenticationAdminModule to pick the correct
authenticator, when other admin services protected for authentication being
invoked] So, let's restrict the service only to those two methods by the
services.xml..

Thanks & regards.
-Prabath


>
> Thanks,
> Senaka.
>
>>
>> Thanks & regards.
>> -Prabath
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> --
>>> Senaka Fernando
>>> Associate Technical Lead
>>> WSO2 Inc.
>>> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>>>
>>> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath Siriwardena
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com 
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Senaka Fernando
> Associate Technical Lead
> WSO2 Inc.
> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks & Regards,
Prabath Siriwardena

http://blog.facilelogin.com
http://RampartFAQ.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Why does AuthenticationAdmin implement CarbonServerAuthenticator?

[Senaka Fernando]

On Mon, Aug 16, 2010 at 8:09 PM, Prabath Siriwardana wrote:

>
>
> On Mon, Aug 16, 2010 at 5:26 PM, Senaka Fernando  wrote:
>
>> Hi Prabath,
>>
>> Just wondering what are the reasons to $subject? Due to this the
>> AuthenticationAdmin service exposes several public methods. Some of these
>> can't even be invoked (which I excluded in r72047), and also causes build
>> failures when generating code using the given WSDL. The Iridium based
>> releases have this issue as well.
>>
>
> CarbonServerAuthenticator needs to be implemented by any authenticator
> written to fit in to the carbon authentication architecture.
>
> AuthenticationAdmin is the default one - it should implement
> CarbonServerAuthenticator.
>

Ok I see. But, AuthenticationAdmin is also an admin service. Now, are these
methods supposed to be invoked using a client? If not, Azeez was suggesting
that it might be better to have a separate class. WDYT?

Thanks,
Senaka.

>
> Thanks & regards.
> -Prabath
>
>>
>> Thanks,
>> Senaka.
>>
>> --
>> Senaka Fernando
>> Associate Technical Lead
>> WSO2 Inc.
>> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>>
>> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath Siriwardena
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Senaka Fernando
Associate Technical Lead
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] State of the health monitor component

[Afkham Azeez]

Shariq will take over this work from Heshan.

Azeez

On Fri, Aug 13, 2010 at 6:47 PM, Heshan Suriyaarachchi wrote:

> Hi Azeez,
>This was in experimental state. Initially this was done as a
> POC and I think there might be areas to improve.
>
> +1 for adding the Health Monitor to Stratos. I can help you to get this to
> work on Stratos.
>
> On Thu, Aug 12, 2010 at 1:06 PM, Afkham Azeez  wrote:
>
>> Hi Heshan,
>> Is this in a usable state? I'd like to have this running on all Stratos
>> services. Can you help with getting this working on Stratos?
>>
>> Thanks
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> Lean . Enterprise . Middleware
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: az...@wso2.com cell: +94 77 3320919
>> blog: http://blog.afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> ___
>> Stratos-dev mailing list
>> stratos-...@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>
>>
>
>
> --
> Regards,
> Heshan Suriyaarachchi
> Software Engineer
> WSO2 Inc.; http://wso2.com/
>
> Blog: http://heshans.blogspot.com/
>



-- 
Afkham Azeez
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
Lean . Enterprise . Middleware
Member; Apache Software Foundation; http://www.apache.org/
email: az...@wso2.com cell: +94 77 3320919
blog: http://blog.afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Hiranya Jayathilaka]

On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.
>
> I prefer the second approach.
>


Further to this, I believe we should keep some metadata about each sample in
some meta descriptor file (XML or properties file). Things like sample name,
description, prerequisites etc should go into this meta file and displayed
on the UI. It would be great if we can automatically enforce certain
prerequisites too. For instance for JMS samples we should verify that jms
transport is enabled and if not we should show an error. I think this is
doable through some kind of an interface (SamplePrerequisite ?).

Thanks,
Hiranya


>
> Thanks,
> Supun..
>
> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
> 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  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
> >> > 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
> >
> > Thanks,
> > Samisa...
> >
> > Samisa Abeysinghe
> > VP Engineering
> >
> > WSO2 Inc.
> > http://wso2.com
> > http://wso2.org
> >
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> 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;  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

Re: [Carbon-dev] Samples carbon component for ESB

[Hiranya Jayathilaka]

On Mon, Aug 16, 2010 at 10:54 AM, Supun Kamburugamuva 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.
>

This sounds reasonable. Anyway could you please explain why and how we
reinit the persistence manager?

Thanks,
Hiranya


>
> I prefer the second approach.
>
> Thanks,
> Supun..
>
> On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe 
> 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  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
> >> > 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
> >
> > Thanks,
> > Samisa...
> >
> > Samisa Abeysinghe
> > VP Engineering
> >
> > WSO2 Inc.
> > http://wso2.com
> > http://wso2.org
> >
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> 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;  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

Re: [Carbon-dev] Why does AuthenticationAdmin implement CarbonServerAuthenticator?

[Prabath Siriwardana]

On Mon, Aug 16, 2010 at 5:26 PM, Senaka Fernando  wrote:

> Hi Prabath,
>
> Just wondering what are the reasons to $subject? Due to this the
> AuthenticationAdmin service exposes several public methods. Some of these
> can't even be invoked (which I excluded in r72047), and also causes build
> failures when generating code using the given WSDL. The Iridium based
> releases have this issue as well.
>

CarbonServerAuthenticator needs to be implemented by any authenticator
written to fit in to the carbon authentication architecture.

AuthenticationAdmin is the default one - it should implement
CarbonServerAuthenticator.

Thanks & regards.
-Prabath

>
> Thanks,
> Senaka.
>
> --
> Senaka Fernando
> Associate Technical Lead
> WSO2 Inc.
> E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks & Regards,
Prabath Siriwardena

http://blog.facilelogin.com
http://RampartFAQ.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Why does AuthenticationAdmin implement CarbonServerAuthenticator?

[Senaka Fernando]

Hi Prabath,

Just wondering what are the reasons to $subject? Due to this the
AuthenticationAdmin service exposes several public methods. Some of these
can't even be invoked (which I excluded in r72047), and also causes build
failures when generating code using the given WSDL. The Iridium based
releases have this issue as well.

Thanks,
Senaka.

-- 
Senaka Fernando
Associate Technical Lead
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

http://www.wso2.com/ - "Lean . Enterprise . Middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Unexpected return value from SVN server when fetching oauth external

[Milinda Pathirage]

Full warning:

Fetching external item into 'oauth'
svn: warning: Server sent unexpected return value (502 Bad Gateway) in
response to REPORT request for '/svn/!svn/vcc/default'

Happened when updating carbon trunk dependencies.

Thanks
Milinda

-- 
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@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] carbon core failed to build on trunk

[Amila Jayasekara]

Hi Samisa,
I couldnt reproduce this issue. Also pom's are seems to be ok. My 
svn revision is 72041. Is this an offline build ?
Thankx
AmilaJ

Samisa Abeysinghe wrote:
> This is with a fresh repo.
>
> On Mon, Aug 16, 2010 at 3:41 PM, Sumedha Rubasinghe  > wrote:
>
> I am on revision71987 & it works for me.
> /sumedha
>
> On Mon, Aug 16, 2010 at 3:31 PM, Samisa Abeysinghe
> mailto:sam...@wso2.com>> wrote:
>
> [ERROR] BUILD ERROR
> [INFO]
> 
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>  mvn install:install-file
> -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18
> -Dpackaging=jar -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy
> the file there:
>  mvn deploy:deploy-file
> -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
>  Path to dependency:
>1)
> org.wso2.carbon:org.wso2.carbon.server:jar:3.0.0-SNAPSHOT
>2)
> org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc. 
> http://wso2.com
> http://wso2.org
>
>  
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> ___
> Carbon-dev mailing list
> 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
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


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

Re: [Carbon-dev] carbon core failed to build on trunk

[Amila Jayasekara]

I will look into this.

Samisa Abeysinghe wrote:
> This is with a fresh repo.
>
> On Mon, Aug 16, 2010 at 3:41 PM, Sumedha Rubasinghe  > wrote:
>
> I am on revision71987 & it works for me.
> /sumedha
>
> On Mon, Aug 16, 2010 at 3:31 PM, Samisa Abeysinghe
> mailto:sam...@wso2.com>> wrote:
>
> [ERROR] BUILD ERROR
> [INFO]
> 
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>  mvn install:install-file
> -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18
> -Dpackaging=jar -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy
> the file there:
>  mvn deploy:deploy-file
> -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
>  Path to dependency:
>1)
> org.wso2.carbon:org.wso2.carbon.server:jar:3.0.0-SNAPSHOT
>2)
> org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc. 
> http://wso2.com
> http://wso2.org
>
>  
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> ___
> Carbon-dev mailing list
> 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
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


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

Re: [Carbon-dev] carbon core failed to build on trunk

[Samisa Abeysinghe]

This is with a fresh repo.

On Mon, Aug 16, 2010 at 3:41 PM, Sumedha Rubasinghe wrote:

> I am on revision71987 & it works for me.
> /sumedha
>
> On Mon, Aug 16, 2010 at 3:31 PM, Samisa Abeysinghe wrote:
>
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> --
>> 1) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>>
>>  Try downloading the file manually from the project website.
>>
>>  Then, install it using the command:
>>  mvn install:install-file -DgroupId=org.apache.directory.shared
>> -DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
>> -Dfile=/path/to/file
>>
>>  Alternatively, if you host your own repository you can deploy the file
>> there:
>>  mvn deploy:deploy-file -DgroupId=org.apache.directory.shared
>> -DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
>> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>>
>>  Path to dependency:
>>1) org.wso2.carbon:org.wso2.carbon.server:jar:3.0.0-SNAPSHOT
>>2) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> 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
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] carbon core failed to build on trunk

[Sumedha Rubasinghe]

I am on revision71987 & it works for me.
/sumedha

On Mon, Aug 16, 2010 at 3:31 PM, Samisa Abeysinghe  wrote:

> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
>  Try downloading the file manually from the project website.
>
>  Then, install it using the command:
>  mvn install:install-file -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
> -Dfile=/path/to/file
>
>  Alternatively, if you host your own repository you can deploy the file
> there:
>  mvn deploy:deploy-file -DgroupId=org.apache.directory.shared
> -DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>  Path to dependency:
>1) org.wso2.carbon:org.wso2.carbon.server:jar:3.0.0-SNAPSHOT
>2) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon core compilation failure

[Selvaratnam Uthaiyashankar]

This is a windows specific issue, due to file separator ( using d:/
instead of d:\). Fixed now.

Regards,
Shankar

On Mon, Aug 16, 2010 at 1:31 PM, Selvaratnam Uthaiyashankar
 wrote:
> When compiling carbon core, getting following error (I am in windows,
> and using JDK 1.6). Any idea?
>
> [INFO] 
> 
> [INFO] Building WSO2 Carbon - Carbon P2 Profile
> [INFO]    task-segment: [clean, install]
> [INFO] 
> 
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting directory
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target
> [INFO] [dependency:unpack {execution: 1-unpack-p2-agent-distribution}]
> [INFO] Configured Artifact: org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
> [INFO] Configured Artifact: org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
> [INFO] Expanding:
> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
> int
> o 
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\p2-agent
> [INFO] Expanding:
> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
> int
> o 
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\carbon-p2-profile
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [carbon-p2:p2-repo-gen {execution: 2-p2-repo-generation}]
> [ERROR] URI is not hierarchical
> java.lang.IllegalArgumentException: URI is not hierarchical
>        at java.io.File.(File.java:363)
>        at 
> org.wso2.maven.p2.RepositoryGenMojo.createAndSetupPaths(RepositoryGenMojo.java:419)
>        at 
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:195)
>        at 
> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
>        at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
> 6)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:387)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>        at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>        at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>        at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] URI is not hierarchical
>
> --
> S.Uthaiyashankar
> Senior Software Architect
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>



-- 
S.Uthaiyashankar
Senior Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

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

[Carbon-dev] carbon core failed to build on trunk

[Samisa Abeysinghe]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18

 Try downloading the file manually from the project website.

 Then, install it using the command:
 mvn install:install-file -DgroupId=org.apache.directory.shared
-DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
-Dfile=/path/to/file

 Alternatively, if you host your own repository you can deploy the file
there:
 mvn deploy:deploy-file -DgroupId=org.apache.directory.shared
-DartifactId=shared-ldap-schema -Dversion=0.9.18 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

 Path to dependency:
   1) org.wso2.carbon:org.wso2.carbon.server:jar:3.0.0-SNAPSHOT
   2) org.apache.directory.shared:shared-ldap-schema:jar:0.9.18

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Samisa Abeysinghe]

On Mon, Aug 16, 2010 at 1:46 PM, Miyuru Wanninayaka  wrote:

>
>
> On Mon, Aug 16, 2010 at 11:25 AM, Ruwan Linton  wrote:
>
>>   On 8/16/10 10:54 AM, Supun Kamburugamuva 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.
>> >
>> > I prefer the second approach.
>> +1, actually if we can keep the synapse configurations which are loaded
>> at runtime as alternate configurations and have only one configuration
>> as active that would be the ideal.
>>
>
This is what we do in test automation FW.

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon core compilation failure

[Selvaratnam Uthaiyashankar]

On Mon, Aug 16, 2010 at 2:01 PM, Afkham Azeez  wrote:
> Try updating the P2 plugin.


It is in latest revision.

Regards,
Shankar


> Azeez
>
> On Mon, Aug 16, 2010 at 1:31 PM, Selvaratnam Uthaiyashankar
>  wrote:
>>
>> When compiling carbon core, getting following error (I am in windows,
>> and using JDK 1.6). Any idea?
>>
>> [INFO]
>> 
>> [INFO] Building WSO2 Carbon - Carbon P2 Profile
>> [INFO]    task-segment: [clean, install]
>> [INFO]
>> 
>> [INFO] [clean:clean {execution: default-clean}]
>> [INFO] Deleting directory
>> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target
>> [INFO] [dependency:unpack {execution: 1-unpack-p2-agent-distribution}]
>> [INFO] Configured Artifact:
>> org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
>> [INFO] Configured Artifact:
>> org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
>> [INFO] Expanding:
>>
>> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
>> int
>> o
>> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\p2-agent
>> [INFO] Expanding:
>>
>> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
>> int
>> o
>> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\carbon-p2-profile
>> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
>> [INFO] [carbon-p2:p2-repo-gen {execution: 2-p2-repo-generation}]
>> [ERROR] URI is not hierarchical
>> java.lang.IllegalArgumentException: URI is not hierarchical
>>        at java.io.File.(File.java:363)
>>        at
>> org.wso2.maven.p2.RepositoryGenMojo.createAndSetupPaths(RepositoryGenMojo.java:419)
>>        at
>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:195)
>>        at
>> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
>>        at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
>> 6)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
>> a:387)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>>        at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>        at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>        at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>        at java.lang.reflect.Method.invoke(Method.java:597)
>>        at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>        at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] URI is not hierarchical
>>
>> --
>> S.Uthaiyashankar
>> Senior Software Architect
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> Lean . Enterprise . Middleware
> Member; Apache Software Foundation; http://www.apache.org/
> email: az...@wso2.com cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 
S.Uthaiyashankar
Senior Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

___
Car

Re: [Carbon-dev] Carbon core compilation failure

[Afkham Azeez]

Try updating the P2 plugin.

Azeez

On Mon, Aug 16, 2010 at 1:31 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

> When compiling carbon core, getting following error (I am in windows,
> and using JDK 1.6). Any idea?
>
> [INFO]
> 
> [INFO] Building WSO2 Carbon - Carbon P2 Profile
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting directory
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target
> [INFO] [dependency:unpack {execution: 1-unpack-p2-agent-distribution}]
> [INFO] Configured Artifact:
> org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
> [INFO] Configured Artifact:
> org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
> [INFO] Expanding:
>
> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
> int
> o
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\p2-agent
> [INFO] Expanding:
>
> G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
> int
> o
> G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\carbon-p2-profile
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [carbon-p2:p2-repo-gen {execution: 2-p2-repo-generation}]
> [ERROR] URI is not hierarchical
> java.lang.IllegalArgumentException: URI is not hierarchical
>at java.io.File.(File.java:363)
>at
> org.wso2.maven.p2.RepositoryGenMojo.createAndSetupPaths(RepositoryGenMojo.java:419)
>at
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:195)
>at
> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
>at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
> 6)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:387)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> 
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] URI is not hierarchical
>
> --
> S.Uthaiyashankar
> Senior Software Architect
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Afkham Azeez
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
Lean . Enterprise . Middleware
Member; Apache Software Foundation; http://www.apache.org/
email: az...@wso2.com cell: +94 77 3320919
blog: http://blog.afkham.org
twitter: http://twitter.com/afkham_azeez
linked-in: http://lk.linkedin.com/in/afkhamazeez
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Samples carbon component for ESB

[Miyuru Wanninayaka]

On Mon, Aug 16, 2010 at 11:25 AM, Ruwan Linton  wrote:

>   On 8/16/10 10:54 AM, Supun Kamburugamuva 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.
> >
> > I prefer the second approach.
> +1, actually if we can keep the synapse configurations which are loaded
> at runtime as alternate configurations and have only one configuration
> as active that would be the ideal.
>

+1 for Ruwan's idea.

BTW how do we manage server level configuration such as
transports configurations? Ex: for Mail, JMS samples

>
> Ruwan
> > Thanks,
> > Supun..
> >
> > On Mon, Aug 16, 2010 at 9:14 AM, Samisa Abeysinghe
>  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  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
>  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
> >> Thanks,
> >> Samisa...
> >>
> >> Samisa Abeysinghe
> >> VP Engineering
> >>
> >> WSO2 Inc.
> >> http://wso2.com
> >> http://wso2.org
> >>
> >>
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >>
> > ___
> > 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
>



-- 
Thanks,
Miyuru
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Carbon core compilation failure

[Selvaratnam Uthaiyashankar]

When compiling carbon core, getting following error (I am in windows,
and using JDK 1.6). Any idea?

[INFO] 
[INFO] Building WSO2 Carbon - Carbon P2 Profile
[INFO]task-segment: [clean, install]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory
G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target
[INFO] [dependency:unpack {execution: 1-unpack-p2-agent-distribution}]
[INFO] Configured Artifact: org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
[INFO] Configured Artifact: org.wso2.carbon:wso2-p2-agent:3.0.0-SNAPSHOT:zip
[INFO] Expanding:
G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
int
o 
G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\p2-agent
[INFO] Expanding:
G:\Garbage\MavenRepo\org\wso2\carbon\wso2-p2-agent\3.0.0-SNAPSHOT\wso2-p2-agent-3.0.0-SNAPSHOT.zip
int
o 
G:\src\java\carbon\core\p2-profile-generation\carbon-p2-profile\target\carbon-p2-profile
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [carbon-p2:p2-repo-gen {execution: 2-p2-repo-generation}]
[ERROR] URI is not hierarchical
java.lang.IllegalArgumentException: URI is not hierarchical
at java.io.File.(File.java:363)
at 
org.wso2.maven.p2.RepositoryGenMojo.createAndSetupPaths(RepositoryGenMojo.java:419)
at 
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:195)
at 
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:187)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
6)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] URI is not hierarchical

-- 
S.Uthaiyashankar
Senior Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

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