Re: [Carbon-dev] Shindig upgrading effort

2011-09-07 Thread Nuwan Bandara
On Thu, Sep 8, 2011 at 11:53 AM, Pradeep Fernando wrote: > Hi, > > if you are branching new versions of these projects in to dependencies, > make sure they are maven3 compatible. :) > yap already done :) > > thanks, > --Pradeep > -- *Thanks & Regards, Nuwan Bandara Senior Software Enginee

Re: [Carbon-dev] Shindig upgrading effort

2011-09-07 Thread Pradeep Fernando
Hi, if you are branching new versions of these projects in to dependencies, make sure they are maven3 compatible. :) thanks, --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Shindig upgrading effort

2011-09-07 Thread Nuwan Bandara
Hi all, I was working on upgrading shindig for last few weeks; and have almost completed the task. However I have not committed any of the changes to the trunk yet due to few concerns. The latest shindig made me to upgrade some of the orbit bundles [1] and that might effect their usages in other c

Re: [Carbon-dev] Invitation: [Group E] Deployment Synchronizer Code Review @ Thu Sep 8 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Srinath Perera
https://wso2.org/crucible/cru/COMPONENT-57 On Thu, Sep 8, 2011 at 10:54 AM, Hiranya Jayathilaka wrote: > We are going to start this in the lobby at 11am. All Group-E members, > please be present. > > Thanks, > Hiranya > > On Mon, Sep 5, 2011 at 12:40 PM, Hiranya Jayathilaka wrote: > >> more deta

Re: [Carbon-dev] Invitation: [Group E] Deployment Synchronizer Code Review @ Thu Sep 8 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Hiranya Jayathilaka
We are going to start this in the lobby at 11am. All Group-E members, please be present. Thanks, Hiranya On Mon, Sep 5, 2011 at 12:40 PM, Hiranya Jayathilaka wrote: > more details > ยป

[Carbon-dev] Updated Invitation: [Code Review] [Group D] Registry Indexing @ Fri Sep 9 10am - 11am (carbon-dev@wso2.org)

2011-09-07 Thread Janaka Ranabahu
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20110909T043000Z DTEND:20110909T053000Z DTSTAMP:20110908T050721Z ORGANIZER;CN=jan...@wso2.com:mailto:jan...@wso2.com UID:9n06sifo8n2nvmv9etsolng...@google.com ATTENDE

Re: [Carbon-dev] Invitation: [Code Review] [Group A] BAM Event Receiver @ Mon Sep 5 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Kasun Weranga
On Wed, Sep 7, 2011 at 7:29 PM, Tharindu Mathew wrote: > The nice thing was running find bugs showed this wrong use of double > checked locking. > > There is a lot we can learn by running find bugs, and this is one of those. > The link was also provided by find bugs. > +1 > > > On Wed, Sep 7,

Re: [Carbon-dev] Progress on CS Trunk

2011-09-07 Thread Chathuri Wimalasena
We are planing to do a M1 on 09/09/2011. Following items are pending for that. - adding artifacts organizing menu items - creating features - adding poms Regards, Chathuri On Wed, Sep 7, 2011 at 8:55 PM, Melan Nimesh wrote: > Hi All, > > Here is a progress update of the CS Trunk. > >

[Carbon-dev] Invitation: [Code Review] [Group D] Registry Indexing @ Thu Sep 8 10:30am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Janaka Ranabahu
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20110908T05Z DTEND:20110908T063000Z DTSTAMP:20110907T153442Z ORGANIZER;CN=jan...@wso2.com:mailto:jan...@wso2.com UID:9n06sifo8n2nvmv9etsolng...@google.com ATTENDE

[Carbon-dev] Progress on CS Trunk

2011-09-07 Thread Melan Nimesh
Hi All, Here is a progress update of the CS Trunk. At the moment, we have completed about 9 artifacts and there are about 11 more artifacts pending. completed artifacts wizards - BPEL - Data Services - WebApp - Proxy - Endpoint - Sequnce - Registry Resource - Axis2 -

Re: [Carbon-dev] Invitation: [Code Review] [Group A] BAM Event Receiver @ Mon Sep 5 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Senaka Fernando
On Wed, Sep 7, 2011 at 7:29 PM, Tharindu Mathew wrote: > The nice thing was running find bugs showed this wrong use of double > checked locking. Strong, +1. I found the same issue in Registry Indexing. Janaka please note. Thanks, Senaka. > There is a lot we can learn by running find bugs, an

Re: [Carbon-dev] Invitation: [Code Review] [Group A] BAM Event Receiver @ Mon Sep 5 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Tharindu Mathew
The nice thing was running find bugs showed this wrong use of double checked locking. There is a lot we can learn by running find bugs, and this is one of those. The link was also provided by find bugs. On Wed, Sep 7, 2011 at 7:19 PM, Senaka Fernando wrote: > Good one, > > You need to follow th

Re: [Carbon-dev] Invitation: [Code Review] [Group A] BAM Event Receiver @ Mon Sep 5 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Senaka Fernando
Good one, You need to follow the mechanism mentioned under, "Under the new Java Memory Model". Unless its volatile, there can be issues of ordering when it comes to multiple threads. Thanks, Senaka. On Wed, Sep 7, 2011 at 6:35 PM, Tharindu Mathew wrote: > The use of double checked locking was

Re: [Carbon-dev] Invitation: [Code Review] [Group A] BAM Event Receiver @ Mon Sep 5 11am - 12pm (carbon-dev@wso2.org)

2011-09-07 Thread Tharindu Mathew
The use of double checked locking was suggested during this code review. Here is why it doesn't work, and ways to make it work: http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html On Mon, Sep 5, 2011 at 10:36 PM, Tharindu Mathew wrote: > Hi Azeez, > > It did definitely happen

Re: [Carbon-dev] [Architecture] HTTP and Proxy Authenticators for Carbon

2011-09-07 Thread Senaka Fernando
Hi all, As discussed offline with Thilina, .* server name password .*

Re: [Carbon-dev] [Architecture] HTTP and Proxy Authenticators for Carbon

2011-09-07 Thread Senaka Fernando
Hi Thilina/Prabath, On Wed, Sep 7, 2011 at 12:26 PM, Senaka Fernando wrote: > > > On Wed, Sep 7, 2011 at 12:17 PM, Thilina Buddhika wrote: > >> >> >> On Wed, Sep 7, 2011 at 11:51 AM, Senaka Fernando wrote: >> >>> That's a choice we need to make; but this still is an Authenticator >>> (which is