[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #67 has FAILED. Change made by senaka.

2012-01-01 Thread Bamboo 

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #67 failed.
---
This build was triggered at the scheduled time of 12:00 PM
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-67/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 7733 tests passed.


--
Code Changes
--
senaka (118361):

>Fixing JIRA Issue CARBON-11365.

senaka (118362):

>Fixing JIRA issue CARBON-11909.

senaka (118360):

>Making it possible to override the default eventing handlers with custom ones.
>



--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Qpid in Trunk

2012-01-01 Thread Amila Suriarachchi 
On Sun, Jan 1, 2012 at 10:20 AM, Senaka Fernando  wrote:

> Hi Amila,
>
> On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi  wrote:
>
>>
>>
>> On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando  wrote:
>>
>>> Hi again,
>>>
>>> I was mistaken. In G-Reg 4.1.1, we have imported, event server, event
>>> common and qpid server features. In trunk, the feature imports in P2
>>> profile are the same.
>>
>>
>> For branch you need to have Qpid feature  and for trunk you can remove it.
>>
>
> Ok.
>
>>
>>
>>> Also after reading through r117481, its just a fix to the versions, and
>>> has no impact on this.
>>>
>>> So, it is not the feature imports but something else as it seems. Can
>>> you check?
>>>
>>
>> if you look at the event feature here[1] it does not include the qpid
>> feature. So if GReg getting it in the distribution it should be some other
>> problem. Please check from which feature GReg getting Qpid bundle.
>>
>
> In both branch and trunk, the Qpid feature is directly imported from the
> product's P2 profile. So, from what I understand, we have not gotten rid of
> the Qpid feature from trunk which is what we should be doing.
>

hi Senaka,

if the GRegs P2 profile import the Qpid feature, I am not sure why you want
me to look at it. What I am saying is it is not through event feature since
it does not import that.


>
> Also, I just tried out eventing on trunk and it is not working. Have you
> made any changes to the code or the way it works? I'm getting,
>
> 
> ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} -  Can not
> send the notification
> org.wso2.carbon.event.core.exception.EventBrokerException: Event
> dispatcher with name /registry/notifications is not exists
>

this dispatcher should register from some registry code. Please check
whether it is working.

thanks,
Amila.


> at
> org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59)
> at
> org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 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)
> 
>
> The code in the registry eventing component is identical in branch and
> trunk, so I believe that this is directly related to something in the event
> component. So, in addition to getting rid of Qpid what should I do?
>
> Thanks,
> Senaka.
>
>>
>> thanks,
>> Amila.
>>
>> [1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando wrote:
>>>
 Hi Amila,

 I found this in G-Reg (checked ESB and it seems to be ok - not sure
 about other products), and yes the Qpid feature is not excluded. I believe
 that r117481 did not make it to the trunk. I will fix this and commit.

 Thanks,
 Senaka.


 On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi wrote:

>
>
> On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando wrote:
>
>> Hi Amila,
>>
>> I believe that it was decided to get rid of the embedded Qpid Broker
>> from products, which was done on the 3.2.x branch. Now when starting the
>> servers on the trunk I see Qpid is still hanging around. Any reason to 
>> why
>> this was not removed from trunk?
>>
>
> What is the product? Can you please check whether the product has
> explicitly imported that?
>
> thanks
> Amila.
>
>>
>> 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
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
>


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

Re: [Carbon-dev] Qpid in Trunk

2012-01-01 Thread Amila Suriarachchi 
On Sun, Jan 1, 2012 at 10:20 AM, Senaka Fernando  wrote:

> Hi Amila,
>
> On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi  wrote:
>
>>
>>
>> On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando  wrote:
>>
>>> Hi again,
>>>
>>> I was mistaken. In G-Reg 4.1.1, we have imported, event server, event
>>> common and qpid server features. In trunk, the feature imports in P2
>>> profile are the same.
>>
>>
>> For branch you need to have Qpid feature  and for trunk you can remove it.
>>
>
> Ok.
>
>>
>>
>>> Also after reading through r117481, its just a fix to the versions, and
>>> has no impact on this.
>>>
>>> So, it is not the feature imports but something else as it seems. Can
>>> you check?
>>>
>>
>> if you look at the event feature here[1] it does not include the qpid
>> feature. So if GReg getting it in the distribution it should be some other
>> problem. Please check from which feature GReg getting Qpid bundle.
>>
>
> In both branch and trunk, the Qpid feature is directly imported from the
> product's P2 profile. So, from what I understand, we have not gotten rid of
> the Qpid feature from trunk which is what we should be doing.
>

you still have Qpid feature imported here[1]. Please remove it.

thanks,
Amila.

[1]
https://svn.wso2.org/repos/wso2/trunk/carbon/products/greg/modules/p2-profile-gen/product/pom.xml


>
> Also, I just tried out eventing on trunk and it is not working. Have you
> made any changes to the code or the way it works? I'm getting,
>
> 
> ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} -  Can not
> send the notification
> org.wso2.carbon.event.core.exception.EventBrokerException: Event
> dispatcher with name /registry/notifications is not exists
> at
> org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59)
> at
> org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 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)
> 
>
> The code in the registry eventing component is identical in branch and
> trunk, so I believe that this is directly related to something in the event
> component. So, in addition to getting rid of Qpid what should I do?
>
> Thanks,
> Senaka.
>
>>
>> thanks,
>> Amila.
>>
>> [1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando wrote:
>>>
 Hi Amila,

 I found this in G-Reg (checked ESB and it seems to be ok - not sure
 about other products), and yes the Qpid feature is not excluded. I believe
 that r117481 did not make it to the trunk. I will fix this and commit.

 Thanks,
 Senaka.


 On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi wrote:

>
>
> On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando wrote:
>
>> Hi Amila,
>>
>> I believe that it was decided to get rid of the embedded Qpid Broker
>> from products, which was done on the 3.2.x branch. Now when starting the
>> servers on the trunk I see Qpid is still hanging around. Any reason to 
>> why
>> this was not removed from trunk?
>>
>
> What is the product? Can you please check whether the product has
> explicitly imported that?
>
> thanks
> Amila.
>
>>
>> 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
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
>


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


>>>
>>>
>>> --
>>> *Senaka Fernando*
>>> Product Manager - WSO2 Governance Registry;
>>> Associate Technical Lea

Re: [Carbon-dev] Qpid in Trunk

2012-01-01 Thread Senaka Fernando 
Hi Amila,

Sorry it was a busy day, :-). I fixed it then and there but just finished
testing this after building the whole thing. After removing the Qpid
feature both the issues are solved. This is committed in r118367.

Thanks,
Senaka.

On Sun, Jan 1, 2012 at 2:46 PM, Amila Suriarachchi  wrote:

>
>
> On Sun, Jan 1, 2012 at 10:20 AM, Senaka Fernando  wrote:
>
>> Hi Amila,
>>
>> On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando wrote:
>>>
 Hi again,

 I was mistaken. In G-Reg 4.1.1, we have imported, event server, event
 common and qpid server features. In trunk, the feature imports in P2
 profile are the same.
>>>
>>>
>>> For branch you need to have Qpid feature  and for trunk you can remove
>>> it.
>>>
>>
>> Ok.
>>
>>>
>>>
 Also after reading through r117481, its just a fix to the versions, and
 has no impact on this.

 So, it is not the feature imports but something else as it seems. Can
 you check?

>>>
>>> if you look at the event feature here[1] it does not include the qpid
>>> feature. So if GReg getting it in the distribution it should be some other
>>> problem. Please check from which feature GReg getting Qpid bundle.
>>>
>>
>> In both branch and trunk, the Qpid feature is directly imported from the
>> product's P2 profile. So, from what I understand, we have not gotten rid of
>> the Qpid feature from trunk which is what we should be doing.
>>
>
> you still have Qpid feature imported here[1]. Please remove it.
>
> thanks,
> Amila.
>
> [1]
> https://svn.wso2.org/repos/wso2/trunk/carbon/products/greg/modules/p2-profile-gen/product/pom.xml
>
>
>>
>> Also, I just tried out eventing on trunk and it is not working. Have you
>> made any changes to the code or the way it works? I'm getting,
>>
>> 
>> ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} -  Can not
>> send the notification
>> org.wso2.carbon.event.core.exception.EventBrokerException: Event
>> dispatcher with name /registry/notifications is not exists
>> at
>> org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59)
>> at
>> org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> 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)
>> 
>>
>> The code in the registry eventing component is identical in branch and
>> trunk, so I believe that this is directly related to something in the event
>> component. So, in addition to getting rid of Qpid what should I do?
>>
>> Thanks,
>> Senaka.
>>
>>>
>>> thanks,
>>> Amila.
>>>
>>> [1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event
>>>

 Thanks,
 Senaka.


 On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando wrote:

> Hi Amila,
>
> I found this in G-Reg (checked ESB and it seems to be ok - not sure
> about other products), and yes the Qpid feature is not excluded. I believe
> that r117481 did not make it to the trunk. I will fix this and commit.
>
> Thanks,
> Senaka.
>
>
> On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi wrote:
>
>>
>>
>> On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando wrote:
>>
>>> Hi Amila,
>>>
>>> I believe that it was decided to get rid of the embedded Qpid Broker
>>> from products, which was done on the 3.2.x branch. Now when starting the
>>> servers on the trunk I see Qpid is still hanging around. Any reason to 
>>> why
>>> this was not removed from trunk?
>>>
>>
>> What is the product? Can you please check whether the product has
>> explicitly imported that?
>>
>> thanks
>> Amila.
>>
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Amila Suriarachchi*
>>
>> Software Architect
>> WSO2 Inc. ; http://wso2.com
>> lean . enterprise . middleware
>>
>> phone : +94 71 3082805
>>
>>
>
>
> --
> *Senaka Fernando*
> Product

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #68 has FAILED. Change made by senaka and buddhikac.

2012-01-01 Thread Bamboo 

---
WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #68 failed.
---
This build was triggered at the scheduled time of 12:00 AM
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-68/


--
Failing Jobs
--
  - WSO2 Carbon Trunk Build Process (Default Stage): 7733 tests passed.


--
Code Changes
--
buddhikac (118366):

>Switching to new persistence layer.
>

buddhikac (118364):

>Switching analyzers to new persistence layer.
>

buddhikac (118365):

>Adding BAM database ui for defining indexes. 
>



--
This message is automatically generated by Atlassian Bamboo___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] How we broke the build in 2011 :-)

2012-01-01 Thread Prabath Siriwardena 
Welcome back folks, after the vacation - and wish you all very happy
new year...!!!

[1] lists all possible ways how we broke the build in 2011 :-) Please
take two minutes go through them...

It's boring to break the build in the same way we did in 2011 - so
let's not repeat them - if you find much innovative ways - please
update [1] :-)

Thanks everyone who contributed to build the list...

Thanks & regards,
-Prabath

[1]: 
https://docs.google.com/a/wso2.com/document/d/1Cuj62jX8nA2bcZSDEpfIp72fF6ts9_7ASyChkARgOcw/edit

-- Forwarded message --
From: Prabath Siriwardena 
Date: Thu, Dec 8, 2011 at 9:12 AM
Subject: How we break the build..? :-)
To: carbon-dev-group 


Nothing serious.. just for fun.. following are few ways how we did
break the build in the past.. :-) Please add whatever you remember how
you or your colleague broke the build... No names please

1. Changed a public API, built the components in my product and committed
2. Added a new method to an interface - updated it's implementation in
my product and committed - forgot to send mail to carbon-dev on the
interface change
3. Added new class - builds fine locally - committed all the other
changes - forgot to commit the new file
4. Added new a component - added a new feature - committed both -
updated the root pom of features - but, forgot to update the root pom
of components
5. Added a new dependency to the pom of my component - did some code
changes - did an svn stat from ../src - committed all code changes -
missed the pom with the new dependency

Let's build this list.. :)

--
Thanks & Regards,
Prabath

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


-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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] TestNG migration : Which API is preferred ?

2012-01-01 Thread Subash Chaturanga 
Hi Azeez,

When migrating to TestNG from JUnit, there are slight changes in the APIs
(in Assertions). I have already started re-factoring most of them.
But I just saw that there is an alternative JUnit compatible
testng.AssertJUnit class. Which one is preferred ?
(As we're completely moving away from JUnit, I thought of using the pure
org.testng.Assert class and re-factor our tests accordingly).

WDYT ?

Thanks
/subash
-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] TestNG migration : Which API is preferred ?

2012-01-01 Thread Afkham Azeez 
Use

import static org.testng.Assert.*

Don't use the JUnit stuff. Just migrate the Junit stuff. Putting an import
static will fix the compilation errors.

On Mon, Jan 2, 2012 at 12:01 PM, Subash Chaturanga  wrote:

> Hi Azeez,
>
> When migrating to TestNG from JUnit, there are slight changes in the APIs
> (in Assertions). I have already started re-factoring most of them.
> But I just saw that there is an alternative JUnit compatible
> testng.AssertJUnit class. Which one is preferred ?
> (As we're completely moving away from JUnit, I thought of using the pure
> org.testng.Assert class and re-factor our tests accordingly).
>
> WDYT ?
>
> Thanks
> /subash
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 
*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] TestNG migration : Which API is preferred ?

2012-01-01 Thread Subash Chaturanga 
On Mon, Jan 2, 2012 at 12:15 PM, Afkham Azeez  wrote:

> Use
>
> import static org.testng.Assert.*
>

+1

>
> Don't use the JUnit stuff. Just migrate the Junit stuff. Putting an import
> static will fix the compilation errors.
>
>
> On Mon, Jan 2, 2012 at 12:01 PM, Subash Chaturanga wrote:
>
>> Hi Azeez,
>>
>> When migrating to TestNG from JUnit, there are slight changes in the APIs
>> (in Assertions). I have already started re-factoring most of them.
>> But I just saw that there is an alternative JUnit compatible
>> testng.AssertJUnit class. Which one is preferred ?
>> (As we're completely moving away from JUnit, I thought of using the pure
>> org.testng.Assert class and re-factor our tests accordingly).
>>
>> WDYT ?
>>
>> Thanks
>> /subash
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> *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*
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] New Features planned for IS - 4.0.0

2012-01-01 Thread Thilina Buddhika 
Hi Folks,

Following is the list of features planned for *IS - 4.0.0*.

https://wso2.org/jira/browse/IDENTITY-239 -  Adding OAuth 2.0 support - 1
month [implementing OAuth 2.0 support in IS and adapting it within the
platform for API authentication.] - Thilina

https://wso2.org/jira/browse/IDENTITY-240 - Implement XACML 3.0 support - 6
weeks [Implementing XACML 3.0 in the forked Sun-XACML source] - Asela

https://wso2.org/jira/browse/IDENTITY-241 - Implement Simple Cloud Identity
Management (SCIM) 1.0 support - 1 month - Hasini

https://wso2.org/jira/browse/IDENTITY-242 - Policy Distribution Component
for XACML PAP - 1 week - Prabath

https://wso2.org/jira/browse/IDENTITY-243 - Extension points to initiate
work-flows for privileged actions - 2 weeks - Hasini

Following tasks are related to *Carbon platform*.

https://wso2.org/jira/browse/CARBON-12094 - Migrate Rampart to WSS4J 1.6 -
1 month - AmilaJ

https://wso2.org/jira/browse/CARBON-12095 - Sender-Vouches support in STS
[Above task incorporates this.] - AmilaJ

https://wso2.org/jira/browse/CARBON-12092 - Re-factoring Secure Vault - 2
weeks - Manjula


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

[Carbon-dev] Axis2 version in trunk.

2012-01-01 Thread Ajith Vitharana 
Hi All ,

Component root pom has following properties as axis2 versions .

 1.6.1.wso2v1
 1.6.1-wso2v1

Those version numbers should be correct as 1.6.1-wso2v4.

-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Axis2 version in trunk.

2012-01-01 Thread Sameera Jayasoma 
Hi Ajith,

Are there any usages of these properties? We should be using the properties
in the carbon-platform pom.

Thanks,
Sameera.


On Mon, Jan 2, 2012 at 12:51 PM, Ajith Vitharana  wrote:

>
> Hi All ,
>
> Component root pom has following properties as axis2 versions .
>
>  1.6.1.wso2v1
>  1.6.1-wso2v1
>
> Those version numbers should be correct as 1.6.1-wso2v4.
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>
> ___
> 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] Axis2 version in trunk.

2012-01-01 Thread Supun Malinga 
On Mon, Jan 2, 2012 at 1:11 PM, Sameera Jayasoma  wrote:

> Hi Ajith,
>
> Are there any usages of these properties? We should be using the
> properties in the carbon-platform pom.
>
+1, We should move all version properties to root pom.

>
> Thanks,
> Sameera.
>
>
> On Mon, Jan 2, 2012 at 12:51 PM, Ajith Vitharana  wrote:
>
>>
>> Hi All ,
>>
>> Component root pom has following properties as axis2 versions .
>>
>>  1.6.1.wso2v1
>>  1.6.1-wso2v1
>>
>> Those version numbers should be correct as 1.6.1-wso2v4.
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94714631794
>>
>>
>>
>> ___
>> 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