Re: [Carbon-dev] Next G-Reg version

2010-09-17 Thread Samisa Abeysinghe 
+1.

On Sat, Sep 18, 2010 at 8:32 AM, Lahiru Gunathilake  wrote:

> Hi all,
>
> What would be the next G-Reg version, currently we are having
> 3.5.0-SNAPSHOT. I think it has to be 3.6.0, WDYT ?
>
> Thanks
> Lahiru
>
> --
> Lahiru Gunathilake
> Senior Software Engineer - WSO2 Inc. www.wso2.com
>
> Email:lah...@wso2.com  Blog: www.lahiru.org
> Mobile: +94716381143
>
> Lean . Enterprise . Middleware
>
>
> ___
> 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] Code Review Notes - BAM_28/10/09:(Resending)

2010-09-17 Thread Ajith Vitharana 
Hi BAM folks,

Shall we start to enhance things that we have discussed at BAM code reviews
?
I think most of the review note points are still pending.

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

[Carbon-dev] Next G-Reg version

2010-09-17 Thread Lahiru Gunathilake 
Hi all,

What would be the next G-Reg version, currently we are having
3.5.0-SNAPSHOT. I think it has to be 3.6.0, WDYT ?

Thanks
Lahiru

-- 
Lahiru Gunathilake
Senior Software Engineer - WSO2 Inc. www.wso2.com

Email:lah...@wso2.com  Blog: www.lahiru.org
Mobile: +94716381143

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

[Carbon-dev] Inconsistencies in Data Source API

2010-09-17 Thread Anjana Fernando 
Hi,

I'm a bit confused on how data sources component's data source lookup is
working. In the data source UI, we have the "Name" and the "Data Source
Name" (the fields themselves are a bit confusing to start with) .. and in
the code, the backend admin service assigns them to the "alias"  and the
"dataSourceName" fields to a "DataSourceInformation" instance, respectively.

In
"org.apache.synapse.commons.datasource.factory.DataSourceInformationFactory"
class's "createDataSourceInformation" method is like this,

   public static DataSourceInformation createDataSourceInformation(String
dsName,

 Properties properties) {

...
   DataSourceInformation datasourceInformation = new
DataSourceInformation();
   datasourceInformation.setAlias(dsName);
...
   String dataSourceName = MiscellaneousUtil.getProperty(
   properties, prefix + DataSourceConstants.PROP_DSNAME, dsName,
   String.class);
   datasourceInformation.setDatasourceName(dataSourceName);

So "dsName" parameter is what we get from our UI's "Name" field, and the
property bags' "PROP_DSNAME" is from the UI's "Data Source Name".

Starting from the data sources admin service, when a data source is added,
it calls
"DataSourceInformantionManager->addDataSourceInformation(DataSourceInformation)".


   public void addDataSourceInformation(DataSourceInformation information) {
   repository.addDataSourceInformation(information);
   }

Here "repository" is
"org.apache.synapse.commons.datasource.DataSourceInformationRepository".

   public void addDataSourceInformation(DataSourceInformation
dataSourceInformation) {
   assertNull(dataSourceInformation, "DataSource information is null");
   dataSourceInformationMap.put(dataSourceInformation.getAlias(),
dataSourceInformation);
...

So here, they store the data source info in a map using the alias as the
key. So many data sources with different aliases and possibly with the same
"Data Source Name" can coexist. This is compatible with the UI we have. But
looking at how the data sources are actually saved, not the info, but the
actual DataSource objects, in
org.apache.synapse.commons.datasource.DataSourceRepositoryManager,

   public void addDataSourceInformation(DataSourceInformation
dataSourceInformation) {
   if (dataSourceInformation == null) {
   return;
   }
   String repositoryType = dataSourceInformation.getRepositoryType();
   if (DataSourceConstants.PROP_REGISTRY_JNDI.equals(repositoryType)) {
   jndiBasedDataSourceRepository.register(dataSourceInformation);
   } else {
   inMemoryDataSourceRepository.register(dataSourceInformation);
   }
   }

A look at
"org.apache.synapse.commons.datasource.InMemoryDataSourceRepository",

   public void register(DataSourceInformation dataSourceInformation) {
...
   String name = dataSourceInformation.getDatasourceName();
...
   dataSources.put(name, dataSource);
...

So here effectively at the end, the "dataSourceName" field is used in
storing the actual data sources, and not the alias. So in this place, if we
have registered several data source from our UI that have the same "Data
Source Name" field, those will be replaced and only the last data source
will survive.

Ultimately the point is, the class "DataSourceInformationRepository" works
with the "alias" and the class "DataSourceRepositoryManager" works with the
other property "dataSourceName", to store/retrieve data sources.

I was checking this because, in DSS i was using the following code to get a
registered data source,

private DataSource
createDataSource(DataSourceInformationRepositoryService cdService) {
DataSourceInformationRepository datasourceRepo = cdService.
getDataSourceInformationRepository();
DataSourceHelper dataSourceHelper = DataSourceHelper.getInstance();
dataSourceHelper.init(datasourceRepo, null);
return
dataSourceHelper.getDataSourceRepositoryManager().getDataSource(
this.getDataSourceName());
}

And there for the "getDataSource" method, you have to give the "Data Source
Name" that's there in the UI (2'nd field) not the alias, and you actually
can't use the alias as I explained earlier.

So can someone who's familiar with the data source component, please look
into this, maybe I'm missing something here.

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] Carbon 3.0.1 RC1 Build

2010-09-17 Thread Asela Pathberiya 
On Fri, Sep 17, 2010 at 5:18 PM, Charitha Kankanamge wrote:

>
>
> On Fri, Sep 17, 2010 at 4:08 PM, Asela Pathberiya  wrote:
>
>>
>>
>> On Thu, Sep 16, 2010 at 10:20 PM, Charitha Kankanamge 
>> wrote:
>>
>>> Can we have DS, GS and BPS RC2 builds please? AFAIK, we need to release
>>> these packs in order to do CStudio release.
>>>
>>>
>> Please find the GS and BPS RC2 builds here [1] .
>>
>> [1] 
>> http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC2/
>>
>
>
> DS? Can we have DS as well? there are issues which need to be verified.
>

There is an issue with DS doc packs. Anjana will look into it. When it is
fixed, will update.

Thanks,
Asela.

>
> Regards
> Charitha
>
>
>>
>> Thanks,
>> Asela.
>>
>>
>>
>>
>>> Regards
>>> Charitha
>>>
>>>
>>>
>>> On Mon, Sep 6, 2010 at 12:38 PM, Asela Pathberiya wrote:
>>>


 On Mon, Sep 6, 2010 at 10:20 AM, Samisa Abeysinghe wrote:

>
>
> On Mon, Sep 6, 2010 at 10:15 AM, Asela Pathberiya wrote:
>
>>
>>
>> On Mon, Sep 6, 2010 at 8:18 AM, Chathuri Wimalasena <
>> chath...@wso2.com> wrote:
>>
>>> We need BPS packs for CStudio as well.
>>>
>>
>> Please find BPS build from same location.
>>
>
> DS and GS?
>

 Please find DS and GS builds from same location.

 Thanks,
 Asela.

>
>> Thanks,
>> Asela.
>>
>>>
>>> Regards,
>>> Chathuri
>>>
>>>
>>> On Mon, Sep 6, 2010 at 8:04 AM, Samisa Abeysinghe 
>>> wrote:
>>>
 Can we also have DS and GS packs?

 What other packs do we need for CStudio?

 On Sun, Sep 5, 2010 at 10:17 PM, Asela Pathberiya 
 wrote:

> Hi All,
>
> Please find the 3.0.1 RC1 build of ESB,WSAS,GREG and IS here [1]
>
> [1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC1
>
> Thanks,
> Asela
> ___
> 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
>>>
>>>
>>
>> ___
>> 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


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

Re: [Carbon-dev] Carbon 3.0.1 RC1 Build

2010-09-17 Thread Charitha Kankanamge 
On Fri, Sep 17, 2010 at 4:08 PM, Asela Pathberiya  wrote:

>
>
> On Thu, Sep 16, 2010 at 10:20 PM, Charitha Kankanamge 
> wrote:
>
>> Can we have DS, GS and BPS RC2 builds please? AFAIK, we need to release
>> these packs in order to do CStudio release.
>>
>>
> Please find the GS and BPS RC2 builds here [1] .
>
> [1] 
> http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC2/
>


DS? Can we have DS as well? there are issues which need to be verified.

Regards
Charitha


>
> Thanks,
> Asela.
>
>
>
>
>> Regards
>> Charitha
>>
>>
>>
>> On Mon, Sep 6, 2010 at 12:38 PM, Asela Pathberiya  wrote:
>>
>>>
>>>
>>> On Mon, Sep 6, 2010 at 10:20 AM, Samisa Abeysinghe wrote:
>>>


 On Mon, Sep 6, 2010 at 10:15 AM, Asela Pathberiya wrote:

>
>
> On Mon, Sep 6, 2010 at 8:18 AM, Chathuri Wimalasena  > wrote:
>
>> We need BPS packs for CStudio as well.
>>
>
> Please find BPS build from same location.
>

 DS and GS?

>>>
>>> Please find DS and GS builds from same location.
>>>
>>> Thanks,
>>> Asela.
>>>

> Thanks,
> Asela.
>
>>
>> Regards,
>> Chathuri
>>
>>
>> On Mon, Sep 6, 2010 at 8:04 AM, Samisa Abeysinghe wrote:
>>
>>> Can we also have DS and GS packs?
>>>
>>> What other packs do we need for CStudio?
>>>
>>> On Sun, Sep 5, 2010 at 10:17 PM, Asela Pathberiya wrote:
>>>
 Hi All,

 Please find the 3.0.1 RC1 build of ESB,WSAS,GREG and IS here [1]

 [1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC1

 Thanks,
 Asela
 ___
 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
>>
>>
>
> ___
> 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
>>>
>>>
>>
>> ___
>> 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] Unified way for a component to know when it should initialize/destroy

2010-09-17 Thread Ruwan Linton 
  Hmmm, I didn't get it. A component initialization, (which will happen 
most of the time inline with the system initialization) and a tenant 
initialization are 2 different things.

A particular component would want to initialize itself at the system 
initialization while it might want to do certain task for each and every 
tenant when it is initializing. Note that all tenants are using the same 
instance of a given component.

Ruwan

On 9/17/10 2:22 PM, Srinath Perera wrote:
> +1
>
> On Fri, Sep 17, 2010 at 2:16 PM, Supun Kamburugamuva  wrote:
>> I'm looking for way for a component to know when it has to initialize
>> and when it has to destroy?
>>
>> At the moment we have two instances where a component should initialize.
>>
>> 1. Carbon initialization
>> 2. Tenant initialization
>>
>> But these two are two different cases. From a component perspective
>> they shouldn't know weather it is a system initialization or a tenant
>> initialization. It would be great to have a unified mechanism across
>> the platform for a component to decide when to initialize and when to
>> destroy.
>>
>> Thanks,
>>
>> --
>> Supun Kamburugamuva
>> Technical Lead
>> WSO2 Inc.;  http://wso2.org
>> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
>> Blog: http://supunk.blogspot.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>


-- 
Ruwan Linton
Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton


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

Re: [Carbon-dev] Carbon 3.0.1 RC1 Build

2010-09-17 Thread Asela Pathberiya 
On Thu, Sep 16, 2010 at 10:20 PM, Charitha Kankanamge wrote:

> Can we have DS, GS and BPS RC2 builds please? AFAIK, we need to release
> these packs in order to do CStudio release.
>
>
Please find the GS and BPS RC2 builds here [1] .

[1] http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC2/

Thanks,
Asela.




> Regards
> Charitha
>
>
>
> On Mon, Sep 6, 2010 at 12:38 PM, Asela Pathberiya  wrote:
>
>>
>>
>> On Mon, Sep 6, 2010 at 10:20 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Mon, Sep 6, 2010 at 10:15 AM, Asela Pathberiya wrote:
>>>


 On Mon, Sep 6, 2010 at 8:18 AM, Chathuri Wimalasena 
 wrote:

> We need BPS packs for CStudio as well.
>

 Please find BPS build from same location.

>>>
>>> DS and GS?
>>>
>>
>> Please find DS and GS builds from same location.
>>
>> Thanks,
>> Asela.
>>
>>>
 Thanks,
 Asela.

>
> Regards,
> Chathuri
>
>
> On Mon, Sep 6, 2010 at 8:04 AM, Samisa Abeysinghe wrote:
>
>> Can we also have DS and GS packs?
>>
>> What other packs do we need for CStudio?
>>
>> On Sun, Sep 5, 2010 at 10:17 PM, Asela Pathberiya wrote:
>>
>>> Hi All,
>>>
>>> Please find the 3.0.1 RC1 build of ESB,WSAS,GREG and IS here [1]
>>>
>>> [1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC1
>>>
>>> Thanks,
>>> Asela
>>> ___
>>> 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
>
>

 ___
 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
>>
>>
>
> ___
> 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] WSAS artifact related improvements in CStudio

2010-09-17 Thread Sumedha Rubasinghe 
Isuru,
Tx for the suggestions. :-) . Very valuable indeed.
/sumedha

On Fri, Sep 17, 2010 at 2:48 PM, Isuru Suriarachchi  wrote:

> Hi all,
>
> I had a discussion with Saminda about the improvements that can be made on
> WSAS related tools on Carbon studio. Here is the list of items.
>
> 1. Editor to write/edit the services.xml. This should provide options to
> easily engage a module, attach a policy, add parameters, add Message
> Receivers etc..
> 2. Option to create Message Receivers. This will generate MR class by
> implementing the MessageReceiver interface and the user only has to write
> the logic inside.
> 3. Editor to create jaxws services. Currently it can only import an
> existing .jar file into the project. In addition to that, it should be
> possible to simply write a java class and add annotations into it.
> 4. Tool to generate sprig services using the context.xml and beans. This
> will use the spring component in Carbon to create the .aar file out of the
> spring beans.
> 5. Ability to write Axis2 modules. It should generate classes which
> implements Handler interface etc..
>
> Saminda, please add if I've missed anything..
>
> Thanks,
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Web Services Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> 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] WSAS artifact related improvements in CStudio

2010-09-17 Thread Saminda Wijeratne 
On Fri, Sep 17, 2010 at 2:48 PM, Isuru Suriarachchi  wrote:

> Hi all,
>
> I had a discussion with Saminda about the improvements that can be made on
> WSAS related tools on Carbon studio. Here is the list of items.
>
> 1. Editor to write/edit the services.xml. This should provide options to
> easily engage a module, attach a policy, add parameters, add Message
> Receivers etc..
> 2. Option to create Message Receivers. This will generate MR class by
> implementing the MessageReceiver interface and the user only has to write
> the logic inside.

3. Editor to create jaxws services. Currently it can only import an existing
> .jar file into the project. In addition to that, it should be possible to
> simply write a java class and add annotations into it.
>
After the discussion with Isuru I went and rechecked the JAX-WS support from
eclipse [1]. As it turns-out they had released it with the Helios this
time.
But since galileo does not include this by default and
cannot guarantee proper support it might not be good to depend on this for
now. Also the current release in Helios seems to be a bit unstable at times.
Will have to wait for their RC1 which'll be in a couple of months.

> 4. Tool to generate sprig services using the context.xml and beans. This
> will use the spring component in Carbon to create the .aar file out of the
> spring beans.
> 5. Ability to write Axis2 modules. It should generate classes which
> implements Handler interface etc..
>
note: Axis2 modules will not be related to capp tools

Regards,
Saminda

[1] http://wiki.eclipse.org/JAXWS

> Saminda, please add if I've missed anything..
>
> Thanks,
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead & Product Manager, WSO2 Web Services Application Server
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> 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] WSAS artifact related improvements in CStudio

2010-09-17 Thread Isuru Suriarachchi 
Hi all,

I had a discussion with Saminda about the improvements that can be made on
WSAS related tools on Carbon studio. Here is the list of items.

1. Editor to write/edit the services.xml. This should provide options to
easily engage a module, attach a policy, add parameters, add Message
Receivers etc..
2. Option to create Message Receivers. This will generate MR class by
implementing the MessageReceiver interface and the user only has to write
the logic inside.
3. Editor to create jaxws services. Currently it can only import an existing
.jar file into the project. In addition to that, it should be possible to
simply write a java class and add annotations into it.
4. Tool to generate sprig services using the context.xml and beans. This
will use the spring component in Carbon to create the .aar file out of the
spring beans.
5. Ability to write Axis2 modules. It should generate classes which
implements Handler interface etc..

Saminda, please add if I've missed anything..

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead & Product Manager, WSO2 Web Services Application Server
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Carbon-dev] Unified way for a component to know when it should initialize/destroy

2010-09-17 Thread Srinath Perera 
+1

On Fri, Sep 17, 2010 at 2:16 PM, Supun Kamburugamuva  wrote:
> I'm looking for way for a component to know when it has to initialize
> and when it has to destroy?
>
> At the moment we have two instances where a component should initialize.
>
> 1. Carbon initialization
> 2. Tenant initialization
>
> But these two are two different cases. From a component perspective
> they shouldn't know weather it is a system initialization or a tenant
> initialization. It would be great to have a unified mechanism across
> the platform for a component to decide when to initialize and when to
> destroy.
>
> Thanks,
>
> --
> Supun Kamburugamuva
> Technical Lead
> WSO2 Inc.;  http://wso2.org
> E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
> Blog: http://supunk.blogspot.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 

Srinath Perera, Ph.D.
   WSO2 Inc. http://wso2.com
   Blog: http://srinathsview.blogspot.com/

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

[Carbon-dev] DataService Insert Exception Handling

2010-09-17 Thread Hodchenkov, Paul 
Hi!
I hope someone can help me. I am using db dataservice to perform insert queries.
For insert statements data service acts as in-only service. Errors are not 
returned back to client. At http://wso2.org/forum/404 i have read that was 
planned to implement error handling for insert statements. So is possible to 
handle insert errors?
Thx
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Unified way for a component to know when it should initialize/destroy

2010-09-17 Thread Supun Kamburugamuva 
I'm looking for way for a component to know when it has to initialize
and when it has to destroy?

At the moment we have two instances where a component should initialize.

1. Carbon initialization
2. Tenant initialization

But these two are two different cases. From a component perspective
they shouldn't know weather it is a system initialization or a tenant
initialization. It would be great to have a unified mechanism across
the platform for a component to decide when to initialize and when to
destroy.

Thanks,

-- 
Supun Kamburugamuva
Technical Lead
WSO2 Inc.;  http://wso2.org
E-mail: su...@wso2.com;  Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com

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

Re: [Carbon-dev] Next WSAS version from trunk

2010-09-17 Thread Ruwan Linton 

 On 9/17/10 12:02 PM, Senaka Fernando wrote:
+1. I believe that we need to change versions of other products as 
well. Ex:- G-Reg 3.6.0.

ESB and IS has been update with the move of the carbon version.

Ruwan


Thanks,
Senaka.

On Fri, Sep 17, 2010 at 12:00 PM, Samisa Abeysinghe > wrote:


+1

Samisa...


On Friday, September 17, 2010, Isuru Suriarachchi mailto:is...@wso2.com>> wrote:
> Hi all,
>
> WSAS trunk version is still 3.2.0-SNAPSHOT. I'm going to upgrade
it to 3.3.0-SNAPSHOT as I think the next WSAS release from trunk
should be 3.3.0. WDYT??..
>
> Thanks,
> ~Isuru
> --
> Isuru SuriarachchiTechnical Lead & Product Manager, WSO2 Web
Services Application Server
> WSO2 Inc. http://wso2.comemail : is...@wso2.com

> blog : http://isurues.wordpress.com/
> lean . enterprise . middleware
>
>

___
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



--
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] Multiple configuration management in ESB

2010-09-17 Thread Ruwan Linton 

 On 9/17/10 11:08 AM, Samisa Abeysinghe wrote:



On Fri, Sep 17, 2010 at 11:03 AM, Supun Kamburugamuva > wrote:


On Fri, Sep 17, 2010 at 10:52 AM, Samisa Abeysinghe
mailto:sam...@wso2.com>> wrote:
> Looks good.
> Can I make a copy an existing config and modify? The UI does not
show a copy
> option.

Actually this is something yet to be implemented. I would like to make
it a "Save as" option.


um..I think it is copy - not save as


>
> In add configuration, can I upload an existing XML config file?

Since our synapse configuration is a collection of files in a
directory, we may want to zip and upload. But this is not possible as
of now. With the current implementation if the files are in the
synapse configurations directory we can add them to the configurations
management.


OK, we need some solution to this problem. Because, like in the case 
of copy, people want to start with something existing and edit.


Even now it is possible, where you can create a new configuration and 
paste the content of the existing config into the new config edit area, 
but I agree uploading a configuration xml is also a valid case. We could 
support both .xml and .zip file uploads, and by looking at the file type 
distinguish the behavior.


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