[Dev] Anybody interested in creating some cool open social gadgets for the upcoming UES release ???

[Nuwan Bandara]

If its upto the standard, we will ship it with UES as default gadgets. We
can give a gift for the best five enterprise gadgets.

Regards,
/Nuwan

-- 
*Thanks & Regards,

Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629
*

___
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.7 > #143 has FAILED. Change made by 21 authors.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.7 > #143 failed.
---
Code has been updated by Ajanthan Balachandiran , Ruchira Wageesha, Oleg 
Kalnichevski, Prabath Siriwardena, Dharshana kasun Warusavitharana , Dimuthu 
Leelarathne, Janaka Ranabahu, Manjula Rathnayaka, Chathura Kulasinghe, Chanaka 
Jayasena, Ashansa Perera, Hasini Gunasinghe, Manisha Eleperuma, Nuwan Bandara, 
Miyuru  Wanninayaka, praveena sarathchana, Harsha Thirimanna, Sanjeewa 
Malalgoda, Nuwan Wimalasekara, Dilshan Edirisuriya, Ramith Jayasinghe.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA007-143/

-
Currently Responsible
-

Ajith Vitharana (Automatically assigned)
Asela Pathberiya (Automatically assigned)
Chanaka Jayasena (Automatically assigned)
Chathura Kulasinghe (Automatically assigned)
Dinusha Dilrukshi (Automatically assigned)
Harsha Thirimanna (Automatically assigned)
Ishara Karunarathna (Automatically assigned)
Nuwan Wimalasekara (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): 329 tests passed.



--
Code Changes
--
Dilshan Edirisuriya (167917):

>making gadget urls http

Nuwan Bandara (167908):

>dnd fixes

Nuwan Wimalasekara (167885):

>update class



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

[Dev] Fwd: Access denied to generate the OAuth Access token for REST API.

[Sriragu Arudsothy]

-- Forwarded message --
From: Ajith Vitharana 
Date: Thu, Mar 14, 2013 at 6:02 PM
Subject: Re: Access denied to generate the OAuth Access token for REST API.
To: Sriragu Arudsothy 
Cc: chand...@wso2.com, Prabath Siriwardana , Senaka
Fernando , Eranda Sooriyabandara 


Hi Ragu,

Please discuss those things on dev list.
No need to be private.

Thanks
Ajith

On Mar 14, 2013 5:44 PM, "Sriragu Arudsothy"  wrote:
>
> Since the admin/manage permission is defined to use the OAuthAdminService
at the identity.oauth component's service.xml file. Therefore any user role
has the above permission is able to generate the access token. it is given
below.
>
> /permission/admin/manage
>
> But by default, API publisher/subscriber role can't generate the token
since they don't have the above permission. but if we created a new role
including the manage permission or update the above roles with the manage
permission will able to generate the token.
>
> I have modified the code as follows: If the login user has the
admin/manage permission, who can see the Registry REST API panel under the
user management and able to generate the token.
>
> Thanks!
> Ragu
>
>
> On Thu, Mar 14, 2013 at 3:42 PM, Senaka Fernando  wrote:
>>
>> Hi Ragu,
>>
>> We are going in circles, :). Ok, so what admin permission do you need
for this OAuthAdminService?
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Thu, Mar 14, 2013 at 1:42 AM, Sriragu Arudsothy 
wrote:
>>>
>>> Thanks for responding prabath..!
>>>
>>> Hai Greg,
>>>
>>>  Therefore according to the current user management
perspective, If the user does not have the admin permissions , who is not
able to generate the access token since it uses the OAuthAdminService to
register an app. So that, he/she is unable to access the REST API.
>>>
>>> Therefore Why do we need to show the Registry REST API panel under the
user management for the users not assigned to admin role ???
>>>
>>> Thanks!
>>> Ragu
>>>
>>> On Wed, Mar 13, 2013 at 5:28 PM, Prabath Siriwardena 
wrote:

 Earlier anyone can access anything.. It was security hole and now its
fixed..

 Thanks & regards,
 -Prabath


 On Wed, Mar 13, 2013 at 5:22 PM, Sriragu Arudsothy 
wrote:
>
> I am not sure who is..! I guess the IS team did significant amount of
 work on User-management for WM release. They have done a major refactoring
on User-management.
>
> Thanks!
> Ragu
>
>
>
> On Wed, Mar 13, 2013 at 4:49 PM, Senaka Fernando 
wrote:
>>
>> Hi Ragu,
>>
>> May be somebody changed the permissions of the admin service?
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Mar 13, 2013 at 6:43 AM, Sriragu Arudsothy 
wrote:
>>>
>>> Hai  !
>>>
>>> there were some restrictions after updated.
>>> 1) There were more restrictions on admin services regarding the
user management aspects. Earlier, whoever has the login permission to login
to the Greg console were able to generate the OAuth access token to access
the Registry REST API. I tested the current REST API today with the recent
update. If the user has the admin role/above is allowed to generate the
access token since OAuthAdminService  is used to register an app and
generate the access token using the generated client id/secret for the
given user.
>>>
>>> I have assigned API Publisher and subscriber  roles for 2 users,
when tested there were denied access to register an app. Therefore unable
to get the access token. The following error was thrown.
>>>
>>> [2013-03-13 15:22:53,525] ERROR {java.lang.Class} -  Access Denied.
Failed authorization attempt to access service 'OAuthAdminService'
operation 'getAllOAuthApplicationData' by 'ragu'
>>> [2013-03-13 15:22:53,526] ERROR
{org.apache.axis2.engine.AxisEngine} -  Access Denied.
>>> org.apache.axis2.AxisFault: Access Denied.
>>>
>>> where the "ragu" has been assigned API publisher role.
>>>
>>> Is there any alternative way we can allow every body has the login
permission to generate the Token as like earlier?
>>>
>>> Thanks!
>>> Ragu
>>>
>>
>>
>>
>> --
>>
>>
>> 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
>
>



 --
 Thanks & Regards,
 Prabath

 Mobile : +94 71 809 6732

 http://blog.facilelogin.com
 http://RampartFAQ.com
>>>
>>>
>>
>>
>>
>> --
>>
>>
>> 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 w

[Dev] Build Fail on project org.wso2.carbon.automation.test.platform.scenario

[Geeth Munasinghe]

HI

There is build failure on platform 4.1.0 branch, This happens when building
with clean repo

[INFO]
[INFO] WSO2 Platform Automated Suite - Platform scenarios  FAILURE [11.840s]
[INFO] WSO2 Platform Automated Suite - Distribution .. SKIPPED
[INFO] WSO2 Carbon - Platform Aggregator Pom . SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 49.854s
[INFO] Finished at: Thu Mar 14 20:42:24 PDT 2013
[INFO] Final Memory: 280M/989M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.automation.test.platform.scenario: Could not resolve
dependencies for project
org.wso2.carbon.automation:org.wso2.carbon.automation.test.platform.scenario:jar:1.1.0:
Failure to find org.wso2.esb:org.wso2.carbon.esb.tests:jar:tests:4.6.0 in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of wso2-nexus has elapsed or updates are forced -> [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/DependencyResolutionException

Thanks

*G. K. S. Munasinghe
*
*Software Engineer,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: ge...@wso2.com
phone:(+94) 777911226
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Urgent]Have we done the 4.1.0 branching correctly?

[Janaka Ranabahu]

Hi,

I see that the version of the org.wso2.carbon.hostobjects.carbonutil/4.1.0
bundle is set to 1.0.1. Please refer [1]. But please note that this version
is already released and can be found in [2].

Have we done the versions correctly when we branched 4.1.0. Please check
and confirm.

Thanks,
Janaka


[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/hostobjects/org.wso2.carbon.hostobjects.carbonutil/4.1.0/pom.xml
[2]
http://dist.wso2.org/maven2/org/wso2/carbon/org.wso2.carbon.hostobjects.carbonutil/1.0.1/

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

*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 > Kernel 4.0.7 > #69 has FAILED. Change made by Hasini Gunasinghe, Prabath Siriwardena and Johann Nallathamby.

[Bamboo]

---
WSO2 Carbon 4.0.x > Kernel 4.0.7 > #69 failed.
---
Code has been updated by Hasini Gunasinghe, Prabath Siriwardena, Johann 
Nallathamby.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER007-69/

-
Currently Responsible
-

Asela Pathberiya (Automatically assigned)
Chanaka Jayasena (Automatically assigned)
Hasini Gunasinghe (Automatically assigned)
Johann Nallathamby (Automatically assigned)
Prabath Siriwardena (Automatically assigned)



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



--
Code Changes
--
Prabath Siriwardena (167915):

>changes in regex

Johann Nallathamby (167913):

>Fixing Internal case in drop down in role-mgt.jsp

Hasini Gunasinghe (167973):

>committing a patch by Sumedha



--
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.7 > #128 has FAILED. Change made by 16 authors.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.7 > #128 failed.
---
Code has been updated by Ajanthan Balachandiran , Oleg Kalnichevski, Prabath 
Siriwardena, Janaka Ranabahu, Manjula Rathnayaka, Chathura Kulasinghe, Chanaka 
Jayasena, Isuru Udana Loku Narangoda, Nuwan Bandara, praveena sarathchana, 
Dinusha Dilrukshi, Sanjeewa Malalgoda, Harsha Thirimanna, Nuwan Wimalasekara, 
Dilshan Edirisuriya, Ramith Jayasinghe.
No failed tests found, a possible compilation error.

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

-
Currently Responsible
-

Chathura Kulasinghe (Automatically assigned)
Harsha Thirimanna (Automatically assigned)
Ishara Karunarathna (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): 9 tests passed.



--
Code Changes
--
Prabath Siriwardena (167856):

>fixing pom error

Sanjeewa Malalgoda (167834):

>adding multi tenant API manager fixes

Janaka Ranabahu (167858):

>Adding S2 related changes
>



--
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.7 > #68 has FAILED. Change made by Prabath Siriwardena.

[Bamboo]

---
WSO2 Carbon 4.0.x > Kernel 4.0.7 > #68 failed.
---
Code has been updated by Prabath Siriwardena.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER007-68/

-
Currently Responsible
-

Asela Pathberiya (Automatically assigned)
Chanaka Jayasena (Automatically assigned)
Hasini Gunasinghe (Automatically assigned)
Johann Nallathamby (Automatically assigned)
Prabath Siriwardena (Automatically assigned)



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



--
Code Changes
--
Prabath Siriwardena (167872):

>fixing regex issues



--
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.7 > #142 has FAILED. Change made by 14 authors.

[Bamboo]

---
WSO2 Carbon 4.0.x > Platform 4.0.7 > #142 failed.
---
Code has been updated by Ajanthan Balachandiran , Prabath Siriwardena, Janaka 
Ranabahu, Manjula Rathnayaka, Chathura Kulasinghe, Chanaka Jayasena, Isuru 
Udana Loku Narangoda, Nuwan Bandara, praveena sarathchana, Dinusha Dilrukshi, 
Sanjeewa Malalgoda, Harsha Thirimanna, Nuwan Wimalasekara, Ramith Jayasinghe.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA007-142/

-
Currently Responsible
-

Ajith Vitharana (Automatically assigned)
Asela Pathberiya (Automatically assigned)
Chanaka Jayasena (Automatically assigned)
Chathura Kulasinghe (Automatically assigned)
Dinusha Dilrukshi (Automatically assigned)
Harsha Thirimanna (Automatically assigned)
Ishara Karunarathna (Automatically assigned)
Nuwan Wimalasekara (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): 329 tests passed.



--
Code Changes
--
Prabath Siriwardena (167856):

>fixing pom error

Sanjeewa Malalgoda (167834):

>adding multi tenant API manager fixes

Janaka Ranabahu (167858):

>Adding S2 related changes
>



--
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.7 > #16 has FAILED. Change made by 4 authors.

[Bamboo]

---
WSO2 Carbon 4.0.x - Nightly > Kernel_4.0.7 > #16 failed.
---
This build occurred because it is a dependant of WCB002-NORB004-66.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB002-NKER005-16/

-
Currently Responsible
-

Asela Pathberiya (Automatically assigned)
Hasini Gunasinghe (Automatically assigned)
Prabath Siriwardena (Automatically assigned)



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



--
Code Changes
--
Prabath Siriwardena (167915):

>changes in regex

Prabath Siriwardena (16):

>https://wso2.org/jira/browse/IDENTITY-911

Johann Nallathamby (167772):

>Fixing ReadOnly users in UI



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

Re: [Dev] Uploading Same Jaggery App Again Without Deleting Previous One

[Ajanthan Balachandran]

What is the verdict in this?

On Mon, Mar 4, 2013 at 2:21 PM, Kishanthan Thangarajah
 wrote:
>
>
> On Mon, Mar 4, 2013 at 1:34 PM, Tharindu Mathew  wrote:
>>
>> Overwriting the existing is the standard behavior in web apps. This makes
>> deployment and testing easy as well. I think it should be the same for
>> jaggery apps. So, this behavior should be changed.
>
>
> Jaggery deployment follows a different model where the changes to the app
> gets reflected on the fly, which is different form the normal axis2
> hot-deployment concept (unDeploy first and deploy again). Also if i remember
> correctly, that was the requirement as you can just edit the jag files or
> add new jag files on the fly, to the jaggery app (without the need to
> redeploy them every time) and the changes will get reflected instantly.
>
> For other app types, when deploying a new app with the same name, first it
> will undeploy the existing one and the deploy the new one, which is the
> normal axis2 deployment model.
>
> Thanks,
> Kishanthan.
>>
>>
>> On Mon, Mar 4, 2013 at 12:57 PM, Supun Malinga  wrote:
>>>
>>> Hi,
>>>
>>> +1 For allowing the user to upload after confirmation. As for the current
>>> implementation user cannot upload a jaggery app with the same name twice.
>>> But saying that, all other artifact deployment happens blindly copying
>>> over the existing artifact. We may need to take a decision regarding that as
>>> well.
>>>
>>> thanks,
>>>
>>> On Mon, Mar 4, 2013 at 12:47 PM, Nuwan Bandara  wrote:




 On Mon, Mar 4, 2013 at 12:16 PM, Ajanthan Balachandran
  wrote:
>
> Hi All,
> $subject fails with back end log "Jaggery app with the same name
> already exists".But in the case of Web App it first undeploy the
> previous one and deploy the new one.Which is the correct behavior ?


 I think Jaggery behaves correctly. Imagine, user X creates an app called
 Foo and uses it, and later User Y logs in and add a new app called foo, If
 we silently replace the app, then its a problem. we give a warning. If its 
 a
 conscious decision, he can remove the old foo first and deploy the new one.

 Regards,
 /Nuwan

>
> Thanks
> --
> ajanthan
> --
> Ajanthan Balachandiran
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> email: ajant...@wso2.com; cell: +94775581497
> blog: http://bkayts.blogspot.com/
>
> Lean . Enterprise . Middleware
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thanks & Regards,

 Nuwan Bandara
 Associate Technical Lead & Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
 9629


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

>>>
>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>> email - sup...@wso2.com
>>> mobile - 071 56 91 321
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu Mathew
>>
>> Associate Technical Lead, WSO2 BAM
>> Member - Data Mgmt. Committee
>>
>> blog: http://tharindumathew.com/
>> M: +9459908
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Kishanthan Thangarajah
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - http://kishanthan.wordpress.com
> Twitter - http://twitter.com/kishanthan
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



--
ajanthan
-- 
Ajanthan Balachandiran
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: ajant...@wso2.com; cell: +94775581497
blog: http://bkayts.blogspot.com/

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

[Dev] Using two different methods each to retrieve lifecycle name and lifecycle state in GovernanceArtifact

[Eranda Sooriyabandara]

Hi all,
In GovernanceArtifact there are two methods each to retrieve lifecyle name
and lifecycle namespace.

   1. getLCName / getLifecycleName
   2. getLCState / getLCState

There is no significant difference between the usage, both can be use to
retrieve the lifecycle name and state. But these methods are totally
different in their implementations.
getLCName and getLCState methods are the getter method for the lcName and
lcState attributes which are in GovernanceArtifact. These attributes are
initialized when we retrieve artifact instance and not changed afterwards.
getLifecycleName and getLifecycleState are methods which retrieve the
lifecycle name and lifecycle state directly from the database by calling
registry.get method.
So getLifecycleName and getLifecycleState is reliable but with the cost of
additional registry.get.

Additionally getLCName and getLCState ethods are using to list down the
governance artifacts in list view in Management Console. If we used
 getLifecycleName and getLifecycleState methods to list artifacts, then
there will be a considerable performance hit.
Also if we use the getLCName and getLCState to retrieve the lifecycle name
and state, then there will be a reliability issue.

AFAIU, Only solution for this is introduce BE pagination and use
getLifecycleName and getLifecycleState methods. So shall we keep methods
until we introduce the BE pagination? Any other solutions?

thanks
Eranda


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

Re: [Dev] Error on running Identity Server with MySQL ODBC Connector on Windows 7 64bit

[Dulanja Liyanage]

Hi Sumedha,

Thanks a lot for helping with this.

No, I didn't write to the forum yet; will do that. And yes, it was
downloaded from that location.

As I told in the chat, one thing I forgot to mention in the previous mail
is, server did not crash when the older connector version (5.1.24) is used.
Rather, it threw an UnsupportedOperationException:

[2013-03-14 18:37:55,612] ERROR
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Failed to activate Registry Core bundle
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to add
the root collection to the coreRegistry.
at
org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:400)

at
org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:300)

at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:227)

at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:206)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:276)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:262)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.configure(EmbeddedRegistryService.java:219)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.(EmbeddedRegistryService.java:99)

at
org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.getEmbeddedRegistryService(RegistryCoreServiceComponent.java:632)

at
org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.buildRegistryService(RegistryCoreServiceComponent.java:566)

at
org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.activate(RegistryCoreServiceComponent.java:120)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)

at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)

at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)

at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)

at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)

at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)

at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)

at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)

at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)

at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)

at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)

at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)

at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)

at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)

at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)

at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:68)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)

at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)

at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)

at
org.eclipse.osgi.framework.internal.core.Frame

Re: [Dev] Error on running Identity Server with MySQL ODBC Connector on Windows 7 64bit

[Sumedha Rubasinghe]

Dulanja,
This looks like a problem in the JDBC ODBC bridge.
Did you try writing to MySQL forum? This was downloaded from
http://dev.mysql.com/downloads/connector/odbc/ . right?

Did you try writing to MySQL forum on this?
I am afraid very little can be done on our front to solve this other than
trying various OS+JDK+MySQL combinations.


On Thu, Mar 14, 2013 at 2:52 PM, Dulanja Liyanage  wrote:

> Hi,
>
> I have tried to run Identity Server with ODBC on Windows 7 64bit, but the
> server crashes at the startup with the following output:
>
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6c5deafd, pid=4664,
> tid=520
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode windows-x86 )
> # Problematic frame:
> # C  [myodbc5w.dll+0xeafd]
>
> Connection to the MySQL was successful because tables were created in it.
> From the error logs I deduced the crash happens outside the JVM, in
> myodbc5w.dll. The full error logs are attached with this mail.
>
> Following are the configurations I have tested with:
>
> Windows 7 (64bit)
> MySQL 5.6
> JDK 1.7.0_09 (64bit) with MySQL-Connector/ODBC 5.2.4 (64bit)
> JDK 1.6.0_43 (64bit) with MySQL-Connector/ODBC 5.2.4 (64bit) and 5.1.24
> (64bit)
> JDK 1.6.0_43 (32bit) with MySQL-Connector/ODBC 5.2.4 (32bit)
>
> Appreciate a lot if someone can help me with this.
>
> Thanks!
> Dulanja
>
> --
> Dulanja Liyanage
> Senior Software Engineer - WSO2 Inc.
> M: +94776764717




-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Disable ArtifactCacheManager

[Danushka Fernando]

Hi
I debugged the code and checked these paths. Although the content in the
RXT is correct cache returns a wrong value which is old. But before we move
the RXT it was giving us the current value. But after we move it gives a
wrong value. Another thing is we are not searching the RXT using the path
but the UUID. So after we move the RXT the cache doesn't seems to be
returning correct value. But after an update it again read the correct
value.

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Tue, Mar 12, 2013 at 12:40 PM, Eranda Sooriyabandara wrote:

> Hi Dhanushka,
> It does not seems to be a caching issue to me. It seems you have pointed
> to the old artifact than the new artifact.
>
> thanks
> Eranda
>
>
> On Tue, Mar 12, 2013 at 11:04 AM, Danushka Fernando wrote:
>
>> I forgot to mention that this get method gives correct values before the
>> Promote action occurs. After the promote action it gives some old values.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>>
>> On Tue, Mar 12, 2013 at 10:47 AM, Danushka Fernando 
>> wrote:
>>
>>> Hi,
>>> The problem occurs when a Promote Governance action is happened. At this
>>> point one registry key is copied to somewhere else and delete the original
>>> one.
>>> /
>>> _system
>>> /
>>> *governance*
>>>
>>> 
>>> /
>>> *repository*
>>>
>>> 
>>> /
>>> *applications*
>>>
>>> 
>>> /
>>> *issuetracker2399*
>>>
>>> 
>>> /
>>> *Development*
>>>
>>> 
>>> /
>>> *1.0.0*
>>>
>>> 
>>> /
>>> *appversion
>>> *
>>> is copied to 
>>> /
>>> _system
>>> /
>>> *governance*
>>>
>>> 
>>> /
>>> *repository*
>>>
>>> 
>>> /
>>> *applications*
>>>
>>> 
>>> /
>>> *issuetracker2399*
>>>
>>> 

[Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products 4.0.7 > #127 has FAILED. Change made by Ajanthan Balachandiran and Chathura Kulasinghe.

[Bamboo]

---
WSO2 Carbon 4.0.x > Products 4.0.7 > #127 failed.
---
Code has been updated by Ajanthan Balachandiran , Chathura Kulasinghe.
No failed tests found, a possible compilation error.

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

-
Currently Responsible
-

Chathura Kulasinghe (Automatically assigned)
Harsha Thirimanna (Automatically assigned)
Ishara Karunarathna (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): 9 tests passed.



--
Code Changes
--
Ajanthan Balachandiran  (167800):

>application type+refactoring

Chathura Kulasinghe (167778):

>Notification bar, usability enhancements
>

Ajanthan Balachandiran  (167802):

>application type+refactoring



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

Re: [Dev] ESB 4.7.0 build admin login failure

[Ravi Undupitiya]

Hi,

Changes made to carbon kernel on r167864 seems to have fixed this issue.


Thanks,
Ravi

On Thu, Mar 14, 2013 at 12:39 PM, Ravi Undupitiya  wrote:

> Hi,
>
> I've built the latest ESB 4.7.0 pack and I'm trying to run integration
> tests but I get the following error:
>
>  WARN - CarbonAuthenticationUtil Failed Administrator login attempt
> 'admin[-1234]' at [2013-03-14 12:21:21,206+0530]
>
> I have checked by running the built pack and trying to login through the
> carbon web console with admin/admin and I get the same error.
>
> I checked user-mgt.xml and it has the following contents:
>
> 
> 
> true
> admin
> 
>  admin
>  admin
> 
> everyone 
> jdbc/WSO2CarbonDB
>  name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder
> 
>
>  class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager">
>  false
> 100
> false
>
> false
> default
> SHA-256
> true
> true
>  true
> false
> ^[\S]{5,30}$
>  name="PasswordJavaScriptRegEx">^[\\S]{5,30}$
>   name="UsernameJavaRegEx">^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
>  ^[\\S]{3,30}$
>   name="RolenameJavaRegEx">^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
>  ^[\\S]{3,30}$
> true
> 100
> 100
> 
>
> 
> class="org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager">
>  name="AdminRoleManagementPermissions">/permission
> true
> 
> 
>
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>



-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*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 > Kernel 4.0.7 > #67 has FAILED. Change made by Prabath Siriwardena and Ishan Jayawardena.

[Bamboo]

---
WSO2 Carbon 4.0.x > Kernel 4.0.7 > #67 failed.
---
Code has been updated by Prabath Siriwardena, Ishan Jayawardena.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER007-67/

-
Currently Responsible
-

Asela Pathberiya (Automatically assigned)
Chanaka Jayasena (Automatically assigned)
Hasini Gunasinghe (Automatically assigned)
Johann Nallathamby (Automatically assigned)
Prabath Siriwardena (Automatically assigned)



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



--
Code Changes
--
Prabath Siriwardena (167779):

>fixing regex validation

Ishan Jayawardena (167792):

>adding old version 4.1.0-wso2v1 of httpcore back
>

Ishan Jayawardena (167794):

>adding old version of httpcore 4.1.0-wso2v1 again.
>



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

[Dev] ESB 4.7.0 build admin login failure

[Ravi Undupitiya]

Hi,

I've built the latest ESB 4.7.0 pack and I'm trying to run integration
tests but I get the following error:

 WARN - CarbonAuthenticationUtil Failed Administrator login attempt
'admin[-1234]' at [2013-03-14 12:21:21,206+0530]

I have checked by running the built pack and trying to login through the
carbon web console with admin/admin and I get the same error.

I checked user-mgt.xml and it has the following contents:



true
admin

 admin
 admin

everyone 
jdbc/WSO2CarbonDB
org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder



 false
100
false

false
default
SHA-256
true
true
 true
false
^[\S]{5,30}$
^[\\S]{5,30}$
 ^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
 ^[\\S]{3,30}$
 ^[^~!#$;%^*+={}\\|<>,\'\"]{3,30}$
 ^[\\S]{3,30}$
true
100
100



/permission
true






-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Synapse(v3) VFSTransportTest test issue in 4.1.0 branch

[Supun Malinga]

Thanks Pamod, Charitha..


On Thu, Mar 14, 2013 at 12:32 PM, Charitha Madurangi wrote:

> Hi,
>
> This test fail could be resolved by applying the patch attached to [1] by
> Pamod. Committed the fix with revision 167846..
>
> [1] https://wso2.org/jira/browse/ESBJAVA-1804
>
> Thanks,
> CharithaM.
>
> On Tue, Mar 12, 2013 at 10:53 PM, Kasun Indrasiri  wrote:
>
>> I think Pamod has fixed this on 4.0 branch. May be patch is not added to
>> 4.1. Will check and fix.
>>
>>
>> On Tue, Mar 12, 2013 at 10:33 PM, Supun Malinga  wrote:
>>
>>> T E S T S
>>> ---
>>> Running org.apache.synapse.transport.vfs.VFSTransportTest
>>> [IsolatedClassLoader@70922804] weaveinfo Join point 'method-call(void
>>> org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
>>> org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in
>>> Type 'org.apache.synapse.transport.vfs.VFSTransportSender'
>>> (VFSTransportSender.java:235) advised by around advice from
>>> 'org.apache.axis2.transport.testkit.axis2.LogAspect' (LogAspect.java)
>>> [IsolatedClassLoader@70922804] weaveinfo Join point
>>> 'method-call(org.apache.axiom.om.OMElement
>>> org.apache.axis2.builder.Builder.processDocument(java.io.InputStream,
>>> java.lang.String, org.apache.axis2.context.MessageContext))' in Type
>>> 'org.apache.synapse.transport.vfs.VFSTransportListener'
>>> (VFSTransportListener.java:558) advised by around advice from
>>> 'org.apache.axis2.transport.testkit.axis2.LogAspect' (LogAspect.java)
>>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>>> unable to acquire the lock even after 4 retries
>>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>>> unable to acquire the lock even after 4 retries
>>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>>> unable to acquire the lock even after 4 retries
>>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>>> unable to acquire the lock even after 4 retries
>>>
>>> thanks,
>>> --
>>> Supun Malinga,
>>>
>>> Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>> email - sup...@wso2.com 
>>> mobile - 071 56 91 321
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Supun Malinga,

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

Re: [Dev] Synapse(v3) VFSTransportTest test issue in 4.1.0 branch

[Charitha Madurangi]

Hi,

This test fail could be resolved by applying the patch attached to [1] by
Pamod. Committed the fix with revision 167846..

[1] https://wso2.org/jira/browse/ESBJAVA-1804

Thanks,
CharithaM.

On Tue, Mar 12, 2013 at 10:53 PM, Kasun Indrasiri  wrote:

> I think Pamod has fixed this on 4.0 branch. May be patch is not added to
> 4.1. Will check and fix.
>
>
> On Tue, Mar 12, 2013 at 10:33 PM, Supun Malinga  wrote:
>
>> T E S T S
>> ---
>> Running org.apache.synapse.transport.vfs.VFSTransportTest
>> [IsolatedClassLoader@70922804] weaveinfo Join point 'method-call(void
>> org.apache.axis2.transport.MessageFormatter.writeTo(org.apache.axis2.context.MessageContext,
>> org.apache.axiom.om.OMOutputFormat, java.io.OutputStream, boolean))' in
>> Type 'org.apache.synapse.transport.vfs.VFSTransportSender'
>> (VFSTransportSender.java:235) advised by around advice from
>> 'org.apache.axis2.transport.testkit.axis2.LogAspect' (LogAspect.java)
>> [IsolatedClassLoader@70922804] weaveinfo Join point
>> 'method-call(org.apache.axiom.om.OMElement
>> org.apache.axis2.builder.Builder.processDocument(java.io.InputStream,
>> java.lang.String, org.apache.axis2.context.MessageContext))' in Type
>> 'org.apache.synapse.transport.vfs.VFSTransportListener'
>> (VFSTransportListener.java:558) advised by around advice from
>> 'org.apache.axis2.transport.testkit.axis2.LogAspect' (LogAspect.java)
>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>> unable to acquire the lock even after 4 retries
>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>> unable to acquire the lock even after 4 retries
>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>> unable to acquire the lock even after 4 retries
>> ERROR [main] VFSTransportSender Couldn't send the message to file :
>> file:///home/wso2/as501/latest/platform/dependencies/synapse/2.1.1-wso2v3/modules/transports/core/vfs/target/vfs3/req/in,
>> unable to acquire the lock even after 4 retries
>>
>> thanks,
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - sup...@wso2.com 
>> mobile - 071 56 91 321
>>
>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
> ___
> 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