Re: [Dev] Build Error - 4.0.7 patch release

[Buddhika Chamith]

Looking in to this.

Regards
Buddhika

On Mon, Jan 28, 2013 at 12:15 PM, Hasini Gunasinghe  wrote:

> I got a test failure at following component.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
> project org.wso2.carbon.databridge.persistence.cassandra: There are test
> failures.
> [ERROR]
> [ERROR] Please refer to
> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/branches/4.0.0/components/data-bridge/org.wso2.carbon.databridge.persistence.cassandra/4.0.7/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
>
> Thanks,
> Hasini.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build Error - 4.0.7 patch release

[Hasini Gunasinghe]

I got a test failure at following component.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on
project org.wso2.carbon.databridge.persistence.cassandra: There are test
failures.
[ERROR]
[ERROR] Please refer to
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/branches/4.0.0/components/data-bridge/org.wso2.carbon.databridge.persistence.cassandra/4.0.7/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command

Thanks,
Hasini.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS 4.1.0-M2 pack for testing

[Dinuka Malalanayake]

Hi All,

I'll stop the IS testing due to QA patch queue,
once it's finished I'll continue the testing on IS release.


On Thu, Jan 24, 2013 at 9:47 AM, Dulanja Liyanage  wrote:

> Hi,
>
> Please find the IS 4.1.0-M2 pack hosted at
> https://svn.wso2.org/repos/wso2/scratch/wso2is-4.1.0/M2/
>
>  This M2 pack newly includes:
> - SCIM Broker mode support
> - Extension for custom provisioning connectors
>
> Thanks & Regards,
>
> Dulanja Liyanage
> Senior Software Engineer - WSO2 Inc.
> Phone: +94776764717




-- 
Thanks,
Dinuka Malalanayake
*Software Engineer*, WSO2, Inc.; http://www.wso2.com,
*Linked In* : http://lk.linkedin.com/pub/dinuka-malalanayake/24/438/169
*Blog* : http://malalanayake.wordpress.com/
*Contact*  : 0772508354 , dinuka.malalanay...@gmail.com   *Skype *:
dinuka_malalanayake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #119 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #119 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-119/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154012):

>Moving data bridge test thrift  4.0.6 to 4.0.7.
>



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

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #130 has FAILED. Change made by buddhikac.

[Muhammed Shariq]

Hi Maheshika,

Again the build is failing because it cannot update .. it seems the working
copy is locked .. can we stop any plans that in progress and clean up the
working directory manually and try running bamboo .. ?! Wouldn't be a bad
idea to always clean before checking out ..

On Mon, Jan 28, 2013 at 7:39 AM, Bamboo  wrote:

>  [image: Failed]  WSO2 Carbon 
> 4.0.x› Platform
> 4.0.6  › 
> #130
> failed
>
> Changes by buddhikac 
>
> No failed tests found, a possible compilation error.
>Responsible No one is responsible for this build.
>Failing Jobs  Job
> Duration Tests[image: Failed]  Default 
> Job (Default
> Stage)  Unknown  No tests found  
> Logs|
> Artifacts  
> Code
> Changes   View
> full change details
> buddhikac 
> Moving data bridge receiver thrift 4.0.6 to 4.0.7.
>  154011 View Online 
> | Add 
> Comments
>
> This message was sent by Atlassian Bamboo .
>
> If you wish to stop receiving these emails edit your user 
> profileor notify
> your administrator .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks,
Shariq.
Phone: +94 777 202 225
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #131 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #131 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-131/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154012):

>Moving data bridge test thrift  4.0.6 to 4.0.7.
>



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Kernel 4.0.6 > #38 was SUCCESSFUL. Change made by nirmal.

[Bamboo]

---
WSO2 Carbon 4.0.x > Kernel 4.0.6 > #38 was successful.
---
This build occurred because it is a dependant of WCB001-ORB006-5.

http://wso2.org/bamboo/browse/WCB001-KER006-38/




--
Code Changes
--
nirmal (154179):

>committing Isuruh's patch for SPI-70



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

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Prabath Siriwardena]

Hi Ragu,

Can we have a chat on this around 2.30 PM today.. We also need Senaka and
Suresh there..

Thanks & regards,
-Prabath

On Mon, Jan 28, 2013 at 9:49 AM, Senaka Fernando  wrote:

> Hi Ragu,
>
> Well, I am referring to the OAuth feature and its UI and not IS
> specifically. Anybody can install and/or improve the OAuth feature, and it
> does not require any modification to IS nor it be done by the so called IS
> people, :). Having said that, my feeling is that #2 is more usable compared
> to #1 (considering SLive usage etc).
>
> Thanks,
> Senaka.
>
>
> On Mon, Jan 28, 2013 at 7:37 AM, Sriragu Arudsothy wrote:
>
>> There are two things:
>>
>> 1) As Suresh said we can do it as a complete OAuth tool which facilitates
>> the existing OAuth functionalities provided by the IS + We can write a
>> access token generation UI. This can be installable as what you said.
>>
>> 2) second option is as what senaka said, I just wanted to add one jsp
>> file(access token generation UI) + 2 test fields + one more button to the
>> existing OAuth component to make it complete.
>>
>> Both of the scenarios requires the same slot of work. Bz OAuth feature
>> provides upto certain level of functionality. But we wanted to know whether
>> the IS people will accept to improve the existing feature or they wants
>> this to be a separate feature.?
>>
>> bz IS  ship this with their product. some time they dont like to extend
>> the feature by default ...!
>>
>> I will talk to prabath. I m available tuesday evening. If any body from
>> Greg team have a chance to meet prabath pls ask him, and share it with this
>> mail.
>>
>>
>> On Sun, Jan 27, 2013 at 11:33 PM, Senaka Fernando wrote:
>>
>>> Hi Suresh,
>>>
>>> That might work, but I was thinking about something else actually. There
>>> is an OAuth UI that you get once you install the OAuth feature. This UI has
>>> everything a typical user requires (I mean a user with necessary privileges
>>> to see the details) to access an application secured with OAuth. However,
>>> it does not provide a button to generate or refresh an access token. So, I
>>> was thinking whether we could improve that UI to have this capability?
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sun, Jan 27, 2013 at 10:40 PM, Suresh Attanayaka wrote:
>>>
 Hi Senaka,

 On Sun, Jan 27, 2013 at 7:01 PM, Senaka Fernando wrote:

> Hi all,
>
> Two things.
>
> Ragu, first of all, for the moment, we should not block ourselves
> until any UI is made available for this since the approach explained by
> Suresh can be used to obtain the token.
>
> Suresh, though it is not a roadblock, we need some user interface to
> obtain and/or refresh the OAuth token. AM has this, but it is not a 
> generic
> component. To test or to try out things, curl might be useful, but we need
> something more usable so that users can make use of it.
>

 You mean something like a developer tool ? +1 on the idea. We can make
 it a UI component which can be downloaded and installed from the P2 as a
 tool.

 Thanks,
 -Suresh

>
> Thanks,
> Senaka.
>
> On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka wrote:
>
>> Hi,
>>
>> On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy 
>> wrote:
>>
>>> Another approach:
>>>
>>> To avoid writing an addition UI components to generate the Access
>>> token.
>>>
>>> We can just write a REST class to generate the access token and pass
>>> the client id, client secret, access token endpoint, encoded username,
>>> encoded password from the REST client. Inside the code I have to decode 
>>> the
>>> username and password.
>>>
>>
>> Yes, you can write a REST client to get the access token using the
>> password grant type.
>>
>>
>>> This will solve. WDYT?
>>>
>>> RAGU
>>>
>>> On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy >> > wrote:
>>>
 Yes you are right .

 The Greg' requirement is like this:

 Any REST client (ex: Chrome Advanced REST client) we just wanted to
 pass the Bearer token to get use of REST API.

 Currently we use the curl command to generate the access token. But
 we are not intended to have a REST web client with (Forms to enter the
 client id/ secret ...etc) and click a button to generate the access 
 token)

 Very brief: Greg team finalized that the client want to see the
 Accesstoken value, who has to use it straight away with Authorization
 header. For that we need to do the Access token generation UI. So any
 product in future if needs they can use it.

 How can I approach?

 Ragu.



 On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka >>> > wrote:

> Hi
>

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Senaka Fernando]

Hi Ragu,

Well, I am referring to the OAuth feature and its UI and not IS
specifically. Anybody can install and/or improve the OAuth feature, and it
does not require any modification to IS nor it be done by the so called IS
people, :). Having said that, my feeling is that #2 is more usable compared
to #1 (considering SLive usage etc).

Thanks,
Senaka.

On Mon, Jan 28, 2013 at 7:37 AM, Sriragu Arudsothy  wrote:

> There are two things:
>
> 1) As Suresh said we can do it as a complete OAuth tool which facilitates
> the existing OAuth functionalities provided by the IS + We can write a
> access token generation UI. This can be installable as what you said.
>
> 2) second option is as what senaka said, I just wanted to add one jsp
> file(access token generation UI) + 2 test fields + one more button to the
> existing OAuth component to make it complete.
>
> Both of the scenarios requires the same slot of work. Bz OAuth feature
> provides upto certain level of functionality. But we wanted to know whether
> the IS people will accept to improve the existing feature or they wants
> this to be a separate feature.?
>
> bz IS  ship this with their product. some time they dont like to extend
> the feature by default ...!
>
> I will talk to prabath. I m available tuesday evening. If any body from
> Greg team have a chance to meet prabath pls ask him, and share it with this
> mail.
>
>
> On Sun, Jan 27, 2013 at 11:33 PM, Senaka Fernando  wrote:
>
>> Hi Suresh,
>>
>> That might work, but I was thinking about something else actually. There
>> is an OAuth UI that you get once you install the OAuth feature. This UI has
>> everything a typical user requires (I mean a user with necessary privileges
>> to see the details) to access an application secured with OAuth. However,
>> it does not provide a button to generate or refresh an access token. So, I
>> was thinking whether we could improve that UI to have this capability?
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Sun, Jan 27, 2013 at 10:40 PM, Suresh Attanayaka wrote:
>>
>>> Hi Senaka,
>>>
>>> On Sun, Jan 27, 2013 at 7:01 PM, Senaka Fernando wrote:
>>>
 Hi all,

 Two things.

 Ragu, first of all, for the moment, we should not block ourselves until
 any UI is made available for this since the approach explained by Suresh
 can be used to obtain the token.

 Suresh, though it is not a roadblock, we need some user interface to
 obtain and/or refresh the OAuth token. AM has this, but it is not a generic
 component. To test or to try out things, curl might be useful, but we need
 something more usable so that users can make use of it.

>>>
>>> You mean something like a developer tool ? +1 on the idea. We can make
>>> it a UI component which can be downloaded and installed from the P2 as a
>>> tool.
>>>
>>> Thanks,
>>> -Suresh
>>>

 Thanks,
 Senaka.

 On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka wrote:

> Hi,
>
> On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy 
> wrote:
>
>> Another approach:
>>
>> To avoid writing an addition UI components to generate the Access
>> token.
>>
>> We can just write a REST class to generate the access token and pass
>> the client id, client secret, access token endpoint, encoded username,
>> encoded password from the REST client. Inside the code I have to decode 
>> the
>> username and password.
>>
>
> Yes, you can write a REST client to get the access token using the
> password grant type.
>
>
>> This will solve. WDYT?
>>
>> RAGU
>>
>> On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy 
>> wrote:
>>
>>> Yes you are right .
>>>
>>> The Greg' requirement is like this:
>>>
>>> Any REST client (ex: Chrome Advanced REST client) we just wanted to
>>> pass the Bearer token to get use of REST API.
>>>
>>> Currently we use the curl command to generate the access token. But
>>> we are not intended to have a REST web client with (Forms to enter the
>>> client id/ secret ...etc) and click a button to generate the access 
>>> token)
>>>
>>> Very brief: Greg team finalized that the client want to see the
>>> Accesstoken value, who has to use it straight away with Authorization
>>> header. For that we need to do the Access token generation UI. So any
>>> product in future if needs they can use it.
>>>
>>> How can I approach?
>>>
>>> Ragu.
>>>
>>>
>>>
>>> On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka 
>>> wrote:
>>>
 Hi

 On Sat, Jan 26, 2013 at 2:00 PM, Sriragu Arudsothy <
 srir...@wso2.com> wrote:

> Hai All,
>
>  Greg need the OAuth Access token to be produced in UI
> which should be a installable feature from Identity Server side 
> feature. At
> the moment once we installed

Re: [Dev] Do we allow creating roles without users?

[Janaka Ranabahu]

Hi,

Thanks Hasini. I've set the correct parameter value and It worked without
any issue.

Thanks,
Janaka


On Mon, Jan 28, 2013 at 9:16 AM, Hasini Gunasinghe  wrote:

> Hi Janaka,
>
> Based on the underlying LDAP user store, you need to configure  name="EmptyRolesAllowed">true accordingly.
> For eg: in embedded LDAP, we have changed the schema to allow empty roles.
> However, if you are connecting to an external LDAP, most of the time, empty
> roles are not allowed. So based, on that, you need to configure above
> property.
>
> Thanks,
> Hasini.
>
>
> On Mon, Jan 28, 2013 at 8:44 AM, Janaka Ranabahu  wrote:
>
>> Hi,
>>
>> Do we allow creating roles without any users, through the API? I went
>> through the org.wso2.carbon.user.api.UserStoreManager interface but could
>> not find anything related in the comments.
>>
>> I have noticed that API Manager components have added roles without any
>> users(in APIManagerComponent class).
>>
>> *manager.addRole(role, null, null);*
>>
>>  But this code failed when I tried to connect API Manager to
>> AppFactory(same LDAP). The exception says that we can not create a role
>> without a user.
>>
>> *Caused by: org.wso2.carbon.user.core.UserStoreException: Can not create
>> empty role. There should be at least one user for the role.*
>> * at
>> org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doAddRole(ReadWriteLDAPUserStoreManager.java:968)
>> *
>>
>> Therefore, I wan't to clarify whether it is possible to create roles
>> without users.
>>
>> Thanks,
>> Janaka
>>
>> --
>> Janaka Ranabahu
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile +94 718370861
>> Email : jan...@wso2.com
>> Blog : janakaranabahu.blogspot.com
>>
>
>


-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Do we allow creating roles without users?

[Hasini Gunasinghe]

Hi Janaka,

Based on the underlying LDAP user store, you need to configure true accordingly.
For eg: in embedded LDAP, we have changed the schema to allow empty roles.
However, if you are connecting to an external LDAP, most of the time, empty
roles are not allowed. So based, on that, you need to configure above
property.

Thanks,
Hasini.

On Mon, Jan 28, 2013 at 8:44 AM, Janaka Ranabahu  wrote:

> Hi,
>
> Do we allow creating roles without any users, through the API? I went
> through the org.wso2.carbon.user.api.UserStoreManager interface but could
> not find anything related in the comments.
>
> I have noticed that API Manager components have added roles without any
> users(in APIManagerComponent class).
>
> *manager.addRole(role, null, null);*
>
>  But this code failed when I tried to connect API Manager to
> AppFactory(same LDAP). The exception says that we can not create a role
> without a user.
>
> *Caused by: org.wso2.carbon.user.core.UserStoreException: Can not create
> empty role. There should be at least one user for the role.*
> * at
> org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doAddRole(ReadWriteLDAPUserStoreManager.java:968)
> *
>
> Therefore, I wan't to clarify whether it is possible to create roles
> without users.
>
> Thanks,
> Janaka
>
> --
> Janaka Ranabahu
> Senior Software Engineer
> WSO2 Inc.
>
> Mobile +94 718370861
> Email : jan...@wso2.com
> Blog : janakaranabahu.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #118 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #118 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-118/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154011):

>Moving data bridge receiver thrift 4.0.6 to 4.0.7.
>



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

[Dev] Do we allow creating roles without users?

[Janaka Ranabahu]

Hi,

Do we allow creating roles without any users, through the API? I went
through the org.wso2.carbon.user.api.UserStoreManager interface but could
not find anything related in the comments.

I have noticed that API Manager components have added roles without any
users(in APIManagerComponent class).

*manager.addRole(role, null, null);*

But this code failed when I tried to connect API Manager to AppFactory(same
LDAP). The exception says that we can not create a role without a user.

*Caused by: org.wso2.carbon.user.core.UserStoreException: Can not create
empty role. There should be at least one user for the role.*
* at
org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doAddRole(ReadWriteLDAPUserStoreManager.java:968)
*

Therefore, I wan't to clarify whether it is possible to create roles
without users.

Thanks,
Janaka

-- 
Janaka Ranabahu
Senior Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : jan...@wso2.com
Blog : janakaranabahu.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Sriragu Arudsothy]

There are two things:

1) As Suresh said we can do it as a complete OAuth tool which facilitates
the existing OAuth functionalities provided by the IS + We can write a
access token generation UI. This can be installable as what you said.

2) second option is as what senaka said, I just wanted to add one jsp
file(access token generation UI) + 2 test fields + one more button to the
existing OAuth component to make it complete.

Both of the scenarios requires the same slot of work. Bz OAuth feature
provides upto certain level of functionality. But we wanted to know whether
the IS people will accept to improve the existing feature or they wants
this to be a separate feature.?

bz IS  ship this with their product. some time they dont like to extend the
feature by default ...!

I will talk to prabath. I m available tuesday evening. If any body from
Greg team have a chance to meet prabath pls ask him, and share it with this
mail.

On Sun, Jan 27, 2013 at 11:33 PM, Senaka Fernando  wrote:

> Hi Suresh,
>
> That might work, but I was thinking about something else actually. There
> is an OAuth UI that you get once you install the OAuth feature. This UI has
> everything a typical user requires (I mean a user with necessary privileges
> to see the details) to access an application secured with OAuth. However,
> it does not provide a button to generate or refresh an access token. So, I
> was thinking whether we could improve that UI to have this capability?
>
> Thanks,
> Senaka.
>
>
> On Sun, Jan 27, 2013 at 10:40 PM, Suresh Attanayaka wrote:
>
>> Hi Senaka,
>>
>> On Sun, Jan 27, 2013 at 7:01 PM, Senaka Fernando  wrote:
>>
>>> Hi all,
>>>
>>> Two things.
>>>
>>> Ragu, first of all, for the moment, we should not block ourselves until
>>> any UI is made available for this since the approach explained by Suresh
>>> can be used to obtain the token.
>>>
>>> Suresh, though it is not a roadblock, we need some user interface to
>>> obtain and/or refresh the OAuth token. AM has this, but it is not a generic
>>> component. To test or to try out things, curl might be useful, but we need
>>> something more usable so that users can make use of it.
>>>
>>
>> You mean something like a developer tool ? +1 on the idea. We can make it
>> a UI component which can be downloaded and installed from the P2 as a tool.
>>
>>
>> Thanks,
>> -Suresh
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka wrote:
>>>
 Hi,

 On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy wrote:

> Another approach:
>
> To avoid writing an addition UI components to generate the Access
> token.
>
> We can just write a REST class to generate the access token and pass
> the client id, client secret, access token endpoint, encoded username,
> encoded password from the REST client. Inside the code I have to decode 
> the
> username and password.
>

 Yes, you can write a REST client to get the access token using the
 password grant type.


> This will solve. WDYT?
>
> RAGU
>
> On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy 
> wrote:
>
>> Yes you are right .
>>
>> The Greg' requirement is like this:
>>
>> Any REST client (ex: Chrome Advanced REST client) we just wanted to
>> pass the Bearer token to get use of REST API.
>>
>> Currently we use the curl command to generate the access token. But
>> we are not intended to have a REST web client with (Forms to enter the
>> client id/ secret ...etc) and click a button to generate the access 
>> token)
>>
>> Very brief: Greg team finalized that the client want to see the
>> Accesstoken value, who has to use it straight away with Authorization
>> header. For that we need to do the Access token generation UI. So any
>> product in future if needs they can use it.
>>
>> How can I approach?
>>
>> Ragu.
>>
>>
>>
>> On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka 
>> wrote:
>>
>>> Hi
>>>
>>> On Sat, Jan 26, 2013 at 2:00 PM, Sriragu Arudsothy >> > wrote:
>>>
 Hai All,

  Greg need the OAuth Access token to be produced in UI
 which should be a installable feature from Identity Server side 
 feature. At
 the moment once we installed the OAuth feature that produces upto 
 client
 id, client secret, auth endpoint, access endpoint details. But we need 
 the
 access token generation also as a UI components under the IS. I have 
 been
 given this task.

>>>
>>> Why do you need a UI to generate access tokens ? Theoretically the
>>> access token is a secrete which should be delivered directly to the
>>> client.
>>>
>>> Thanks,
>>>  -Suresh
>>>
>>>
 Currently the G-reg restapi cxf web app does not have any UI, we
 d

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #130 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #130 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-130/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154011):

>Moving data bridge receiver thrift 4.0.6 to 4.0.7.
>



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x - Nightly > Platform_4.0.6 > #17 has FAILED. Change made by 9 authors.

[Bamboo]

---
WSO2 Carbon 4.0.x - Nightly > Platform_4.0.6 > #17 failed.
---
This build occurred because it is a dependant of WCB002-NKER004-22.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB002-NPLA004-17/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
kasunw (154148):

>Adding BAM to the product build

kasunw (154170):

>Fixed BAM-1030

kasunw (154146):

>Added missing dependencies,components and features for BAM.



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #129 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #129 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-129/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154010):

>Moving data bridge receiver 4.0.6 to 4.0.7.
>



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #117 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #117 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-117/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154010):

>Moving data bridge receiver 4.0.6 to 4.0.7.
>



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #116 has FAILED. Change made by johann.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #116 failed.
---
Code has been updated by johann.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-116/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
johann (154009):

>Adding user profiles as composite feature



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x - Nightly > Kernel_4.0.6 > #22 was SUCCESSFUL

[Bamboo]

---
WSO2 Carbon 4.0.x - Nightly > Kernel_4.0.6 > #22 was successful.
---
This build occurred because it is a dependant of WCB002-NORB004-20.

http://wso2.org/bamboo/browse/WCB002-NKER004-22/





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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #128 has FAILED. Change made by johann.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #128 failed.
---
Code has been updated by johann.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-128/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
johann (154009):

>Adding user profiles as composite feature



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #127 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #127 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-127/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154007):

>Moving data bridge commons 4.0.6 to 4.0.7.
>



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #115 has FAILED. Change made by buddhikac.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #115 failed.
---
Code has been updated by buddhikac.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-115/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
buddhikac (154007):

>Moving data bridge commons 4.0.6 to 4.0.7.
>



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

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Senaka Fernando]

Hi Suresh,

That might work, but I was thinking about something else actually. There is
an OAuth UI that you get once you install the OAuth feature. This UI has
everything a typical user requires (I mean a user with necessary privileges
to see the details) to access an application secured with OAuth. However,
it does not provide a button to generate or refresh an access token. So, I
was thinking whether we could improve that UI to have this capability?

Thanks,
Senaka.

On Sun, Jan 27, 2013 at 10:40 PM, Suresh Attanayaka  wrote:

> Hi Senaka,
>
> On Sun, Jan 27, 2013 at 7:01 PM, Senaka Fernando  wrote:
>
>> Hi all,
>>
>> Two things.
>>
>> Ragu, first of all, for the moment, we should not block ourselves until
>> any UI is made available for this since the approach explained by Suresh
>> can be used to obtain the token.
>>
>> Suresh, though it is not a roadblock, we need some user interface to
>> obtain and/or refresh the OAuth token. AM has this, but it is not a generic
>> component. To test or to try out things, curl might be useful, but we need
>> something more usable so that users can make use of it.
>>
>
> You mean something like a developer tool ? +1 on the idea. We can make it
> a UI component which can be downloaded and installed from the P2 as a tool.
>
>
> Thanks,
> -Suresh
>
>>
>> Thanks,
>> Senaka.
>>
>> On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka wrote:
>>
>>> Hi,
>>>
>>> On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy wrote:
>>>
 Another approach:

 To avoid writing an addition UI components to generate the Access token.

 We can just write a REST class to generate the access token and pass
 the client id, client secret, access token endpoint, encoded username,
 encoded password from the REST client. Inside the code I have to decode the
 username and password.

>>>
>>> Yes, you can write a REST client to get the access token using the
>>> password grant type.
>>>
>>>
 This will solve. WDYT?

 RAGU

 On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy wrote:

> Yes you are right .
>
> The Greg' requirement is like this:
>
> Any REST client (ex: Chrome Advanced REST client) we just wanted to
> pass the Bearer token to get use of REST API.
>
> Currently we use the curl command to generate the access token. But we
> are not intended to have a REST web client with (Forms to enter the client
> id/ secret ...etc) and click a button to generate the access token)
>
> Very brief: Greg team finalized that the client want to see the
> Accesstoken value, who has to use it straight away with Authorization
> header. For that we need to do the Access token generation UI. So any
> product in future if needs they can use it.
>
> How can I approach?
>
> Ragu.
>
>
>
> On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka wrote:
>
>> Hi
>>
>> On Sat, Jan 26, 2013 at 2:00 PM, Sriragu Arudsothy 
>> wrote:
>>
>>> Hai All,
>>>
>>>  Greg need the OAuth Access token to be produced in UI which
>>> should be a installable feature from Identity Server side feature. At 
>>> the
>>> moment once we installed the OAuth feature that produces upto client id,
>>> client secret, auth endpoint, access endpoint details. But we need the
>>> access token generation also as a UI components under the IS. I have 
>>> been
>>> given this task.
>>>
>>
>> Why do you need a UI to generate access tokens ? Theoretically the
>> access token is a secrete which should be delivered directly to the
>> client.
>>
>> Thanks,
>>  -Suresh
>>
>>
>>> Currently the G-reg restapi cxf web app does not have any UI, we
>>> dont want any UIs in the webapp. We need some UI to generate the access
>>> token too from the IS side. This is our requirement.
>>>  delieverddelieverd
>>> Also we want to know how to get the Tenant ID of the person who
>>> belongs to the given access token ???
>>>
>>> Please provide the way to do? we dont want any UIs in our cxf
>>> webapp(REST API).
>>>
>>> Thanks!
>>> Sriragu
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Suresh Attanayake
>> Software Engineer; WSO2 Inc. http://wso2.com/
>> Blog : http://sureshatt.blogspot.com/
>> Twitter : https://twitter.com/sureshatt
>> LinkedIn : http://lk.linkedin.com/in/sureshatt
>> Mobile : +94755012060,+94770419136,+94710467976
>>
>
>

>>>
>>>
>>> --
>>> Suresh Attanayake
>>> Software Engineer; WSO2 Inc. http://wso2.com/
>>> Blog : http://sureshatt.blogspot.com/
>>> Twitter : https://twitter.com/sureshatt
>>> LinkedIn : http://lk.linkedin.com/in/sureshatt
>>> Mobile : +94755012060,+94770

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Suresh Attanayaka]

Hi Senaka,

On Sun, Jan 27, 2013 at 7:01 PM, Senaka Fernando  wrote:

> Hi all,
>
> Two things.
>
> Ragu, first of all, for the moment, we should not block ourselves until
> any UI is made available for this since the approach explained by Suresh
> can be used to obtain the token.
>
> Suresh, though it is not a roadblock, we need some user interface to
> obtain and/or refresh the OAuth token. AM has this, but it is not a generic
> component. To test or to try out things, curl might be useful, but we need
> something more usable so that users can make use of it.
>

You mean something like a developer tool ? +1 on the idea. We can make it a
UI component which can be downloaded and installed from the P2 as a tool.

Thanks,
-Suresh

>
> Thanks,
> Senaka.
>
> On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka wrote:
>
>> Hi,
>>
>> On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy wrote:
>>
>>> Another approach:
>>>
>>> To avoid writing an addition UI components to generate the Access token.
>>>
>>> We can just write a REST class to generate the access token and pass the
>>> client id, client secret, access token endpoint, encoded username, encoded
>>> password from the REST client. Inside the code I have to decode the
>>> username and password.
>>>
>>
>> Yes, you can write a REST client to get the access token using the
>> password grant type.
>>
>>
>>> This will solve. WDYT?
>>>
>>> RAGU
>>>
>>> On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy wrote:
>>>
 Yes you are right .

 The Greg' requirement is like this:

 Any REST client (ex: Chrome Advanced REST client) we just wanted to
 pass the Bearer token to get use of REST API.

 Currently we use the curl command to generate the access token. But we
 are not intended to have a REST web client with (Forms to enter the client
 id/ secret ...etc) and click a button to generate the access token)

 Very brief: Greg team finalized that the client want to see the
 Accesstoken value, who has to use it straight away with Authorization
 header. For that we need to do the Access token generation UI. So any
 product in future if needs they can use it.

 How can I approach?

 Ragu.



 On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka wrote:

> Hi
>
> On Sat, Jan 26, 2013 at 2:00 PM, Sriragu Arudsothy 
> wrote:
>
>> Hai All,
>>
>>  Greg need the OAuth Access token to be produced in UI which
>> should be a installable feature from Identity Server side feature. At the
>> moment once we installed the OAuth feature that produces upto client id,
>> client secret, auth endpoint, access endpoint details. But we need the
>> access token generation also as a UI components under the IS. I have been
>> given this task.
>>
>
> Why do you need a UI to generate access tokens ? Theoretically the
> access token is a secrete which should be delivered directly to the
> client.
>
> Thanks,
>  -Suresh
>
>
>> Currently the G-reg restapi cxf web app does not have any UI, we dont
>> want any UIs in the webapp. We need some UI to generate the access token
>> too from the IS side. This is our requirement.
>>  delieverddelieverd
>> Also we want to know how to get the Tenant ID of the person who
>> belongs to the given access token ???
>>
>> Please provide the way to do? we dont want any UIs in our cxf
>> webapp(REST API).
>>
>> Thanks!
>> Sriragu
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Suresh Attanayake
> Software Engineer; WSO2 Inc. http://wso2.com/
> Blog : http://sureshatt.blogspot.com/
> Twitter : https://twitter.com/sureshatt
> LinkedIn : http://lk.linkedin.com/in/sureshatt
> Mobile : +94755012060,+94770419136,+94710467976
>


>>>
>>
>>
>> --
>> Suresh Attanayake
>> Software Engineer; WSO2 Inc. http://wso2.com/
>> Blog : http://sureshatt.blogspot.com/
>> Twitter : https://twitter.com/sureshatt
>> LinkedIn : http://lk.linkedin.com/in/sureshatt
>> Mobile : +94755012060,+94770419136,+94710467976
>>
>
>
>
> --
> * 
> *
> *
>
> Senaka Fernando*
> Member - Integration Technologies Management Committee;
> 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
>



-- 
Suresh Attanayake
Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060,+94770419136,+94710467976
__

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #114 has FAILED. Change made by ajanthan.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #114 failed.
---
Code has been updated by ajanthan.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-114/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajanthan (153984):

>removing job delete permission for project role



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #126 has FAILED. Change made by ajanthan.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #126 failed.
---
Code has been updated by ajanthan.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-126/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajanthan (153984):

>removing job delete permission for project role



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

Re: [Dev] OAuth Access token Generation UI- Urgent help is needed

[Senaka Fernando]

Hi all,

Two things.

Ragu, first of all, for the moment, we should not block ourselves until any
UI is made available for this since the approach explained by Suresh can be
used to obtain the token.

Suresh, though it is not a roadblock, we need some user interface to obtain
and/or refresh the OAuth token. AM has this, but it is not a generic
component. To test or to try out things, curl might be useful, but we need
something more usable so that users can make use of it.

Thanks,
Senaka.

On Sat, Jan 26, 2013 at 6:03 PM, Suresh Attanayaka  wrote:

> Hi,
>
> On Sat, Jan 26, 2013 at 4:13 PM, Sriragu Arudsothy wrote:
>
>> Another approach:
>>
>> To avoid writing an addition UI components to generate the Access token.
>>
>> We can just write a REST class to generate the access token and pass the
>> client id, client secret, access token endpoint, encoded username, encoded
>> password from the REST client. Inside the code I have to decode the
>> username and password.
>>
>
> Yes, you can write a REST client to get the access token using the
> password grant type.
>
>
>> This will solve. WDYT?
>>
>> RAGU
>>
>> On Sat, Jan 26, 2013 at 4:01 PM, Sriragu Arudsothy wrote:
>>
>>> Yes you are right .
>>>
>>> The Greg' requirement is like this:
>>>
>>> Any REST client (ex: Chrome Advanced REST client) we just wanted to pass
>>> the Bearer token to get use of REST API.
>>>
>>> Currently we use the curl command to generate the access token. But we
>>> are not intended to have a REST web client with (Forms to enter the client
>>> id/ secret ...etc) and click a button to generate the access token)
>>>
>>> Very brief: Greg team finalized that the client want to see the
>>> Accesstoken value, who has to use it straight away with Authorization
>>> header. For that we need to do the Access token generation UI. So any
>>> product in future if needs they can use it.
>>>
>>> How can I approach?
>>>
>>> Ragu.
>>>
>>>
>>>
>>> On Sat, Jan 26, 2013 at 2:45 PM, Suresh Attanayaka wrote:
>>>
 Hi

 On Sat, Jan 26, 2013 at 2:00 PM, Sriragu Arudsothy wrote:

> Hai All,
>
>  Greg need the OAuth Access token to be produced in UI which
> should be a installable feature from Identity Server side feature. At the
> moment once we installed the OAuth feature that produces upto client id,
> client secret, auth endpoint, access endpoint details. But we need the
> access token generation also as a UI components under the IS. I have been
> given this task.
>

 Why do you need a UI to generate access tokens ? Theoretically the
 access token is a secrete which should be delivered directly to the
 client.

 Thanks,
  -Suresh


> Currently the G-reg restapi cxf web app does not have any UI, we dont
> want any UIs in the webapp. We need some UI to generate the access token
> too from the IS side. This is our requirement.
>  delieverddelieverd
> Also we want to know how to get the Tenant ID of the person who
> belongs to the given access token ???
>
> Please provide the way to do? we dont want any UIs in our cxf
> webapp(REST API).
>
> Thanks!
> Sriragu
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Suresh Attanayake
 Software Engineer; WSO2 Inc. http://wso2.com/
 Blog : http://sureshatt.blogspot.com/
 Twitter : https://twitter.com/sureshatt
 LinkedIn : http://lk.linkedin.com/in/sureshatt
 Mobile : +94755012060,+94770419136,+94710467976

>>>
>>>
>>
>
>
> --
> Suresh Attanayake
> Software Engineer; WSO2 Inc. http://wso2.com/
> Blog : http://sureshatt.blogspot.com/
> Twitter : https://twitter.com/sureshatt
> LinkedIn : http://lk.linkedin.com/in/sureshatt
> Mobile : +94755012060,+94770419136,+94710467976
>



-- 
* 
*
*

Senaka Fernando*
Member - Integration Technologies Management Committee;
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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #113 has FAILED. Change made by ajanthan.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #113 failed.
---
Code has been updated by ajanthan.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-113/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajanthan (153981):

>adding ability to drfine project role permission through config



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #125 has FAILED. Change made by ajanthan.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #125 failed.
---
Code has been updated by ajanthan.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-125/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
ajanthan (153981):

>adding ability to drfine project role permission through config



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.6 > #112 has FAILED. Change made by krishantha.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.6 > #112 failed.
---
Code has been updated by krishantha.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO006-112/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
krishantha (153979):

>Refactoring selenium page classes



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

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Platform 4.0.6 > #124 has FAILED. Change made by krishantha.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.6 > #124 failed.
---
Code has been updated by krishantha.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA006-124/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
krishantha (153979):

>Refactoring selenium page classes



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