Re: [Carbon-dev] Optional features in products

[Afkham Azeez]

Can the PMs please identify what are the optional features in their
respective products? Please reply ASAP to this thread.


On Mon, May 16, 2011 at 12:01 PM, Sameera Jayasoma  wrote:

> But we should not remove features in point releases. Users might get
> confused.  Hence we better remove them for this release.
>
> Sameera
>
>
> On Sat, May 14, 2011 at 9:19 PM, Samisa Abeysinghe wrote:
>
>> If we remove them now, it will go all unstable, We should do this for the
>> point release.
>>
>>
>> On Fri, May 13, 2011 at 10:01 PM, Afkham Azeez  wrote:
>>
>>> Folks,
>>> Some of the product have increased by about 50MB. One reason is because
>>> of duplicate jars that are embedded in bundles. The other could be because
>>> we are shipping rarely used features with some products. First of all, we
>>> need to go through all the bundles and eliminate duplicate jars. The other
>>> thing we could do is remove optional features. Those can be installed from
>>> the P2 repo anyway. Can the product teams please list down features you feel
>>> are optional?
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
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*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Afkham Azeez]

There is no issue here. I will see how this can be implemented. This will
address the situations where;

1. You need full control over the ports & define all ports
2. You just want to start some servers, and do not require full control over
the ports.

Azeez

On Mon, May 16, 2011 at 11:30 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 16, 2011 at 11:18 AM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> Yeah, but from the usability point of view also, scripting the server
>> startup wont be much of an user-friendly thing to do I guess,
>>
>
> You need to script the server startup only of you want to enforce some
> startup order. For most scenarios you don't need that. If you want to setup
> a simple DSS+ESB scenario on the same machine for a quick demo it doesn't
> matter which starts up first.
>
>
>> and IMHO, the dynamic port assignment is too unpredictable to be used in a
>> consistent manner, where if we use something similar to what I suggested, it
>> will either succeed or the server will fail to startup.
>
>
> If you need consistency then you can go through the trouble of setting
> distinct port numbers in config files. The solution suggested here is just a
> usability thing - to make the simple case simpler. If I want to try out a
> simple ESB cluster I don't care which one takes which port number.
>
>
>> Also, the extension mechanism as you mentioned won't be guaranteed to
>> support in every library we use :) ..
>>
>
> I agree this is a bit problematic. But we can always find a way.
>
> Thanks,
> Hiranya
>
>
> This
>
>
>>
>> Cheers,
>> Anjana.
>>
>>
>> On Mon, May 16, 2011 at 11:12 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> On Mon, May 16, 2011 at 11:05 AM, Anjana Fernando wrote:
>>>
 Hi,

 On Mon, May 16, 2011 at 10:48 AM, Hiranya Jayathilaka >>> > wrote:

>
>
> On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando wrote:
>
>> Hi Hiranya,
>>
>> On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi 
>>> wrote:
>>>


 On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez wrote:

> This will be a great usability enhancement. People will be able to
> startup multiple carbon servers without changing anything. Everything 
> will
> work OOTB.


 I think it depends on the requirement. For me most of the time I
 need to run an ESB, DSS, Rules in order to do some integration 
 testing. In
 this case ESB proxies should know the port addresses of the DSS, 
 Rules. So
 random port generation won't work for such senarios.

>>>
>>> Most of the time you will start up all the servers before start
>>> configuring stuff. So by the time you create the proxy, DSS will be up 
>>> and
>>> running and you will know the endpoint. We log these information at 
>>> startup
>>> and if needed it can be found from the management console as well.
>>>
>>
>> I'm not sure if everyone does that .. that is startup all the servers
>> before configuring, also another problem is, your approach will require 
>> to
>> start the servers in a specific order .. it's a first come-first served
>> approach as I see. So in the second time around, if you start the 
>> servers in
>> a different order, the server ports will be totally different.
>>
>
> Not a problem IMO. You can always script server start up to maintain
> order.
>
>
>>
>> Also, as for the common utils method you suggested for opening a
>> socket, this will require we always hack into the code that we use, for
>> example, Qpid code and LDAP server and so on, and if in the future, if we
>> have a dependency which we don't customise the code, like, if we just 
>> have
>> an orbit bundle which points to the official library directly, we can't
>> change the code.
>>
>
> This is a valid concern. But most products allow some level of
> extensions in this space. Axis2 has the concept of AxisConfigurator for an
> example.
>

 I think we are making things a bit complicated to do a simple thing :)
 ..

>>>
>>> Well, usability matters :)
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Cheers,
 Anjana.


>
> Thanks,
> Hiranya
>
>
>>
>> Cheers,
>> Anjana.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 thanks,
 Amila.

>
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez wrote:
>
>> In Tomcat, the following method is used when certain ports need to
>> be used;
>>
>> protected int bind(ServerSocket socket, int portstart, int
>> retries) throws IOException {
>> In

Re: [Carbon-dev] Optional features in products

[Sameera Jayasoma]

But we should not remove features in point releases. Users might get
confused.  Hence we better remove them for this release.

Sameera

On Sat, May 14, 2011 at 9:19 PM, Samisa Abeysinghe  wrote:

> If we remove them now, it will go all unstable, We should do this for the
> point release.
>
>
> On Fri, May 13, 2011 at 10:01 PM, Afkham Azeez  wrote:
>
>> Folks,
>> Some of the product have increased by about 50MB. One reason is because of
>> duplicate jars that are embedded in bundles. The other could be because we
>> are shipping rarely used features with some products. First of all, we need
>> to go through all the bundles and eliminate duplicate jars. The other thing
>> we could do is remove optional features. Those can be installed from the P2
>> repo anyway. Can the product teams please list down features you feel are
>> optional?
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

On Mon, May 16, 2011 at 11:18 AM, Anjana Fernando  wrote:

> Hi,
>
> Yeah, but from the usability point of view also, scripting the server
> startup wont be much of an user-friendly thing to do I guess,


You need to script the server startup only of you want to enforce some
startup order. For most scenarios you don't need that. If you want to setup
a simple DSS+ESB scenario on the same machine for a quick demo it doesn't
matter which starts up first.


> and IMHO, the dynamic port assignment is too unpredictable to be used in a
> consistent manner, where if we use something similar to what I suggested, it
> will either succeed or the server will fail to startup.


If you need consistency then you can go through the trouble of setting
distinct port numbers in config files. The solution suggested here is just a
usability thing - to make the simple case simpler. If I want to try out a
simple ESB cluster I don't care which one takes which port number.


> Also, the extension mechanism as you mentioned won't be guaranteed to
> support in every library we use :) ..
>

I agree this is a bit problematic. But we can always find a way.

Thanks,
Hiranya


This


>
> Cheers,
> Anjana.
>
>
> On Mon, May 16, 2011 at 11:12 AM, Hiranya Jayathilaka wrote:
>
>> Hi,
>>
>> On Mon, May 16, 2011 at 11:05 AM, Anjana Fernando wrote:
>>
>>> Hi,
>>>
>>> On Mon, May 16, 2011 at 10:48 AM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando wrote:

> Hi Hiranya,
>
> On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi 
>> wrote:
>>
>>>
>>>
>>> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez wrote:
>>>
 This will be a great usability enhancement. People will be able to
 startup multiple carbon servers without changing anything. Everything 
 will
 work OOTB.
>>>
>>>
>>> I think it depends on the requirement. For me most of the time I need
>>> to run an ESB, DSS, Rules in order to do some integration testing. In 
>>> this
>>> case ESB proxies should know the port addresses of the DSS, Rules. So 
>>> random
>>> port generation won't work for such senarios.
>>>
>>
>> Most of the time you will start up all the servers before start
>> configuring stuff. So by the time you create the proxy, DSS will be up 
>> and
>> running and you will know the endpoint. We log these information at 
>> startup
>> and if needed it can be found from the management console as well.
>>
>
> I'm not sure if everyone does that .. that is startup all the servers
> before configuring, also another problem is, your approach will require to
> start the servers in a specific order .. it's a first come-first served
> approach as I see. So in the second time around, if you start the servers 
> in
> a different order, the server ports will be totally different.
>

 Not a problem IMO. You can always script server start up to maintain
 order.


>
> Also, as for the common utils method you suggested for opening a
> socket, this will require we always hack into the code that we use, for
> example, Qpid code and LDAP server and so on, and if in the future, if we
> have a dependency which we don't customise the code, like, if we just have
> an orbit bundle which points to the official library directly, we can't
> change the code.
>

 This is a valid concern. But most products allow some level of
 extensions in this space. Axis2 has the concept of AxisConfigurator for an
 example.

>>>
>>> I think we are making things a bit complicated to do a simple thing :) ..
>>>
>>
>> Well, usability matters :)
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>>

 Thanks,
 Hiranya


>
> Cheers,
> Anjana.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> thanks,
>>> Amila.
>>>


 On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez wrote:

> In Tomcat, the following method is used when certain ports need to
> be used;
>
> protected int bind(ServerSocket socket, int portstart, int retries)
> throws IOException {
> InetSocketAddress addr = null;
> while ( retries > 0 ) {
> try {
> addr = new InetSocketAddress(getBind(), portstart);
> socket.bind(addr);
> setPort(portstart);
> log.info("Receiver Server Socket bound to:"+addr);
> return 0;
> }catch ( IOException x) {
> retries--;
> if ( retries <= 0 ) {
> log

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Anjana Fernando]

Hi,

Yeah, but from the usability point of view also, scripting the server
startup wont be much of an user-friendly thing to do I guess, and IMHO, the
dynamic port assignment is too unpredictable to be used in a consistent
manner, where if we use something similar to what I suggested, it will
either succeed or the server will fail to startup. Also, the extension
mechanism as you mentioned won't be guaranteed to support in every library
we use :) ..

Cheers,
Anjana.

On Mon, May 16, 2011 at 11:12 AM, Hiranya Jayathilaka wrote:

> Hi,
>
> On Mon, May 16, 2011 at 11:05 AM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> On Mon, May 16, 2011 at 10:48 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>>
>>>
>>> On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando wrote:
>>>
 Hi Hiranya,

 On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez wrote:
>>
>>> This will be a great usability enhancement. People will be able to
>>> startup multiple carbon servers without changing anything. Everything 
>>> will
>>> work OOTB.
>>
>>
>> I think it depends on the requirement. For me most of the time I need
>> to run an ESB, DSS, Rules in order to do some integration testing. In 
>> this
>> case ESB proxies should know the port addresses of the DSS, Rules. So 
>> random
>> port generation won't work for such senarios.
>>
>
> Most of the time you will start up all the servers before start
> configuring stuff. So by the time you create the proxy, DSS will be up and
> running and you will know the endpoint. We log these information at 
> startup
> and if needed it can be found from the management console as well.
>

 I'm not sure if everyone does that .. that is startup all the servers
 before configuring, also another problem is, your approach will require to
 start the servers in a specific order .. it's a first come-first served
 approach as I see. So in the second time around, if you start the servers 
 in
 a different order, the server ports will be totally different.

>>>
>>> Not a problem IMO. You can always script server start up to maintain
>>> order.
>>>
>>>

 Also, as for the common utils method you suggested for opening a socket,
 this will require we always hack into the code that we use, for example,
 Qpid code and LDAP server and so on, and if in the future, if we have a
 dependency which we don't customise the code, like, if we just have an 
 orbit
 bundle which points to the official library directly, we can't change the
 code.

>>>
>>> This is a valid concern. But most products allow some level of extensions
>>> in this space. Axis2 has the concept of AxisConfigurator for an example.
>>>
>>
>> I think we are making things a bit complicated to do a simple thing :) ..
>>
>
> Well, usability matters :)
>
> Thanks,
> Hiranya
>
>
>>
>> Cheers,
>> Anjana.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Cheers,
 Anjana.


>
> Thanks,
> Hiranya
>
>
>>
>> thanks,
>> Amila.
>>
>>>
>>>
>>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez wrote:
>>>
 In Tomcat, the following method is used when certain ports need to
 be used;

 protected int bind(ServerSocket socket, int portstart, int retries)
 throws IOException {
 InetSocketAddress addr = null;
 while ( retries > 0 ) {
 try {
 addr = new InetSocketAddress(getBind(), portstart);
 socket.bind(addr);
 setPort(portstart);
 log.info("Receiver Server Socket bound to:"+addr);
 return 0;
 }catch ( IOException x) {
 retries--;
 if ( retries <= 0 ) {
 log.info("Unable to bind server socket
 to:"+addr+" throwing error.");
 throw x;
 }
 portstart++;
 try {Thread.sleep(25);}catch( InterruptedException
 ti){Thread.interrupted();}
 retries = bind(socket,portstart,retries);
 }
 }
 return retries;
 }

 We can provide such a util method and whoever wants to open ports,
 can request for a port from that util method.


 On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

> 1. Change the HTTP/S ports in mgt-transports.xml (2)
> 2. Change the HTTP/S ports in axis2.xml (2)
> 3. Change the LDAP ports in c

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

Hi,

On Mon, May 16, 2011 at 11:05 AM, Anjana Fernando  wrote:

> Hi,
>
> On Mon, May 16, 2011 at 10:48 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando wrote:
>>
>>> Hi Hiranya,
>>>
>>> On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:

>
>
> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>
>> This will be a great usability enhancement. People will be able to
>> startup multiple carbon servers without changing anything. Everything 
>> will
>> work OOTB.
>
>
> I think it depends on the requirement. For me most of the time I need
> to run an ESB, DSS, Rules in order to do some integration testing. In this
> case ESB proxies should know the port addresses of the DSS, Rules. So 
> random
> port generation won't work for such senarios.
>

 Most of the time you will start up all the servers before start
 configuring stuff. So by the time you create the proxy, DSS will be up and
 running and you will know the endpoint. We log these information at startup
 and if needed it can be found from the management console as well.

>>>
>>> I'm not sure if everyone does that .. that is startup all the servers
>>> before configuring, also another problem is, your approach will require to
>>> start the servers in a specific order .. it's a first come-first served
>>> approach as I see. So in the second time around, if you start the servers in
>>> a different order, the server ports will be totally different.
>>>
>>
>> Not a problem IMO. You can always script server start up to maintain
>> order.
>>
>>
>>>
>>> Also, as for the common utils method you suggested for opening a socket,
>>> this will require we always hack into the code that we use, for example,
>>> Qpid code and LDAP server and so on, and if in the future, if we have a
>>> dependency which we don't customise the code, like, if we just have an orbit
>>> bundle which points to the official library directly, we can't change the
>>> code.
>>>
>>
>> This is a valid concern. But most products allow some level of extensions
>> in this space. Axis2 has the concept of AxisConfigurator for an example.
>>
>
> I think we are making things a bit complicated to do a simple thing :) ..
>

Well, usability matters :)

Thanks,
Hiranya


>
> Cheers,
> Anjana.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>>

 Thanks,
 Hiranya


>
> thanks,
> Amila.
>
>>
>>
>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez wrote:
>>
>>> In Tomcat, the following method is used when certain ports need to be
>>> used;
>>>
>>> protected int bind(ServerSocket socket, int portstart, int retries)
>>> throws IOException {
>>> InetSocketAddress addr = null;
>>> while ( retries > 0 ) {
>>> try {
>>> addr = new InetSocketAddress(getBind(), portstart);
>>> socket.bind(addr);
>>> setPort(portstart);
>>> log.info("Receiver Server Socket bound to:"+addr);
>>> return 0;
>>> }catch ( IOException x) {
>>> retries--;
>>> if ( retries <= 0 ) {
>>> log.info("Unable to bind server socket
>>> to:"+addr+" throwing error.");
>>> throw x;
>>> }
>>> portstart++;
>>> try {Thread.sleep(25);}catch( InterruptedException
>>> ti){Thread.interrupted();}
>>> retries = bind(socket,portstart,retries);
>>> }
>>> }
>>> return retries;
>>> }
>>>
>>> We can provide such a util method and whoever wants to open ports,
>>> can request for a port from that util method.
>>>
>>>
>>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>
 1. Change the HTTP/S ports in mgt-transports.xml (2)
 2. Change the HTTP/S ports in axis2.xml (2)
 3. Change the LDAP ports in carbon.xml (2)
 4. Change the Qpid ports in carbon.xml (2)
 5. Change the JMX ports in advanced/jmx.xml (2)

 Total 10 ports to change :(


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Anjana Fernando]

Hi,

On Mon, May 16, 2011 at 10:48 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando  wrote:
>
>> Hi Hiranya,
>>
>> On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:
>>>


 On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:

> This will be a great usability enhancement. People will be able to
> startup multiple carbon servers without changing anything. Everything will
> work OOTB.


 I think it depends on the requirement. For me most of the time I need to
 run an ESB, DSS, Rules in order to do some integration testing. In this 
 case
 ESB proxies should know the port addresses of the DSS, Rules. So random 
 port
 generation won't work for such senarios.

>>>
>>> Most of the time you will start up all the servers before start
>>> configuring stuff. So by the time you create the proxy, DSS will be up and
>>> running and you will know the endpoint. We log these information at startup
>>> and if needed it can be found from the management console as well.
>>>
>>
>> I'm not sure if everyone does that .. that is startup all the servers
>> before configuring, also another problem is, your approach will require to
>> start the servers in a specific order .. it's a first come-first served
>> approach as I see. So in the second time around, if you start the servers in
>> a different order, the server ports will be totally different.
>>
>
> Not a problem IMO. You can always script server start up to maintain order.
>
>
>>
>> Also, as for the common utils method you suggested for opening a socket,
>> this will require we always hack into the code that we use, for example,
>> Qpid code and LDAP server and so on, and if in the future, if we have a
>> dependency which we don't customise the code, like, if we just have an orbit
>> bundle which points to the official library directly, we can't change the
>> code.
>>
>
> This is a valid concern. But most products allow some level of extensions
> in this space. Axis2 has the concept of AxisConfigurator for an example.
>

I think we are making things a bit complicated to do a simple thing :) ..

Cheers,
Anjana.


>
> Thanks,
> Hiranya
>
>
>>
>> Cheers,
>> Anjana.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 thanks,
 Amila.

>
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries)
>> throws IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket
>> to:"+addr+" throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http:/

Re: [Carbon-dev] WSDL Validator tool

[Harshana Martin]

Hi Jorge,

WSDL validation is basically used for the following things [1].

1. Check the WSDL document for XML well formedness. (That is, ensure all
tags are properly nested and closed.)
2. Validate the WSDL document against its XML schema.
3. Validate the WSDL document using semantic rules defined in the WSDL
specification.
4. Validate the WSDL document against custom validation rules, such as those
defined by the Web Services Interoperability (WS-I) organization. [Optional]

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

Hope this helps!

Thanks and Regards,
Harshana

On Mon, May 16, 2011 at 1:25 AM, Jorge Infante Osorio wrote:

> Hi all.
> The $subject validate again what? In the documentation I can find this
> information.
>
> The wsdl generates in WSAS 3.2.1 came with problem in the HTTP binding and
> was validated: “WSDL DOCUMENT IS VALID” in AppServer 4.0.
>
> Thanks,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> UCI
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Harshana Martin
Software Engineer
WSO2 Inc.
Web:http://wso2.com
  http://wso2.org

Mobile: +94 716062650
Blog: http://harshana05.blogspot.com
Profile: https://www.google.com/profiles/harshana05
Twitter: http://twitter.com/harshana05
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

On Mon, May 16, 2011 at 10:40 AM, Anjana Fernando  wrote:

> Hi Hiranya,
>
> On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>>>
 This will be a great usability enhancement. People will be able to
 startup multiple carbon servers without changing anything. Everything will
 work OOTB.
>>>
>>>
>>> I think it depends on the requirement. For me most of the time I need to
>>> run an ESB, DSS, Rules in order to do some integration testing. In this case
>>> ESB proxies should know the port addresses of the DSS, Rules. So random port
>>> generation won't work for such senarios.
>>>
>>
>> Most of the time you will start up all the servers before start
>> configuring stuff. So by the time you create the proxy, DSS will be up and
>> running and you will know the endpoint. We log these information at startup
>> and if needed it can be found from the management console as well.
>>
>
> I'm not sure if everyone does that .. that is startup all the servers
> before configuring, also another problem is, your approach will require to
> start the servers in a specific order .. it's a first come-first served
> approach as I see. So in the second time around, if you start the servers in
> a different order, the server ports will be totally different.
>

Not a problem IMO. You can always script server start up to maintain order.


>
> Also, as for the common utils method you suggested for opening a socket,
> this will require we always hack into the code that we use, for example,
> Qpid code and LDAP server and so on, and if in the future, if we have a
> dependency which we don't customise the code, like, if we just have an orbit
> bundle which points to the official library directly, we can't change the
> code.
>

This is a valid concern. But most products allow some level of extensions in
this space. Axis2 has the concept of AxisConfigurator for an example.

Thanks,
Hiranya


>
> Cheers,
> Anjana.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> thanks,
>>> Amila.
>>>


 On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:

> In Tomcat, the following method is used when certain ports need to be
> used;
>
> protected int bind(ServerSocket socket, int portstart, int retries)
> throws IOException {
> InetSocketAddress addr = null;
> while ( retries > 0 ) {
> try {
> addr = new InetSocketAddress(getBind(), portstart);
> socket.bind(addr);
> setPort(portstart);
> log.info("Receiver Server Socket bound to:"+addr);
> return 0;
> }catch ( IOException x) {
> retries--;
> if ( retries <= 0 ) {
> log.info("Unable to bind server socket to:"+addr+"
> throwing error.");
> throw x;
> }
> portstart++;
> try {Thread.sleep(25);}catch( InterruptedException
> ti){Thread.interrupted();}
> retries = bind(socket,portstart,retries);
> }
> }
> return retries;
> }
>
> We can provide such a util method and whoever wants to open ports, can
> request for a port from that util method.
>
>
> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka  > wrote:
>
>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>> 2. Change the HTTP/S ports in axis2.xml (2)
>> 3. Change the LDAP ports in carbon.xml (2)
>> 4. Change the Qpid ports in carbon.xml (2)
>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>
>> Total 10 ports to change :(
>>
>>
>> --
>> 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
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache

Re: [Carbon-dev] Context root disappearing in Websphere

[Danushka Menikkumbura]

This should be a Carbon-core level fix right?.

Danushka

On Mon, May 16, 2011 at 3:16 AM, Ranga Siriwardena  wrote:

> Hi all,
>
> I was able to reproduce the issue for GS. Will work with Milinda to sorted
> out the issue.
>
> Thanks.
>
> On Thu, May 12, 2011 at 3:38 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi all,
>>
>> The same issue [1] has been raised sometime back and it has been resolved
>> without doing a proper fix.
>>
>> Thanks
>> Krishantha
>>
>> [1] https://wso2.org/jira/browse/CARBON-7371
>>
>>
>> On Thu, May 12, 2011 at 2:21 PM, Nuwan Bandara  wrote:
>>
>>> Surprisingly this does not happen in other app servers (Tomcat etc),
>>> according to pradeep he has seen this when there are relative URLs, But
>>> there are many places in our UI bundles that we do redirection to relative
>>> URLs.
>>>
>>> Regards,
>>> /Nuwan
>>>
>>>
>>> On Thu, May 12, 2011 at 2:15 PM, Milinda Pathirage wrote:
>>>
 This could be due to recent changes we done to facilitate custom home
 page URLs. Will look into this.

 Thanks
 Milinda

 On Thu, May 12, 2011 at 1:56 PM, Chamara Ariyarathne >>> > wrote:

> Following are the places which Browser redirect with wrong context root
> when server deployed in Websphere. I'm sending this for the request made 
> by
> Pradeep and Nuwan, and according to the offline chat I had with them, 
> there
> will be a similar solution for this.
>
> *Mashup Server;*
> Home button
> Upload Module; Modules -> Add Modules -> Upoload
> Upload JavaScript services -> Upload
> *
> Gadget Server;*
> Add Gadgets
>
>
> *Chamara Ariyarathne*
> Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *0772786766*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 Milinda Pathirage
 Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
 http://wso2.com
 Blog: http://blog.mpathirage.com

 Lean Enterprise Middleware

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


>>>
>>>
>>> --
>>> *Thanks & Regards,
>>>
>>> Nuwan Bandara
>>> Senior Software Engineer
>>>
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> http://nuwan.bandara.co
>>> *
>>> 
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> Blog: http://rangasiriwardena.blogspot.com/
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Anjana Fernando]

Hi Hiranya,

On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>>
>>> This will be a great usability enhancement. People will be able to
>>> startup multiple carbon servers without changing anything. Everything will
>>> work OOTB.
>>
>>
>> I think it depends on the requirement. For me most of the time I need to
>> run an ESB, DSS, Rules in order to do some integration testing. In this case
>> ESB proxies should know the port addresses of the DSS, Rules. So random port
>> generation won't work for such senarios.
>>
>
> Most of the time you will start up all the servers before start configuring
> stuff. So by the time you create the proxy, DSS will be up and running and
> you will know the endpoint. We log these information at startup and if
> needed it can be found from the management console as well.
>

I'm not sure if everyone does that .. that is startup all the servers before
configuring, also another problem is, your approach will require to start
the servers in a specific order .. it's a first come-first served approach
as I see. So in the second time around, if you start the servers in a
different order, the server ports will be totally different.

Also, as for the common utils method you suggested for opening a socket,
this will require we always hack into the code that we use, for example,
Qpid code and LDAP server and so on, and if in the future, if we have a
dependency which we don't customise the code, like, if we just have an orbit
bundle which points to the official library directly, we can't change the
code.

Cheers,
Anjana.


>
> Thanks,
> Hiranya
>
>
>>
>> thanks,
>> Amila.
>>
>>>
>>>
>>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>>>
 In Tomcat, the following method is used when certain ports need to be
 used;

 protected int bind(ServerSocket socket, int portstart, int retries)
 throws IOException {
 InetSocketAddress addr = null;
 while ( retries > 0 ) {
 try {
 addr = new InetSocketAddress(getBind(), portstart);
 socket.bind(addr);
 setPort(portstart);
 log.info("Receiver Server Socket bound to:"+addr);
 return 0;
 }catch ( IOException x) {
 retries--;
 if ( retries <= 0 ) {
 log.info("Unable to bind server socket to:"+addr+"
 throwing error.");
 throw x;
 }
 portstart++;
 try {Thread.sleep(25);}catch( InterruptedException
 ti){Thread.interrupted();}
 retries = bind(socket,portstart,retries);
 }
 }
 return retries;
 }

 We can provide such a util method and whoever wants to open ports, can
 request for a port from that util method.


 On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka 
 wrote:

> 1. Change the HTTP/S ports in mgt-transports.xml (2)
> 2. Change the HTTP/S ports in axis2.xml (2)
> 3. Change the LDAP ports in carbon.xml (2)
> 4. Change the Qpid ports in carbon.xml (2)
> 5. Change the JMX ports in advanced/jmx.xml (2)
>
> Total 10 ports to change :(
>
>
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 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*
 *
 *
 *Lean . Enterprise . Middleware*


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Amila Suriarachchi]

On Mon, May 16, 2011 at 9:51 AM, Hiranya Jayathilaka wrote:

>
>
> On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>>
>>> This will be a great usability enhancement. People will be able to
>>> startup multiple carbon servers without changing anything. Everything will
>>> work OOTB.
>>
>>
>> I think it depends on the requirement. For me most of the time I need to
>> run an ESB, DSS, Rules in order to do some integration testing. In this case
>> ESB proxies should know the port addresses of the DSS, Rules. So random port
>> generation won't work for such senarios.
>>
>
> Most of the time you will start up all the servers before start configuring
> stuff. So by the time you create the proxy, DSS will be up and running and
> you will know the endpoint. We log these information at startup and if
> needed it can be found from the management console as well.
>

Then you need to change the proxy service end point port. if there are 10
endpoints 10 places.

yes, there is no perfect solution for this problem. I prefer offset option
since that is what I was doing by changing two ports with earlier versions.

thanks,
Amila.



>
> Thanks,
> Hiranya
>
>
>>
>> thanks,
>> Amila.
>>
>>>
>>>
>>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>>>
 In Tomcat, the following method is used when certain ports need to be
 used;

 protected int bind(ServerSocket socket, int portstart, int retries)
 throws IOException {
 InetSocketAddress addr = null;
 while ( retries > 0 ) {
 try {
 addr = new InetSocketAddress(getBind(), portstart);
 socket.bind(addr);
 setPort(portstart);
 log.info("Receiver Server Socket bound to:"+addr);
 return 0;
 }catch ( IOException x) {
 retries--;
 if ( retries <= 0 ) {
 log.info("Unable to bind server socket to:"+addr+"
 throwing error.");
 throw x;
 }
 portstart++;
 try {Thread.sleep(25);}catch( InterruptedException
 ti){Thread.interrupted();}
 retries = bind(socket,portstart,retries);
 }
 }
 return retries;
 }

 We can provide such a util method and whoever wants to open ports, can
 request for a port from that util method.


 On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka 
 wrote:

> 1. Change the HTTP/S ports in mgt-transports.xml (2)
> 2. Change the HTTP/S ports in axis2.xml (2)
> 3. Change the LDAP ports in carbon.xml (2)
> 4. Change the Qpid ports in carbon.xml (2)
> 5. Change the JMX ports in advanced/jmx.xml (2)
>
> Total 10 ports to change :(
>
>
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 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*
 *
 *
 *Lean . Enterprise . Middleware*


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://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
> 

Re: [Carbon-dev] XACML 2.0 Conformance Tests

[Pavithra Madurangi]

I tested  some scenarios found in XACML 2.0 confirmation test suite and
reported the issue found. But I could not complete the whole test suite.

Regards,
Pavithra

On Mon, May 16, 2011 at 10:04 AM, Asela Pathberiya  wrote:

>
>
> On Mon, May 16, 2011 at 9:59 AM, Prabath Siriwardena wrote:
>
>> I guess we need to have this for 3.2.0 release.. and fix any
>> non-conformance...
>>
>> Asela, do you have any cycles to work on this...?
>>
>
> Sure.. will look into it...
>
> Thanks,
> Asela.
>
>>
>> Thanks & regards,
>> -Prabath
>>
>> On Tue, Mar 1, 2011 at 1:46 PM, Prabath Siriwardana 
>> wrote:
>> >
>> >
>> > On Tue, Mar 1, 2011 at 1:40 PM, Afkham Azeez  wrote:
>> >>
>> >> Why can't these cases go into the IS product in the Carbon trunk? We
>> have
>> >> plans to move the test framework into the mainstream codebase anyway.
>> >
>> > +1
>> > Thanks & regards,
>> > -Prabath
>> >>
>> >> On Tue, Mar 1, 2011 at 10:47 AM, Charitha Kankanamge <
>> chari...@wso2.com>
>> >> wrote:
>> >>>
>> >>> Hi Prabath,
>> >>>
>> >>> This will be included in IS admin test framework which will be
>> commenced
>> >>> soon.
>> >>>
>> >>> Regards
>> >>> Charitha
>> >>>
>> >>> On Tue, Mar 1, 2011 at 9:47 AM, Prabath Siriwardana > >
>> >>> wrote:
>> 
>>  Great..! Also I guess we can easily automate these tests. The
>>  confirmation test suite comes with a set of predefined requests and
>>  responses in XML. IS XACML engine has an admin service API which
>> accepts the
>>  requests and returns back the response. So lets try to automate
>> this...
>>  Thanks & regards,
>>  -Prabath
>> 
>>  On Tue, Mar 1, 2011 at 9:43 AM, Pavithra Madurangi <
>> pavit...@wso2.com>
>>  wrote:
>> >
>> > Hi Prabath,
>> >
>> > Added them to IS test cases.
>> >
>> > Regards,
>> > Pavithra
>> >
>> > On Mon, Feb 28, 2011 at 10:33 PM, Prabath Siriwardana
>> >  wrote:
>> >>
>> >> Hi Charitha,
>> >> Please add [1] to the IS test cases...
>> >> --
>> >> Thanks & Regards,
>> >> Prabath
>> >>
>> >> [1]:
>> http://www.oasis-open.org/committees/download.php/14846/xacml2.0-ct-v.0.4.zip
>> >> [2]: https://wso2.org/jira/browse/CARBON-6861
>> >>
>> >> http://blog.facilelogin.com
>> >> http://RampartFAQ.com
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>
>> >
>> 
>> 
>> 
>>  --
>>  Thanks & Regards,
>>  Prabath
>> 
>>  http://blog.facilelogin.com
>>  http://RampartFAQ.com
>> 
>>  ___
>>  Carbon-dev mailing list
>>  Carbon-dev@wso2.org
>>  http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> 
>> >>>
>> >>>
>> >>> ___
>> >>> Carbon-dev mailing list
>> >>> Carbon-dev@wso2.org
>> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Afkham Azeez
>> >> Senior Software Architect & Senior Manager; WSO2, Inc.;
>> http://wso2.com,
>> >>
>> >> 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
>> >>
>> >> Lean . Enterprise . Middleware
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Thanks & Regards,
>> > Prabath
>> >
>> > http://blog.facilelogin.com
>> > http://RampartFAQ.com
>> >
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] XACML 2.0 Conformance Tests

[Asela Pathberiya]

On Mon, May 16, 2011 at 9:59 AM, Prabath Siriwardena wrote:

> I guess we need to have this for 3.2.0 release.. and fix any
> non-conformance...
>
> Asela, do you have any cycles to work on this...?
>

Sure.. will look into it...

Thanks,
Asela.

>
> Thanks & regards,
> -Prabath
>
> On Tue, Mar 1, 2011 at 1:46 PM, Prabath Siriwardana 
> wrote:
> >
> >
> > On Tue, Mar 1, 2011 at 1:40 PM, Afkham Azeez  wrote:
> >>
> >> Why can't these cases go into the IS product in the Carbon trunk? We
> have
> >> plans to move the test framework into the mainstream codebase anyway.
> >
> > +1
> > Thanks & regards,
> > -Prabath
> >>
> >> On Tue, Mar 1, 2011 at 10:47 AM, Charitha Kankanamge  >
> >> wrote:
> >>>
> >>> Hi Prabath,
> >>>
> >>> This will be included in IS admin test framework which will be
> commenced
> >>> soon.
> >>>
> >>> Regards
> >>> Charitha
> >>>
> >>> On Tue, Mar 1, 2011 at 9:47 AM, Prabath Siriwardana 
> >>> wrote:
> 
>  Great..! Also I guess we can easily automate these tests. The
>  confirmation test suite comes with a set of predefined requests and
>  responses in XML. IS XACML engine has an admin service API which
> accepts the
>  requests and returns back the response. So lets try to automate
> this...
>  Thanks & regards,
>  -Prabath
> 
>  On Tue, Mar 1, 2011 at 9:43 AM, Pavithra Madurangi  >
>  wrote:
> >
> > Hi Prabath,
> >
> > Added them to IS test cases.
> >
> > Regards,
> > Pavithra
> >
> > On Mon, Feb 28, 2011 at 10:33 PM, Prabath Siriwardana
> >  wrote:
> >>
> >> Hi Charitha,
> >> Please add [1] to the IS test cases...
> >> --
> >> Thanks & Regards,
> >> Prabath
> >>
> >> [1]:
> http://www.oasis-open.org/committees/download.php/14846/xacml2.0-ct-v.0.4.zip
> >> [2]: https://wso2.org/jira/browse/CARBON-6861
> >>
> >> http://blog.facilelogin.com
> >> http://RampartFAQ.com
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
> 
> 
> 
>  --
>  Thanks & Regards,
>  Prabath
> 
>  http://blog.facilelogin.com
>  http://RampartFAQ.com
> 
>  ___
>  Carbon-dev mailing list
>  Carbon-dev@wso2.org
>  http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> 
> >>>
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Afkham Azeez
> >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
> ,
> >>
> >> 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
> >>
> >> Lean . Enterprise . Middleware
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
> >
> >
> > --
> > Thanks & Regards,
> > Prabath
> >
> > http://blog.facilelogin.com
> > http://RampartFAQ.com
> >
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] XACML 2.0 Conformance Tests

[Prabath Siriwardena]

I guess we need to have this for 3.2.0 release.. and fix any non-conformance...

Asela, do you have any cycles to work on this...?

Thanks & regards,
-Prabath

On Tue, Mar 1, 2011 at 1:46 PM, Prabath Siriwardana  wrote:
>
>
> On Tue, Mar 1, 2011 at 1:40 PM, Afkham Azeez  wrote:
>>
>> Why can't these cases go into the IS product in the Carbon trunk? We have
>> plans to move the test framework into the mainstream codebase anyway.
>
> +1
> Thanks & regards,
> -Prabath
>>
>> On Tue, Mar 1, 2011 at 10:47 AM, Charitha Kankanamge 
>> wrote:
>>>
>>> Hi Prabath,
>>>
>>> This will be included in IS admin test framework which will be commenced
>>> soon.
>>>
>>> Regards
>>> Charitha
>>>
>>> On Tue, Mar 1, 2011 at 9:47 AM, Prabath Siriwardana 
>>> wrote:

 Great..! Also I guess we can easily automate these tests. The
 confirmation test suite comes with a set of predefined requests and
 responses in XML. IS XACML engine has an admin service API which accepts 
 the
 requests and returns back the response. So lets try to automate this...
 Thanks & regards,
 -Prabath

 On Tue, Mar 1, 2011 at 9:43 AM, Pavithra Madurangi 
 wrote:
>
> Hi Prabath,
>
> Added them to IS test cases.
>
> Regards,
> Pavithra
>
> On Mon, Feb 28, 2011 at 10:33 PM, Prabath Siriwardana
>  wrote:
>>
>> Hi Charitha,
>> Please add [1] to the IS test cases...
>> --
>> Thanks & Regards,
>> Prabath
>>
>> [1]: http://www.oasis-open.org/committees/download.php/14846/xacml2.0-ct-v.0.4.zip
>> [2]: https://wso2.org/jira/browse/CARBON-6861
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>



 --
 Thanks & Regards,
 Prabath

 http://blog.facilelogin.com
 http://RampartFAQ.com

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

>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> 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
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Thanks & Regards,
Prabath

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

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

On Mon, May 16, 2011 at 7:33 AM, Amila Suriarachchi  wrote:

>
>
> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>
>> This will be a great usability enhancement. People will be able to startup
>> multiple carbon servers without changing anything. Everything will work
>> OOTB.
>
>
> I think it depends on the requirement. For me most of the time I need to
> run an ESB, DSS, Rules in order to do some integration testing. In this case
> ESB proxies should know the port addresses of the DSS, Rules. So random port
> generation won't work for such senarios.
>

Most of the time you will start up all the servers before start configuring
stuff. So by the time you create the proxy, DSS will be up and running and
you will know the endpoint. We log these information at startup and if
needed it can be found from the management console as well.

Thanks,
Hiranya


>
> thanks,
> Amila.
>
>>
>>
>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>>
>>> In Tomcat, the following method is used when certain ports need to be
>>> used;
>>>
>>> protected int bind(ServerSocket socket, int portstart, int retries)
>>> throws IOException {
>>> InetSocketAddress addr = null;
>>> while ( retries > 0 ) {
>>> try {
>>> addr = new InetSocketAddress(getBind(), portstart);
>>> socket.bind(addr);
>>> setPort(portstart);
>>> log.info("Receiver Server Socket bound to:"+addr);
>>> return 0;
>>> }catch ( IOException x) {
>>> retries--;
>>> if ( retries <= 0 ) {
>>> log.info("Unable to bind server socket to:"+addr+"
>>> throwing error.");
>>> throw x;
>>> }
>>> portstart++;
>>> try {Thread.sleep(25);}catch( InterruptedException
>>> ti){Thread.interrupted();}
>>> retries = bind(socket,portstart,retries);
>>> }
>>> }
>>> return retries;
>>> }
>>>
>>> We can provide such a util method and whoever wants to open ports, can
>>> request for a port from that util method.
>>>
>>>
>>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
 1. Change the HTTP/S ports in mgt-transports.xml (2)
 2. Change the HTTP/S ports in axis2.xml (2)
 3. Change the LDAP ports in carbon.xml (2)
 4. Change the Qpid ports in carbon.xml (2)
 5. Change the JMX ports in advanced/jmx.xml (2)

 Total 10 ports to change :(


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

On Mon, May 16, 2011 at 8:33 AM, Anjana Fernando  wrote:

> Hi,
>
> Doesn't that means, that type of a code should be in all the places we open
> a socket? .. is that practical?


If it is implemented as a common util method then it's practical. We still
need to do some work to call the method from different components though.


> .. Also, how about if we provide a simple configuration parameter which
> says, an offset from the base ports, like the default is 0, then you can
> increment it, for example in one server it will be 1, so internally we can
> change the default HTTP/HTTPS ports from 9763/9443 to 9764/9444 and so on.
>

IMO this is not very user friendly. This way user should define the offset
for each and every server. Instead server should pick the port on its own
when the specified port is not available. Only user defined option should be
to turn off this behavior when not necessary.

Thanks,
Hiranya


>
> Cheers,
> Anjana.
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries) throws
>> IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket to:"+addr+"
>> throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] exposeServiceMetadata parameter missing in axis2.xml ships with ESB [trunk]

[Prabath Siriwardena]

$subject

-- 
Thanks & Regards,
Prabath

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

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Amila Suriarachchi]

On Mon, May 16, 2011 at 8:33 AM, Anjana Fernando  wrote:

> Hi,
>
> Doesn't that means, that type of a code should be in all the places we open
> a socket? .. is that practical? .. Also, how about if we provide a simple
> configuration parameter which says, an offset from the base ports, like the
> default is 0, then you can increment it, for example in one server it will
> be 1, so internally we can change the default HTTP/HTTPS ports from
> 9763/9443 to 9764/9444 and so on.
>

+1.

thanks,
Amila.

>
> Cheers,
> Anjana.
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries) throws
>> IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket to:"+addr+"
>> throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Afkham Azeez]

This doesn't mean the server always generates random ports. You can still
specify ports, and another port will be picked only if the port you
specified is unavailable.
On May 16, 2011 7:33 AM, "Amila Suriarachchi"  wrote:
> On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:
>
>> This will be a great usability enhancement. People will be able to
startup
>> multiple carbon servers without changing anything. Everything will work
>> OOTB.
>
>
> I think it depends on the requirement. For me most of the time I need to
run
> an ESB, DSS, Rules in order to do some integration testing. In this case
ESB
> proxies should know the port addresses of the DSS, Rules. So random port
> generation won't work for such senarios.
>
> thanks,
> Amila.
>
>>
>>
>> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>>
>>> In Tomcat, the following method is used when certain ports need to be
>>> used;
>>>
>>> protected int bind(ServerSocket socket, int portstart, int retries)
throws
>>> IOException {
>>> InetSocketAddress addr = null;
>>> while ( retries > 0 ) {
>>> try {
>>> addr = new InetSocketAddress(getBind(), portstart);
>>> socket.bind(addr);
>>> setPort(portstart);
>>> log.info("Receiver Server Socket bound to:"+addr);
>>> return 0;
>>> }catch ( IOException x) {
>>> retries--;
>>> if ( retries <= 0 ) {
>>> log.info("Unable to bind server socket to:"+addr+"
>>> throwing error.");
>>> throw x;
>>> }
>>> portstart++;
>>> try {Thread.sleep(25);}catch( InterruptedException
>>> ti){Thread.interrupted();}
>>> retries = bind(socket,portstart,retries);
>>> }
>>> }
>>> return retries;
>>> }
>>>
>>> We can provide such a util method and whoever wants to open ports, can
>>> request for a port from that util method.
>>>
>>>
>>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>>
 1. Change the HTTP/S ports in mgt-transports.xml (2)
 2. Change the HTTP/S ports in axis2.xml (2)
 3. Change the LDAP ports in carbon.xml (2)
 4. Change the Qpid ports in carbon.xml (2)
 5. Change the JMX ports in advanced/jmx.xml (2)

 Total 10 ports to change :(


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*<
http://twitter.com/afkham_azeez>
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*<
http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Anjana Fernando]

Hi,

Doesn't that means, that type of a code should be in all the places we open
a socket? .. is that practical? .. Also, how about if we provide a simple
configuration parameter which says, an offset from the base ports, like the
default is 0, then you can increment it, for example in one server it will
be 1, so internally we can change the default HTTP/HTTPS ports from
9763/9443 to 9764/9444 and so on.

Cheers,
Anjana.

On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:

> In Tomcat, the following method is used when certain ports need to be used;
>
> protected int bind(ServerSocket socket, int portstart, int retries) throws
> IOException {
> InetSocketAddress addr = null;
> while ( retries > 0 ) {
> try {
> addr = new InetSocketAddress(getBind(), portstart);
> socket.bind(addr);
> setPort(portstart);
> log.info("Receiver Server Socket bound to:"+addr);
> return 0;
> }catch ( IOException x) {
> retries--;
> if ( retries <= 0 ) {
> log.info("Unable to bind server socket to:"+addr+"
> throwing error.");
> throw x;
> }
> portstart++;
> try {Thread.sleep(25);}catch( InterruptedException
> ti){Thread.interrupted();}
> retries = bind(socket,portstart,retries);
> }
> }
> return retries;
> }
>
> We can provide such a util method and whoever wants to open ports, can
> request for a port from that util method.
>
>
> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>
>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>> 2. Change the HTTP/S ports in axis2.xml (2)
>> 3. Change the LDAP ports in carbon.xml (2)
>> 4. Change the Qpid ports in carbon.xml (2)
>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>
>> Total 10 ports to change :(
>>
>>
>> --
>> 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
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Anjana Fernando*
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] XACML policies export

[Jorge Infante Osorio]

Thanks Prabath.

Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI

-Mensaje original-
De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Prabath Siriwardena
Enviado el: domingo, 15 de mayo de 2011 22:54
Para: carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] XACML policies export

If you are using IS 3.0.1, you can go to
_system/config/repository/identity/Entitlement/Policies through Registry
Browser and Download the policy..

Thanks & regards,
-Prabath

On Mon, May 16, 2011 at 8:06 AM, Jorge Infante Osorio 
wrote:
> Hi all.
> How I can export the XACML policies inside IS as xml files? Or the 
> only way is the copy/paste method.
>
> Thanks,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> UCI
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



--
Thanks & Regards,
Prabath

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

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

Re: [Carbon-dev] XACML policies export

[Prabath Siriwardena]

If you are using IS 3.0.1, you can go to
_system/config/repository/identity/Entitlement/Policies through
Registry Browser and Download the policy..

Thanks & regards,
-Prabath

On Mon, May 16, 2011 at 8:06 AM, Jorge Infante Osorio  wrote:
> Hi all.
> How I can export the XACML policies inside IS as xml files? Or the only way
> is the copy/paste method.
>
> Thanks,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> UCI
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Thanks & Regards,
Prabath

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

[Carbon-dev] How to check for Admin Role

[Amila Suriarachchi]

hi,

This is regarding this issue[1].

Can we change the admin role name? if so what is the meaning of the
ADMIN_ROLE = "admin" in
 org.wso2.carbon.utils.ServerConstants?

And also,

userRealm.getAuthorizationManager().isUserAuthorized(
loggedInUser, topicResourcePath,
EventBrokerConstants.EB_PERMISSION_CHANGE_PERMISSION)

returns false if user is not explicitly given the permission to that
resource. But in carbon there is a convention to
allow any user in admin role to do any activity. Then why don't we add that
rule too to the user manager.

Then everyone does not have to repeat admin role check every where.

thanks,
Amila.


[1] https://wso2.org/jira/browse/CARBON-9959
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] XACML policies export

[Jorge Infante Osorio]

Hi all.
How I can export the XACML policies inside IS as xml files? Or the only way
is the copy/paste method.

Thanks,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI


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

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Amila Suriarachchi]

On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:

> This will be a great usability enhancement. People will be able to startup
> multiple carbon servers without changing anything. Everything will work
> OOTB.


I think it depends on the requirement. For me most of the time I need to run
an ESB, DSS, Rules in order to do some integration testing. In this case ESB
proxies should know the port addresses of the DSS, Rules. So random port
generation won't work for such senarios.

thanks,
Amila.

>
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries) throws
>> IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket to:"+addr+"
>> throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] "WSO2 Carbon Continuous Build was SUCCESSFUL"

[WSO2 EC2 Carbon Builder]

[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.sts.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.servicehosting.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.dataservices.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mgt.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.jms.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mail.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.statistics.transport.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.client.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.core.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.mediation.ext.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.proxy.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.wsdl.tools.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.xkms.mgt.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.multiple.instance.feature
[INFO] Extracting feature org.wso2.esb:org.wso2.esb.styles.feature
[INFO] Extracting feature org.wso2.governance:org.wso2.governance.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.menu.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.styles.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.utils.feature
[INFO] Extracting feature org.wso2.ms:org.wso2.ms.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.utils.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.cloud.csg.agent.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.cloud.csg.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.mgt.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.deployer.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.unifiedendpoint.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.event.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.messagebox.feature
[INFO] Copying resources
[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Generating metadata for ..
[INFO] Generation completed with success [48 seconds].
[INFO] Running Equinox P2 Category Publisher Application for the Generated 
Repository
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/carbon/carbon/features/repository/pom.xml to 
/home/carbon/.m2/repository/org/wso2/carbon/wso2carbon-feature-repository/3.2.0-SNAPSHOT/wso2carbon-feature-repository-3.2.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 2 minutes 18 seconds
[INFO] Finished at: Sun May 15 23:11:23 UTC 2011
[INFO] Final Memory: 25M/981M
[INFO] 
2011-05-15_23-01-04
Carbon  packs are available at : 
http://builder.wso2.org/~carbon/releases/carbon/3.2.0/latest/
tail -n50 $CARBON_SRC_HOME/build.log
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Context root disappearing in Websphere

[Ranga Siriwardena]

Hi all,

I was able to reproduce the issue for GS. Will work with Milinda to sorted
out the issue.

Thanks.

On Thu, May 12, 2011 at 3:38 PM, Krishantha Samaraweera  wrote:

> Hi all,
>
> The same issue [1] has been raised sometime back and it has been resolved
> without doing a proper fix.
>
> Thanks
> Krishantha
>
> [1] https://wso2.org/jira/browse/CARBON-7371
>
>
> On Thu, May 12, 2011 at 2:21 PM, Nuwan Bandara  wrote:
>
>> Surprisingly this does not happen in other app servers (Tomcat etc),
>> according to pradeep he has seen this when there are relative URLs, But
>> there are many places in our UI bundles that we do redirection to relative
>> URLs.
>>
>> Regards,
>> /Nuwan
>>
>>
>> On Thu, May 12, 2011 at 2:15 PM, Milinda Pathirage wrote:
>>
>>> This could be due to recent changes we done to facilitate custom home
>>> page URLs. Will look into this.
>>>
>>> Thanks
>>> Milinda
>>>
>>> On Thu, May 12, 2011 at 1:56 PM, Chamara Ariyarathne 
>>> wrote:
>>>
 Following are the places which Browser redirect with wrong context root
 when server deployed in Websphere. I'm sending this for the request made by
 Pradeep and Nuwan, and according to the offline chat I had with them, there
 will be a similar solution for this.

 *Mashup Server;*
 Home button
 Upload Module; Modules -> Add Modules -> Upoload
 Upload JavaScript services -> Upload
 *
 Gadget Server;*
 Add Gadgets


 *Chamara Ariyarathne*
 Software Engineer - QA;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; *0772786766*


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


>>>
>>>
>>> --
>>> Milinda Pathirage
>>> Technical Lead and Product Manager, Business Process Server - WSO2 Inc;
>>> http://wso2.com
>>> Blog: http://blog.mpathirage.com
>>>
>>> Lean Enterprise Middleware
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Senior Software Engineer
>>
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> http://nuwan.bandara.co
>> *
>> 
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Ranga Siriwardena
Software Engineer
WSO2 Inc.

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

[Carbon-dev] WSDL Validator tool

[Jorge Infante Osorio]

Hi all.
The $subject validate again what? In the documentation I can find this
information.

The wsdl generates in WSAS 3.2.1 came with problem in the HTTP binding and
was validated: “WSDL DOCUMENT IS VALID” in AppServer 4.0.

Thanks,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI


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

Re: [Carbon-dev] Carbon Management Console Left Menu

[Afkham Azeez]

Not s trivial change IMO
On May 16, 2011 12:12 AM, "Chanaka Jayasena"  wrote:
> On Sun, May 15, 2011 at 8:49 PM, Senaka Fernando  wrote:
>
>> Hi Chanaka,
>>
>> I'm not trying to ask a lot here.
>>
>> But, in the same way that you added the configure menu, there can be
other
>> menus which is better to be hidden as such. For example, G-Reg has a menu
>> titled 'Extensions' which allows users to deploy extensions, such as
>> Handlers and Lifecycles. This too is a hindrance and takes up some space
on
>> the left side.
>>
> Yes. Senaka. It is possible. But right now the left side strip is
> done completely by client side HTML DOM manipulation. I am bit unclear
about
> product specific menu items. Let's give it a try and see.
>
> thanks,
> Chanaka
>
>>
>> So, is this implementation something extensible in way that we could do
>> something similar for that menu as well?
>>
>> On Sun, May 15, 2011 at 8:29 PM, Afkham Azeez  wrote:
>>
>>> This looks great.
>>
>>
>> +1.
>>
>> Thanks,
>> Senaka.
>>
>>
>>> The Configure Menu at the top is less frequently used. The way Chanaka
has
>>> implemented it, there is minimal change, only to the template.jsp.
>>>
>>> We will need better names for the menus buttons. Configurre Menu can be
>>> renamed to Configure. Main menu can be Main?
>>>
>>> On Sun, May 15, 2011 at 4:40 PM, Chanaka Jayasena wrote:
>>>
 Hi all,

 I am doing an update to the Carbon management console left menu base on
 an offline discussion I had with Azeez. This is not yet committed to
the
 trunk. Screen shot is attached with this mail. The idea is to show the
 frequently used menu items as "Main Menu" and hide the long list of
 "Configuration" menu items.

 thanks,
 Chanaka

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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> 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*<
http://twitter.com/afkham_azeez>
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon Management Console Left Menu

[Chanaka Jayasena]

On Sun, May 15, 2011 at 8:49 PM, Senaka Fernando  wrote:

> Hi Chanaka,
>
> I'm not trying to ask a lot here.
>
> But, in the same way that you added the configure menu, there can be other
> menus which is better to be hidden as such. For example, G-Reg has a menu
> titled 'Extensions' which allows users to deploy extensions, such as
> Handlers and Lifecycles. This too is a hindrance and takes up some space on
> the left side.
>
Yes. Senaka. It is possible. But right now the left side strip is
done completely by client side HTML DOM manipulation. I am bit unclear about
product specific menu items. Let's give it a try and see.

thanks,
Chanaka

>
> So, is this implementation something extensible in way that we could do
> something similar for that menu as well?
>
> On Sun, May 15, 2011 at 8:29 PM, Afkham Azeez  wrote:
>
>> This looks great.
>
>
> +1.
>
> Thanks,
> Senaka.
>
>
>> The Configure Menu at the top is less frequently used. The way Chanaka has
>> implemented it, there is minimal change, only to the template.jsp.
>>
>> We will need better names for the menus buttons. Configurre Menu can be
>> renamed to Configure. Main menu can be Main?
>>
>> On Sun, May 15, 2011 at 4:40 PM, Chanaka Jayasena wrote:
>>
>>> Hi all,
>>>
>>> I am doing an update to the Carbon management console left menu base on
>>> an offline discussion I had with Azeez. This is not yet committed to the
>>> trunk. Screen shot is attached with this mail. The idea is to show the
>>> frequently used menu items as "Main Menu" and hide the long list of
>>> "Configuration" menu items.
>>>
>>> thanks,
>>> Chanaka
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] problem in data service with sub queries.

[Jorge Infante Osorio]

Hi Anjana.
Your dataservice work fine, with some differences in the implementation with
respect to  my data service but show all data types fine.

I send you the full wsdl of my service with the default namespace and the
dataservice .dbs taken from WSAS.

I try it in the DataService Server 2.5.1 with the same result.

Thanks,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI

De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Anjana Fernando
Enviado el: domingo, 15 de mayo de 2011 0:50
Para: carbon-dev@wso2.org; carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] problem in data service with sub queries.

Hi Jorge,

I made somewhat of a similar data service (without the input params), I'm
attaching the data service and it's WSDL here, can you please deploy that
and see if you get the same problem? (it's based in the samples, so you can
just deploy it) .. because I can't seem to reproduce the problem. And also,
can you attach the full WSDL of the data service you've. 

Cheers,
Anjana.
On Sun, May 15, 2011 at 4:14 AM, Jorge Infante Osorio 
wrote:
Thanks a lot Anjana.
 
In this case If I delete the operation related with the query that doesn’t 
appear  in the wsdl, it appear again in the wsdl.
 
 
Before delete the operation:
 





 

 





 
After delete the operation obtenerTramitesPublicosPorPersona:
 





 

 






 
It´s not a namespace problem. I change the namespace of the two subqueries
with the same result:
 





 

 





 
Only appear one query.   The element in the namespace with prefix ax238
doesn’t show.
 
Thanks,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI
 
De: carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] En
nombre de Anjana Fernando
Enviado el: sábado, 14 de mayo de 2011 6:13
Para: carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] problem in data service with sub queries.
 
Hi Jorge, 
 
I'll take a look at it and let you know.
 
Cheers,
Anjana.
On Sat, May 14, 2011 at 1:35 AM, Jorge Infante Osorio 
wrote:
Sorry the delay.
 
Attach a sample data Service with the same problem.
 
The query with the two queries as result only show one of them. And all are
in the same namespace as you can see in the generate wsdl.
 
 
Thanks,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI
De: Sumedha Rubasinghe [mailto:sume...@wso2.com]
Enviado el: jueves, 14 de abril de 2011 12:40
Para: Jorge Infante Osorio
CC: carbon-dev@wso2.org
Asunto: Re: [Carbon-dev] problem in data service with sub queries.
 
Hi Jorge,
Is it possible for you to attach the data service for our reference?
/sumedha
On Wed, Apr 13, 2011 at 10:53 AM, Jorge Infante Osorio 
wrote:
Thanks Sumedha.
 
When I implemented the data Service it was as you say. All the queries have
different namespaces. The data service don´t generate the wsdl as I need.
After that, I change the namespace thinking that this was the error but with
no success.
 
Now I change again the namespace.
 
If all the result types are the same they cannot be in the same namespace,
and this is not the case. The queries results are different.
 
My doubt are in the relation between the operation and the changes in WSDL,
this is right in this way?
I think that the operations, is appears or not,  don´t  modified the data
schema generation in wsdl in this case, and it do.
 
 
Here is  a part of wsdl:
 
                 xmlns:ax233="http://uci.cu/servicios/schema/query4";
                 xmlns:ax227="http://uci.cu/servicios/schema/query1";
                 xmlns:ax232="http://uci.cu/servicios/schema/query2";
                 xmlns:ax234="http://uci.cu/servicios/schema/query3";
 

               
                   
               
           
           
           
               
                   
               
           
 
If I  the query1, query2 and query3 operation the data schema are
generate just fine.
 
Jorge.
 
De: Sumedha Rubasinghe [mailto:sume...@wso2.com]
Enviado el: martes, 12 de abril de 2011 22:40
Para: carbon-dev@wso2.org
CC: Jorge Infante Osorio
Asunto: Re: [Carbon-dev] problem in data service with sub queries.
 
Hi Jorge,
It seems your using same namespace for all result types in all four queries.
Unless all the result types are the same you cannot do this. Use four
different namespace definitions for four result types in your queries.
 
/sumedha
 
 
 
On Wed, Apr 13, 2011 at 7:52 AM, Jorge Infante Osorio 
wrote:
More information about this issue:
 
All this work fine with try it I don´t know why, but in the WSDL schema  I
don´t see the element with the three elements that reference the complex
type of the queries.
 
For example:
http://schemas.xmlsoap.org/wsdl/";
                 xmlns:ns1="http://ws.wso2.org/dataservice";
                 xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
                 xmlns:http1="http://schemas.xmlsoap.org/wsdl/http/";
 
xmlns:ax229="http://mpprij.gob.ve/servicios/schema/bienespersonajuridica";
                 xmlns:xs="http://www.w3.org/

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Hiranya Jayathilaka]

On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:

> This will be a great usability enhancement. People will be able to startup
> multiple carbon servers without changing anything. Everything will work
> OOTB.


+1

Much better than having to change 10-12 ports in config files

Thanks,
Hiranya


>
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries) throws
>> IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket to:"+addr+"
>> throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://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
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Thilina Buddhika]

+1 given the number of ports we need to change at the moment.

Thanks,
Thilina

On Sun, May 15, 2011 at 10:19 PM, Afkham Azeez  wrote:

> This will be a great usability enhancement. People will be able to startup
> multiple carbon servers without changing anything. Everything will work
> OOTB.
>
>
> On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:
>
>> In Tomcat, the following method is used when certain ports need to be
>> used;
>>
>> protected int bind(ServerSocket socket, int portstart, int retries) throws
>> IOException {
>> InetSocketAddress addr = null;
>> while ( retries > 0 ) {
>> try {
>> addr = new InetSocketAddress(getBind(), portstart);
>> socket.bind(addr);
>> setPort(portstart);
>> log.info("Receiver Server Socket bound to:"+addr);
>> return 0;
>> }catch ( IOException x) {
>> retries--;
>> if ( retries <= 0 ) {
>> log.info("Unable to bind server socket to:"+addr+"
>> throwing error.");
>> throw x;
>> }
>> portstart++;
>> try {Thread.sleep(25);}catch( InterruptedException
>> ti){Thread.interrupted();}
>> retries = bind(socket,portstart,retries);
>> }
>> }
>> return retries;
>> }
>>
>> We can provide such a util method and whoever wants to open ports, can
>> request for a port from that util method.
>>
>>
>> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>>
>>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>>> 2. Change the HTTP/S ports in axis2.xml (2)
>>> 3. Change the LDAP ports in carbon.xml (2)
>>> 4. Change the Qpid ports in carbon.xml (2)
>>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>>
>>> Total 10 ports to change :(
>>>
>>>
>>> --
>>> 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
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> 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*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thilina Buddhika
Senior Software Engineer
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Afkham Azeez]

This will be a great usability enhancement. People will be able to startup
multiple carbon servers without changing anything. Everything will work
OOTB.


On Sun, May 15, 2011 at 10:17 PM, Afkham Azeez  wrote:

> In Tomcat, the following method is used when certain ports need to be used;
>
> protected int bind(ServerSocket socket, int portstart, int retries) throws
> IOException {
> InetSocketAddress addr = null;
> while ( retries > 0 ) {
> try {
> addr = new InetSocketAddress(getBind(), portstart);
> socket.bind(addr);
> setPort(portstart);
> log.info("Receiver Server Socket bound to:"+addr);
> return 0;
> }catch ( IOException x) {
> retries--;
> if ( retries <= 0 ) {
> log.info("Unable to bind server socket to:"+addr+"
> throwing error.");
> throw x;
> }
> portstart++;
> try {Thread.sleep(25);}catch( InterruptedException
> ti){Thread.interrupted();}
> retries = bind(socket,portstart,retries);
> }
> }
> return retries;
> }
>
> We can provide such a util method and whoever wants to open ports, can
> request for a port from that util method.
>
>
> On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:
>
>> 1. Change the HTTP/S ports in mgt-transports.xml (2)
>> 2. Change the HTTP/S ports in axis2.xml (2)
>> 3. Change the LDAP ports in carbon.xml (2)
>> 4. Change the Qpid ports in carbon.xml (2)
>> 5. Change the JMX ports in advanced/jmx.xml (2)
>>
>> Total 10 ports to change :(
>>
>>
>> --
>> 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
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
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*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] To Start Multiple ESB Instances on the Same Machine...

[Afkham Azeez]

In Tomcat, the following method is used when certain ports need to be used;

protected int bind(ServerSocket socket, int portstart, int retries) throws
IOException {
InetSocketAddress addr = null;
while ( retries > 0 ) {
try {
addr = new InetSocketAddress(getBind(), portstart);
socket.bind(addr);
setPort(portstart);
log.info("Receiver Server Socket bound to:"+addr);
return 0;
}catch ( IOException x) {
retries--;
if ( retries <= 0 ) {
log.info("Unable to bind server socket to:"+addr+"
throwing error.");
throw x;
}
portstart++;
try {Thread.sleep(25);}catch( InterruptedException
ti){Thread.interrupted();}
retries = bind(socket,portstart,retries);
}
}
return retries;
}

We can provide such a util method and whoever wants to open ports, can
request for a port from that util method.


On Fri, May 13, 2011 at 2:20 PM, Hiranya Jayathilaka wrote:

> 1. Change the HTTP/S ports in mgt-transports.xml (2)
> 2. Change the HTTP/S ports in axis2.xml (2)
> 3. Change the LDAP ports in carbon.xml (2)
> 4. Change the Qpid ports in carbon.xml (2)
> 5. Change the JMX ports in advanced/jmx.xml (2)
>
> Total 10 ports to change :(
>
>
> --
> 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
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
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*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Please assign issues to relevant products/components/people

[Danushka Menikkumbura]

I just ran through open JIRA's that were created during last couple of days
and assigned ones which should be looked into by the Event team. Respective
PM's please assign issues that are not intended to be handled by your team
as soon as you see them so that relevant teams can act on them quickly.

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

Re: [Carbon-dev] [CS] Build error in registry

[Melan Nimesh]

Hi,

ESB package issue now fixed (committed to branch, Rev. 94276). but still
cannot build on windows from fresh check-out without manually changing some
files, I am currently working on  overcome this issues.

Thanks

--Melan

On Sat, May 14, 2011 at 9:39 AM, Melan Nimesh  wrote:

> Hi,
>
>
> On Sat, May 14, 2011 at 9:10 AM, Samisa Abeysinghe wrote:
>
>> I do not want to apply patches. Please let e know once it is committed and
>> then I can try to build.
>>
>> And I have waited on this long enough. Please own this and see it through
>> to completion.
>>
>
> Will work on this today.
>
>
>>
>>
>> On Sat, May 14, 2011 at 7:45 AM, Melan Nimesh  wrote:
>>
>>> Hi,
>>>
>>> On Sat, May 14, 2011 at 7:12 AM, Samisa Abeysinghe wrote:
>>>
 I tried applying the patch. But the build seem to be broken at this
 point. So no way to verify.
>>>
>>>
>>> Please apply patch from CS source's (your local copy's) root directory
>>>
>>>

 One checkout build does not seem to work at all for CS.

 We do this for Carbon, which is much more complex and larger in size.
 Why not CS?


>>>

 On Sat, May 14, 2011 at 5:22 AM, Samisa Abeysinghe wrote:

>
>
> On Sat, May 14, 2011 at 12:12 AM, Melan Nimesh  wrote:
>
>> Hi,
>>
>> sorry for late reply, please find the attached patch file [1]  fix
>> this issue. please apply this patch from CS Branch root (
>> https://svn.wso2.org/repos/wso2/branches/tools/eclipse/carbon-studio/1.0.0)
>> . also build log [2] attached for your information
>>
>
> Um, I thought you are a committer. Why are you attaching a patch?
>
>
>> [1] Windows_fix.patch
>> [2] build.log
>>
>>
>> Thanks
>>
>> --Melan
>>
>>
>> On Fri, May 13, 2011 at 6:52 PM, Samisa Abeysinghe 
>> wrote:
>>
>>> Ping...
>>>
>>> Is this fixed now?
>>>
>>>
>>> On Tue, May 10, 2011 at 7:03 PM, Samisa Abeysinghe 
>>> wrote:
>>>
 What would be the ETA?


 On Mon, May 9, 2011 at 10:52 PM, Melan Nimesh wrote:

> Hi,
>
> I have successfully built CS on Windows with my changed local copy,
> I'll update progress after  build same code (modified code) with Linux
>
> Thanks
> --Melan
>
> On Mon, May 9, 2011 at 9:46 PM, Samisa Abeysinghe  > wrote:
>
>> Any luck with this? I am awaiting for this to load the code into
>> my Eclipse on Windows :(
>>
>>
>> On Thu, May 5, 2011 at 2:50 PM, Saminda Wijeratne <
>> samin...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, May 5, 2011 at 2:40 PM, Samisa Abeysinghe <
>>> sam...@wso2.com> wrote:
>>>
 Can we rename the package to mediators and be done with it?
>>>
>>> That package was codegen from eclipse emf framework. We have
>>> customized some of the classes in it. Package name should be 
>>> updated Codegen
>>> configuration level & then once the new package is created we need 
>>> to merge
>>> our changes. This might take a little while. Melan is working on 
>>> this.
>>>
>>> Saminda
>>>


 On Thu, May 5, 2011 at 2:36 PM, Melan Nimesh wrote:

> Hi,
>
>
> On Thu, May 5, 2011 at 2:12 PM, Samisa Abeysinghe <
> sam...@wso2.com> wrote:
> >
> >
> > On Thu, May 5, 2011 at 1:44 PM, Melan Nimesh 
> wrote:
> >>
> >> Hi,
> >>
> >> I also got same error when building Carbon Studio  in
> Windows (I am
> >> using Windows 7 x64). this is due to collision  with
> >> org.wso2.carbonstudio.eclipse.esb.Mediator class and
> >> org.wso2.carbonstudio.eclipse.esb.mediator.provider package,
> >
> > How did you conclude that this is the error from my build
> log?
>
> I also tried to build Carbon Studio in my machine and my error
> log
> also bit similar to your error log, then I looked at
> corresponding
> source code (org.wso2.carbonstudio.eclipse.esb)
>
> >
> >>
> >> In Java we can not have a class name that is the same as a
> package
> >> name.( even this class and package not in same case, but
> windows treat
> >> them as same)
> >>
> >> I am trying to fix this bug with minimum code change,
> >
> > What is the change you are trying?:
>
> Most codes contains in this java package
> (org.wso2.carbonstudio.eclipse.es

Re: [Carbon-dev] Transports Initialized Before Carbon has been completely loaded

[Afkham Azeez]

Fixed by adding the bindOnInit parameter to the Tomcat connectors and
setting that to false.


On Sun, May 15, 2011 at 3:39 PM, Senaka Fernando  wrote:

> FYI. This is very easy to reproduce. Simply start the server in two
> consoles, and you will see that the transports are initialized when the
> webapp is getting deployed, much before Carbon has been initialized.
>
> ./wso2server.sh
> JAVA_HOME environment variable is set to /usr/lib/jvm/java-6-sun-1.6.0.20
> CARBON_HOME environment variable is set to
> /home/senaka/carbon-trunk/products/greg/modules/distribution/product/target/wso2greg-4.0.0-SNAPSHOT
> [2011-05-15 15:36:32,408]  INFO {org.wso2.carbon.server.Main} -
> Initializing system...
> [2011-05-15 15:36:32,608]  INFO
> {org.wso2.carbon.server.transports.http.HttpTransport} -  Created Connector
> [HTTP_11_NIO://*:9763]
> [2011-05-15 15:36:32,612]  INFO
> {org.wso2.carbon.server.transports.http.HttpTransport} -  Created Connector
> [HTTPS_11_NIO://*:9443]
> [2011-05-15 15:36:32,709]  INFO
> {org.wso2.carbon.server.TomcatCarbonWebappDeployer} -  Deployed Carbon
> webapp: StandardEngine[Tomcat].StandardHost[defaulthost].StandardContext[/]
> May 15, 2011 3:36:33 PM org.apache.coyote.AbstractProtocolHandler init
> SEVERE: Failed to initialize end point associated with ProtocolHandler
> ["http-nio-9763"]
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:459)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:483)
> at
> org.apache.coyote.AbstractProtocolHandler.init(AbstractProtocolHandler.java:345)
> at
> org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:910)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:781)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:136)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:305)
> at org.wso2.carbon.tomcat.BetterTomcat.start(BetterTomcat.java:71)
> at org.wso2.carbon.server.TomcatServer.start(TomcatServer.java:110)
> at org.wso2.carbon.server.Main.startServer(Main.java:64)
> at org.wso2.carbon.server.Main.start(Main.java:156)
> 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.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62)
> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43)
> May 15, 2011 3:36:33 PM org.apache.catalina.core.StandardService
> initInternal
> SEVERE: Failed to initialize connector
> [Connector[org.apache.coyote.http11.Http11NioProtocol-9763]]
> org.apache.catalina.LifecycleException: Protocol handler initialization
> failed
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:912)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:781)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:136)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:305)
> at org.wso2.carbon.tomcat.BetterTomcat.start(BetterTomcat.java:71)
> at org.wso2.carbon.server.TomcatServer.start(TomcatServer.java:110)
> at org.wso2.carbon.server.Main.startServer(Main.java:64)
> at org.wso2.carbon.server.Main.start(Main.java:156)
> 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.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62)
> at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43)
> Caused by: java.net.BindException: Address already in use
>  

Re: [Carbon-dev] Carbon Management Console Left Menu

[Senaka Fernando]

Hi Chanaka,

I'm not trying to ask a lot here.

But, in the same way that you added the configure menu, there can be other
menus which is better to be hidden as such. For example, G-Reg has a menu
titled 'Extensions' which allows users to deploy extensions, such as
Handlers and Lifecycles. This too is a hindrance and takes up some space on
the left side.

So, is this implementation something extensible in way that we could do
something similar for that menu as well?

On Sun, May 15, 2011 at 8:29 PM, Afkham Azeez  wrote:

> This looks great.


+1.

Thanks,
Senaka.


> The Configure Menu at the top is less frequently used. The way Chanaka has
> implemented it, there is minimal change, only to the template.jsp.
>
> We will need better names for the menus buttons. Configurre Menu can be
> renamed to Configure. Main menu can be Main?
>
> On Sun, May 15, 2011 at 4:40 PM, Chanaka Jayasena wrote:
>
>> Hi all,
>>
>> I am doing an update to the Carbon management console left menu base on an
>> offline discussion I had with Azeez. This is not yet committed to the trunk.
>> Screen shot is attached with this mail. The idea is to show the frequently
>> used menu items as "Main Menu" and hide the long list of "Configuration"
>> menu items.
>>
>> thanks,
>> Chanaka
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

Re: [Carbon-dev] Carbon Management Console Left Menu

[Afkham Azeez]

This looks great. The Configure Menu at the top is less frequently used. The
way Chanaka has implemented it, there is minimal change, only to the
template.jsp.

We will need better names for the menus buttons. Configurre Menu can be
renamed to Configure. Main menu can be Main?

On Sun, May 15, 2011 at 4:40 PM, Chanaka Jayasena  wrote:

> Hi all,
>
> I am doing an update to the Carbon management console left menu base on an
> offline discussion I had with Azeez. This is not yet committed to the trunk.
> Screen shot is attached with this mail. The idea is to show the frequently
> used menu items as "Main Menu" and hide the long list of "Configuration"
> menu items.
>
> thanks,
> Chanaka
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
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*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Troubleshooting LDAP configuration errors

[Amila Jayasekara]

On Fri, May 13, 2011 at 1:15 AM, Afkham Azeez  wrote:
 Thilina & I discovered today that it is a nightmare to troubleshoot
 configuration errors with the current embedded LDAP server. There was an
 authentication failure, and there was no proper error message, and even
 after debugging, it was not exactly clear what was wrong. Is there a way to
 make this more use friendly, and make the configuration less cryptic?

Hi Azeez/Thilina,

What sort of a configuration error you encountered ? Let me try to
reproduce it and see the possibility of improving error messages.
Thanks
AmilaJ

>
> --
> Afkham Azeez
> Director of Architecture; WSO2, Inc.; http://wso2.com
> 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
>
> Lean . Enterprise . Middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error in deployment synchronizer

[Supun Kamburugamuva]

Now I'm getting the following exception while starting the ESB

[2011-05-15 17:20:34,704] ERROR - DeploymentSynchronizer Error while
performing the initial sync-up on the repository at:
/Users/supun/dev/wso2/trunk/carbon/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/deployment/server/.
Auto sync tasks will not be engaged.
org.wso2.carbon.registry.synchronization.SynchronizationException:
message code: RESOLVE_CONFLICTS, parameters: {
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:350)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElement(CheckInCommand.java:294)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.restoreFromFileSystem(CheckInCommand.java:214)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.execute(CheckInCommand.java:149)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.execute(CheckInCommand.java:163)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:62)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:80)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:127)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer.commit(DeploymentSynchronizer.java:134)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer.doInitialSyncUp(DeploymentSynchronizer.java:203)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer.start(DeploymentSynchronizer.java:95)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:107)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:65)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
at 
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
at 
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
at 
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at 
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextI

[Carbon-dev] Error in deployment synchronizer

[Supun Kamburugamuva]

While playing with the ESB I got the following exception. I was just
doing things from the UI like creating proxy services, endpoints etc.

[2011-05-15 16:41:23,284] ERROR - DeploymentSynchronizer Registry
synchronization error encountered in the repository at:
/Users/supun/dev/wso2/trunk/carbon/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/deployment/server/
org.wso2.carbon.registry.synchronization.SynchronizationException:
message code: RESOLVE_CONFLICTS, parameters: {
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:350)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElement(CheckInCommand.java:294)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.restoreFromFileSystem(CheckInCommand.java:214)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.execute(CheckInCommand.java:149)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.execute(CheckInCommand.java:163)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:62)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:80)
at 
org.wso2.carbon.registry.synchronization.RegistrySynchronizer.checkIn(RegistrySynchronizer.java:127)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer.commit(DeploymentSynchronizer.java:134)
at 
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizer$AutoSyncTask.run(DeploymentSynchronizer.java:227)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
[2011-05-15 16:42:23,192] ERROR - DeploymentSynchronizer Registry
synchronization error encountered in the repository at:
/Users/supun/dev/wso2/trunk/carbon/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/deployment/server/
org.wso2.carbon.registry.synchronization.SynchronizationException:
message code: RESOLVE_CONFLICTS, parameters: {
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:350)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElementForChild(CheckInCommand.java:430)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createDirectoryMetaElement(CheckInCommand.java:361)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.createMetaElement(CheckInCommand.java:294)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.restoreFromFileSystem(CheckInCommand.java:214)
at 
org.wso2.carbon.registry.synchronization.operation.CheckInCommand.execute(CheckInCommand.java:149)
at 
org.wso2.carbon.re

[Carbon-dev] Carbon Management Console Left Menu

[Chanaka Jayasena]

Hi all,

I am doing an update to the Carbon management console left menu base on an
offline discussion I had with Azeez. This is not yet committed to the trunk.
Screen shot is attached with this mail. The idea is to show the frequently
used menu items as "Main Menu" and hide the long list of "Configuration"
menu items.

thanks,
Chanaka
<>___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Transports Initialized Before Carbon has been completely loaded

[Senaka Fernando]

FYI. This is very easy to reproduce. Simply start the server in two
consoles, and you will see that the transports are initialized when the
webapp is getting deployed, much before Carbon has been initialized.

./wso2server.sh
JAVA_HOME environment variable is set to /usr/lib/jvm/java-6-sun-1.6.0.20
CARBON_HOME environment variable is set to
/home/senaka/carbon-trunk/products/greg/modules/distribution/product/target/wso2greg-4.0.0-SNAPSHOT
[2011-05-15 15:36:32,408]  INFO {org.wso2.carbon.server.Main} -
Initializing system...
[2011-05-15 15:36:32,608]  INFO
{org.wso2.carbon.server.transports.http.HttpTransport} -  Created Connector
[HTTP_11_NIO://*:9763]
[2011-05-15 15:36:32,612]  INFO
{org.wso2.carbon.server.transports.http.HttpTransport} -  Created Connector
[HTTPS_11_NIO://*:9443]
[2011-05-15 15:36:32,709]  INFO
{org.wso2.carbon.server.TomcatCarbonWebappDeployer} -  Deployed Carbon
webapp: StandardEngine[Tomcat].StandardHost[defaulthost].StandardContext[/]
May 15, 2011 3:36:33 PM org.apache.coyote.AbstractProtocolHandler init
SEVERE: Failed to initialize end point associated with ProtocolHandler
["http-nio-9763"]
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:459)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:483)
at
org.apache.coyote.AbstractProtocolHandler.init(AbstractProtocolHandler.java:345)
at
org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:910)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:781)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:136)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:305)
at org.wso2.carbon.tomcat.BetterTomcat.start(BetterTomcat.java:71)
at org.wso2.carbon.server.TomcatServer.start(TomcatServer.java:110)
at org.wso2.carbon.server.Main.startServer(Main.java:64)
at org.wso2.carbon.server.Main.start(Main.java:156)
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.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62)
at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43)
May 15, 2011 3:36:33 PM org.apache.catalina.core.StandardService
initInternal
SEVERE: Failed to initialize connector
[Connector[org.apache.coyote.http11.Http11NioProtocol-9763]]
org.apache.catalina.LifecycleException: Protocol handler initialization
failed
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:912)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:781)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:101)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:136)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:305)
at org.wso2.carbon.tomcat.BetterTomcat.start(BetterTomcat.java:71)
at org.wso2.carbon.server.TomcatServer.start(TomcatServer.java:110)
at org.wso2.carbon.server.Main.startServer(Main.java:64)
at org.wso2.carbon.server.Main.start(Main.java:156)
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.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62)
at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:459)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(Abstr

Re: [Carbon-dev] Warning when building Carbon Standalone Server

[Denis Weerasiri]

And also, when building "Apache Axis2 - tool - Intellij IDEA Plugin"

[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o  'org.apache.ws.commons.axiom:axiom-dom:jar'
o  'stax:stax-api:jar'
o  'org.apache.woden:woden:jar'


On Sun, May 15, 2011 at 1:38 PM, Senaka Fernando  wrote:

> FYI.
>
> [WARNING] The following patterns were never triggered in this artifact
> inclusion filter:
> o  'javax.xml.stream:stax-api:jar'
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com* *
blog: **http://ddweerasiri.blogspot.com* *
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Warning when building Carbon Standalone Server

[Senaka Fernando]

FYI.

[WARNING] The following patterns were never triggered in this artifact
inclusion filter:
o  'javax.xml.stream:stax-api:jar'

Thanks,
Senaka.

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

[Carbon-dev] "WSO2 Carbon Continuous Build was SUCCESSFUL"

[WSO2 EC2 Carbon Builder]

[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.sts.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.servicehosting.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.dataservices.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mgt.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.jms.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.transport.mail.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.statistics.transport.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.client.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.core.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.mediation.ext.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.discovery.proxy.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.discovery.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.wsdl.tools.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.wsdl.tools.ui.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.xkms.mgt.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.multiple.instance.feature
[INFO] Extracting feature org.wso2.esb:org.wso2.esb.styles.feature
[INFO] Extracting feature org.wso2.governance:org.wso2.governance.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.styles.feature
[INFO] Extracting feature org.wso2.gs:org.wso2.gs.menu.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.styles.feature
[INFO] Extracting feature org.wso2.identity:org.wso2.identity.utils.feature
[INFO] Extracting feature org.wso2.ms:org.wso2.ms.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.styles.feature
[INFO] Extracting feature org.wso2.appserver:org.wso2.appserver.utils.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.cloud.csg.agent.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.cloud.csg.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.mgt.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.application.deployer.webapp.feature
[INFO] Extracting feature 
org.wso2.carbon:org.wso2.carbon.unifiedendpoint.server.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.event.feature
[INFO] Extracting feature org.wso2.carbon:org.wso2.carbon.messagebox.feature
[INFO] Copying resources
[INFO] Running Equinox P2 Publisher Application for Repository Generation
[INFO] Generating metadata for ..
[INFO] Generation completed with success [47 seconds].
[INFO] Running Equinox P2 Category Publisher Application for the Generated 
Repository
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/carbon/carbon/features/repository/pom.xml to 
/home/carbon/.m2/repository/org/wso2/carbon/wso2carbon-feature-repository/3.2.0-SNAPSHOT/wso2carbon-feature-repository-3.2.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 2 minutes 34 seconds
[INFO] Finished at: Sun May 15 07:04:55 UTC 2011
[INFO] Final Memory: 25M/981M
[INFO] 
2011-05-15_06-51-15
Carbon  packs are available at : 
http://builder.wso2.org/~carbon/releases/carbon/3.2.0/latest/
tail -n50 $CARBON_SRC_HOME/build.log
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev