Re: [Carbon-dev] Performance numbers of Agent Component

[Tharindu Mathew]

Did you try this?
http://lj4newbies.blogspot.com/2007/04/too-many-open-files.html



On Mon, Feb 13, 2012 at 12:42 PM, Suhothayan Sriskandarajah
wrote:

>
>
> On Mon, Feb 13, 2012 at 12:29 PM, Tharindu Mathew wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 12:07 PM, Suhothayan Sriskandarajah <
>> s...@wso2.com> wrote:
>>
>>> According to the given requirements and suggestions I did two
>>> performance tests for Agent Components.
>>>
>>> For the first one, I sent messages from one client to 200 servers, here
>>> for each server I first sent 1M messages to stabilize the system and then
>>> sent anther 1M messages for each server to test the performance.
>>> In this case, the client was sending 0.52M Events/Sec and each server
>>> was processing about 2583 Events/Sec
>>>
>>> I also tested by sending 10M messages from 200 clients to a single
>>> server. To stabilize the follow I initially sent 1M Events and then
>>> monitored for performance, here the server was able to handle 0.3M
>>> Events/Sec
>>>
>> Did the server fail after this...?
>>
>
> No, I was getting the "too many open files" issue.
> I think this has occurred because I'm running all servers and clients on
> the same machine.
> If we increase the file limit and run this in a distributed environment I
> believe this issue can be rectified.
>
> Thanks,
> Suho
>
>>
>>> Thanks
>>> Suho
>>>
>>>
>>> On Thu, Feb 9, 2012 at 7:20 PM, Tharindu Mathew wrote:
>>>
 Hi Srinath,

 I wasn't thinking about doing multiple servers now itself. That would
 be impractical. We can just start by increasing the number of clients. Just
 using a thread pool and increasing the pool size would do...

 On Thu, Feb 9, 2012 at 2:32 PM, Srinath Perera wrote:

> Hi Tharindu,
>
> Agreed .. lets plan to find some HW and do this when we can (will need
> at least 5 servers) .. I just want us not to be blocked on this.
>
> --Srinath
>
> On Thu, Feb 9, 2012 at 2:01 PM, Tharindu Mathew 
> wrote:
> > Not testing for load at start lead to problems earlier.
> >
> > Testing for 20 clients and 10 M messages is not the same for testing
> for 500
> > clients and 10 M messages. At this scale only, connection pooling,
> caching
> > and all of this matters. This is of course, many clients to one
> server, a
> > basic test that can be done easily.
> >
> > Anyway, we can post pone the testing to when we integrate BAM or
> CEP, but
> > please be aware of the implications. This was a situation where
> earlier BAM
> > was not scaling at all.
> >
> >
> > On Thu, Feb 9, 2012 at 1:43 PM, Amila Suriarachchi 
> wrote:
> >>
> >>
> >>
> >> On Thu, Feb 9, 2012 at 12:36 PM, Srinath Perera 
> wrote:
> >>>
> >>> Hi Suho,
> >>>
> >>> IMHO this covers about 90% of our usecases .. I think we should
> move on
> >>
> >>
> >> we do not required to do an performance study. Since anyway we
> don't have
> >> proper CEP or BAM service to consume events.
> >>
> >> But need to test for once client many server scenario to test for
> >> stability.
> >>
> >> thanks,
> >> Amila.
> >>
> >>>
> >>>
> >>> I do not mind doing a larger perf study later .. ..
> >>>
> >>> but getting the server finished from siddhi side and releasing it,
> CEP
> >>> perrf numbers,  and integrating this with BAM are more urget IMHO
> >>>
> >>> --Srinath
> >>>
> >>> On Thu, Feb 9, 2012 at 12:29 PM, Suhothayan Sriskandarajah
> >>>  wrote:
> >>> >
> >>> >
> >>> > On Thu, Feb 9, 2012 at 12:00 PM, Amila Suriarachchi <
> am...@wso2.com>
> >>> > wrote:
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew <
> thari...@wso2.com>
> >>> >> wrote:
> >>> >>>
> >>> >>> Suho,
> >>> >>>
> >>> >>> This does not measure the ability to handle load. Basically,
> what we
> >>> >>> did
> >>> >>> for load testing earlier was send around 2M messages, with
> >>> >>> concurrency as
> >>> >>> high increasing from 100 - 1500 clients.
> >>> >>
> >>> >>
> >>> >> How many back end servers and client programs used for that?
> >>> >>
> >>> >>>
> >>> >>>
> >>> >>> Your test is a measure of being able to consistently handle a
> stream
> >>> >>> of
> >>> >>> messages, which IMO, maybe important but is less interesting
> when
> >>> >>> handling
> >>> >>> load.
> >>> >>
> >>> >>
> >>> >> This test has measured the one client one server. yes it can be
> >>> >> improved
> >>> >> to one client to many servers and many clients to many servers.
> >>> >>
> >>> >
> >>> > This test also covers sending messages from many clients (2,5,10
> & 20)
> >>> > to
> >>> > one server.
> >>> > Yes it could be improved to many clients t

Re: [Carbon-dev] Performance numbers of Agent Component

[Suhothayan Sriskandarajah]

On Mon, Feb 13, 2012 at 12:29 PM, Tharindu Mathew  wrote:

>
>
> On Mon, Feb 13, 2012 at 12:07 PM, Suhothayan Sriskandarajah  > wrote:
>
>> According to the given requirements and suggestions I did two performance
>> tests for Agent Components.
>>
>> For the first one, I sent messages from one client to 200 servers, here
>> for each server I first sent 1M messages to stabilize the system and then
>> sent anther 1M messages for each server to test the performance.
>> In this case, the client was sending 0.52M Events/Sec and each server was
>> processing about 2583 Events/Sec
>>
>> I also tested by sending 10M messages from 200 clients to a single
>> server. To stabilize the follow I initially sent 1M Events and then
>> monitored for performance, here the server was able to handle 0.3M
>> Events/Sec
>>
> Did the server fail after this...?
>

No, I was getting the "too many open files" issue.
I think this has occurred because I'm running all servers and clients on
the same machine.
If we increase the file limit and run this in a distributed environment I
believe this issue can be rectified.

Thanks,
Suho

>
>> Thanks
>> Suho
>>
>>
>> On Thu, Feb 9, 2012 at 7:20 PM, Tharindu Mathew wrote:
>>
>>> Hi Srinath,
>>>
>>> I wasn't thinking about doing multiple servers now itself. That would be
>>> impractical. We can just start by increasing the number of clients. Just
>>> using a thread pool and increasing the pool size would do...
>>>
>>> On Thu, Feb 9, 2012 at 2:32 PM, Srinath Perera  wrote:
>>>
 Hi Tharindu,

 Agreed .. lets plan to find some HW and do this when we can (will need
 at least 5 servers) .. I just want us not to be blocked on this.

 --Srinath

 On Thu, Feb 9, 2012 at 2:01 PM, Tharindu Mathew 
 wrote:
 > Not testing for load at start lead to problems earlier.
 >
 > Testing for 20 clients and 10 M messages is not the same for testing
 for 500
 > clients and 10 M messages. At this scale only, connection pooling,
 caching
 > and all of this matters. This is of course, many clients to one
 server, a
 > basic test that can be done easily.
 >
 > Anyway, we can post pone the testing to when we integrate BAM or CEP,
 but
 > please be aware of the implications. This was a situation where
 earlier BAM
 > was not scaling at all.
 >
 >
 > On Thu, Feb 9, 2012 at 1:43 PM, Amila Suriarachchi 
 wrote:
 >>
 >>
 >>
 >> On Thu, Feb 9, 2012 at 12:36 PM, Srinath Perera 
 wrote:
 >>>
 >>> Hi Suho,
 >>>
 >>> IMHO this covers about 90% of our usecases .. I think we should
 move on
 >>
 >>
 >> we do not required to do an performance study. Since anyway we don't
 have
 >> proper CEP or BAM service to consume events.
 >>
 >> But need to test for once client many server scenario to test for
 >> stability.
 >>
 >> thanks,
 >> Amila.
 >>
 >>>
 >>>
 >>> I do not mind doing a larger perf study later .. ..
 >>>
 >>> but getting the server finished from siddhi side and releasing it,
 CEP
 >>> perrf numbers,  and integrating this with BAM are more urget IMHO
 >>>
 >>> --Srinath
 >>>
 >>> On Thu, Feb 9, 2012 at 12:29 PM, Suhothayan Sriskandarajah
 >>>  wrote:
 >>> >
 >>> >
 >>> > On Thu, Feb 9, 2012 at 12:00 PM, Amila Suriarachchi <
 am...@wso2.com>
 >>> > wrote:
 >>> >>
 >>> >>
 >>> >>
 >>> >> On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew <
 thari...@wso2.com>
 >>> >> wrote:
 >>> >>>
 >>> >>> Suho,
 >>> >>>
 >>> >>> This does not measure the ability to handle load. Basically,
 what we
 >>> >>> did
 >>> >>> for load testing earlier was send around 2M messages, with
 >>> >>> concurrency as
 >>> >>> high increasing from 100 - 1500 clients.
 >>> >>
 >>> >>
 >>> >> How many back end servers and client programs used for that?
 >>> >>
 >>> >>>
 >>> >>>
 >>> >>> Your test is a measure of being able to consistently handle a
 stream
 >>> >>> of
 >>> >>> messages, which IMO, maybe important but is less interesting
 when
 >>> >>> handling
 >>> >>> load.
 >>> >>
 >>> >>
 >>> >> This test has measured the one client one server. yes it can be
 >>> >> improved
 >>> >> to one client to many servers and many clients to many servers.
 >>> >>
 >>> >
 >>> > This test also covers sending messages from many clients (2,5,10
 & 20)
 >>> > to
 >>> > one server.
 >>> > Yes it could be improved to many clients to many server.
 >>> > If there are any specific requirements please suggest me a
 scenario,
 >>> > then I
 >>> > can do the testing and present the findings.
 >>> >
 >>> > Thanks
 >>> > Suho
 >>> >
 >>> >> But this test gives the through put this can handle one client to
 >>> >> server.
 >

Re: [Carbon-dev] Performance numbers of Agent Component

[Tharindu Mathew]

On Mon, Feb 13, 2012 at 12:07 PM, Suhothayan Sriskandarajah
wrote:

> According to the given requirements and suggestions I did two performance
> tests for Agent Components.
>
> For the first one, I sent messages from one client to 200 servers, here
> for each server I first sent 1M messages to stabilize the system and then
> sent anther 1M messages for each server to test the performance.
> In this case, the client was sending 0.52M Events/Sec and each server was
> processing about 2583 Events/Sec
>
> I also tested by sending 10M messages from 200 clients to a single server.
> To stabilize the follow I initially sent 1M Events and then monitored for
> performance, here the server was able to handle 0.3M Events/Sec
>
Did the server fail after this...?

>
> Thanks
> Suho
>
>
> On Thu, Feb 9, 2012 at 7:20 PM, Tharindu Mathew  wrote:
>
>> Hi Srinath,
>>
>> I wasn't thinking about doing multiple servers now itself. That would be
>> impractical. We can just start by increasing the number of clients. Just
>> using a thread pool and increasing the pool size would do...
>>
>> On Thu, Feb 9, 2012 at 2:32 PM, Srinath Perera  wrote:
>>
>>> Hi Tharindu,
>>>
>>> Agreed .. lets plan to find some HW and do this when we can (will need
>>> at least 5 servers) .. I just want us not to be blocked on this.
>>>
>>> --Srinath
>>>
>>> On Thu, Feb 9, 2012 at 2:01 PM, Tharindu Mathew 
>>> wrote:
>>> > Not testing for load at start lead to problems earlier.
>>> >
>>> > Testing for 20 clients and 10 M messages is not the same for testing
>>> for 500
>>> > clients and 10 M messages. At this scale only, connection pooling,
>>> caching
>>> > and all of this matters. This is of course, many clients to one
>>> server, a
>>> > basic test that can be done easily.
>>> >
>>> > Anyway, we can post pone the testing to when we integrate BAM or CEP,
>>> but
>>> > please be aware of the implications. This was a situation where
>>> earlier BAM
>>> > was not scaling at all.
>>> >
>>> >
>>> > On Thu, Feb 9, 2012 at 1:43 PM, Amila Suriarachchi 
>>> wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Feb 9, 2012 at 12:36 PM, Srinath Perera 
>>> wrote:
>>> >>>
>>> >>> Hi Suho,
>>> >>>
>>> >>> IMHO this covers about 90% of our usecases .. I think we should move
>>> on
>>> >>
>>> >>
>>> >> we do not required to do an performance study. Since anyway we don't
>>> have
>>> >> proper CEP or BAM service to consume events.
>>> >>
>>> >> But need to test for once client many server scenario to test for
>>> >> stability.
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>
>>> >>>
>>> >>>
>>> >>> I do not mind doing a larger perf study later .. ..
>>> >>>
>>> >>> but getting the server finished from siddhi side and releasing it,
>>> CEP
>>> >>> perrf numbers,  and integrating this with BAM are more urget IMHO
>>> >>>
>>> >>> --Srinath
>>> >>>
>>> >>> On Thu, Feb 9, 2012 at 12:29 PM, Suhothayan Sriskandarajah
>>> >>>  wrote:
>>> >>> >
>>> >>> >
>>> >>> > On Thu, Feb 9, 2012 at 12:00 PM, Amila Suriarachchi <
>>> am...@wso2.com>
>>> >>> > wrote:
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew <
>>> thari...@wso2.com>
>>> >>> >> wrote:
>>> >>> >>>
>>> >>> >>> Suho,
>>> >>> >>>
>>> >>> >>> This does not measure the ability to handle load. Basically,
>>> what we
>>> >>> >>> did
>>> >>> >>> for load testing earlier was send around 2M messages, with
>>> >>> >>> concurrency as
>>> >>> >>> high increasing from 100 - 1500 clients.
>>> >>> >>
>>> >>> >>
>>> >>> >> How many back end servers and client programs used for that?
>>> >>> >>
>>> >>> >>>
>>> >>> >>>
>>> >>> >>> Your test is a measure of being able to consistently handle a
>>> stream
>>> >>> >>> of
>>> >>> >>> messages, which IMO, maybe important but is less interesting when
>>> >>> >>> handling
>>> >>> >>> load.
>>> >>> >>
>>> >>> >>
>>> >>> >> This test has measured the one client one server. yes it can be
>>> >>> >> improved
>>> >>> >> to one client to many servers and many clients to many servers.
>>> >>> >>
>>> >>> >
>>> >>> > This test also covers sending messages from many clients (2,5,10 &
>>> 20)
>>> >>> > to
>>> >>> > one server.
>>> >>> > Yes it could be improved to many clients to many server.
>>> >>> > If there are any specific requirements please suggest me a
>>> scenario,
>>> >>> > then I
>>> >>> > can do the testing and present the findings.
>>> >>> >
>>> >>> > Thanks
>>> >>> > Suho
>>> >>> >
>>> >>> >> But this test gives the through put this can handle one client to
>>> >>> >> server.
>>> >>> >> For one client scenario whether you add messages with one thread
>>> or
>>> >>> >> many
>>> >>> >> threads does not effect the performance if there are enough
>>> messages
>>> >>> >> to
>>> >>> >> send.
>>> >>> >>
>>> >>> >> thanks,
>>> >>> >> Amila.
>>> >>> >>
>>> >>> >>>
>>> >>> >>> To truly test the ability to handle loads we need to do a
>>> distributed
>>> >>> >>> load test with an extremely high number of clients and see the
>>> >>> >>> breaking
>>> >>> >>> point. Earlier, we

Re: [Carbon-dev] Performance numbers of Agent Component

[Suhothayan Sriskandarajah]

According to the given requirements and suggestions I did two performance
tests for Agent Components.

For the first one, I sent messages from one client to 200 servers, here for
each server I first sent 1M messages to stabilize the system and then sent
anther 1M messages for each server to test the performance.
In this case, the client was sending 0.52M Events/Sec and each server was
processing about 2583 Events/Sec

I also tested by sending 10M messages from 200 clients to a single server.
To stabilize the follow I initially sent 1M Events and then monitored for
performance, here the server was able to handle 0.3M Events/Sec

Thanks
Suho

On Thu, Feb 9, 2012 at 7:20 PM, Tharindu Mathew  wrote:

> Hi Srinath,
>
> I wasn't thinking about doing multiple servers now itself. That would be
> impractical. We can just start by increasing the number of clients. Just
> using a thread pool and increasing the pool size would do...
>
> On Thu, Feb 9, 2012 at 2:32 PM, Srinath Perera  wrote:
>
>> Hi Tharindu,
>>
>> Agreed .. lets plan to find some HW and do this when we can (will need
>> at least 5 servers) .. I just want us not to be blocked on this.
>>
>> --Srinath
>>
>> On Thu, Feb 9, 2012 at 2:01 PM, Tharindu Mathew 
>> wrote:
>> > Not testing for load at start lead to problems earlier.
>> >
>> > Testing for 20 clients and 10 M messages is not the same for testing
>> for 500
>> > clients and 10 M messages. At this scale only, connection pooling,
>> caching
>> > and all of this matters. This is of course, many clients to one server,
>> a
>> > basic test that can be done easily.
>> >
>> > Anyway, we can post pone the testing to when we integrate BAM or CEP,
>> but
>> > please be aware of the implications. This was a situation where earlier
>> BAM
>> > was not scaling at all.
>> >
>> >
>> > On Thu, Feb 9, 2012 at 1:43 PM, Amila Suriarachchi 
>> wrote:
>> >>
>> >>
>> >>
>> >> On Thu, Feb 9, 2012 at 12:36 PM, Srinath Perera 
>> wrote:
>> >>>
>> >>> Hi Suho,
>> >>>
>> >>> IMHO this covers about 90% of our usecases .. I think we should move
>> on
>> >>
>> >>
>> >> we do not required to do an performance study. Since anyway we don't
>> have
>> >> proper CEP or BAM service to consume events.
>> >>
>> >> But need to test for once client many server scenario to test for
>> >> stability.
>> >>
>> >> thanks,
>> >> Amila.
>> >>
>> >>>
>> >>>
>> >>> I do not mind doing a larger perf study later .. ..
>> >>>
>> >>> but getting the server finished from siddhi side and releasing it, CEP
>> >>> perrf numbers,  and integrating this with BAM are more urget IMHO
>> >>>
>> >>> --Srinath
>> >>>
>> >>> On Thu, Feb 9, 2012 at 12:29 PM, Suhothayan Sriskandarajah
>> >>>  wrote:
>> >>> >
>> >>> >
>> >>> > On Thu, Feb 9, 2012 at 12:00 PM, Amila Suriarachchi > >
>> >>> > wrote:
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew <
>> thari...@wso2.com>
>> >>> >> wrote:
>> >>> >>>
>> >>> >>> Suho,
>> >>> >>>
>> >>> >>> This does not measure the ability to handle load. Basically, what
>> we
>> >>> >>> did
>> >>> >>> for load testing earlier was send around 2M messages, with
>> >>> >>> concurrency as
>> >>> >>> high increasing from 100 - 1500 clients.
>> >>> >>
>> >>> >>
>> >>> >> How many back end servers and client programs used for that?
>> >>> >>
>> >>> >>>
>> >>> >>>
>> >>> >>> Your test is a measure of being able to consistently handle a
>> stream
>> >>> >>> of
>> >>> >>> messages, which IMO, maybe important but is less interesting when
>> >>> >>> handling
>> >>> >>> load.
>> >>> >>
>> >>> >>
>> >>> >> This test has measured the one client one server. yes it can be
>> >>> >> improved
>> >>> >> to one client to many servers and many clients to many servers.
>> >>> >>
>> >>> >
>> >>> > This test also covers sending messages from many clients (2,5,10 &
>> 20)
>> >>> > to
>> >>> > one server.
>> >>> > Yes it could be improved to many clients to many server.
>> >>> > If there are any specific requirements please suggest me a scenario,
>> >>> > then I
>> >>> > can do the testing and present the findings.
>> >>> >
>> >>> > Thanks
>> >>> > Suho
>> >>> >
>> >>> >> But this test gives the through put this can handle one client to
>> >>> >> server.
>> >>> >> For one client scenario whether you add messages with one thread or
>> >>> >> many
>> >>> >> threads does not effect the performance if there are enough
>> messages
>> >>> >> to
>> >>> >> send.
>> >>> >>
>> >>> >> thanks,
>> >>> >> Amila.
>> >>> >>
>> >>> >>>
>> >>> >>> To truly test the ability to handle loads we need to do a
>> distributed
>> >>> >>> load test with an extremely high number of clients and see the
>> >>> >>> breaking
>> >>> >>> point. Earlier, we could not find such a point with a single
>> machine.
>> >>> >>>
>> >>> >>>
>> >>> >>> On Thu, Feb 9, 2012 at 11:31 AM, Suhothayan Sriskandarajah
>> >>> >>>  wrote:
>> >>> 
>> >>> 
>> >>> 
>> >>>  On Thu, Feb 9, 2012 at 11:24 AM, Amila Suriarachchi <
>> am...@wso2.com>
>> >>>  wrote:

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Supun Malinga]

On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma  wrote:

> Hi Azeez,
>
> Let me explain the rationale behind this orbit level change.
>
> If you look at the orbit project keeping Carbon aside, it can be
> considered as a third party project,  completely independent from Carbon
> and Graphite projects. The purpose of the orbit project is to produce OSGi
> bundles out of third party legacy jars.  So the orbit project is not
> related to Carbon or Graphite by any means. And also changes to these orbit
> projects is rare, unless we created them in a sloppy manner.  Ideally we
> can upload orbit projects and then developers do not need to build them at
> all.
>
> But, over the time we've missed used the orbit concept. e.g. we have orbit
> projects corresponding the dependencies projects. These orbits change
> frequently, since the corresponding dependencies change.
>
> By considering all these aspects, we came up with the following structure
>
> *orbit* (Consists of all the orbit projects which are used by both Carbon
> and Graphite projects.)
>
> *carbon*
> *|--* *dependencies*
>*|-- orbit* (These orbit projects produce bundles out of the Carbon
> level dependencies.)
>
> *graphite*
> *|-- dependencies*
>*|-- orbit*  (These orbit projects produce bundles out of the Graphite
> level dependencies.)
>
> Please let us know your views on this.
>

+1

thanks,

>
> Thanks,
> Sameera.
>
>
> On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez  wrote:
>
>> In this model,. what happens to dependencies & orbits that are common to
>> both Carbon & Graphite?
>>
>>
>> On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma wrote:
>>
>>> Hi Samisa,
>>>
>>> We have plans commit Pradeep's change in a hackathon mode. His changes
>>> is again platform wide change. We can get help from the AS and Jaggery team
>>> as well.
>>>
>>> Lets plan this during the todays meeting.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>>>


 On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:

>
>
> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>
>> And do we have Tomcat OSGi stuff in there now?
>>
>> No, not yet. Plan is to add them within next two days.
>

 Note that both AS and Jaggery are blocked on this.

 We have arrange a meeting too to discuss these today.

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


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Error while creating a Index with BAM

[Afkham Azeez]

Why not properly display a message which clearly states what you have
suggested below?

On Fri, Feb 10, 2012 at 5:30 PM, Buddhika Chamith wrote:

> Hi Srinath,
>
> You have to provide credentials at "Analyzer Framework" page before
> creating an index.
>
> Regards
> Buddhika
>
>
> On Fri, Feb 10, 2012 at 4:13 PM, Srinath Perera  wrote:
>
>> Got this while trying to create a Index with BAM server .. what is wrong?
>>
>> Can I do the same via configuration file ?
>>
>> org.wso2.carbon.bam.core.persistence.exceptions.ConfigurationException:
>> Credentials not valid or not supplied yet..
>>at
>> org.wso2.carbon.bam.analyzer.service.IndexMgtService.createIndex(IndexMgtService.java:299)
>>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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>at
>> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>> ___
>> 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*
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] NPE in event core - Stratos ESB trunk build

[Rajika Kumarasiri]

Exception in thread "pool-19-thread-7" java.lang.NullPointerException
at
org.wso2.carbon.event.core.internal.delivery.inmemory.InMemoryMatchingManager.getMatchingSubscriptions(InMemoryMatchingManager.java:54)
at
org.wso2.carbon.event.core.internal.delivery.inmemory.InMemoryDeliveryManager.publish(InMemoryDeliveryManager.java:100)
at
org.wso2.carbon.event.core.internal.EventPublisher.run(EventPublisher.java:56)
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:619)

I remember I sent the same NPE earlier as well.

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

Re: [Carbon-dev] Carbon Studio 2.0.0.M8

[Chathuri Wimalasena]

Hi Sumedha,

Updated the release notes.

Thanks and Regards,
Chathuri

On Sun, Feb 12, 2012 at 6:31 PM, Sumedha Rubasinghe wrote:

> Chathuri,
> Hosted release note[1]  still points to an old release note.
> /sumedha
>
> [1]
> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/release_notes.html
>
>
>
> On Fri, Feb 10, 2012 at 11:12 PM, Chathuri Wimalasena 
> wrote:
>
>> Hi All,
>>
>> We have Carbon Studio 2.0.0.M8 ready to be downloaded at [1].
>>
>> *New Features*
>>
>>- Merging branch and the CS trunk is completed for all the artifacts
>>that are available in CS 1.0.14
>>- Content assist to synapse configuration
>>- New editor to modify deploy paths specified for registry resources
>>- New editor to create deployable artifact for each and every artifact
>>- Export distribution projects as CARs within Eclipse as well as
>>using Maven
>>- Improved tree editor which is integrated with source view for DS
>>editor
>>- Syntax colouring
>>   - Sync changes done in the source view to the design view
>>   - Content assist
>>   - ESB graphical editor improvements
>>- Open Dashboard option at Eclipse Welcome page
>>   - This dashboard will point to a page where it lists all the
>>   projects that can be created with Carbon Studio which will allow
>>   users to create different artifacts from the dashboard
>>- Samples
>>- New categorization of features available at Carbon Studio
>>- Completed documentation [2]
>>
>> *Installation*
>>
>>- Offline installation is possible
>>- You can find the installation guide at [3]
>>
>>
>> Your feedbacks are most welcome !!! Please report all the jiras at [4]
>> and specify the version as 2.0.0.
>>
>> Thanks and Regards,
>> WSO2 Tooling Team
>>
>> [1]
>> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/wso2-carbon-studio_2.0.0.M8-SNAPSHOT.zip
>> [2]
>> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/
>> [3]
>> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/install_guide.html
>> [4] https://wso2.org/jira/browse/TOOLS
>>
>>
>>
>> --
>> Chathuri Wimalasena
>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>> email: chath...@wso2.com; phone: +94 772 608 596
>> blog: http://chathuriwimalasena.blogspot.com/
>>
>
>
>
> --
> /sumedha
> +94 773017743
>



-- 
Chathuri Wimalasena
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
email: chath...@wso2.com; phone: +94 772 608 596
blog: http://chathuriwimalasena.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Afkham Azeez]

Sounds good.

On Mon, Feb 13, 2012 at 9:28 AM, Sameera Jayasoma  wrote:

> Hi Azeez,
>
> Let me explain the rationale behind this orbit level change.
>
> If you look at the orbit project keeping Carbon aside, it can be
> considered as a third party project,  completely independent from Carbon
> and Graphite projects. The purpose of the orbit project is to produce OSGi
> bundles out of third party legacy jars.  So the orbit project is not
> related to Carbon or Graphite by any means. And also changes to these orbit
> projects is rare, unless we created them in a sloppy manner.  Ideally we
> can upload orbit projects and then developers do not need to build them at
> all.
>
> But, over the time we've missed used the orbit concept. e.g. we have orbit
> projects corresponding the dependencies projects. These orbits change
> frequently, since the corresponding dependencies change.
>
> By considering all these aspects, we came up with the following structure
>
> *orbit* (Consists of all the orbit projects which are used by both Carbon
> and Graphite projects.)
>
> *carbon*
> *|--* *dependencies*
>*|-- orbit* (These orbit projects produce bundles out of the Carbon
> level dependencies.)
>
> *graphite*
> *|-- dependencies*
>*|-- orbit*  (These orbit projects produce bundles out of the Graphite
> level dependencies.)
>
> Please let us know your views on this.
>
> Thanks,
> Sameera.
>
>
> On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez  wrote:
>
>> In this model,. what happens to dependencies & orbits that are common to
>> both Carbon & Graphite?
>>
>>
>> On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma wrote:
>>
>>> Hi Samisa,
>>>
>>> We have plans commit Pradeep's change in a hackathon mode. His changes
>>> is again platform wide change. We can get help from the AS and Jaggery team
>>> as well.
>>>
>>> Lets plan this during the todays meeting.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>>>


 On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:

>
>
> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>
>> And do we have Tomcat OSGi stuff in there now?
>>
>> No, not yet. Plan is to add them within next two days.
>

 Note that both AS and Jaggery are blocked on this.

 We have arrange a meeting too to discuss these today.

 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
>>
>>
>
>
> --
> 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] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sameera Jayasoma]

Hi Azeez,

Let me explain the rationale behind this orbit level change.

If you look at the orbit project keeping Carbon aside, it can be considered
as a third party project,  completely independent from Carbon and Graphite
projects. The purpose of the orbit project is to produce OSGi bundles out
of third party legacy jars.  So the orbit project is not related to Carbon
or Graphite by any means. And also changes to these orbit projects is rare,
unless we created them in a sloppy manner.  Ideally we can upload orbit
projects and then developers do not need to build them at all.

But, over the time we've missed used the orbit concept. e.g. we have orbit
projects corresponding the dependencies projects. These orbits change
frequently, since the corresponding dependencies change.

By considering all these aspects, we came up with the following structure

*orbit* (Consists of all the orbit projects which are used by both Carbon
and Graphite projects.)

*carbon*
*|--* *dependencies*
   *|-- orbit* (These orbit projects produce bundles out of the Carbon
level dependencies.)

*graphite*
*|-- dependencies*
   *|-- orbit*  (These orbit projects produce bundles out of the Graphite
level dependencies.)

Please let us know your views on this.

Thanks,
Sameera.


On Mon, Feb 13, 2012 at 9:04 AM, Afkham Azeez  wrote:

> In this model,. what happens to dependencies & orbits that are common to
> both Carbon & Graphite?
>
>
> On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma wrote:
>
>> Hi Samisa,
>>
>> We have plans commit Pradeep's change in a hackathon mode. His changes is
>> again platform wide change. We can get help from the AS and Jaggery team as
>> well.
>>
>> Lets plan this during the todays meeting.
>>
>> Thanks,
>> Sameera.
>>
>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>>>


 On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:

> And do we have Tomcat OSGi stuff in there now?
>
> No, not yet. Plan is to add them within next two days.

>>>
>>> Note that both AS and Jaggery are blocked on this.
>>>
>>> We have arrange a meeting too to discuss these today.
>>>
>>> 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
>
>


-- 
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] carbon-kernel:bamboo job

[Pradeep Fernando]

yes, that should solve the problem.

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

Re: [Carbon-dev] carbon-kernel:bamboo job

[Charith Wickramarachchi]

On Mon, Feb 13, 2012 at 7:17 AM, Pradeep Fernando  wrote:

> Hi Charith/Shammi,
>
> There is a integration test failure @ carbon-kernel. But we (sameera,me)
> can't reproduce it locally. Feel like, something wrong with bamboo build
> env. Maybe Ports issue (?)
>
> Can you guys have a look ?
>


This was caused by a Test Failure where in that test it tries to start a
carbon server and login. When i checked the running carbon processors,
There were lot of processing running which where started by the reporting
build.
I killed all the processors and triggered a new build adding Carbon server
process shutdown script to the job.


Lets see..


thanks,
Charith




>
> thanks,
> --Pradeep
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Kathiravelu Pradeeban]

Currently [1] lists the below,

   - .. 
   - carbon/ 
   - commons/ 
   - graphite/ 
   - interop/ 
   - orbit/ 
   - ozone/ 
   - stratos/ 
   - tools/ 
   - wsf/ 


It is somewhat misleading in the importance scale and a bit more difficult
in checking out.
Presence of ozone, stratos, and wsf here are somewhat confusing, at least
for me.
If someone wants to have a one-checkout of all from [1], he will be
checking out unrelated stuff like the above I mentioned.

We might need a bit of clean up in [1], I feel.

[1] https://svn.wso2.org/repos/wso2/trunk/

Regards,
Pradeeban.

On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> We have now completed the SVN restructure effort. Please checkout
> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
> the following instructions before building.
>
> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
> repositories. Avoid using the existing local carbon checkout, if any.
> 2) Backup your .m2 repository and start the build with a fresh one. This
> step is optional.
> 3) Build orbit[1] project.
> 4) Build carbon[2] project.
> 5) Build graphite[3] project.
>
> Apart from some test failures, build is stable now.
>
> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
> this done during the past two days.
>
> Thanks,
> Sameera.
>
> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/
> [2] https://svn.wso2.org/repos/wso2/trunk/carbon/
> [3] https://svn.wso2.org/repos/wso2/trunk/graphite/
>
> --
> 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
>
>


-- 
Kathiravelu Pradeeban.
Software Engineer.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Afkham Azeez]

In this model,. what happens to dependencies & orbits that are common to
both Carbon & Graphite?

On Mon, Feb 13, 2012 at 8:53 AM, Sameera Jayasoma  wrote:

> Hi Samisa,
>
> We have plans commit Pradeep's change in a hackathon mode. His changes is
> again platform wide change. We can get help from the AS and Jaggery team as
> well.
>
> Lets plan this during the todays meeting.
>
> Thanks,
> Sameera.
>
> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>>
>>>
>>>
>>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>>>
 And do we have Tomcat OSGi stuff in there now?

 No, not yet. Plan is to add them within next two days.
>>>
>>
>> Note that both AS and Jaggery are blocked on this.
>>
>> We have arrange a meeting too to discuss these today.
>>
>> 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

[Carbon-dev] [IMPORTANT] Re: Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sameera Jayasoma]

Hi Devs,

those who are still working on the old carbon trunk, please migrate to the
new SVN repositories. Otherwise, you will face problems when trying commit
your changes.

Thanks,
Sameera.

On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> We have now completed the SVN restructure effort. Please checkout
> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
> the following instructions before building.
>
> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
> repositories. Avoid using the existing local carbon checkout, if any.
> 2) Backup your .m2 repository and start the build with a fresh one. This
> step is optional.
> 3) Build orbit[1] project.
> 4) Build carbon[2] project.
> 5) Build graphite[3] project.
>
> Apart from some test failures, build is stable now.
>
> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
> this done during the past two days.
>
> Thanks,
> Sameera.
>
> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/
> [2] https://svn.wso2.org/repos/wso2/trunk/carbon/
> [3] https://svn.wso2.org/repos/wso2/trunk/graphite/
>
> --
> 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
>



-- 
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] Carbon Trunk is Frozen for Commits from 1.00pm IST on 12th Jan, 2012

[Sameera Jayasoma]

Hi Azeez,

I've explain the process of building in another mail. The subject is "Orbit,
Carbon and Graphite - New Face of Carbon SVN Repository."

Orbit, Carbon and Graphite are three separate top level projects. I am not
sure whether we can have one-checkout one-build across all three projects.

Thanks,
Sameera.

On Mon, Feb 13, 2012 at 8:53 AM, Afkham Azeez  wrote:

> What is the process of building now? Do we still have one checkout-one
> build?
>
> On Mon, Feb 13, 2012 at 12:29 AM, Sameera Jayasoma wrote:
>
>>
>>
>> On Sun, Feb 12, 2012 at 12:09 PM, Sameera Jayasoma wrote:
>>
>>> Hi Devs,
>>>
>>> Please note the subject. We will let you know, once the
>>> svn restructuring process is over.
>>>
>>
>> Carbon trunk is unfrozen now.
>>
>> Thanks,
>> Sameera.
>>
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> 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
>
>


-- 
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] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sameera Jayasoma]

Hi Samisa,

We have plans commit Pradeep's change in a hackathon mode. His changes is
again platform wide change. We can get help from the AS and Jaggery team as
well.

Lets plan this during the todays meeting.

Thanks,
Sameera.

On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>>
>>> And do we have Tomcat OSGi stuff in there now?
>>>
>>> No, not yet. Plan is to add them within next two days.
>>
>
> Note that both AS and Jaggery are blocked on this.
>
> We have arrange a meeting too to discuss these today.
>
> 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] Carbon Trunk is Frozen for Commits from 1.00pm IST on 12th Jan, 2012

[Afkham Azeez]

What is the process of building now? Do we still have one checkout-one
build?

On Mon, Feb 13, 2012 at 12:29 AM, Sameera Jayasoma  wrote:

>
>
> On Sun, Feb 12, 2012 at 12:09 PM, Sameera Jayasoma wrote:
>
>> Hi Devs,
>>
>> Please note the subject. We will let you know, once the svn restructuring
>> process is over.
>>
>
> Carbon trunk is unfrozen now.
>
> Thanks,
> Sameera.
>
>>
>> Thanks,
>> Sameera.
>>
>> --
>> 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
>>
>
>
>
> --
> 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] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sameera Jayasoma]

Hi Sanjiva,

Following is model we've been following. We have top level trunk, branches
and tags repositories.

https://svn.wso2.org/repos/wso2/trunk/
https://svn.wso2.org/repos/wso2/branches/
https://svn.wso2.org/repos/wso2/tags/

e.g. Previous Carbon project trunk, branch and tags were created as
following.

https://svn.wso2.org/repos/wso2/trunk/carbon/
https://svn.wso2.org/repos/wso2/branches/carbon/
https://svn.wso2.org/repos/wso2/tags/carbon/

We thought of following the same structure for these new orbit and graphite
projects.

I understand your point.  Lets have a discussion on this.

Thanks,
Sameera.


On Mon, Feb 13, 2012 at 5:04 AM, Sanjiva Weerawarana wrote:

> Hmmm is there a future step we need to take to make each of the repos into
> separate projects? That is:
>
> /repos/wso2/{orbit,carbon,graphite}/{trunk,branches,tags}
>
> I guess without that we still have to branch etc. all together. I guess
> this change is the one which is a lot more dramatic in terms of impact to
> support etc..
>
> Sanjiva.
>
> On Mon, Feb 13, 2012 at 5:00 AM, Sanjiva Weerawarana wrote:
>
>> Great job guys :). This will help tremendously as we go forward with
>> Carbon becoming more and more of a stable platform!
>>
>> Sanjiva.
>>
>> On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma wrote:
>>
>>> Hi Devs,
>>>
>>> We have now completed the SVN restructure effort. Please checkout
>>> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
>>> the following instructions before building.
>>>
>>> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
>>> repositories. Avoid using the existing local carbon checkout, if any.
>>> 2) Backup your .m2 repository and start the build with a fresh one. This
>>> step is optional.
>>> 3) Build orbit[1] project.
>>> 4) Build carbon[2] project.
>>> 5) Build graphite[3] project.
>>>
>>> Apart from some test failures, build is stable now.
>>>
>>> I would like to thank Pradeep, Dileepa and Chethiya for their help to
>>> get this done during the past two days.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/
>>> [2] https://svn.wso2.org/repos/wso2/trunk/carbon/
>>> [3] https://svn.wso2.org/repos/wso2/trunk/graphite/
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
>> 650 265 8311
>> blog: http://sanjiva.weerawarana.org/
>>
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
> ___
> 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] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Pradeep Fernando]

On Mon, Feb 13, 2012 at 8:32 AM, Samisa Abeysinghe  wrote:

> Invite was sent last Friday
>
> On Mon, Feb 13, 2012 at 7:58 AM, Pradeep Fernando wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando wrote:
>>
>>>
>>>
>>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>>>


 On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:

>
>
> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>
>> And do we have Tomcat OSGi stuff in there now?
>>
>> No, not yet. Plan is to add them within next two days.
>

 Note that both AS and Jaggery are blocked on this.

 We have arrange a meeting too to discuss these today.

>>>
>>> please have it 12 noon.
>>>
>>
>> after * 12 noon o
>>
>

my bad. sorry.

>
>>> thanks,
>>> --Pradeep
>>>
>>>
>>>
>>
>>
>> --
>> Pradeep Fernando
>> Software Engineer
>> WSO2 Inc; http://wso2.com/
>>
>> blog: http://pradeepfernando.blogspot.com/
>> m: +94776603662
>>
>> ___
>> 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
>
>


-- 
Pradeep Fernando
Software Engineer
WSO2 Inc; http://wso2.com/

blog: http://pradeepfernando.blogspot.com/
m: +94776603662
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Samisa Abeysinghe]

Invite was sent last Friday

On Mon, Feb 13, 2012 at 7:58 AM, Pradeep Fernando  wrote:

>
>
> On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>>>


 On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:

> And do we have Tomcat OSGi stuff in there now?
>
> No, not yet. Plan is to add them within next two days.

>>>
>>> Note that both AS and Jaggery are blocked on this.
>>>
>>> We have arrange a meeting too to discuss these today.
>>>
>>
>> please have it 12 noon.
>>
>
> after * 12 noon
>
>>
>> thanks,
>> --Pradeep
>>
>>
>>
>
>
> --
> Pradeep Fernando
> Software Engineer
> WSO2 Inc; http://wso2.com/
>
> blog: http://pradeepfernando.blogspot.com/
> m: +94776603662
>
> ___
> 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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Pradeep Fernando]

On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe  wrote:

>
>
> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>>
>>> And do we have Tomcat OSGi stuff in there now?
>>>
>>> No, not yet. Plan is to add them within next two days.
>>
>
> Note that both AS and Jaggery are blocked on this.
>
> We have arrange a meeting too to discuss these today.
>

please have it 12 noon.

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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Pradeep Fernando]

On Mon, Feb 13, 2012 at 7:57 AM, Pradeep Fernando  wrote:

>
>
> On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe wrote:
>
>>
>>
>> On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando wrote:
>>
>>>
>>>
>>> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>>>
 And do we have Tomcat OSGi stuff in there now?

 No, not yet. Plan is to add them within next two days.
>>>
>>
>> Note that both AS and Jaggery are blocked on this.
>>
>> We have arrange a meeting too to discuss these today.
>>
>
> please have it 12 noon.
>

after * 12 noon

>
> thanks,
> --Pradeep
>
>
>


-- 
Pradeep Fernando
Software Engineer
WSO2 Inc; http://wso2.com/

blog: http://pradeepfernando.blogspot.com/
m: +94776603662
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Samisa Abeysinghe]

On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando  wrote:

>
>
> On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe wrote:
>
>> And do we have Tomcat OSGi stuff in there now?
>>
>> No, not yet. Plan is to add them within next two days.
>

Note that both AS and Jaggery are blocked on this.

We have arrange a meeting too to discuss these today.

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

[Carbon-dev] carbon-kernel:bamboo job

[Pradeep Fernando]

Hi Charith/Shammi,

There is a integration test failure @ carbon-kernel. But we (sameera,me)
can't reproduce it locally. Feel like, something wrong with bamboo build
env. Maybe Ports issue (?)

Can you guys have a look ?

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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Pradeep Fernando]

On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe  wrote:

> And do we have Tomcat OSGi stuff in there now?
>
> No, not yet. Plan is to add them within next two days.

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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Samisa Abeysinghe]

And do we have Tomcat OSGi stuff in there now?

On Mon, Feb 13, 2012 at 6:50 AM, Pradeep Fernando  wrote:

>
>
> On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma wrote:
>
>> Hi Devs,
>>
>> We have now completed the SVN restructure effort. Please checkout
>> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
>> the following instructions before building.
>>
>> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
>> repositories. Avoid using the existing local carbon checkout, if any.
>> 2) Backup your .m2 repository and start the build with a fresh one. This
>> step is optional.
>> 3) Build orbit[1] project.
>> 4) Build carbon[2] project.
>> 5) Build graphite[3] project.
>>
>> Apart from some test failures, build is stable now.
>>
>> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
>> this done during the past two days.
>>
>
> and charith and shammi, for helping out with bamboo builds.
>
>
> ___
> 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

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Pradeep Fernando]

On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> We have now completed the SVN restructure effort. Please checkout
> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
> the following instructions before building.
>
> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
> repositories. Avoid using the existing local carbon checkout, if any.
> 2) Backup your .m2 repository and start the build with a fresh one. This
> step is optional.
> 3) Build orbit[1] project.
> 4) Build carbon[2] project.
> 5) Build graphite[3] project.
>
> Apart from some test failures, build is stable now.
>
> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
> this done during the past two days.
>

and charith and shammi, for helping out with bamboo builds.
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sanjiva Weerawarana]

Hmmm is there a future step we need to take to make each of the repos into
separate projects? That is:

/repos/wso2/{orbit,carbon,graphite}/{trunk,branches,tags}

I guess without that we still have to branch etc. all together. I guess
this change is the one which is a lot more dramatic in terms of impact to
support etc..

Sanjiva.

On Mon, Feb 13, 2012 at 5:00 AM, Sanjiva Weerawarana wrote:

> Great job guys :). This will help tremendously as we go forward with
> Carbon becoming more and more of a stable platform!
>
> Sanjiva.
>
> On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma wrote:
>
>> Hi Devs,
>>
>> We have now completed the SVN restructure effort. Please checkout
>> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
>> the following instructions before building.
>>
>> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
>> repositories. Avoid using the existing local carbon checkout, if any.
>> 2) Backup your .m2 repository and start the build with a fresh one. This
>> step is optional.
>> 3) Build orbit[1] project.
>> 4) Build carbon[2] project.
>> 5) Build graphite[3] project.
>>
>> Apart from some test failures, build is stable now.
>>
>> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
>> this done during the past two days.
>>
>> Thanks,
>> Sameera.
>>
>> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/
>> [2] https://svn.wso2.org/repos/wso2/trunk/carbon/
>> [3] https://svn.wso2.org/repos/wso2/trunk/graphite/
>>
>> --
>> 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
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
>
> Lean . Enterprise . Middleware
>



-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.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] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sanjiva Weerawarana]

Great job guys :). This will help tremendously as we go forward with Carbon
becoming more and more of a stable platform!

Sanjiva.

On Mon, Feb 13, 2012 at 12:25 AM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> We have now completed the SVN restructure effort. Please checkout
> orbit[1], carbon[2] and graphite[3] svn repositories. Carefully go through
> the following instructions before building.
>
> 1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
> repositories. Avoid using the existing local carbon checkout, if any.
> 2) Backup your .m2 repository and start the build with a fresh one. This
> step is optional.
> 3) Build orbit[1] project.
> 4) Build carbon[2] project.
> 5) Build graphite[3] project.
>
> Apart from some test failures, build is stable now.
>
> I would like to thank Pradeep, Dileepa and Chethiya for their help to get
> this done during the past two days.
>
> Thanks,
> Sameera.
>
> [1] https://svn.wso2.org/repos/wso2/trunk/orbit/
> [2] https://svn.wso2.org/repos/wso2/trunk/carbon/
> [3] https://svn.wso2.org/repos/wso2/trunk/graphite/
>
> --
> 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
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.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] Carbon Trunk is Frozen for Commits from 1.00pm IST on 12th Jan, 2012

[Sameera Jayasoma]

On Sun, Feb 12, 2012 at 12:09 PM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> Please note the subject. We will let you know, once the svn restructuring
> process is over.
>

Carbon trunk is unfrozen now.

Thanks,
Sameera.

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



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

[Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.

[Sameera Jayasoma]

Hi Devs,

We have now completed the SVN restructure effort. Please checkout orbit[1],
carbon[2] and graphite[3] svn repositories. Carefully go through the
following instructions before building.

1) Take fresh checkouts of the orbit[1], carbon[2] and graphite[3] svn
repositories. Avoid using the existing local carbon checkout, if any.
2) Backup your .m2 repository and start the build with a fresh one. This
step is optional.
3) Build orbit[1] project.
4) Build carbon[2] project.
5) Build graphite[3] project.

Apart from some test failures, build is stable now.

I would like to thank Pradeep, Dileepa and Chethiya for their help to get
this done during the past two days.

Thanks,
Sameera.

[1] https://svn.wso2.org/repos/wso2/trunk/orbit/
[2] https://svn.wso2.org/repos/wso2/trunk/carbon/
[3] https://svn.wso2.org/repos/wso2/trunk/graphite/

-- 
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] Carbon Studio 2.0.0.M8

[Sumedha Rubasinghe]

Chathuri,
Hosted release note[1]  still points to an old release note.
/sumedha

[1]
http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/release_notes.html


On Fri, Feb 10, 2012 at 11:12 PM, Chathuri Wimalasena wrote:

> Hi All,
>
> We have Carbon Studio 2.0.0.M8 ready to be downloaded at [1].
>
> *New Features*
>
>- Merging branch and the CS trunk is completed for all the artifacts
>that are available in CS 1.0.14
>- Content assist to synapse configuration
>- New editor to modify deploy paths specified for registry resources
>- New editor to create deployable artifact for each and every artifact
>- Export distribution projects as CARs within Eclipse as well as using
>Maven
>- Improved tree editor which is integrated with source view for DS
>editor
>- Syntax colouring
>   - Sync changes done in the source view to the design view
>   - Content assist
>   - ESB graphical editor improvements
>- Open Dashboard option at Eclipse Welcome page
>   - This dashboard will point to a page where it lists all the
>   projects that can be created with Carbon Studio which will allow
>   users to create different artifacts from the dashboard
>- Samples
>- New categorization of features available at Carbon Studio
>- Completed documentation [2]
>
> *Installation*
>
>- Offline installation is possible
>- You can find the installation guide at [3]
>
>
> Your feedbacks are most welcome !!! Please report all the jiras at [4] and
> specify the version as 2.0.0.
>
> Thanks and Regards,
> WSO2 Tooling Team
>
> [1]
> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/wso2-carbon-studio_2.0.0.M8-SNAPSHOT.zip
> [2]
> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/
> [3]
> http://builder1.us1.wso2.org/~carbonstudio/carbon-studio/2.0.0/M8/documentation/install_guide.html
> [4] https://wso2.org/jira/browse/TOOLS
>
>
>
> --
> Chathuri Wimalasena
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> email: chath...@wso2.com; phone: +94 772 608 596
> blog: http://chathuriwimalasena.blogspot.com/
>



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

Re: [Carbon-dev] Trouble with a RESTfull Axis2 Service

[KasunG Gajasinghe]

On Sun, Feb 12, 2012 at 3:52 PM, Nirmal Fernando  wrote:

> Hi Kasun,
>
> On Sun, Feb 12, 2012 at 3:30 PM, KasunG Gajasinghe wrote:
>
>> Hi,
>>
>> I believe ResponseTimeCalculator might not be the reason for this,
>> because it isn't the root cause most of the time in cases like this. The
>> stacktrace for the real cause has been swallowed by someone.
>>
>
> Yes, exactly! AFAIS the reason is Axis2 dispatchers can't find the correct
> operation mapping (mobile -> addMobileNumber), hence there's a null in
> message context object for axis operation.
>

This mapping indeed happens inside AS standalone. Analyze the SOAP message
via SOAP Tracer or tcpmon. Could there be any stratos specific reason to
have a different behavior?

And, one more thing. Rest samples takes ages (At least 3min+ ) to deploy.
So, just wait around 5-10 minutes to let the service deploy. [3] I've faced
this issue for a REST service I wrote. And, I'm seeing this in the provided
aar as well. The issue might be that it couldn't resolve xml.xsd. This
might not relate to you anyway.



>
>
>
>>
>> Saying that, I tried the very service in AS trunk pack standalone
>> version. It worked as expected though.
>>
>
> Oh...
>
>
>> ie. [1] worked as it should, and [2] worked fine too to my surprise.
>>
>
> [2] should work fine, it's SOAP based invocation!
>

Please see my last comment.


>
>
 But the same error you posted generated for me when there was ANOTHER user
>> with the same "user" id. So, that might be the case of you. Have you tried
>> with different users and see how it behave?
>>
>
> I tried with different users, still the same issue. Anyhow if that's the
> case I should get that same error when using [2], but I didn't.
>

I see. In the wsdl, outfault MobileNumberAlreadyExistsException is there
for addMobileNumber. Can't be certain because I don't have the source, but
I did faced the said issue. Seems Exception name is misleading though; it
should be UserAlreadyExistsException.


>
>
>> Since whttp:location="mobile" is defined as the location
>> for ref="tns:addMobileNumber", [1] is the correct POST url.
>>
>
> Not really, both are correct! [1] for REST based invocations!
>


Only one binding is defined (MobileDirectoryServiceHttpBinding) in the
wsdl. And, in there, location "mobile" is set for addMobileNumber
operation. So, does the /addMobileNumber is also exposed as an API even
when a different location is set? What did I miss?

--KasunG


>
>> [1] curl --data "user=test5&mobileNumber=1234" -X POST
>> https://127.0.0.1:9443/services/MobileDirectoryService/mobile -k
>>
>> [2] curl --data "user=test10&mobileNumber=1234" -X POST
>> https://127.0.0.1:9443/services/MobileDirectoryService/addMobileNumber -k
>>
>

[3]

osgi> [Warning] XMLSchema.xsd:91:110: schema_reference.4: Failed to read
schema document 'http://www.w3.org/2001/xml.xsd', because 1) could not find
the document; 2) the document could not be read; 3) the root element of the
document is not .
[Error] XMLSchema.xsd:260:36: src-resolve: Cannot resolve the name
'xml:lang' to a(n) 'attribute declaration' component.
[Error] XMLSchema.xsd:260:36: s4s-elt-invalid-content.1: The content of
'#AnonType_schema' is invalid.  Element 'attribute' is invalid, misplaced,
or occurs too often.
[Error] XMLSchema.xsd:1277:35: s4s-elt-invalid-content.1: The content of
'#AnonType_documentation' is invalid.  Element 'attribute' is invalid,
misplaced, or occurs too often.
Woden[Warning],0:0,WSDL522,Could not parse a schema imported from URL "
http://www.w3.org/2001/XMLSchema.xsd".,org.apache.ws.commons.schema.XmlSchemaException:Could
not evaluate Schema Definition. This Schema contains Schema Imports that
were not resolved
osgi> Woden[Warning],0:0,Description-1001,The targetNamespace '
http://axis2.apache.org' is not dereferencable.
[2012-02-12 15:09:44,035] DEBUG
{org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying
service group : MobileDirectoryService {super-tenant}
[2012-02-12 15:09:44,036] DEBUG
{org.wso2.carbon.core.persistence.ServiceGroupPersistenceManager} -
 Successfully retrieved resource for MobileDirectoryService Service Group
[2012-02-12 15:09:44,055] DEBUG
{org.wso2.carbon.core.persistence.ServiceGroupPersistenceManager} -  Added
new service group - MobileDirectoryService
[2012-02-12 15:09:44,056] DEBUG
{org.wso2.carbon.core.persistence.ServicePersistenceManager} -
 Successfully retrieved resource for MobileDirectoryService Service
[2012-02-12 15:09:44,057]  INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
service: MobileDirectoryService {super-tenant}
[2012-02-12 15:09:44,230] DEBUG
{org.wso2.carbon.core.persistence.ServicePersistenceManager} -  Added new
service - MobileDirectoryService
[2012-02-12 15:09:44,232]  INFO
{org.apache.axis2.deployment.DeploymentEngine} -  Deploying Web service:
MobileDirectoryService.aar -
file:/home/kasun/wso2/as/wso2as-4.5.0-SNAPSHOT-222012/repository/deployment/server/axis2services/MobileDirectoryService.aar

Re: [Carbon-dev] Trouble with a RESTfull Axis2 Service

[Nirmal Fernando]

Hi Kasun,

On Sun, Feb 12, 2012 at 3:30 PM, KasunG Gajasinghe  wrote:

> Hi,
>
> I believe ResponseTimeCalculator might not be the reason for this, because
> it isn't the root cause most of the time in cases like this. The stacktrace
> for the real cause has been swallowed by someone.
>

Yes, exactly! AFAIS the reason is Axis2 dispatchers can't find the correct
operation mapping (mobile -> addMobileNumber), hence there's a null in
message context object for axis operation.



>
> Saying that, I tried the very service in AS trunk pack standalone version.
> It worked as expected though.
>

Oh...


> ie. [1] worked as it should, and [2] worked fine too to my surprise.
>

[2] should work fine, it's SOAP based invocation!


> But the same error you posted generated for me when there was ANOTHER user
> with the same "user" id. So, that might be the case of you. Have you tried
> with different users and see how it behave?
>

I tried with different users, still the same issue. Anyhow if that's the
case I should get that same error when using [2], but I didn't.


> Since whttp:location="mobile" is defined as the location
> for ref="tns:addMobileNumber", [1] is the correct POST url.
>

Not really, both are correct! [1] for REST based invocations!

>
> [1] curl --data "user=test5&mobileNumber=1234" -X POST
> https://127.0.0.1:9443/services/MobileDirectoryService/mobile -k
>
> [2] curl --data "user=test10&mobileNumber=1234" -X POST
> https://127.0.0.1:9443/services/MobileDirectoryService/addMobileNumber -k
>
> Regards.
> --KasunG
>
> On Sun, Feb 12, 2012 at 11:10 AM, Hiranya Jayathilaka wrote:
>
>> Have you tried debugging into the  ResponseTimeCalculator? Should be
>> pretty easy to figure out what's wrong.
>>
>> Thanks,
>> Hiranya
>>
>> On Sun, Feb 12, 2012 at 10:21 AM, Nirmal Fernando wrote:
>>
>>> Hi All,
>>>
>>> I'm having a trouble to make work a RESTfull Axis2 Service ( which is
>>> worked a month back [1] ), in a trunk version and even in Axis2 1.6.1
>>> binary distribution.
>>> Related scenario is pasted at [2].
>>>
>>> Wonder what's wrong! Any help is highly appreciated.
>>>
>>> You can find the service attached at [1].
>>>
>>> [1] https://wso2.org/jira/browse/STRATOS-1971
>>>
>>> [2]
>>>
>>> nirmal@nirmal:/media/wso2/new-autoscaler$ curl --data
>>> "user=nirmal&mobileNumber=1234" -X POST
>>> https://127.0.0.1:9443/services/MobileDirectoryService/mobile -k
>>> Apache Tomcat/7.0.14 - Error
>>> report
>>> HTTP Status 500 - >> noshade="noshade">type Exception reportmessage
>>> description The server encountered an internal
>>> error () that prevented it from fulfilling this
>>> request.exception java.lang.NullPointerException
>>>
>>> org.wso2.carbon.statistics.internal.ResponseTimeCalculator.updateCurrentInvocationStatistic(ResponseTimeCalculator.java:120)
>>>
>>> org.wso2.carbon.statistics.internal.ResponseTimeCalculator.calculateResponseTimes(ResponseTimeCalculator.java:61)
>>>
>>> org.wso2.carbon.statistics.module.FaultHandler.updateStatistics(FaultHandler.java:151)
>>>
>>> org.wso2.carbon.statistics.module.FaultHandler.invoke(FaultHandler.java:50)
>>> org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>> org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
>>> org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:516)
>>>
>>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>>>
>>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>>>
>>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processFault(AxisServlet.java:857)
>>>
>>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processXMLRequest(AxisServlet.java:830)
>>>
>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:227)
>>>
>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:206)
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>
>>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>>>
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>>>
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(P

Re: [Carbon-dev] Trouble with a RESTfull Axis2 Service

[KasunG Gajasinghe]

Hi,

I believe ResponseTimeCalculator might not be the reason for this, because
it isn't the root cause most of the time in cases like this. The stacktrace
for the real cause has been swallowed by someone.

Saying that, I tried the very service in AS trunk pack standalone version.
It worked as expected though.
ie. [1] worked as it should, and [2] worked fine too to my surprise. But
the same error you posted generated for me when there was ANOTHER user with
the same "user" id. So, that might be the case of you. Have you tried with
different users and see how it behave?

Since whttp:location="mobile" is defined as the location
for ref="tns:addMobileNumber", [1] is the correct POST url.

[1] curl --data "user=test5&mobileNumber=1234" -X POST
https://127.0.0.1:9443/services/MobileDirectoryService/mobile -k

[2] curl --data "user=test10&mobileNumber=1234" -X POST
https://127.0.0.1:9443/services/MobileDirectoryService/addMobileNumber -k

Regards.
--KasunG

On Sun, Feb 12, 2012 at 11:10 AM, Hiranya Jayathilaka wrote:

> Have you tried debugging into the  ResponseTimeCalculator? Should be
> pretty easy to figure out what's wrong.
>
> Thanks,
> Hiranya
>
> On Sun, Feb 12, 2012 at 10:21 AM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> I'm having a trouble to make work a RESTfull Axis2 Service ( which is
>> worked a month back [1] ), in a trunk version and even in Axis2 1.6.1
>> binary distribution.
>> Related scenario is pasted at [2].
>>
>> Wonder what's wrong! Any help is highly appreciated.
>>
>> You can find the service attached at [1].
>>
>> [1] https://wso2.org/jira/browse/STRATOS-1971
>>
>> [2]
>>
>> nirmal@nirmal:/media/wso2/new-autoscaler$ curl --data
>> "user=nirmal&mobileNumber=1234" -X POST
>> https://127.0.0.1:9443/services/MobileDirectoryService/mobile -k
>> Apache Tomcat/7.0.14 - Error
>> report
>> HTTP Status 500 - > noshade="noshade">type Exception reportmessage
>> description The server encountered an internal
>> error () that prevented it from fulfilling this
>> request.exception java.lang.NullPointerException
>>
>> org.wso2.carbon.statistics.internal.ResponseTimeCalculator.updateCurrentInvocationStatistic(ResponseTimeCalculator.java:120)
>>
>> org.wso2.carbon.statistics.internal.ResponseTimeCalculator.calculateResponseTimes(ResponseTimeCalculator.java:61)
>>
>> org.wso2.carbon.statistics.module.FaultHandler.updateStatistics(FaultHandler.java:151)
>>
>> org.wso2.carbon.statistics.module.FaultHandler.invoke(FaultHandler.java:50)
>> org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
>> org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:516)
>>
>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>>
>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>>
>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processFault(AxisServlet.java:857)
>>
>> org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processXMLRequest(AxisServlet.java:830)
>>
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:227)
>>
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:206)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>>
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>>
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:164)
>> javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>> note The full stack trace of the root cause is
>> available in the Apache Tomcat/7.0.14 logs.> noshade="noshade">Apache Tomcat/7.0.14
>>
>>
>> nirmal@nirmal:/media/wso2/new-autoscaler$ curl --data
>> "user=nirmal&mobileNumber=1234" -X POST
>> https://127.0.0.1:9443/services/MobileDirectoryService/addMobileNumber -k
>> http://axis2.apache.org
>> ">
>> http://127.0.0.1:9763/services/MobileDirectoryService/mobile/nirmal
>>

[Carbon-dev] Adding Apache Amber as an orbit

[Thilina Buddhika]

Hi Folks,

We will be adding Apache Amber to Orbit for implementing OAuth 2.0 support
in trunk.  [I am holding the commit until the svn restructuring is done.]

Thanks,
Thilina
-- 
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

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