Re: [Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Hi Vijitha,

I took svn up under both components/governance & components/registry. But
when trying to build platform/components, I still get the same error.

Thanks,
Hasini.


On Mon, May 27, 2013 at 11:05 PM, Vijitha Kumara  wrote:

> This is fixed, please update governance.registry.extensions component and
> build.
>
>
> On Mon, May 27, 2013 at 3:51 PM, Vijitha Kumara  wrote:
>
>> Running a new build in a clean repo, will check and update here.
>>
>>
>> On Mon, May 27, 2013 at 3:33 PM, Hasini Gunasinghe wrote:
>>
>>> Hi Vijitha,
>>>
>>> Still fails with the same error..
>>>
>>> Thanks,
>>>  Hasini.
>>>
>>>
>>> On Mon, May 27, 2013 at 3:10 PM, Vijitha Kumara wrote:
>>>
>>>> There was an error in relative path, can you update and check now?
>>>>
>>>>
>>>> On Mon, May 27, 2013 at 3:04 PM, Hasini Gunasinghe wrote:
>>>>
>>>>> Same fails with following compilation error as well. Appreciate if
>>>>> this could be fixed.
>>>>>
>>>>> [INFO] BUILD FAILURE
>>>>> [INFO]
>>>>> 
>>>>> [INFO] Total time: 2:30.573s
>>>>> [INFO] Finished at: Mon May 27 14:53:29 IST 2013
>>>>> [INFO] Final Memory: 682M/924M
>>>>> [INFO]
>>>>> 
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>>>> (default-compile) on project org.wso2.carbon.registry.extensions:
>>>>> Compilation failure: Compilation failure:
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[265,20]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[434,19]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,12]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>>>>> [ERROR]
>>>>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,46]
>>>>> cannot find symbol
>>>>> [ERROR] symbol  : class WADLProcessor
>>>>> [ERROR] location: class
>>>>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>>>>> [ERROR] -> [Help 1]
>>>>> [ERROR]
>>>>> [ERROR] To see the full stack tra

Re: [Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Hi Vijitha,

Still fails with the same error..

Thanks,
Hasini.


On Mon, May 27, 2013 at 3:10 PM, Vijitha Kumara  wrote:

> There was an error in relative path, can you update and check now?
>
>
> On Mon, May 27, 2013 at 3:04 PM, Hasini Gunasinghe wrote:
>
>> Same fails with following compilation error as well. Appreciate if this
>> could be fixed.
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 2:30.573s
>> [INFO] Finished at: Mon May 27 14:53:29 IST 2013
>> [INFO] Final Memory: 682M/924M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.registry.extensions:
>> Compilation failure: Compilation failure:
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[265,20]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[434,19]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,12]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>> [ERROR]
>> /home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,46]
>> cannot find symbol
>> [ERROR] symbol  : class WADLProcessor
>> [ERROR] location: class
>> org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
>> [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
>> [ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions
>>
>> Thanks,
>> Hasini.
>>
>> On Mon, May 27, 2013 at 2:49 PM, Hasini Gunasinghe wrote:
>>
>>> Hi,
>>>
>>> Trunk build failed with following error. Fixed with r173186. Please
>>> verify.
>>>
>>> [INFO] Scanning for projects...
>>> [ERROR] The build could not read 1 project -> [Help 1]
>>> [ERROR]
>>> [ERROR]   The project
>>> org.wso2.carbon:org.wso2.carbon.registry.extensions:4.1.3
>>> (/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/pom.xml)
>>> has 1 error
>>> [ERROR] Non-resolvable parent POM: The repository system is offline
>>> but the artifact org.wso2.carbon:registry:pom:4.1.0 is not availab

Re: [Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Same fails with following compilation error as well. Appreciate if this
could be fixed.

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 2:30.573s
[INFO] Finished at: Mon May 27 14:53:29 IST 2013
[INFO] Final Memory: 682M/924M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.registry.extensions:
Compilation failure: Compilation failure:
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[433,14]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[265,20]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ServiceMediaTypeHandler.java:[434,19]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ServiceMediaTypeHandler
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,12]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
[ERROR]
/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/src/main/java/org/wso2/carbon/registry/extensions/handlers/ZipWSDLMediaTypeHandler.java:[454,46]
cannot find symbol
[ERROR] symbol  : class WADLProcessor
[ERROR] location: class
org.wso2.carbon.registry.extensions.handlers.ZipWSDLMediaTypeHandler
[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
[ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions

Thanks,
Hasini.

On Mon, May 27, 2013 at 2:49 PM, Hasini Gunasinghe  wrote:

> Hi,
>
> Trunk build failed with following error. Fixed with r173186. Please verify.
>
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project
> org.wso2.carbon:org.wso2.carbon.registry.extensions:4.1.3
> (/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: The repository system is offline
> but the artifact org.wso2.carbon:registry:pom:4.1.0 is not available in the
> local repository. and 'parent.relativePath' points at wrong local POM @
> line 22, column 13 -> [Help 2]
> [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/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> Thanks,
> Hasini.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build failed in trunk - org.wso2.carbon:org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Hi,

Trunk build failed with following error. Fixed with r173186. Please verify.

[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project
org.wso2.carbon:org.wso2.carbon.registry.extensions:4.1.3
(/home/hasini/WSO2/CARBON_TRUNK/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.extensions/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: The repository system is offline but
the artifact org.wso2.carbon:registry:pom:4.1.0 is not available in the
local repository. and 'parent.relativePath' points at wrong local POM @
line 22, column 13 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

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

Re: [Dev] [DEV] Issue in trunk when initializing Velocity engine inside a jaxwebapp, through opensaml

[Hasini Gunasinghe]

Hi KasunG and Supun,

Thanks for the responses. Yes, webapp-classloading.xml file is in the
META-INF dir of the webapp and the class loading environments mentioned
there are: CXF, Carbon.

WEB-INF/lib directory only contains the wstx-asl-3.2.9.jar.

Thanks,
Hasini.


On Fri, May 17, 2013 at 7:40 PM, Supun Malinga  wrote:

> Hi Hasini,
>
> Please check if webapp-classloading.xml file is in the META-INF dir and it
> specifies the cxf runtime env.
>
> thanks,
>
> On Fri, May 17, 2013 at 6:27 PM, Kasun Gajasinghe  wrote:
>
>> What are the Classloading environments used by this webapp? If you have
>> the CXF environment, the webapp sees this jar.
>> And, have you placed any jars in WEB-INF/lib that is related to velocity?
>> If so, please provide a list of those jars.
>>
>>
>> Thanks,
>> KasunG
>>
>>
>> On Fri, May 17, 2013 at 8:15 AM, Hasini Gunasinghe wrote:
>>
>>> Hi,
>>>
>>> $subject is a blocking issue in latest trunk.
>>>
>>> OAuth endpoints are exposed as resources in a jaxwebapp. When invoking
>>> oauth token endpoint, following error[1] is printed at the backend.
>>>
>>> When searched for the error in google, found that Velocity jar needs to
>>> be in the classpath. As per recent jaxwebapp related changes, we have
>>> included velocity-1.7.jar in [CARBON_HOME]/lib/runtime/cxf folder of the
>>> product.
>>>
>>> Appreciate if someone could provide some insights on what could be the
>>> cause for this.
>>>
>>> FYI. The same functionality was working fine in platform 4.0.8.
>>>
>>> [1]
>>> [trace]
>>> ***
>>>  [debug] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29)
>>>  [trace] RuntimeInstance initializing.
>>>  [debug] Default Properties File:
>>> org/apache/velocity/runtime/defaults/velocity.properties
>>>  [debug] Trying to use logger class
>>> org.apache.velocity.runtime.log.NullLogChute
>>>  [error] The specifid logger class
>>> org.apache.velocity.runtime.log.NullLogChute isn't a valid LogChute
>>> implementation.
>>>  [debug] Using SystemLogChute.
>>>  [error] The specified class for ResourceManager
>>> (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not
>>> implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is
>>> not initialized correctly.
>>> [2013-05-17 15:47:36,592] ERROR
>>> {org.wso2.carbon.identity.oauth2.token.handlers.grant.SAML2BearerGrantTypeHandler}
>>> -  Unable to initialize Velocity template engine
>>> org.opensaml.xml.ConfigurationException: Unable to initialize Velocity
>>> template engine
>>>  at
>>> org.opensaml.DefaultBootstrap.initializeVelocity(DefaultBootstrap.java:168)
>>> at org.opensaml.DefaultBootstrap.bootstrap(DefaultBootstrap.java:85)
>>>
>>> Thanks,
>>> Hasini.
>>>
>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>
>>  ,
>> *email: **kasung AT spamfree wso2.com
>>
>> ** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>> *
>> *
>> *blog: **http://kasunbg.org* <http://kasunbg.org>
>>
>> *
>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>>
>> *
>> *
>>
>
>
>
> --
> 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

[Dev] [DEV] Issue in trunk when initializing Velocity engine inside a jaxwebapp, through opensaml

[Hasini Gunasinghe]

Hi,

$subject is a blocking issue in latest trunk.

OAuth endpoints are exposed as resources in a jaxwebapp. When invoking
oauth token endpoint, following error[1] is printed at the backend.

When searched for the error in google, found that Velocity jar needs to be
in the classpath. As per recent jaxwebapp related changes, we have included
velocity-1.7.jar in [CARBON_HOME]/lib/runtime/cxf folder of the product.

Appreciate if someone could provide some insights on what could be the
cause for this.

FYI. The same functionality was working fine in platform 4.0.8.

[1]
[trace] ***
 [debug] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29)
 [trace] RuntimeInstance initializing.
 [debug] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
 [debug] Trying to use logger class
org.apache.velocity.runtime.log.NullLogChute
 [error] The specifid logger class
org.apache.velocity.runtime.log.NullLogChute isn't a valid LogChute
implementation.
 [debug] Using SystemLogChute.
 [error] The specified class for ResourceManager
(org.apache.velocity.runtime.resource.ResourceManagerImpl) does not
implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is
not initialized correctly.
[2013-05-17 15:47:36,592] ERROR
{org.wso2.carbon.identity.oauth2.token.handlers.grant.SAML2BearerGrantTypeHandler}
-  Unable to initialize Velocity template engine
org.opensaml.xml.ConfigurationException: Unable to initialize Velocity
template engine
at
org.opensaml.DefaultBootstrap.initializeVelocity(DefaultBootstrap.java:168)
at org.opensaml.DefaultBootstrap.bootstrap(DefaultBootstrap.java:85)

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

Re: [Dev] Identity Server 4.5.0 - M1 build

[Hasini Gunasinghe]

FYI.

Suresh and Darshana will be the release managers for IS 4.5.0 release.

Thanks,
Hasini.


On Fri, May 17, 2013 at 4:03 PM, Hasini Gunasinghe  wrote:

> Hi,
>
> Please find the $subject at
> https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M1/
>
> This is a milestone build from trunk after merging IS 4.1.1 improvements
> to trunk and fixing blocking issues related to tenant mgt, UI, jax webapps
> changes etc..
>
> Currently the team is working on new features including following and bug
> fixes...
> - User Mgt configuration UI - Pushpalanka
> - Authenticator framework for OpenID, SAML2SSO, OAuth login - Ishara
> - New Permission API - Venura
> - Statistics for Identity Features - Darshana
>
> Branching will be done after the feature freeze.
>
> ChamathG, since you are getting familiarized with user.core code base, can
> you please test multiple user store feature and provide fixes as patches if
> any issues found?
>
> Thanks,
> Hasini.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Identity Server 4.5.0 - M1 build

[Hasini Gunasinghe]

Hi,

Please find the $subject at
https://svn.wso2.org/repos/wso2/scratch/Identity-Server-4.5.0/M1/

This is a milestone build from trunk after merging IS 4.1.1 improvements to
trunk and fixing blocking issues related to tenant mgt, UI, jax webapps
changes etc..

Currently the team is working on new features including following and bug
fixes...
- User Mgt configuration UI - Pushpalanka
- Authenticator framework for OpenID, SAML2SSO, OAuth login - Ishara
- New Permission API - Venura
- Statistics for Identity Features - Darshana

Branching will be done after the feature freeze.

ChamathG, since you are getting familiarized with user.core code base, can
you please test multiple user store feature and provide fixes as patches if
any issues found?

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

Re: [Dev] javax.naming.NameNotFoundException: Name [jdbc/WSO2UM1] is not bound in this Context. Unable to find [jdbc]

[Hasini Gunasinghe]

On Thu, May 16, 2013 at 2:27 PM, Vijayaratha Vijayasingam
wrote:

> Hi hasini;
> we are not calling user.core form our end, we try
> to retrieve user-registry from our end to get the API data for tenants[1];
> Regsitry calls usercore.
> May be the tenant login/creation doesn't  involve in this realmConf
> initialization(im not sure)
>

Tenant creation do involve initialization of tenant realm.

Please note the following line in the stack trace you have printed above:

*at org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(
DefaultRealmService.java:169)*

This can not be invoked being in an individual tenant flow.

Thanks,
Hasini.

you can check attached usermsgt.xml with latest APIm pack. Try to login
> from store, you will see the issue.(after publishing api, restart the
> server)
>
>   tenantConfRegistry = ServiceReferenceHolder.getInstance().
>
> getRegistryService().getConfigUserRegistry(CarbonConstants.REGISTRY_ANONNYMOUS_USERNAME,
> tenant.getId());
>   tenantRegistry = ServiceReferenceHolder.getInstance().
>
> getRegistryService().getGovernanceUserRegistry(CarbonConstants.REGISTRY_ANONNYMOUS_USERNAME,
> tenant.getId());
>
> thansk
>
>
>
> On 16 May 2013 14:19, Hasini Gunasinghe  wrote:
>
>> Hi Ratha,
>>
>> On Thu, May 16, 2013 at 10:43 AM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Hi all;
>>> I checked the user.core component to find out the root cause.
>>> When we login from api store to retrieve public apis, we do
>>> an iteration for all tenant's publicAPI. For that we check the
>>> particular tenant's  registry. Registry calls-->usercore-->realmservice,
>>> where we  initialize the relamConfiguration for tenants.
>>>
>>
>> Do you observe this issue only when you go through the aforementioned
>> flow? If so, you need to make sure that it is initiated in the correct
>> tenant scope.
>>
>>  AFAIK, already existing multi tenant operations work fine in the APIM
>> pack - eg: tenant creation, tenant login etc.., where the tenant specific
>> realm initialization work fine without issue. Therefore, IMO, this can not
>> be a generic issue in user.core - rather you might have observed this due
>> to the way you initialize the above flow.
>>
>> Thanks,
>> Hasini.
>>
>>
>>>  When we try to initialize the realm, system couldn't do lookup for the
>>> particular datasource; which is *jdbc/WSO2UM1.* (this datasources we
>>> define for multiple userstore)
>>> The error im getting for this is[1];
>>> But when we start the server, system is able to initialize the realm
>>> configuration properly, that is it is able to do jndi lookup properly. What
>>> might be the issue? (I found some similar issues , but all stating driver
>>> is missing or, entry is wrong etc..but none is relevant to me)
>>>  There is a carbonjira also reported same and resolved, but the reason
>>> provided for the issue looks irrelevant for me[2].
>>> If anybody knows the root cause please reply to the thread.
>>> p.s: attched the uesrmgt+datasourec
>>>
>>> Thanks.
>>>
>>> [2]https://wso2.org/jira/browse/CARBON-11674
>>>
>>> *
>>> *
>>> *[1]*
>>> *
>>> Caused by: javax.naming.NameNotFoundException: Name [jdbc/WSO2UM1] is
>>> not bound in this Context. Unable to find [jdbc].
>>>  at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
>>> at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
>>>  at org.apache.naming.SelectorContext.lookup(SelectorContext.java:158)
>>> at
>>> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:1030)
>>>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>> at javax.naming.InitialContext.doLookup(InitialContext.java:265)
>>>  at
>>> org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:90)
>>> *
>>> *
>>> *
>>>
>>>
>>>
>>> On 14 May 2013 15:43, Vijayaratha Vijayasingam  wrote:
>>>
>>>> Hi all;
>>>> we are getting above issue in APIManager 1.4.0, with multiple userstore
>>>> configuration.
>>>> What we did is, after publishing/subscribing the API, we allowed the
>>>> store app to session timeout then re login the system. We couldnt see the
>>>> APIs at that time;
>>>> The error we got is.
>>>>
&g

Re: [Dev] javax.naming.NameNotFoundException: Name [jdbc/WSO2UM1] is not bound in this Context. Unable to find [jdbc]

[Hasini Gunasinghe]

Hi Ratha,

On Thu, May 16, 2013 at 10:43 AM, Vijayaratha Vijayasingam
wrote:

> Hi all;
> I checked the user.core component to find out the root cause.
> When we login from api store to retrieve public apis, we do
> an iteration for all tenant's publicAPI. For that we check the
> particular tenant's  registry. Registry calls-->usercore-->realmservice,
> where we  initialize the relamConfiguration for tenants.
>

Do you observe this issue only when you go through the aforementioned flow?
If so, you need to make sure that it is initiated in the correct tenant
scope.

AFAIK, already existing multi tenant operations work fine in the APIM pack
- eg: tenant creation, tenant login etc.., where the tenant specific realm
initialization work fine without issue. Therefore, IMO, this can not be a
generic issue in user.core - rather you might have observed this due to the
way you initialize the above flow.

Thanks,
Hasini.


> When we try to initialize the realm, system couldn't do lookup for the
> particular datasource; which is *jdbc/WSO2UM1.* (this datasources we
> define for multiple userstore)
> The error im getting for this is[1];
> But when we start the server, system is able to initialize the realm
> configuration properly, that is it is able to do jndi lookup properly. What
> might be the issue? (I found some similar issues , but all stating driver
> is missing or, entry is wrong etc..but none is relevant to me)
>  There is a carbonjira also reported same and resolved, but the reason
> provided for the issue looks irrelevant for me[2].
> If anybody knows the root cause please reply to the thread.
> p.s: attched the uesrmgt+datasourec
>
> Thanks.
>
> [2]https://wso2.org/jira/browse/CARBON-11674
>
> *
> *
> *[1]*
> *
> Caused by: javax.naming.NameNotFoundException: Name [jdbc/WSO2UM1] is not
> bound in this Context. Unable to find [jdbc].
>  at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
>  at org.apache.naming.SelectorContext.lookup(SelectorContext.java:158)
> at
> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:1030)
>  at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at javax.naming.InitialContext.doLookup(InitialContext.java:265)
>  at
> org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:90)
> *
> *
> *
>
>
>
> On 14 May 2013 15:43, Vijayaratha Vijayasingam  wrote:
>
>> Hi all;
>> we are getting above issue in APIManager 1.4.0, with multiple userstore
>> configuration.
>> What we did is, after publishing/subscribing the API, we allowed the
>> store app to session timeout then re login the system. We couldnt see the
>> APIs at that time;
>> The error we got is.
>>
>> ... 32 more
>> [2013-05-14 15:35:29,756] ERROR - DefaultRealm Cannot create
>> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager
>> java.lang.reflect.InvocationTargetException
>> at
>> sun.reflect.GeneratedConstructorAccessor126.newInstance(Unknown Source)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealm.createObjectWithOptions(DefaultRealm.java:225)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealm.initializeObjects(DefaultRealm.java:147)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:113)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.getTenantUserRealm(DefaultRealmService.java:169)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:267)
>> 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.getLocalRepository(EmbeddedRegistryService.java:481)
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getLocalRepository(CarbonRepositoryUtils.java:351)
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getDeploymentSyncConfigurationFromRegistry(CarbonReposito
>> ryUtils.java:257)
>>
>>
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: java.lang.reflect.InvocationTargetException
>> at
>> sun.reflect.GeneratedConstructorAccessor126.newInsta

[Dev] [Important] Issue in trunk when referencing carbon taglib uri

[Hasini Gunasinghe]

Hi,

So far, the taglib uri "
http://wso2.org/projects/carbon/taglibs/carbontags.jar"; with
prefix="carbon" has been mapped to carbontags.tld in org.wso2.carbon.ui
bundle. This was working fine till kernel 4.0.7

However, in latest trunk, the above uri is referenced to carbontags.tld
in jstl_1.2.1.wso2v1.jar.

Therefore, any updates we do in org.wso2.carbon.ui tag definitions, do not
get effected when referenced with the same above uri.

Could some one please clarify why the carbontags.tld is duplicated
inside jstl_1.2.1.wso2v1.jar and referenced with the same uri?

Due to this issue, the UI functionality of IS related to new updates in
carbon.ui is broken. Therefore, we need to fins a solution for this asap.

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

Re: [Dev] kernal server startup fail - 4.2.0.SNAPSHOT

[Hasini Gunasinghe]

Test failures are not due to the above fixes. There were some test failures
due to multiple user store changes and most of them are fixed now.
There are two more test failures to be fixed. They too will be fixed soon.

Thanks,
Hasini.


On Mon, May 13, 2013 at 10:20 PM, Shameera Rathnayaka wrote:

> Yes this issue has been fixed with latest commit, But now there are few
> test failures in org.wso2.carbon.user.core component.
>
> Thanks,
> Shameera.
>
>
> On Mon, May 13, 2013 at 6:32 PM, Hasini Gunasinghe wrote:
>
>> This is fixed with r172277
>>
>> Thanks,
>> Hasini.
>>
>>
>> On Mon, May 13, 2013 at 5:14 PM, Shameera Rathnayaka 
>> wrote:
>>
>>> Hi Hasinin/Darshana,
>>>
>>> This issue is still there in current trunk. According to my findings,
>>>  org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.java expect
>>> tenant-mgt.xml file inside the repository/conf/ directory but that is not
>>> there. Please have a look.
>>>
>>> Thanks,
>>> Shameera.
>>>
>>>
>>> On Fri, May 10, 2013 at 3:04 PM, Ananda Manoj Kumara wrote:
>>>
>>>> Hi,
>>>>
>>>> What I was referring was trunk/kernal server. In
>>>> /repository/conf/ there is no   tenant-mgt.xml file. It
>>>> has a user-mgt.xml and I checked it but it doesn't have those tags you
>>>> mentioned.
>>>>
>>>>
>>>> Thanks,
>>>> Manoj
>>>>
>>>> On 5/10/13, Darshana Gunawardana  wrote:
>>>> > Hi Manoj,
>>>> >
>>>> > Can you please list the contents of tenant-mgt.xml which is located in
>>>> > /repository/conf/
>>>> >
>>>> > There should be an element like this,
>>>> > >>> > class="org.wso2.carbon.user.core.tenant.JDBCTenantManager">
>>>> > >>> >
>>>> name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder
>>>> > 
>>>> >
>>>> > Thanks,
>>>> > Darshana.
>>>> >
>>>> >
>>>> >
>>>> > On Fri, May 10, 2013 at 11:56 AM, Ananda Manoj Kumara
>>>> > wrote:
>>>> >
>>>> >> Hi,
>>>> >>
>>>> >> Getting following error when I started the server,
>>>> >>
>>>> >>
>>>> >> [2013-05-10 11:32:15,006]  INFO
>>>> >> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User
>>>> :
>>>> >> manoj, en-US, Asia/Colombo
>>>> >> [2013-05-10 11:32:15,573] ERROR
>>>> >> {org.wso2.carbon.user.core.internal.Activator} -  Cannot start User
>>>> >> Manager
>>>> >> Core bundle
>>>> >> org.wso2.carbon.user.core.UserStoreException: Error in locating
>>>> >> TenantManager compatible with PrimaryUserStore. Required a
>>>> TenantManager
>>>> >> using
>>>> >>
>>>> org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder in
>>>> >> tenant-mgt.xml.
>>>> >>  at
>>>> >>
>>>> org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.buildTenantMgtConfiguration(TenantMgtXMLProcessor.java:110)
>>>> >> at
>>>> >>
>>>> org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.buildTenantMgtConfigFromFile(TenantMgtXMLProcessor.java:68)
>>>> >>  at
>>>> >>
>>>> org.wso2.carbon.user.core.common.DefaultRealmService.buildTenantMgtConfig(DefaultRealmService.java:146)
>>>> >> at
>>>> >>
>>>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:90)
>>>> >>  at
>>>> >>
>>>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:117)
>>>> >> at
>>>> >>
>>>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67)
>>>> >>  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)

Re: [Dev] kernal server startup fail - 4.2.0.SNAPSHOT

[Hasini Gunasinghe]

This is fixed with r172277

Thanks,
Hasini.


On Mon, May 13, 2013 at 5:14 PM, Shameera Rathnayaka wrote:

> Hi Hasinin/Darshana,
>
> This issue is still there in current trunk. According to my findings,
>  org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.java expect
> tenant-mgt.xml file inside the repository/conf/ directory but that is not
> there. Please have a look.
>
> Thanks,
> Shameera.
>
>
> On Fri, May 10, 2013 at 3:04 PM, Ananda Manoj Kumara wrote:
>
>> Hi,
>>
>> What I was referring was trunk/kernal server. In
>> /repository/conf/ there is no   tenant-mgt.xml file. It
>> has a user-mgt.xml and I checked it but it doesn't have those tags you
>> mentioned.
>>
>>
>> Thanks,
>> Manoj
>>
>> On 5/10/13, Darshana Gunawardana  wrote:
>> > Hi Manoj,
>> >
>> > Can you please list the contents of tenant-mgt.xml which is located in
>> > /repository/conf/
>> >
>> > There should be an element like this,
>> > > > class="org.wso2.carbon.user.core.tenant.JDBCTenantManager">
>> > > >
>> name="MultiTenantRealmConfigBuilder">org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder
>> > 
>> >
>> > Thanks,
>> > Darshana.
>> >
>> >
>> >
>> > On Fri, May 10, 2013 at 11:56 AM, Ananda Manoj Kumara
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> Getting following error when I started the server,
>> >>
>> >>
>> >> [2013-05-10 11:32:15,006]  INFO
>> >> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User
>>   :
>> >> manoj, en-US, Asia/Colombo
>> >> [2013-05-10 11:32:15,573] ERROR
>> >> {org.wso2.carbon.user.core.internal.Activator} -  Cannot start User
>> >> Manager
>> >> Core bundle
>> >> org.wso2.carbon.user.core.UserStoreException: Error in locating
>> >> TenantManager compatible with PrimaryUserStore. Required a
>> TenantManager
>> >> using
>> >> org.wso2.carbon.user.core.config.multitenancy.SimpleRealmConfigBuilder
>> in
>> >> tenant-mgt.xml.
>> >>  at
>> >>
>> org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.buildTenantMgtConfiguration(TenantMgtXMLProcessor.java:110)
>> >> at
>> >>
>> org.wso2.carbon.user.core.config.TenantMgtXMLProcessor.buildTenantMgtConfigFromFile(TenantMgtXMLProcessor.java:68)
>> >>  at
>> >>
>> org.wso2.carbon.user.core.common.DefaultRealmService.buildTenantMgtConfig(DefaultRealmService.java:146)
>> >> at
>> >>
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:90)
>> >>  at
>> >>
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:117)
>> >> at
>> >>
>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67)
>> >>  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:390)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
>> >>  at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
>> >>  at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
>> >>  at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
>> >>  at
>> >>
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> >> at
>> >>
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
>> >>
>> >> Thanks,
>> >> Manoj
>> >>
>> >>
>> >>
>> >> Best Regards..
>> >>
>> >>
>> >> Manoj Kumara
>> >> Software Engineer
>> >> WSO2, Inc.; http://wso2.com
>> >>
>> >> Twitter:  http://twitter.com/ManKuma
>> >> Mobile: +94713448188
>> >>
>> >> ___
>> >> Dev mailing list
>> >> Dev@wso2.org
>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >>
>> >>
>> >
>> >
>> > --
>> > Regards,
>> >
>> > *
>> > Darshana Gunawardana
>> > *Software Engineer
>> > WSO2 Inc.; http://wso2.com*
>> > E-mail: darsh...@wso2.com
>> > **Mobile: +94718566859
>> > *Lean . Enterprise . Middleware
>> >
>>
>>
>> --
>> Best Regards

Re: [Dev] [Trunk] Build failed in appfactory components

[Hasini Gunasinghe]

Getting the same error in the latest trunk as well.

Thanks,
Hasini.


On Mon, Apr 22, 2013 at 1:11 PM, Johann Nallathamby  wrote:

> Hi,
>
> This is due to the new user.core API changes. This code needs to be
> updated to work with the new user.core.
>
> Thanks,
> Johann.
>
>
> On Mon, Apr 22, 2013 at 12:52 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi,
>>
>> Getting the following error in platform trunk. Please fix this.
>>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 21.980s
>> [INFO] Finished at: Mon Apr 22 12:39:11 IST 2013
>> [INFO] Final Memory: 237M/1119M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.appfactory.userstore:
>> Compilation failure: Compilation failure:
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[32,19]
>> authenticate(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> authenticate(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[45,20]
>> listUsers(java.lang.String,int) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> listUsers(java.lang.String,int) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[66,16]
>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>> in org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> addUser(java.lang.String,java.lang.Object,java.lang.String[],java.util.Map,java.lang.String,boolean)
>> in org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR]
>> /home/kicha/checkouts/wso2/carbon/platform/merged-trunk/trunk/components/appfactory/org.wso2.carbon.appfactory.userstore/src/main/java/org/wso2/carbon/appfactory/userstore/AppFactoryUserStore.java:[77,16]
>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.appfactory.userstore.AppFactoryUserStore cannot override
>> updateCredentialByAdmin(java.lang.String,java.lang.Object) in
>> org.wso2.carbon.user.core.common.AbstractUserStoreManager; overridden
>> method is final
>> [ERROR] -> [Help 1]
>> [ERROR]
>>
>> Thanks,
>> Kishanthan.
>> --
>> *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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 IS 4.1.1 Active directory read-only mode can write to the AD

[Hasini Gunasinghe]

Hi Nuwan,

It is the "ReadOnlyLDAPUserStoreManager" that you need to use for read only
access to AD.

Thanks,
Hasini.

On Wed, Mar 27, 2013 at 9:08 PM, Nuwan Bandara  wrote:

> Hi Guys,
>
> My configurations is,
>
>  class="org.wso2.carbon.user.core.ldap.ActiveDirectoryUserStoreManager">
> true
> WSO2.ORG
> bar.com
> false
>
> false
> ldaps://10.100.3.131:636
> 
>  name="ConnectionName">CN=#,CN=Users,DC=WSO2,DC=Com
> #
> PLAIN_TEXT
>  name="UserSearchBase">CN=Users,DC=WSO2,DC=Com
> ...
>
>
> Even though the readonly property is true, I can add new users to the AD.
> I am testing in multiple user store mode with AD as the secondary store.
>
> 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 mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Check what keystore is used on carbon application

[Hasini Gunasinghe]

Hi Ananda,

Default keystore is wso2carbon.jks. But it is not appropriate to check just
the keystore name, because someone can create their own keystore with the
same name. One thing you can consider is, obtain the public certificate
associated with the private key of the default keystore, read the CN value
and check if it is the same as in public cert in the default keystore.

Thanks,
Hasini.

On Tue, Mar 19, 2013 at 4:45 PM, Ananda Manoj Kumara  wrote:

> hi,
>
> currently I'm trying to add a warning at the carbon server start-up to
> check wether the custemer using the default JKS. If so need to notify the
> customer about security risks when default keystore is used. so during
> application start I need to check what keystore is used.
>
> thank you
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Tue, Mar 19, 2013 at 3:56 PM, Ananda Manoj Kumara wrote:
>
>> Hi,
>>
>>  I need to check which keystore is used on the carbon application at
>> runtime. How can I get that property.
>>
>>
>>
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>
>
> ___
> 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

Re: [Dev] Compilation error in components/identity/org.wso2.carbon.identity.oauth/4.0.8

[Hasini Gunasinghe]

Compilation failures that were in oauth component are fixed.

Thanks,
Hasini.

On Thu, Feb 28, 2013 at 8:18 PM, Dinusha Senanayaka wrote:

> Could you check it please..Build triggered with r166369..
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.identity.oauth: Compilation
> failure: Compilation failure:
> [ERROR]
> /home/wso2/4.0.8/platform/4.0.0/components/identity/org.wso2.carbon.identity.oauth/4.0.8/src/main/java/org/wso2/carbon/identity/oauth2/token/handlers/grant/AbstractAuthorizationGrantHandler.java:[50,16]
> duplicate class:
> org.wso2.carbon.identity.oauth2.token.handlers.AbstractAuthorizationGrantHandler
> [ERROR]
> /home/wso2/4.0.8/platform/4.0.0/components/identity/org.wso2.carbon.identity.oauth/4.0.8/src/main/java/org/wso2/carbon/identity/oauth2/token/handlers/grant/AuthorizationCodeHandler.java:[36,-1]
> cannot access
> org.wso2.carbon.identity.oauth2.token.handlers.grant.AbstractAuthorizationGrantHandler
> [ERROR] bad class file:
> /home/wso2/4.0.8/platform/4.0.0/components/identity/org.wso2.carbon.identity.oauth/4.0.8/src/main/java/org/wso2/carbon/identity/oauth2/token/handlers/grant/AbstractAuthorizationGrantHandler.java
> [ERROR] file does not contain class
> org.wso2.carbon.identity.oauth2.token.handlers.grant.AbstractAuthorizationGrantHandler
>
> Regards,
> Dinusha.
>
>
>
> ___
> 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

Re: [Dev] Assigning roles for users through Management console throws errors

[Hasini Gunasinghe]

Hi Lakmali,

I tested the above scenario with latest user.core and it works fine.
Issue you faced might be fixed with other fixes we added.

Can you please take a svn up in user.core and check again?

Thanks,
Hasini.

On Thu, Feb 28, 2013 at 5:36 PM, Lakmali Baminiwatta wrote:

> Hi ,
>
>
> On Thursday, 28 February 2013, Nuwan Dias  wrote:
> > Hi,
> > Are you having multiple user stores enabled in the user-mgt.xml? I have
> seen this error before when I try to assign a role in one user store to a
> user in another user store.
>
> No this is in the standalone mode. Also I am getting these errors with
> latest user core changes.
>
> Thanks,
> Lakmali
>
>
> > Thanks,
> > NuwanD.
> >
> > On Thu, Feb 28, 2013 at 5:06 PM, Lakmali Baminiwatta 
> wrote:
> >>
> >> Hi all,
> >>
> >> In APIM management console, I created a new role with API create
> permission.
> >> The created a new user, and selected the above role for that user.
> >> Then when I save the user, following exceptions are thrown.
> >>
> >>
> >> ERROR - DatabaseUtil NULL not allowed for column "UM_ROLE_ID"; SQL
> statement:
> >> INSERT INTO UM_USER_ROLE (UM_ROLE_ID, UM_USER_ID, UM_TENANT_ID) VALUES
> ((SELECT UM_ID FROM UM_ROLE WHERE UM_ROLE_NAME=? AND
> UM_TENANT_ID=?),(SELECT UM_ID FROM UM_USER WHERE UM_USER_NAME=? AND
> UM_TENANT_ID=?), ?) [90006-140]
> >> org.h2.jdbc.JdbcBatchUpdateException: NULL not allowed for column
> "UM_ROLE_ID"; SQL statement:
> >> INSERT INTO UM_USER_ROLE (UM_ROLE_ID, UM_USER_ID, UM_TENANT_ID) VALUES
> ((SELECT UM_ID FROM UM_ROLE WHERE UM_ROLE_NAME=? AND
> UM_TENANT_ID=?),(SELECT UM_ID FROM UM_USER WHERE UM_USER_NAME=? AND
> UM_TENANT_ID=?), ?) [90006-140]
> >> at
> org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedStatement.java:1098)
> >> at
> org.wso2.carbon.user.core.util.DatabaseUtil.udpateUserRoleMappingInBatchMode(DatabaseUtil.java:352)
> >> at
> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.persistUser(JDBCUserStoreManager.java:1003)
> >> at
> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.doAddUser(JDBCUserStoreManager.java:910)
> >> at
> org.wso2.carbon.user.core.common.AbstractUserStoreManager.addUser(AbstractUserStoreManager.java:1078)
> >> at
> org.wso2.carbon.user.mgt.UserRealmProxy.addUser(UserRealmProxy.java:360)
> >> at org.wso2.carbon.user.mgt.UserAdmin.addUser(UserAdmin.java:119)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> at java.lang.reflect.Method.invoke(Method.java:597)
> >> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> >> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
> >> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> >> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> >> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> >> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> >> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> >> at
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
> >> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> >> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
> >> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
> >> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> >> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1529)
> >> at
> org.wso2.carbon.user.mgt.ui.UserAdminClient.addUser(UserAdminClient.java:105)
> >> at
> org.apache.jsp.user.add_002dfinish_jsp._jspService(add_002dfinish_jsp.java:132)
> >> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> >> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
> >> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> >> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> >> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161)
> >> at
> org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> >> at javax.ser

Re: [Dev] Issues in APIManager latest builds, due to recent changes done in Kernel

[Hasini Gunasinghe]

I will look into this..

Thanks,
Hasini.

On Wed, Feb 27, 2013 at 3:32 PM, Lakmali Baminiwatta wrote:

>
>
>
> On 27 February 2013 12:40, Sumedha Rubasinghe  wrote:
>
>> org.wso2.carbon.identity.self.registration.server.feature is still
>> pointing to the old user core.
>>
>> Prabath is updating it now..
>>
>
> The above mentioned issue is fixed now. But when saving the user following
> exception is thrown.
>
>
> [2013-02-27 15:26:55,746] ERROR - JDBCUserStoreManager Null data provided.
> org.wso2.carbon.user.core.UserStoreException: Null data provided.
> at
> org.wso2.carbon.user.core.util.DatabaseUtil.udpateUserRoleMappingInBatchMode(DatabaseUtil.java:335)
> at
> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.persistUser(JDBCUserStoreManager.java:1071)
> at
> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.doAddUser(JDBCUserStoreManager.java:979)
> at
> org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.doAddUser(JDBCUserStoreManager.java:968)
> at
> org.wso2.carbon.user.core.common.AbstractUserStoreManager.addUser(AbstractUserStoreManager.java:1121)
> at
> org.wso2.carbon.identity.user.registration.UserRegistrationService.addUser(UserRegistrationService.java:152)
> at
> org.wso2.carbon.identity.user.registration.UserRegistrationService.addUser(UserRegistrationService.java:100)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:172)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadP

Re: [Dev] Build error in org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Above build error got fixed after building latest orbit patch release.

Thanks,
Hasini.

On Mon, Feb 25, 2013 at 8:28 PM, Hasini Gunasinghe  wrote:

> Hi,
>
> I am getting the following build error when building 4.0.8 platform-patch
> release - in an online build.
>
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.registry.extensions: Could not resolve dependencies for
> project org.wso2.carbon:org.wso2.carbon.registry.extensions:bundle:4.0.8:
> Could not find artifact org.wso2.wadl.core.wso2:wadl-core:jar:1.1.3.wso2v1
> in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
> -> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions
>
> Thanks,
> Hasini.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build error in org.wso2.carbon.registry.extensions

[Hasini Gunasinghe]

Hi,

I am getting the following build error when building 4.0.8 platform-patch
release - in an online build.

[ERROR] Failed to execute goal on project
org.wso2.carbon.registry.extensions: Could not resolve dependencies for
project org.wso2.carbon:org.wso2.carbon.registry.extensions:bundle:4.0.8:
Could not find artifact org.wso2.wadl.core.wso2:wadl-core:jar:1.1.3.wso2v1
in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.registry.extensions

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

Re: [Dev] Build Error - 4.0.7 patch-release - could not find "org.wso2.carbon:org.wso2.carbon.cep.siddhi:jar:4.0.5"

[Hasini Gunasinghe]

I got a similar build error due to cep/org.wso2.carbon.cep.siddhi/4.0.7 not
in the patch release pom. Fixed it with r160741.

Thanks,
Hasini.

On Sat, Feb 2, 2013 at 12:13 AM, Sriskandarajah Suhothayan wrote:

> Thanks for reporting
> Fixed the issue in r160231.
>
> Suho
>
> On Fri, Feb 1, 2013 at 4:54 PM, Dulanja Liyanage  wrote:
>
>> Hi,
>>
>> $subject. Maven error log is.
>>
>> ERROR] Failed to execute goal on project
>> org.wso2.carbon.cep.server.feature: Could not resolve dependencies for
>> project org.wso2.carbon:org.wso2.carbon.cep.server.feature:pom:4.0.7: Could
>> not find artifact org.wso2.carbon:org.wso2.carbon.cep.siddhi:jar:4.0.5 in
>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
>> [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
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :org.wso2.carbon.cep.server.feature
>>
>> Thanks
>> Dulanja
>> --
>> Dulanja Liyanage
>> Senior Software Engineer - WSO2 Inc.
>> M: +94776764717
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *S. Suhothayan
> *
> Software Engineer,
> Data Technologies Team,
>  *WSO2, Inc. **http://wso2.com
>  *
> *lean.enterprise.middleware.*
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* 
> *
> twitter: **http://twitter.com/suhothayan* *
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
> ___
> 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

Re: [Dev] IS 4.1.0 build failure P2-profile generation

[Hasini Gunasinghe]

Hi Dharshana,

I could build IS without any issue yesterday with a latest svn up.

Thanks,
Hasini.

On Sun, Jan 27, 2013 at 5:14 AM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:

> Hi ,
>
> Im Getting following error in IS p2- profile generation.
>
>
> Installing org.wso2.identity.ui.feature.group 4.0.0.
> Installing org.wso2.stratos.identity.saml2.sso.mgt.feature.group 2.0.6.
> Installing org.wso2.carbon.stratos.usage.agent.feature.group 2.0.5.
> Installing org.wso2.carbon.stratos.throttling.agent.feature.group 2.0.5.
> Installing org.wso2.carbon.registry.contentsearch.feature.group 4.0.5.
> Installing org.wso2.carbon.stratos.deployment.feature.group 2.0.0.
> Installation failed.
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: WSO2 Carbon - Registry Content Search Feature
> 4.0.5 (org.wso2.carbon.registry.contentsearch.feature.group 4.0.5)
>  Software being installed: WSO2 Carbon - Registry Core Common Feature
> 4.0.5 (org.wso2.carbon.registry.core.common.feature.group 4.0.5)
>  Only one of the following can be installed at once:
>   WSO2 Carbon - Registry Core Common Feature 4.0.2
> (org.wso2.carbon.registry.core.common.feature.jar 4.0.2)
>   WSO2 Carbon - Registry Core Common Feature 4.0.5
> (org.wso2.carbon.registry.core.common.feature.jar 4.0.5)
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Content Search Feature 4.0.5
> (org.wso2.carbon.registry.contentsearch.feature.group 4.0.5)
>   To: org.wso2.carbon.registry.core.feature.group [4.0.0,4.1.0)
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Core Common Feature 4.0.2
> (org.wso2.carbon.registry.core.common.feature.group 4.0.2)
>   To: org.wso2.carbon.registry.core.common.feature.jar [4.0.2]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Core Common Feature 4.0.5
> (org.wso2.carbon.registry.core.common.feature.group 4.0.5)
>   To: org.wso2.carbon.registry.core.common.feature.jar [4.0.5]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Core Feature 4.0.5
> (org.wso2.carbon.registry.core.feature.group 4.0.5)
>   To: org.wso2.carbon.registry.core.common.feature.group [4.0.2]
> Application failed, log file location:
> /home/dharshana/.m3/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1359242869399.log
>
>
>
> Thank You,
> Dharshana.
>
> Dharshana Warusavitharana
> Software Engineer , Test Automation
> WSO2 Inc. http://wso2.com
> email : dharsha...@wso2.com 
> cell : +94772202595
> blog : http://dharshanaw.blogspot.com
>
> lean . enterprise . middleware
>
___
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] 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

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

[Hasini Gunasinghe]

On Thu, Jan 24, 2013 at 12:38 PM, Dinuka Malalanayake wrote:

> Hi Nuwan,
>
> Its like this, the first configuration in the user-mgt.xml consider as a
> primary one and all others are secondary
>

And as per the recent improvements we have done, convention is not to have
domain name for primary user store.

Thanks,
Hasini.

>
>
> On Thu, Jan 24, 2013 at 12:33 PM, Nuwan Dias  wrote:
>
>> How is it that we distinguish the primary user store from the others?
>>
>> In the carbon 4.0.5 release, the user store defined in the top most
>>  element in the user-mgt.xml was considered primary. Are
>> we going with the same principle or are we going to consider the user store
>> which lacks the 'DomainName' property as primary?
>>
>> On a side note, I came across an issue when the 'DomainName' property is
>> set. Jira reported at [1].
>>
>> [1] - https://wso2.org/jira/browse/IDENTITY-644
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Thu, Jan 24, 2013 at 12:26 PM, Dinuka Malalanayake 
>> wrote:
>>
>>> Even if we applied this domain name for primary user store *
>>> domain.com/wso2.anonymous.user *will appear in the management console.
>>>
>>>
>>>
>>> On Thu, Jan 24, 2013 at 12:22 PM, Dinuka Malalanayake 
>>> wrote:
>>>
 Hi All,

 By default domain name (domain.com) is there in user-mgt.xml for the
 primary user store.
 This is ok, but the case is when we try to log in to the IS with* un-
 domain.com/admin pw - admin *it didn't work.
 If we are not supporting this domain name for primary user store we
 have to remove form default configurations.


 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

>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Engineer - WSO2, Inc.
>> Integration Technologies Team
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> 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 mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Basic development completed for SCIM BulkEndpoint

[Hasini Gunasinghe]

I have reviewed and committed your code and design diagrams to Charon trunk.
Also added some comments for improvements in the jira [1] itself.
Well done and thank for the contribution.

[1] https://wso2.org/jira/browse/COMMONS-90

Thanks,
Hasini.

On Sat, Jan 19, 2013 at 12:06 PM, Dinuka Malalanayake wrote:

> Hi Hasini,
>
> Successfully done all the changes that you have mention. I have attached
> the patch in to Jira [1].
> Is there anything need to be change please feel free to comment.
>
> [1] https://wso2.org/jira/browse/COMMONS-90
>
>
> On Wed, Jan 16, 2013 at 11:44 PM, Dinuka Malalanayake wrote:
>
>> Hi Hasini,
>>
>> I have changed the UML diagrams according to your comments.
>> Please refer the attached images. If there is any changes need to be done
>> feel free to comment.
>>
>>
>> On Fri, Jan 11, 2013 at 4:59 PM, Dinuka Malalanayake wrote:
>>
>>> Hi Hasini,
>>>
>>> Thanks for the comments. Ill be back with corrections and improvements.
>>>
>>>
>>> On Fri, Jan 11, 2013 at 4:47 PM, Hasini Gunasinghe wrote:
>>>
>>>> Hi Dinuka,
>>>>
>>>> Went through the code and please find the points for improvement below:
>>>>
>>>> - Like in other endpoints, you can select the encoder, decoder
>>>> dynamically based on the content type and accept headers without hard
>>>> coding the JSON encoder and JSON decoder.
>>>> - In an improved version, bulk requests needs to be processed in a
>>>> generic manner and distinguish different operations based on "method" and
>>>> "path" in each operation. BulkRequestProcessor, BulkRequestData and
>>>> BulkResponseData in your patch could be improved accordingly.
>>>> - SCIMClient API could be improved to generate the payload in a generic
>>>> manner and use that in the sample provided in this patch.
>>>> - When improving this, we can avoid hard coded values as much as
>>>> possible. For eg: 200 OK in response in BulkResourceEndpoint
>>>> - Please use constants to refer to different values in the code.
>>>> Refer SCIMConstants and its usages.
>>>> - Please use the wso2-coding styles found at
>>>> https://sites.google.com/a/wso2.com/engineering/Home/masteringintellijidea
>>>> .
>>>>
>>>> It is good that you have done the design diagrams too. We can add them
>>>> under documentations [1].
>>>> - You can use UML notations to show the relationships between the
>>>> classes in the class diagram
>>>>
>>>> [1] https://svn.wso2.org/repos/wso2/trunk/commons/charon/documentation/
>>>>
>>>> Overall It is a very good job. Hope above comments would help you to
>>>> further improve.
>>>>
>>>> Thanks,
>>>> Hasini.
>>>>
>>>>
>>>> On Tue, Jan 8, 2013 at 12:42 PM, Hasini Gunasinghe wrote:
>>>>
>>>>> Great job Dinuka..!
>>>>> Appreciate a lot all your voluntarily efforts on adding bulk endpoint
>>>>> to Charon.. I think we can try to ship this with IS 4.1.0, if time 
>>>>> permits.
>>>>> Will review it and get back to you with the feedback.. And once it is
>>>>> completed, we also can have a code review session when you have some free
>>>>> time..
>>>>>
>>>>> Thanks,
>>>>> Hasini,
>>>>>
>>>>>
>>>>> On Mon, Jan 7, 2013 at 11:52 AM, Dinuka Malalanayake >>>> > wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I have complete the basic development of SCIM bulk endpoint. This is
>>>>>> created according to the specification [1]. Appreciate if some one can do
>>>>>> the code review and give me some feedback.
>>>>>>
>>>>>> Sequence diagram and class association diagram attached here with
>>>>>>
>>>>>> As well as I have attached the patch file as a improvement in Commons
>>>>>> project [2]
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>> http://www.simplecloud.info/specs/draft-scim-api-01.html#delete-resource
>>>>>>
>>>>>> [2] https://wso2.org/jira/browse/COMMONS-90
>>>>>>
>>>>>> --
>>>>>> Thanks,
>>>>>> Dinuka Malalanayake
>>>>>> *So

Re: [Dev] [BUILD FAILED] WSO2 Carbon 4.0.x - Kernel 4.0.6 build #23

[Hasini Gunasinghe]

Hi Maheshika,

user.api:4.0.6 has been added to patch release pom with r153421.
May be the build was run in between the commits r153371 and r153421..
Taking svn up in kernel/patch-release/4.0.6/core/pom.xml will solve this.

Thanks,
Hasini.

On Fri, Jan 18, 2013 at 4:54 PM, Maheshika Goonetilleke
wrote:

> Hi All
>
> Kernel 4.0.6 build #23 has failed to the following error;
>
>  18-Jan-2013 02:15:42 [INFO]
> 18-Jan-2013
> 02:15:42 [INFO] BUILD FAILURE 18-Jan-2013 02:15:42[INFO]
>  
> 18-Jan-2013
> 02:15:42 [INFO] Total time: 2:01.087s18-Jan-2013 02:15:42 [INFO] Finished
> at: Fri Jan 18 02:15:42 PST 201318-Jan-2013 02:15:42 [INFO] Final Memory:
> 96M/736M18-Jan-2013 02:15:44 [INFO]
> 18-Jan-2013
> 02:15:44 [ERROR] Failed to execute goal on project
> org.wso2.carbon.user.core: Could not resolve dependencies for project
> org.wso2.carbon:org.wso2.carbon.user.core:bundle:4.0.6: Could not find
> artifact org.wso2.carbon:org.wso2.carbon.user.api:jar:4.0.6 in wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1] 
> 18-Jan-2013
> 02:15:44 [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5:p2-feature-gen
> (4-p2-feature-generation) on project org.wso2.carbon.core.common.feature:
> ERROR: Failure to find org.wso2.carbon:org.wso2.carbon.user.api:jar:4.0.6
> 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 18-Jan-2013
> 02:15:44 [ERROR]
>
>
> Can someone please check on this.
>
> http://wso2.org/bamboo/browse/WCB001-KER006-JOB1-23/log
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
> WSO2 Inc
>
> www.wso2.com/
>
> M : 0773 596707
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ApacheDSUserStoreManager Not found exception, App Server 5.0.1

[Hasini Gunasinghe]

Hi Charitha,

org.wso2.carbon.user.core.ldap.ApacheDSUserStoreManager has been
renamed to org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager
from Carbon 4.0.0 onwards.

And user-mgt.xml file is updated accordingly. Are you using an old
user-mgt.xml?

Thanks,
Hasini.

On Fri, Jan 18, 2013 at 3:12 PM, Charitha Goonetilleke
wrote:

> org.wso2.carbon.user.core.ldap.ApacheDSUserStoreManager
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Registry core test failure after updating the dependency version

[Hasini Gunasinghe]

Hi,

I get the following test failure after updating dependency: user.core
version of registry.core to 4.0.6.
Any idea what might the cause for this?

testVersioningProperties(org.wso2.carbon.registry.core.test.jdbc.StaticConfigurationTrueTest)
 Time elapsed: 3.075 sec  <<< ERROR!
java.lang.NoClassDefFoundError:
org/wso2/carbon/ndatasource/rdbms/RDBMSConfiguration
at
org.wso2.carbon.user.core.util.DatabaseUtil.createRealmDataSource(DatabaseUtil.java:180)
at
org.wso2.carbon.user.core.util.DatabaseUtil.getRealmDataSource(DatabaseUtil.java:72)
at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:125)
at
org.wso2.carbon.registry.core.jdbc.realm.InMemoryRealmService.(InMemoryRealmService.java:67)
at
org.wso2.carbon.registry.core.test.utils.BaseTestCase.setupContext(BaseTestCase.java:41)
at
org.wso2.carbon.registry.core.test.jdbc.StaticConfigurationTrueTest.setUp(StaticConfigurationTrueTest.java:46)

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

[Dev] IS 4.1.0-M1 pack for testing

[Hasini Gunasinghe]

Hi,

Please find the IS 4.1.0-M1 pack at
https://svn.wso2.org/repos/wso2/scratch/wso2is-4.1.0/M1.

This M1 pack newly includes:
- OAuth token revocation feature
- Improvements to multiple user store feature
- Fixes for bugs reported on IS 4.0.0

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

Re: [Dev] Platform patch release 4.0.7 added to the branch

[Hasini Gunasinghe]

Hi Pradeep,

On Wed, Jan 16, 2013 at 7:38 PM, Pradeep Fernando  wrote:

> hi all,
>
> - we should not create 4.0.7 components till we release 4.0.6 ones. When
> you create 4.0.6 components, add them to the patch release poms, it has
> nothing to do with product releases.
> - do not include your  *product* build in patch release pom if it is not
> get released with current patch release cycle. do the product builds
> separately  (for alpha/beta releases based on 4.0.6 components)
>

When set of products get released, it is not quite feasible to build the
products without adding them to patch release pom - specially when we are
taking builds from builder machine. Also, 4.0.7 products needs 4.0.6 kernel
to be built while 4.0.6 products do not.

- You guys havent done anything wrong, but above is the convention that we
> sticked to..
>

If there is not anything wrong, can't we change the convention when
requirement arises and for valid requirement?  :)

Thanks,
Hasini.

>
> I know, this is a tedious thing to do. Lets refine the process in the next
> release. :)
>
> thanks,
> --Pradeep
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform patch release 4.0.7 added to the branch

[Hasini Gunasinghe]

On Wed, Jan 16, 2013 at 5:02 PM, Dileepa Jayakody  wrote:

>
>
> On Wed, Jan 16, 2013 at 4:19 PM, Hasini Gunasinghe wrote:
>
>> Hi all,
>>
>> FYI...
>> - $subject was done for the products to be released with platform 4.0.7
>> - IS 4.1.0 uses kernel 4.0.6 which will also be released with platform
>> 4.0.7
>> - I hope there wont be issues in having two non-released platform patch
>> release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
>> if there is any..
>>
>
> I think this can result in the 4.0.6 tag having 4.0.7 components, then it
> will be not compliant to our previous releases isn't it?
> How about we commit the changes to 4.0.6 until it gets released and soon
> after copy the changes and create 4.0.7?
>

Yes, we have been doing that, but since products which are not released
with 4.0.6 were removed from 4.0.6 patch release, went for the option of
creating 4.0.7. We can add them back to 4.0.6 till it is released.

However, kernel 4.0.6 will not be released with platform 4.0.6 since 4.0.6
products are using kernel 4.0.5. Therefore, even if we move 4.0.7 products
and components to platform 4.0.6, we need to build kernel 4.0.6 with
platform 4.0.6 if we go for the above option. Won't that add an additional
overhead for 4.0.6 product release?

Thanks,
Hasini.


> - When building the packs for QA from builder machine, we can build
>> platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
>> - so that packs from both 4.0.6 and 4.0.7 will be available.
>>
>> Thanks,
>> Hasini.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Platform patch release 4.0.7 added to the branch

[Hasini Gunasinghe]

Hi all,

FYI...
- $subject was done for the products to be released with platform 4.0.7
- IS 4.1.0 uses kernel 4.0.6 which will also be released with platform 4.0.7
- I hope there wont be issues in having two non-released platform patch
release versions (i.e 4.0.6 and 4.0.7) at the moment - please let us know
if there is any..
- When building the packs for QA from builder machine, we can build
platform patch release 4.0.6, kernel 4.0.6 and platform patch release 4.0.7
- so that packs from both 4.0.6 and 4.0.7 will be available.

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

Re: [Dev] Basic development completed for SCIM BulkEndpoint

[Hasini Gunasinghe]

Hi Dinuka,

Went through the code and please find the points for improvement below:

- Like in other endpoints, you can select the encoder, decoder dynamically
based on the content type and accept headers without hard coding the JSON
encoder and JSON decoder.
- In an improved version, bulk requests needs to be processed in a generic
manner and distinguish different operations based on "method" and "path" in
each operation. BulkRequestProcessor, BulkRequestData and BulkResponseData
in your patch could be improved accordingly.
- SCIMClient API could be improved to generate the payload in a generic
manner and use that in the sample provided in this patch.
- When improving this, we can avoid hard coded values as much as possible.
For eg: 200 OK in response in BulkResourceEndpoint
- Please use constants to refer to different values in the code.
Refer SCIMConstants and its usages.
- Please use the wso2-coding styles found at
https://sites.google.com/a/wso2.com/engineering/Home/masteringintellijidea.

It is good that you have done the design diagrams too. We can add them
under documentations [1].
- You can use UML notations to show the relationships between the classes
in the class diagram

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

Overall It is a very good job. Hope above comments would help you to
further improve.

Thanks,
Hasini.

On Tue, Jan 8, 2013 at 12:42 PM, Hasini Gunasinghe  wrote:

> Great job Dinuka..!
> Appreciate a lot all your voluntarily efforts on adding bulk endpoint to
> Charon.. I think we can try to ship this with IS 4.1.0, if time permits.
> Will review it and get back to you with the feedback.. And once it is
> completed, we also can have a code review session when you have some free
> time..
>
> Thanks,
> Hasini,
>
>
> On Mon, Jan 7, 2013 at 11:52 AM, Dinuka Malalanayake wrote:
>
>> Hi All,
>>
>> I have complete the basic development of SCIM bulk endpoint. This is
>> created according to the specification [1]. Appreciate if some one can do
>> the code review and give me some feedback.
>>
>> Sequence diagram and class association diagram attached here with
>>
>> As well as I have attached the patch file as a improvement in Commons
>> project [2]
>>
>>
>> [1]
>> http://www.simplecloud.info/specs/draft-scim-api-01.html#delete-resource
>>
>> [2] https://wso2.org/jira/browse/COMMONS-90
>>
>> --
>> 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

Re: [Dev] Basic development completed for SCIM BulkEndpoint

[Hasini Gunasinghe]

Great job Dinuka..!
Appreciate a lot all your voluntarily efforts on adding bulk endpoint to
Charon.. I think we can try to ship this with IS 4.1.0, if time permits.
Will review it and get back to you with the feedback.. And once it is
completed, we also can have a code review session when you have some free
time..

Thanks,
Hasini,


On Mon, Jan 7, 2013 at 11:52 AM, Dinuka Malalanayake wrote:

> Hi All,
>
> I have complete the basic development of SCIM bulk endpoint. This is
> created according to the specification [1]. Appreciate if some one can do
> the code review and give me some feedback.
>
> Sequence diagram and class association diagram attached here with
>
> As well as I have attached the patch file as a improvement in Commons
> project [2]
>
>
> [1]
> http://www.simplecloud.info/specs/draft-scim-api-01.html#delete-resource
>
> [2] https://wso2.org/jira/browse/COMMONS-90
>
> --
> 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

Re: [Dev] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.sts.store:jar:4.0.5 in wso2-nexus

[Hasini Gunasinghe]

Thanks Chamara..

On Thu, Jan 3, 2013 at 4:38 PM, Chamara Silva  wrote:

> Issue fixed in revision 152711 and 152715.
>
> Regards,
> Chamara Silva
>
>
> On Thu, Jan 3, 2013 at 12:28 PM, Chamara Silva  wrote:
>
>> Look in to the issue.
>>
>> Regards,
>> Chamara Silva
>>
>>
>> On Thu, Jan 3, 2013 at 12:08 PM, Hasini Gunasinghe wrote:
>>
>>> Hi Chamara,
>>>
>>> Going though the commits, it seems like you have added the org.wso2.
>>> carbon.identity.sts.store-4.0.5 and included it in the
>>> identity.provider.server.feature-4.0.5, but not added it to
>>> 4.0.5-components-patch release pom.
>>> However, since the identity.provider.server.feature also was not
>>> included in the 4.0.5-features-patch release pom, it has not caused an
>>> issue during 4.0.5 release.
>>> When Suresh has copied from 4.0.5 feature into 4.0.6 and included it in
>>> the 4.0.6-features-patch release pom, this issue has occurred.
>>>
>>> I fixed it temporarily by changing the version of org.wso2.carbon.
>>> identity.sts.store to 4.0.3 in the feature pom.
>>>
>>> It would be great if all the steps are considered when adding a new
>>> version of a component to make sure that the fix is included up to the
>>> product level.
>>>
>>> Thanks,
>>> Hasini.
>>>
>>> On Thu, Jan 3, 2013 at 11:26 AM, Janaka Ranabahu wrote:
>>>
>>>> Hi Shariq,
>>>>
>>>> Yes, and as it seem the above mentioned version is not there is 4.0.5
>>>> patch release pom. Can someone please explain why we have a 4.0.5 component
>>>> that was not included in the release and why we have included that version
>>>> in the 4.0.6 feature? Also, if this was intended to be a 4.0.6 component,
>>>> please fix the version issue and the build.
>>>>
>>>> Thanks,
>>>> Janaka
>>>>
>>>>
>>>> On Thu, Jan 3, 2013 at 10:54 AM, Muhammed Shariq wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I checked in the patch release pom and org.wso2.carbon.identity.sts.store
>>>>> is not listed in the patch-release pom, so its not deployed in the repo ..
>>>>>
>>>>> [1] -
>>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/4.0.5/components/pom.xml
>>>>>
>>>>> On Thu, Jan 3, 2013 at 8:36 AM, Janaka Ranabahu wrote:
>>>>>
>>>>>> org.wso2.carbon.identity.sts.store
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Shariq.
>>>>> Phone: +94 777 202 225
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Janaka Ranabahu
>>>> Senior Software Engineer
>>>> WSO2 Inc.
>>>>
>>>> Mobile +94 718370861
>>>> Email : jan...@wso2.com
>>>> Blog : janakaranabahu.blogspot.com
>>>>
>>>
>>>
>>
>>
>> --
>> Suminda Chamara Silva
>> WSO2 Inc.
>> Mobile: +94718302858
>> blog: http://chamaras.blogspot.com
>>
>
>
>
> --
> Suminda Chamara Silva
> WSO2 Inc.
> Mobile: +94718302858
> blog: http://chamaras.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Could not find artifact org.wso2.carbon:org.wso2.carbon.identity.sts.store:jar:4.0.5 in wso2-nexus

[Hasini Gunasinghe]

Hi Chamara,

Going though the commits, it seems like you have added the org.wso2.carbon.
identity.sts.store-4.0.5 and included it in the
identity.provider.server.feature-4.0.5, but not added it to
4.0.5-components-patch release pom.
However, since the identity.provider.server.feature also was not included
in the 4.0.5-features-patch release pom, it has not caused an issue during
4.0.5 release.
When Suresh has copied from 4.0.5 feature into 4.0.6 and included it in the
4.0.6-features-patch release pom, this issue has occurred.

I fixed it temporarily by changing the version of org.wso2.carbon.identity.
sts.store to 4.0.3 in the feature pom.

It would be great if all the steps are considered when adding a new version
of a component to make sure that the fix is included up to the product
level.

Thanks,
Hasini.

On Thu, Jan 3, 2013 at 11:26 AM, Janaka Ranabahu  wrote:

> Hi Shariq,
>
> Yes, and as it seem the above mentioned version is not there is 4.0.5
> patch release pom. Can someone please explain why we have a 4.0.5 component
> that was not included in the release and why we have included that version
> in the 4.0.6 feature? Also, if this was intended to be a 4.0.6 component,
> please fix the version issue and the build.
>
> Thanks,
> Janaka
>
>
> On Thu, Jan 3, 2013 at 10:54 AM, Muhammed Shariq  wrote:
>
>> Hi,
>>
>> I checked in the patch release pom and org.wso2.carbon.identity.sts.store
>> is not listed in the patch-release pom, so its not deployed in the repo ..
>>
>> [1] -
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/4.0.5/components/pom.xml
>>
>> On Thu, Jan 3, 2013 at 8:36 AM, Janaka Ranabahu  wrote:
>>
>>> org.wso2.carbon.identity.sts.store
>>>
>>
>>
>>
>> --
>> Thanks,
>> Shariq.
>> Phone: +94 777 202 225
>>
>
>
>
> --
> 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] Removing IS 4.0.1 from 4.0.5 patch release (?)

[Hasini Gunasinghe]

Hi all,

Since IS 4.0.1 was not released with carbon 4.0.5, its features are updated
to 4.0.6 versions be released with carbon 4.0.6.

But IS 4.0.1 was included in 4.0.5 patch-release pom since it was used in
Stratos setup. This causes build failure when IS features are updated to
4.0.6 versions.
Therefore, for the moment, I commented out IS 4.0.1 from 4.0.5
patch-release poms and included only in 4.0.6 patch-release poms.

But I am concerned whether it will affect for the source of stratos
release.. Please let us know if there is a proper/better approach to handle
this..

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

Re: [Dev] [Blocker] carbon.core->AdminServiceUtil->getSystemRegistry() returns null

[Hasini Gunasinghe]

Hi Shariq,

Tenant ID is -1234.

Thanks,
Hasini.

On Thu, Dec 13, 2012 at 5:22 PM, Muhammed Shariq  wrote:

> On Thu, Dec 13, 2012 at 5:12 PM, Hasini Gunasinghe wrote:
>
>> Hi Shariq,
>>
>> I was testing in the stand alone mode. i.e super tenant mode.
>>
>
> You need to check what the tenantId is in CC context when ur getting null
> .. do a .getTenantId() and check whats the tennatId .. I think it should be
> -1 ...  there was a similar issue in kernel integration test that we fixed
> be starting a super tenant flow ...
>
>>
>> Thanks,
>> Hasini.
>>
>>
>> On Thu, Dec 13, 2012 at 5:08 PM, Muhammed Shariq  wrote:
>>
>>> On Thu, Dec 13, 2012 at 4:53 PM, Hasini Gunasinghe wrote:
>>>
>>>> Hi,
>>>>
>>>> The deprecated method in the $subject is called when accessing OpenID
>>>> page of IS which throws a null pointer exception.
>>>>
>>>> Any idea why the above method is returning null? This worked perfectly
>>>> with carbon 4.0.3..?
>>>>
>>>> Inside the above method, it executes the following which is the cause
>>>> for returning null:
>>>>
>>>>
>>>> CarbonContext.getCurrentContext().getRegistry(RegistryType.SYSTEM_CONFIGURATION);
>>>>
>>>
>>> Is the tenant information in the CarbonContext correct, check what the
>>> tenantId is .. ? Previously CC was simply returning the ST registry
>>> regardless of the tenant, so before you would always get the ST registry.
>>> Make sure the tenant information is correct in the CC when retrieving
>>> registry ..
>>>
>>>>
>>>> Thanks,
>>>> Hasini.
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks,
>>> Shariq.
>>> Phone: +94 777 202 225
>>>
>>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Blocker] carbon.core->AdminServiceUtil->getSystemRegistry() returns null

[Hasini Gunasinghe]

Hi Shariq,

I was testing in the stand alone mode. i.e super tenant mode.

Thanks,
Hasini.

On Thu, Dec 13, 2012 at 5:08 PM, Muhammed Shariq  wrote:

> On Thu, Dec 13, 2012 at 4:53 PM, Hasini Gunasinghe wrote:
>
>> Hi,
>>
>> The deprecated method in the $subject is called when accessing OpenID
>> page of IS which throws a null pointer exception.
>>
>> Any idea why the above method is returning null? This worked perfectly
>> with carbon 4.0.3..?
>>
>> Inside the above method, it executes the following which is the cause
>> for returning null:
>>
>>
>> CarbonContext.getCurrentContext().getRegistry(RegistryType.SYSTEM_CONFIGURATION);
>>
>
> Is the tenant information in the CarbonContext correct, check what the
> tenantId is .. ? Previously CC was simply returning the ST registry
> regardless of the tenant, so before you would always get the ST registry.
> Make sure the tenant information is correct in the CC when retrieving
> registry ..
>
>>
>> Thanks,
>> Hasini.
>>
>> ___
>> 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] [Blocker] carbon.core->AdminServiceUtil->getSystemRegistry() returns null

[Hasini Gunasinghe]

Hi,

The deprecated method in the $subject is called when accessing OpenID page
of IS which throws a null pointer exception.

Any idea why the above method is returning null? This worked perfectly with
carbon 4.0.3..?

Inside the above method, it executes the following which is the cause
for returning null:

CarbonContext.getCurrentContext().getRegistry(RegistryType.SYSTEM_CONFIGURATION);

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

Re: [Dev] Compilation failure on org.wso2.carbon.webapp.mgt

[Hasini Gunasinghe]

Hi Supun,

I too got the same compilation error. I have taken a full svn up of both
kernel and platform.
Can we please have a fix for this since this is blocking getting a  latest
pack...

Thanks,
Hasini.

On Wed, Dec 12, 2012 at 12:27 PM, Supun Malinga  wrote:

> Hi,
>
> Can you check core.util 4.0.5 jar is upto date?
>
> thanks,
>
>
> On Wed, Dec 12, 2012 at 12:19 PM, Subash Chaturanga wrote:
>
>> Hi,
>> The compilation fails seems due to this commit 150882.
>> Can we please have this fixed ASAP.
>>
>> On Wed, Dec 12, 2012 at 10:16 AM, Subash Chaturanga wrote:
>>
>>> isPartialUpdateEnabled
>>
>>
>>
>>
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Any reason for not having OAuth 4.0.5 feature

[Hasini Gunasinghe]

Hi Suresh,

As per commits, you have created the 4.0.5 version of oauth component
with r147700
to add JWT implementation in IS.
Can you please complete it by adding the corresponding feature as well to
IS?

Thanks,
Hasini.

On Tue, Dec 11, 2012 at 1:27 PM, Sumedha Rubasinghe wrote:

> Security folks,
> There is a 4.0.5 component for OAuth[1] to which some fixes have been
> committed. But there is no corresponding feature[2] that includes this
> 4.0.5 component.
> Isn't 4.0.5 being using in latest IS release?
>
> AM is relying on some of fixes done in [1] for it's 1.3.0 release.
>
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/identity/org.wso2.carbon.identity.oauth/4.0.5
>
>
> [2]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/features/identity/oauth/org.wso2.carbon.identity.oauth.server.feature
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build Error in Registry Core Feature

[Hasini Gunasinghe]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 52:22.637s
[INFO] Finished at: Mon Dec 10 11:37:03 IST 2012
[INFO] Final Memory: 703M/871M
[INFO]

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5:p2-feature-gen
(4-p2-feature-generation) on project org.wso2.carbon.registry.core.feature:
ERROR: The repository system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.registry.search.ui.feature:zip:4.0.5 is not
available in the local repository.
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.registry.search.ui.feature -Dversion=4.0.5
-Dpackaging=zip -Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the
file there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.registry.search.ui.feature -Dversion=4.0.5
-Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]
[ERROR]
[ERROR] org.wso2.carbon:org.wso2.carbon.registry.search.ui.feature:zip:4.0.5
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification on features present in the IS p2-profile {was:Lot of unnecessary Jars in Carbon Core}

[Hasini Gunasinghe]

Thanks all..

@Nirmal, then I will remove org.wso2.carbon.load.balance.agent.server.feature
from p2-profile for the moment. Hope it can be added back when the
functionality you have mentioned is supported..

Thanks,
Hasini.

On Thu, Dec 6, 2012 at 3:40 PM, Amani Soysa  wrote:

>
>
> On Thu, Dec 6, 2012 at 12:12 PM, Hasini Gunasinghe wrote:
>
>> Hi,
>>
>> I was checking the IS p2-profile to clean up if any unnecessary features
>> are present.
>> Out of the existing features, I am not very much clear whether following
>> features are must to have in IS.
>> Appreciate the feedback to get this confirmed..
>>
>> org.wso2.carbon.databridge.datapublisher.feature
>>
> We need databridge.datapublisher in IS to publish IS logs to BAM in
> logging (For BAMLogEventAppender).
>
>
>> org.wso2.carbon.xfer.feature
>> org.wso2.carbon.mex.feature
>> org.wso2.carbon.registry.profiles.feature
>>
>> Got clarified from Sanjeewa
>> that org.wso2.carbon.stratos.usage.agent.feature, 
>> org.wso2.carbon.stratos.throttling.agent.feature
>> and org.wso2.carbon.load.balance.agent.server.feature are needed.
>>
>> On a side note, I think it would be useful if we can maintain a wiki
>> page/doc containing the information about the features - such as the
>> purpose/functionality, owner etc, so that we can look at it when needed and
>> can update it when ever we add a new feature.
>>
>> Thanks,
>> Hasini.
>>
>>
>> -- Forwarded message --
>> From: Srinath Perera 
>> Date: Wed, Nov 28, 2012 at 9:45 AM
>> Subject: [Dev] Lot of unneccasry Jars in Carbon Core
>> To: architecture , dev 
>>
>>
>> We were building a minimal pack and observed this. I created a L1 for this
>> https://wso2.org/jira/browse/CARBON-14010
>>
>> For example we have solr jar, jgorups, both ehcache and inifnispan etc in
>> carbon core ..
>> Pradeep please  send the list we created
>>
>> Also there are similar problems in IS, and I am sure in others. Please
>> check the product profiles.
>>
>> --Srinath
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>   Photos: http://www.flickr.com/photos/hemapani/
>>  Phone: 0772360902
>>
>> ___
>> 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 mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername() returns null.

[Hasini Gunasinghe]

Thanks Sinthuja.. Yes, it is fixed after updating the kernel.

On Thu, Dec 6, 2012 at 2:44 PM, Sinthuja Ragendran wrote:

> Hi,
>
> Similar issue was found earlier and fixed in r150208. Please update
> core/org.wso2.carbon.tomcat.ext/4.0.5 and check.
>
> Thanks,
> Sinthuja.
>
>
> On Thu, Dec 6, 2012 at 2:32 PM, Hasini Gunasinghe  wrote:
>
>> Hi all,
>>
>> I have used
>> PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername() to
>> obtain the username of the logged in user at the back end, which correctly
>> returned the username in carbon 4.0.3 (i.e IS 4.0.0)
>>
>> But now this returns null, even though a user is logged in (encountered
>> in IS 4.0.1). Was there any changes in this space which might have caused
>> this issue?
>> Appreciate any feedback since this is a blocking issue..
>>
>> 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] [DEV] PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername() returns null.

[Hasini Gunasinghe]

Hi all,

I have used
PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername() to
obtain the username of the logged in user at the back end, which correctly
returned the username in carbon 4.0.3 (i.e IS 4.0.0)

But now this returns null, even though a user is logged in (encountered in
IS 4.0.1). Was there any changes in this space which might have caused this
issue?
Appreciate any feedback since this is a blocking issue..

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

Re: [Dev] Build failure : Identity SCIM Feature

[Hasini Gunasinghe]

Hi Ajith,

The fix you have done with r150439 is not the correct fix, since it will
cause a build failure at product level.
I have fixed this issue with r150411 today morning.
Can you please take svn up in 4.0.5 patch-release/features and revert the
above commit?

Thanks,
Hasini.

On Thu, Dec 6, 2012 at 12:53 PM, Ajith Vitharana  wrote:

> Fixed.
>
> Thanks
> Ajith
>
>
> On Thu, Dec 6, 2012 at 12:49 PM, Ajith Vitharana  wrote:
>
>>
>>
>> [INFO] Identity SCIM Feature . FAILURE
>> [1.819s]
>> [INFO] Identity XACML Server Feature . SKIPPED
>>
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 25:51.693s
>> [INFO] Finished at: Thu Dec 06 12:43:01 IST 2012
>> [INFO] Final Memory: 1270M/1849M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.identity.scim.feature: Could not resolve dependencies for
>> project org.wso2.carbon:org.wso2.carbon.identity.scim.feature:pom:4.0.5:
>> Could not find artifact
>> org.wso2.carbon:org.wso2.carbon.identity.scim.provider.feature:zip:4.0.5 in
>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
>> [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
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :org.wso2.carbon.identity.scim.feature
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Clarification on features present in the IS p2-profile {was:Lot of unnecessary Jars in Carbon Core}

[Hasini Gunasinghe]

Hi,

I was checking the IS p2-profile to clean up if any unnecessary features
are present.
Out of the existing features, I am not very much clear whether following
features are must to have in IS.
Appreciate the feedback to get this confirmed..

org.wso2.carbon.databridge.datapublisher.feature
org.wso2.carbon.xfer.feature
org.wso2.carbon.mex.feature
org.wso2.carbon.registry.profiles.feature

Got clarified from Sanjeewa
that org.wso2.carbon.stratos.usage.agent.feature,
org.wso2.carbon.stratos.throttling.agent.feature
and org.wso2.carbon.load.balance.agent.server.feature are needed.

On a side note, I think it would be useful if we can maintain a wiki
page/doc containing the information about the features - such as the
purpose/functionality, owner etc, so that we can look at it when needed and
can update it when ever we add a new feature.

Thanks,
Hasini.


-- Forwarded message --
From: Srinath Perera 
Date: Wed, Nov 28, 2012 at 9:45 AM
Subject: [Dev] Lot of unneccasry Jars in Carbon Core
To: architecture , dev 


We were building a minimal pack and observed this. I created a L1 for this
https://wso2.org/jira/browse/CARBON-14010

For example we have solr jar, jgorups, both ehcache and inifnispan etc in
carbon core ..
Pradeep please  send the list we created

Also there are similar problems in IS, and I am sure in others. Please
check the product profiles.

--Srinath



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902

___
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

Re: [Dev] IS build failed in branch (4.0.5)

[Hasini Gunasinghe]

This is fixed now.

Thanks,
Hasini.

On Tue, Dec 4, 2012 at 10:57 PM, Ajith Vitharana  wrote:

> I'm getting following error in latest branch.
>
> Installation failed.
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: Identity OAuth Feature 4.0.5
> (org.wso2.carbon.identity.oauth.feature.group 4.0.5)
>  Software being installed: Identity SCIM Feature 4.0.5
> (org.wso2.carbon.identity.scim.feature.group 4.0.5)
>  Only one of the following can be installed at once:
>   WSO2 Carbon - Webapp Management Core Feature 4.0.2
> (org.wso2.carbon.webapp.mgt.server.feature.jar 4.0.2)
>   WSO2 Carbon - Webapp Management Core Feature 4.0.5
> (org.wso2.carbon.webapp.mgt.server.feature.jar 4.0.5)
>  Cannot satisfy dependency:
>   From: Identity OAuth Feature 4.0.5
> (org.wso2.carbon.identity.oauth.feature.group 4.0.5)
>   To: org.wso2.carbon.identity.oauth.ui.feature.group [4.0.5]
>  Cannot satisfy dependency:
>   From: Identity OAuth UI Feature 4.0.5
> (org.wso2.carbon.identity.oauth.ui.feature.group 4.0.5)
>   To: org.wso2.carbon.webapp.mgt.server.feature.group [4.0.5]
>  Cannot satisfy dependency:
>   From: Identity SCIM Feature 4.0.5
> (org.wso2.carbon.identity.scim.feature.group 4.0.5)
>   To: org.wso2.carbon.identity.scim.provider.feature.group [4.0.3]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - SCIM - Service Provider Feature 4.0.3
> (org.wso2.carbon.identity.scim.provider.feature.group 4.0.3)
>   To: org.wso2.carbon.webapp.mgt.server.feature.group [4.0.2]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Webapp Management Core Feature 4.0.2
> (org.wso2.carbon.webapp.mgt.server.feature.group 4.0.2)
>   To: org.wso2.carbon.webapp.mgt.server.feature.jar [4.0.2]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Webapp Management Core Feature 4.0.5
> (org.wso2.carbon.webapp.mgt.server.feature.group 4.0.5)
>   To: org.wso2.carbon.webapp.mgt.server.feature.jar [4.0.5]
> Application failed, log file location:
> /home/ajith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1354641629107.log
>
> Thanks
> Ajith
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Announcement] WSO2 Identity Server 4.0.0 Released.

[Hasini Gunasinghe]

Hi all,The WSO2 Identity Server team is pleased to announce the release of
version 4.0.0 of the WSO2 Identity Server (IS).

WSO2 Identity Server is an open source Identity and Entitlement management
server having support for XACML, SAML, OAuth, OpenID and SCIM.

WSO2 Identity Server is developed on top of the revolutionary WSO2 Carbon
platform , an OSGi based framework that
provides seamless modularity to your SOA via componentization.

All the major features have been developed as pluggable Carbon components.

You can download this distribution from
http://wso2.com/products/identity-server/.

The online documentation is available at
http://docs.wso2.org/wiki/display/IS400/WSO2+Identity+Server+Documentation.
How to Run

   1. Extract the downloaded zip
   2. Go to the bin directory in the extracted folder
   3. Run the wso2server.sh or wso2server.bat as appropriate
   4. If you need to start the OSGi console with the server use the
   property -DosgiConsole when starting the server. The INSTALL.txt file found
   on the installation directory will give you a comprehensive set of options
   and properties that can be passed into the startup script

New Features In This Release

   - XACML 3.0
   - OAUTH 2.0
   - SCIM 1.1
   - IWA Authenticator
   - Support for Multiple User Stores
   - WS-XACML
   - SAML2 Basic Attribute Profile
   - Read/Write Active Directory User Store Manager
   - Database based token store for STS
   - Various bug fixes and enhancements including architectural
   improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2
   Carbon and other projects.

Key Features of WSO2 Identity Server

   - Entitlement Engine with XACML 2.0/3.0 and WS-XACML support
   - SAML based Single-Sign-On support
   - OAuth 1.0a/2.0 based Access Delegation support
   - Claim based Security Token Service with SAML 1.1/SAML 2.0
   - OpenID Provider and Relying Party
   - Identity Provisioning with SCIM 1.1
   - Extension points for SAML assertion handling
   - IWA Authenticator
   - Extension points for Authenticators
   - XMPP based multi-factor authentication
   - Improved User Management.
   - Claim Management
   - User Profiles Management
   - XKMS
   - Separable front-end and back-end - a single front-end server can be
   used to administer several back-end servers.

Issues Fixed in This Release

This release of WSO2 Identity Server comes with a number of bug fixes, both
in the base Carbon framework and in the Identity Server specific
components. All the issues which have been fixed in this release can be
found at:

   - Fixed Issues for Identity Server
4.0.0

Known Issues

All the known issues in WSO2 Identity Server 4.0.0 are reported at:

   - Known issues in WSO2 Identity Server
4.0.0

How You Can Contribute Mailing Lists

Join our mailing list and correspond with the developers directly.

   - Developer list : dev@wso2.org |
Subscribe
| Mail Archive 
   - User forum : StackOverflow

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 Identity Server or in the Carbon base framework
through the public WSO2 Identity Server
JIRA
 or Carbon JIRA .
Support

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology. For more
details and to take advantage of this unique opportunity
http://wso2.com/support/

For more information about WSO2 Identity Server, please see
http://wso2.com/products/identity-server or visit the WSO2 Oxygen
Tank developer
portal for addition resources.

Thank you for your interest in WSO2 Identity Server.

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

Re: [Dev] DefaultRelamService#initalizeRelam() is called several times when creating a tenant - IDENTITY-536

[Hasini Gunasinghe]

It seems to be not fixed in the latest packs although the fix for
https://wso2.org/jira/browse/IDENTITY-491 was reverted in
https://wso2.org/jira/browse/IDENTITY-536 with r147001.

Can you please check whether the r147001 is the correct revert?

Thanks,
Hasini.

On Thu, Nov 1, 2012 at 8:51 AM, Dimuthu Leelarathne wrote:

>
>
> On Wed, Oct 31, 2012 at 7:05 PM, Rajika Kumarasiri wrote:
>
>> This is in the latest IS pack at
>> http://builder3.us1.wso2.org/builds/31-oct-2012/.
>>
>> When creating a tenant following logs can be seen repeatedly. See
>> https://wso2.org/jira/browse/IDENTITY-536.
>>
>> [2012-10-31 18:46:12,086]  INFO
>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
>> connection created successfully in read-write mode.
>>
>> When requesting the tenant user relam
>> (DefaultRelamService#getTenantUserRelam()) while creating the tenant it
>> seems that DefaultRelamService#initalizeRelam() is called several time
>> which ends up initialization ReadWriteLDAPUserStoreManager each time(hence
>> the repeating logs). I have attached a screen shot of the stack traces as
>> well.
>>
>> This issue was not there in the IS alpha pack. Cloud you look into this ?
>>
>
> Should be fixed now.
>
> thanks,
> dimuthu
>
>>
>> Rajika
>>
>
>
> ___
> 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] Intermittent error when using cache - Cache: The Disk store is not active

[Hasini Gunasinghe]

Hi,

I get this error intermittently when adding to cache...

Can I please know what might be the cause for this?

[2012-10-31 18:04:32,933] ERROR {net.sf.ehcache.store.DiskStore} -
 SCIM_CACHECache: Could not read disk store element for key
admin@carbon.super. Initial cause was SCIM_CACHE Cache: The Disk store is
not active.
net.sf.ehcache.CacheException: SCIM_CACHE Cache: The Disk store is not
active.
at net.sf.ehcache.store.DiskStore.checkActive(DiskStore.java:232)
at net.sf.ehcache.store.DiskStore.getQuiet(DiskStore.java:322)
at net.sf.ehcache.Cache.searchInDiskStore(Cache.java:1204)
at net.sf.ehcache.Cache.getQuiet(Cache.java:1057)
at net.sf.ehcache.jcache.JCache.put(JCache.java:595)
at net.sf.ehcache.jcache.JCache.put(JCache.java:570)
at
org.wso2.carbon.identity.scim.common.config.SCIMProvisioningConfigManager.addEnabledToCache(SCIMProvisioningConfigManager.java:131)

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

[Dev] Identity Server 4.0.0-Alpha-4 Release

[Hasini Gunasinghe]

Hi All,

WSO2 Identity Server 4.0.0-Alpha-4 release is now available at [1]. We
welcome your feedback and please report issues at our public JIRA [2].

New Features in Identity Server 4.0.0:

   - XACML 3.0
   - OAuth 2.0
   - SCIM 1.1
   - IWA Authenticator
   - Support for Multiple User Stores
   - WS-XACML
   - Read/Write Active Directory User Store Manager
   - SAML2 Basic Attribute Profile

[1]. *https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/alpha-4*
[2]. https://wso2.org/jira/browse/IDENTITY
[3].
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10841

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.0.x > Products_4.0.3 > #7 has FAILED. Change made by 6 authors.

[Hasini Gunasinghe]

Thanks.. and applied the patch with r146742.

Thanks,
Hasini.

On Sun, Oct 28, 2012 at 7:12 PM, Amila Maha Arachchi wrote:

> I have fixed the build error. But cannot commit (no commit rights). I have
> attached the patch here.
>
> On Sun, Oct 28, 2012 at 5:20 AM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 Carbon 
>> 4.0.x›
>> Products_4.0.3  › 
>> #7
>> failed
>>
>> This build occurred because it is a dependant of 
>> WCB001-PLA001-22
>> .
>>
>> 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)  83 minutes  No tests found  
>> Logs|
>> Artifacts  
>> Code
>> Changes   View
>> all 24 code changes
>> asela 
>> adding to patch release pom  146724
>> ajithn
>> update feature with new bundle  146723
>> ajithn
>> add new 4.0.3 bundle  146721   21 more 
>> changes… 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
>>
>>
>
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
>
> ___
> 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] [Blocker] Can not log into newly created tenants due to fully qualified user name is sent to authenticate method

[Hasini Gunasinghe]

Hi

This is regarding https://wso2.org/jira/browse/IDENTITY-479.

When debugged, this is due to fully qualified user name is sent to
authenticate method of UserStoreManager.

Did any recent changes happen in this space?

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

Re: [Dev] C 4.0.3 BB - Identity tests are failing

[Hasini Gunasinghe]

Hi,

This is because, local transport is added for the oauth admin services'
service.xml.
Comparing the sources, this has been added in 4.0.3 version.

Johann, do you have any idea why "local" was added under transports for
these admin services?
Can you please look into fixing this test failure?

Thanks,
Hasini.

On Fri, Oct 26, 2012 at 10:38 AM, Samisa Abeysinghe  wrote:

> [2012-10-25 21:51:34,515] ERROR
> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -  Problem
> reading the [inputStream] due to: Stream closed
> java.io.IOException: Stream closed
> at
> java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:255)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
> at java.io.InputStreamReader.read(InputStreamReader.java:167)
> at java.io.BufferedReader.fill(BufferedReader.java:136)
> at java.io.BufferedReader.readLine(BufferedReader.java:299)
> at java.io.BufferedReader.readLine(BufferedReader.java:362)
> at
> org.wso2.carbon.integration.framework.utils.InputStreamHandler.run(InputStreamHandler.java:60)
> at java.lang.Thread.run(Thread.java:662)
> [2012-10-25 21:51:35,822]  INFO
> {org.wso2.carbon.integration.framework.utils.CodeCoverageUtils} -
>  Generated Emma reports
> Tests run: 18, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 97.188
> sec <<< FAILURE!
>
> Results :
>
> Failed tests:
>
> verifyAdminServiceSecurity(org.wso2.identity.integration.tests.SecurityVerificationTestCase):
> The following admin services are vulnerable:
> 1. OAuthAdminService [https,local,]
> 2. OAuth2TokenValidationService [https,local,]
> These are exposed not only on HTTPS.
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> ___
> 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

Re: [Dev] identity-integration-tests are failing on 4.0.3

[Hasini Gunasinghe]

This is due to an outdated feature version in p2-profile-gen.

This is fixed at IS-p2-profile-gen pom file.

Thanks,
Hasini.

On Wed, Oct 24, 2012 at 12:06 PM, Samisa Abeysinghe  wrote:

> [2012-10-23 23:28:54,187] ERROR
> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -  Problem
> reading the [inputStream] due to: Stream closed
> java.io.IOException: Stream closed
> at
> java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:255)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
> at java.io.InputStreamReader.read(InputStreamReader.java:167)
> at java.io.BufferedReader.fill(BufferedReader.java:136)
> at java.io.BufferedReader.readLine(BufferedReader.java:299)
> at java.io.BufferedReader.readLine(BufferedReader.java:362)
> at
> org.wso2.carbon.integration.framework.utils.InputStreamHandler.run(InputStreamHandler.java:60)
> at java.lang.Thread.run(Thread.java:662)
> [2012-10-23 23:28:55,438]  INFO
> {org.wso2.carbon.integration.framework.utils.CodeCoverageUtils} -
>  Generated Emma reports
> Tests run: 18, Failures: 2, Errors: 0, Skipped: 12, Time elapsed: 96.366
> sec <<< FAILURE!
>
> Results :
>
> Failed tests:
>   addUser(org.wso2.identity.integration.tests.UserAdminTestCase):
> org.wso2.carbon.identity.scim.common.listener.SCIMUserOperationListener.doPostAddUser(Ljava/lang/String;Ljava/lang/Object;[Ljava/lang/String;Ljava/util/Map;Ljava/lang/String;Lorg/wso2/carbon/user/core/UserStoreManager;)Z
>
> verifyAdminServiceSecurity(org.wso2.identity.integration.tests.SecurityVerificationTestCase):
> The following admin services are vulnerable:
> 1. OAuthAdminService [https,local,]
> 2. OAuth2TokenValidationService [https,local,]
> These are exposed not only on HTTPS.
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> ___
> 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] Identity Server 4.0.0-Alpha Release

[Hasini Gunasinghe]

Hi all,

WSO2 Identity Server 4.0.0 Alpha-1 Release is now available at [1].  We
welcome your feedback and please report issues at our public JIRA [2].

New Features in Identity Server 4.0.0:

1. XACML 3.0
2. OAuth 2.0
3. SCIM 1.1
4. IWA-Authenticator
5. Support for Multiple User Stores
6. WS-XACML
7. Read/Write Active Directory User Store Manager
8. SAML2 SSO Attribute Profile

In addition, improvements are done in following features:
1. XACML Policy Editor
2. User Management

Issues fixed for the alpha release can be found at [3]

[1] https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/alpha
[2] https://wso2.org/jira/browse/IDENTITY
[3]
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10833

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

Re: [Dev] Build Error in org.wso2.carbon.governance.metadata.server.feature

[Hasini Gunasinghe]

Now I get the following error when building:
Were you able to build org.wso2.carbon.governance.api/4.0.3?

[ERROR] Failed to execute goal on project org.wso2.carbon.governance.api:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.governance.api:bundle:4.0.3: The repository
system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.3 is not available in
the local repository. -> [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,
Hasini.

On Tue, Oct 23, 2012 at 4:18 PM, Subash Chaturanga  wrote:

> This is fixed in 146225.
> Please take an svn up in org.wso2.carbon.governance.api/4.0.3.
>
>
> On Tue, Oct 23, 2012 at 4:15 PM, Hasini Gunasinghe wrote:
>
>> I get the following build error.
>>
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.governance.metadata.server.feature: Could not resolve
>> dependencies for project
>> org.wso2.carbon:org.wso2.carbon.governance.metadata.server.feature:pom:4.0.3:
>> The repository system is offline but the artifact
>> org.wso2.carbon:org.wso2.carbon.governance.api:jar:4.0.3 is not available
>> in the local repository. -> [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
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf
>> :org.wso2.carbon.governance.metadata.server.feature
>>
>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build Error in org.wso2.carbon.governance.metadata.server.feature

[Hasini Gunasinghe]

I get the following build error.

[ERROR] Failed to execute goal on project
org.wso2.carbon.governance.metadata.server.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.governance.metadata.server.feature:pom:4.0.3:
The repository system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.governance.api:jar:4.0.3 is not available
in the local repository. -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf
:org.wso2.carbon.governance.metadata.server.feature
___
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.2 > #481 was SUCCESSFUL (with 1956 tests). Change made by 4 authors.

[Hasini Gunasinghe]

On Tue, Oct 23, 2012 at 9:18 AM, Amila Maha Arachchi wrote:

> Given that we have 4.0.3 patch-release poms available, Bamboo should be
> configured to build the 4.0.3.
>

+1.

Thanks,
Hasini.

>
> On Tue, Oct 23, 2012 at 4:19 AM, Bamboo  wrote:
>
>>  [image: Successful]  WSO2 Carbon 
>> 4.0.x›
>> Platform_4.0.2  › 
>> #481 was
>> successful
>>
>> This build occurred because it is a dependant of 
>> WCB001-KER000-294
>> .
>>
>> *1956* tests in total.
>>Code Changes   
>> View
>> all 44 code changes
>> hasini 
>> updating versions  146140
>> johann
>> Changing versions in POM  146139
>> johann
>> Creating 4.0.3 patch-release version again
>>  146138   41 more 
>> changes… 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
>>
>>
>
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
>
> ___
> 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

Re: [Dev] Manager & IS build failures at p2-profile-gen

[Hasini Gunasinghe]

Hi,

AFAIK, we didn't do changes wrt these mentioned files. However they are
checked out from svn externals. I will also build locally and check.

Thanks,
Hasini.

On Sat, Oct 13, 2012 at 8:55 PM, Amila Maha Arachchi wrote:

> Seems like IS guys have done some changes. I'll have a look.
>
> On Sat, Oct 13, 2012 at 8:34 PM, Dinusha Senanayaka wrote:
>
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5:p2-profile-gen
>> (3-p2-profile-generation) on project wso2stratos-manager-profile-gen: P2
>> publisher return code was 13 -> [Help 1]
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (4-dist)
>> on project wso2stratos-manager: Failed to create assembly: Error adding
>> file to archive:
>> /var/home/lakmali/branch/platform/4.0.0/products/manager/2.0.0/modules/distribution/../p2-profile-gen/target/wso2carbon-core-4.0.2/repository/resources/security/userRP.jks
>> isn't a file. -> [Help 1]
>>
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5:p2-profile-gen
>> (3-p2-profile-generation) on project identity-profile-gen: P2 publisher
>> return code was 13 -> [Help 1]
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
>> on project wso2is: Failed to create assembly: Error adding file to archive:
>> /var/home/lakmali/branch/platform/4.0.0/products/is/4.0.0/modules/distribution/../p2-profile-gen/target/wso2carbon-core-4.0.2/repository/conf/claim-config.xml
>> isn't a file. -> [Help 1]
>>
>> Regards,
>> Dinusha.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
>
> ___
> 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

Re: [Dev] [Commits] [Carbon-platform] svn commit r145354 - in carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0: oauth2-authzserver/src/main/java/org/apache/amber/oauth2/

[Hasini Gunasinghe]

Hi Chintana,

I think amber jar was released with 4.0.0 release (with APIM). If so, we
can not commit new changes to the same version...

Thanks,
Hasini.

On Fri, Oct 12, 2012 at 1:03 PM,  wrote:

> Author: chintana
> Date: Fri Oct 12 13:03:55 2012
> New Revision: 145354
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=145354
>
> Log:
> Necessary changes to support SAML 2.0 Bearer Assertion Profile for OAuth
> 2.0
>
> Added:
>
>  
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/validator/SAML20BearerAssertionValidator.java
> Modified:
>
>  
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/request/OAuthTokenRequest.java
>
>  
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-common/src/main/java/org/apache/amber/oauth2/common/message/types/GrantType.java
>
> Modified:
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/request/OAuthTokenRequest.java
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/request/OAuthTokenRequest.java?rev=145354&r1=145353&r2=145354&view=diff
>
> ==
> ---
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/request/OAuthTokenRequest.java
>  (original)
> +++
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/request/OAuthTokenRequest.java
>  Fri Oct 12 13:03:55 2012
> @@ -27,6 +27,7 @@
>  import org.apache.amber.oauth2.as.validator.ClientCredentialValidator;
>  import org.apache.amber.oauth2.as.validator.PasswordValidator;
>  import org.apache.amber.oauth2.as.validator.RefreshTokenValidator;
> +import
> org.apache.amber.oauth2.as.validator.SAML20BearerAssertionValidator;
>  import org.apache.amber.oauth2.common.OAuth;
>  import org.apache.amber.oauth2.common.exception.OAuthProblemException;
>  import org.apache.amber.oauth2.common.exception.OAuthSystemException;
> @@ -53,6 +54,7 @@
>  validators.put(GrantType.CLIENT_CREDENTIALS.toString(),
> ClientCredentialValidator.class);
>  validators.put(GrantType.AUTHORIZATION_CODE.toString(),
> AuthorizationCodeValidator.class);
>  validators.put(GrantType.REFRESH_TOKEN.toString(),
> RefreshTokenValidator.class);
> +validators.put(GrantType.SAML20_BEARER_ASSERTION.toString(),
> SAML20BearerAssertionValidator.class);
>  String requestTypeValue = getParam(OAuth.OAUTH_GRANT_TYPE);
>  if (OAuthUtils.isEmpty(requestTypeValue)) {
>  throw OAuthUtils.handleOAuthProblemException("Missing
> grant_type parameter value");
> @@ -84,4 +86,8 @@
>  return getParam(OAuth.OAUTH_GRANT_TYPE);
>  }
>
> +public String getAssertion() {
> +return getParam(OAuth.OAUTH_ASSERTION);
> +}
> +
>  }
>
> Added:
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/validator/SAML20BearerAssertionValidator.java
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/validator/SAML20BearerAssertionValidator.java?pathrev=145354
>
> ==
> --- (empty file)
> +++
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-authzserver/src/main/java/org/apache/amber/oauth2/as/validator/SAML20BearerAssertionValidator.java
>   Fri Oct 12 13:03:55 2012
> @@ -0,0 +1,12 @@
> +package org.apache.amber.oauth2.as.validator;
> +
> +import org.apache.amber.oauth2.common.OAuth;
> +import org.apache.amber.oauth2.common.validators.AbstractValidator;
> +
> +import javax.servlet.http.HttpServletRequest;
> +
> +public class SAML20BearerAssertionValidator extends
> AbstractValidator {
> +public SAML20BearerAssertionValidator() {
> +requiredParams.add(OAuth.OAUTH_ASSERTION);
> +}
> +}
>
> Modified:
> carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-common/src/main/java/org/apache/amber/oauth2/common/message/types/GrantType.java
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/amber/0.22.1358727-wso2v1/oauth-2.0/oauth2-common/src/main/java/org/apache/amber/oauth2/common/message/types/GrantType.java?rev=145354&r1=145353&r2=145354&view=diff
>
> ===

Re: [Dev] [Blocker] Rampart handlers consuming 8% time during an invocation even if security is not engaged

[Hasini Gunasinghe]

Hi,

FYI. I have removed the changes done at Rampart level due to following
reasons:

1. It has introduced a regression issue in secure communication in ESB with
non-secured proxy --> secured service scenario as discussed in another
thread. (Issue could be overcome using send mediator in released packs, but
if send mediator is not present, the issue appears)
2. Changes at Rampart level introduced only a slight performance
improvement. (the majority of the improvement was achieved from axis2 level
change which Azeez did)

Will add the new rampart version to 4.0.2 patch release.

Thanks,
Hasini.

On Tue, Sep 4, 2012 at 11:47 PM, Hasini Gunasinghe  wrote:

> Attaching the modifications at Rampart handlers level which caused slight
> improvement.
> Please review and commit.
>
> We can also consider removing rampart module (i.e security phase) from
> global phase in a future release so that rampart handlers will not be
> invoked for each service call.
>
> Thanks,
> Hasini.
>
>
> On Tue, Sep 4, 2012 at 4:55 PM, Afkham Azeez  wrote:
>
>> Just by making the following change we were able to see a performance
>> improvement of close to 20% !!!
>>
>> Index: src/org/apache/axis2/description/AxisModule.java
>> ===
>> --- src/org/apache/axis2/description/AxisModule.java (revision 141042)
>> +++ src/org/apache/axis2/description/AxisModule.java (working copy)
>> @@ -129,8 +129,17 @@
>>   *
>>   * @return the archive name of the module
>>   */
>> +private String archiveName;
>> +
>>  public String getArchiveName() {
>> -return version == null ? name : (name + "-" + version);
>> +if (archiveName == null){
>> +if(version == null){
>> +archiveName = name;
>> +} else {
>> +archiveName = name + "-" + version;
>> +}
>> +}
>> +return archiveName;
>>  }
>>
>> On Tue, Sep 4, 2012 at 2:27 PM, Afkham Azeez  wrote:
>>
>>> This is a simple echo service which has not been secured. In the in
>>> flow, the overhead caused by the rampart handlers is 8% & in the out flow
>>> the overhead is 12%. So, we can improve performance by 20% just by
>>> optimizing this bit of code.
>>>
>>> Azeez
>>>
>>>
>>> On Tue, Sep 4, 2012 at 2:23 PM, Prabath Siriwardena wrote:
>>>
>>>> What is the security policy you used here..?
>>>>
>>>> Thanks & regards,
>>>> -Prabath
>>>>
>>>>
>>>> On Tue, Sep 4, 2012 at 2:20 PM, Afkham Azeez  wrote:
>>>>
>>>>> Rampart handlers are causing much higher overhead in the outflow. See
>>>>> attached screenshot.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Sep 4, 2012 at 2:16 PM, Hasini Gunasinghe wrote:
>>>>>
>>>>>> Will look into this.
>>>>>>
>>>>>> Thanks,
>>>>>> Hasini.
>>>>>>
>>>>>> On Tue, Sep 4, 2012 at 2:06 PM, Afkham Azeez  wrote:
>>>>>>
>>>>>>> See attached jprofiler screenshot.
>>>>>>>
>>>>>>> The main culprit seems to be the isEngaged method call which is
>>>>>>> repeatedly building the module name. The fix should be simple, we could
>>>>>>> remember the module name. Prabath et. al. please take this up urgently.
>>>>>>>
>>>>>>> --
>>>>>>> *Afkham Azeez*
>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>> * <http://www.apache.org/>**
>>>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>>>> twitter: 
>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>>> *
>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>>> *
>>>>>>> *
>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.or

[Dev] WSO2 Identity Server 4.0.0 Milestone 9

[Hasini Gunasinghe]

Hi,

Please find the Identity Server Milestone 9 build at [1].

M9 build includes:

- WS-XACML as a new feature,

- Improvements to the following features:
  XACML Editor
  SCIM Service Provider and Provisioning Operations
  SAML SSO

- and fixes for the bugs found in testing.

Please report any issues found in this milestone pack at [2].

[1] https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/m9
[2] https://wso2.org/jira/browse/IDENTITY

Thanks,
Hasini.


-- Forwarded message --
From: Suresh Attanayaka 
Date: Wed, Sep 26, 2012 at 12:57 AM
Subject: [Architecture] [User] WSO2 Identity Server 4.0.0 Milestone 8
Released !
To: dev@wso2.org
Cc: architect...@wso2.org, u...@wso2.org


Hi All,

WSO2 Identity Server 4.0.0 Milestone 8 Release is now available at [1].  We
welcome your feedback and please report issues at our public JIRA [2].

[1].
https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/m8/wso2is-4.0.0-M8.zip
[2]. https://wso2.org/jira/browse/IDENTITY

Fixed Issues :

   - https://wso2.org/jira/browse/IDENTITY-310
   - https://wso2.org/jira/browse/IDENTITY-311
   - https://wso2.org/jira/browse/IDENTITY-337
   - https://wso2.org/jira/browse/IDENTITY-338
   - https://wso2.org/jira/browse/IDENTITY-341
   - https://wso2.org/jira/browse/IDENTITY-346
   - https://wso2.org/jira/browse/IDENTITY-366
   - https://wso2.org/jira/browse/IDENTITY-369
   - https://wso2.org/jira/browse/IDENTITY-374
   - https://wso2.org/jira/browse/IDENTITY-377
   - https://wso2.org/jira/browse/IDENTITY-281
   - https://wso2.org/jira/browse/IDENTITY-386
   - https://wso2.org/jira/browse/IDENTITY-387
   - https://wso2.org/jira/browse/IDENTITY-388
   - https://wso2.org/jira/browse/IDENTITY-390
   - https://wso2.org/jira/browse/IDENTITY-392
   - https://wso2.org/jira/browse/IDENTITY-393
   - https://wso2.org/jira/browse/IDENTITY-394
   - https://wso2.org/jira/browse/IDENTITY-395
   - https://wso2.org/jira/browse/IDENTITY-398
   - https://wso2.org/jira/browse/IDENTITY-399
   - https://wso2.org/jira/browse/IDENTITY-401
   - https://wso2.org/jira/browse/IDENTITY-404


Known Issues :

   - https://wso2.org/jira/browse/IDENTITY-398 and in our public JIRA
   https://wso2.org/jira/secure/IssueNavigator.jspa


Thanks,
-Suresh

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


___
Architecture mailing list
architect...@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Intermittent NPE from AuthorizationCache

[Hasini Gunasinghe]

Hi,

I get NPE from AuthorizationCache intermittently.
I could not dig deep into that, but this doesn't happen in the packs built
on 26th Sept. Only getting it in the pack built today.

Caused by: java.lang.NullPointerException
at
org.wso2.carbon.user.core.authorization.AuthorizationCache.isUserAuthorized(AuthorizationCache.java:134)
at
org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.isUserAuthorized(JDBCAuthorizationManager.java:130)
at
org.wso2.carbon.identity.scim.provider.impl.IdentitySCIMManager.getUserManager(IdentitySCIMManager.java:183)


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

Re: [Dev] org.wso2.carbon.hdfs.mgt.feature build failure

[Hasini Gunasinghe]

Hi,

Can you please let me know where should I take svn up to avoid this?
(FYI.. I took svn up in platform,kernel and orbit yesterday and I get the
same error as below)

[ERROR] Failed to execute goal on project org.wso2.carbon.hdfs.mgt.feature:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.hdfs.mgt.feature:pom:4.0.2: The repository
system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.hdfs.dataaccess:jar:4.0.0 is not available
in the local repository. -> [Help 1]

Thanks,
Hasini.

On Tue, Oct 2, 2012 at 10:43 AM, Deependra Ariyadewa  wrote:

>
>
> On Tue, Oct 2, 2012 at 10:37 AM, Lakmali Baminiwatta wrote:
>
>> Following error is thrown when building org.wso2.carbon.hdfs.mgt.feature
>> in a clean-repo.
>>
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.hdfs.mgt.feature: Could not resolve dependencies for
>> project org.wso2.carbon:org.wso2.carbon.hdfs.mgt.feature:pom:4.0.2: Could
>> not find artifact org.wso2.carbon:org.wso2.carbon.hdfs.dataaccess:jar:4.0.0
>> in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>> -> [Help 3]
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.1:p2-repo-gen (2-p2-repo-generation) on
>> project wso2carbon-feature-repository: Error occured when processing the
>> Feature Artifact:
>> org.wso2.carbon:org.wso2.carbon.service.mgt.feature:4.0.2: ERROR: Could not
>> find artifact org.wso2.carbon:org.wso2.carbon.service.mgt.feature:zip:4.0.2
>> in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
>> [ERROR]
>> [ERROR] Try downloading the file manually from the project website.
>> [ERROR]
>> [ERROR] Then, install it using the command:
>> [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
>> -DartifactId=org.wso2.carbon.service.mgt.feature -Dversion=4.0.2
>> -Dpackaging=zip -Dfile=/path/to/file
>> [ERROR]
>> [ERROR] Alternatively, if you host your own repository you can deploy the
>> file there:
>> [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
>> -DartifactId=org.wso2.carbon.service.mgt.feature -Dversion=4.0.2
>> -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>> [ERROR]
>> [ERROR]
>> [ERROR] org.wso2.carbon:org.wso2.carbon.service.mgt.feature:zip:4.0.2
>>
>> Please have a look.
>>
>
> I will fix this soon.
>
> Thanks,
>
> Deependra.
>
>>
>> Thanks,
>> Lakmali
>>
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>
> ___
> 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

Re: [Dev] Build failure - Charon - Utils

[Hasini Gunasinghe]

This is fixed.

Thanks,
Hasini.

On Thu, Oct 4, 2012 at 9:30 AM, Ajith Vitharana  wrote:

> Hi all,
>
> I'm getting following build failure in clean repo.
>
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 43:23.855s
> [INFO] Finished at: Wed Oct 03 22:46:22 IST 2012
> [INFO] Final Memory: 552M/1497M
> [INFO]
> 
> [ERROR] Failed to execute goal on project org.wso2.charon.utils: Could not
> resolve dependencies for project
> org.wso2.charon:org.wso2.charon.utils:jar:1.0.0-wso2v3: Could not find
> artifact org.wso2.charon:org.wso2.charon.core:jar:1.0.0-wso2v2 in central (
> http://repo1.maven.org/maven2) -> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.charon.utils
>
>
> Thanks
> ajith
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] NPE when obtaining an OSGiService from PrivilegedCarbonContext

[Hasini Gunasinghe]

Thanks for the update..
I tried replacing the updated carbon.utils jar. But I still get the same
error. Let me know if I can help with debugging to fix this.

Thanks,
Hasini.

On Wed, Sep 19, 2012 at 11:31 AM, Pradeep Fernando  wrote:

> get an svn up in carbon.utils. may fix your issue.
>
>
> --Pradeep
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build Error in 4.0.2 - org.wso2.carbon.dashboard.mgt.oauth.feature

[Hasini Gunasinghe]

Hi,

I am also getting this build error.

Thanks,
Hasini.

On Tue, Sep 18, 2012 at 7:18 PM, Suhothayan Sriskandarajah wrote:

>
> [INFO] Registry TestNG Test Module ... SKIPPED
> [INFO] Registry TestNG Test Module ... SKIPPED
> [INFO] WSO2 Carbon - Patch releases - products - Aggregator Module  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1:28.929s
> [INFO] Finished at: Tue Sep 18 19:09:43 IST 2012
> [INFO] Final Memory: 148M/476M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5:p2-feature-gen (p2-feature-generation)
> on project org.wso2.carbon.dashboard.mgt.oauth.feature: ERROR: Could not
> find artifact
> org.wso2.carbon:org.wso2.carbon.dashboard.mgt.oauth.server.feature:zip:4.0.2
> in carbon-archetype-repo1 (
> http://sr5.us1.wso2.com/nexus/content/repositories/wso2archtype/)
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.dashboard.mgt.oauth.server.feature
> -Dversion=4.0.2 -Dpackaging=zip -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.dashboard.mgt.oauth.server.feature
> -Dversion=4.0.2 -Dpackaging=zip -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> [ERROR]
> [ERROR]
> [ERROR]
> org.wso2.carbon:org.wso2.carbon.dashboard.mgt.oauth.server.feature:zip:4.0.2
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] carbon-archetype-repo1 (
> http://sr5.us1.wso2.com/nexus/content/repositories/wso2archtype/,
> releases=true, snapshots=true),
> [ERROR] carbon-archetype-repo2 (
> http://maven.wso2.org/nexus/content/repositories/wso2archtype/,
> releases=true, snapshots=true),
> [ERROR] wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true,
> snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [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/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.dashboard.mgt.oauth.feature
>
>
>
> --
> *S. Suhothayan
> *
> Software Engineer,
> Data Technologies Team,
>  *WSO2, Inc. **http://wso2.com
>  *
> *lean.enterprise.middleware.*
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* 
> *
> twitter: **http://twitter.com/suhothayan* *
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
>
> ___
> 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] NPE when obtaining an OSGiService from PrivilegedCarbonContext

[Hasini Gunasinghe]

Hi,

Error at [1] is thrown when executing following:
PrivilegedCarbonContext.getCurrentContext().
getOSGiService(RealmService.class);

Earlier it was done as follows and worked fine:
SuperTenantCarbonContext.getCurrentContext().
getOSGiService(RealmService.class);

[1]
Caused by: java.lang.NullPointerException
at org.osgi.util.tracker.ServiceTracker.(ServiceTracker.java:197)
at org.osgi.util.tracker.ServiceTracker.(ServiceTracker.java:268)
at
org.wso2.carbon.context.PrivilegedCarbonContext.getOSGiService(PrivilegedCarbonContext.java:420)

Have we missed anything?

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

Re: [Dev] Error when logging in to DSS server

[Hasini Gunasinghe]

Thanks. It is fixed now.

On Tue, Sep 18, 2012 at 6:50 PM, Pradeep Fernando  wrote:

> committed the changes,
>
> Update the product profile with
> org.wso2.carbon.stratos.common.feature:2.0.2 and see.
>
> --Pradeep
> ___
> 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

Re: [Dev] Error when logging in to DSS server

[Hasini Gunasinghe]

I am also getting this error when logging into latest IS.

Thanks,
Hasini.

On Tue, Sep 18, 2012 at 5:44 PM, Lakmali Baminiwatta wrote:

> Hi all,
>
> I am getting following error while trying to log in to DSS. Is
> org.wso2.carbon.activation/2.0.0 component retired ? It is still coming
> from org.wso2.carbon.stratos.common.server.feature.
>
> java.lang.NoClassDefFoundError: 
> org/wso2/carbon/core/multitenancy/SuperTenantCarbonContext
>   
> org.wso2.carbon.activation.module.ActivationHandler.getTenantId(ActivationHandler.java:125)
>   
> org.wso2.carbon.activation.module.ActivationHandler.invoke(ActivationHandler.java:57)
>   org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>   org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>   org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
>   org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
>   
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
>   
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
>   
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>   
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
>   org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
>   
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
>   
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>   
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>   
> org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
>   
> org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
>   
> org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
>   
> org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:187)
>   
> org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:77)
>   
> org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:330)
>   
> org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:224)
>   
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:86)
>   
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
>   
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>   
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
>   
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>
>
>
> *Thanks,
> Lakmali
> *
>
>
> ___
> 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

Re: [Dev] CarbonContext refactoring across the platform

[Hasini Gunasinghe]

Hi Azeez,

On Fri, Sep 14, 2012 at 5:31 PM, Afkham Azeez  wrote:

>
>
> On Fri, Sep 14, 2012 at 5:26 PM, Hasini Gunasinghe wrote:
>
>> I too think this will negatively affect the products in the queue to be
>> released which are being stabilized at the moment.
>
>
> How do you suppose a find and replace such as for example
> s/CarbonContextHolder.startTenantFlow()/PrivilegedCarbonContext.startTenantFlow()
> destabilize components? 4.0.2 components will be created for most of these
> components anyway.
>

What I was concerned about was that we would find additional issues in the
features that we are stabilizing at the moment, as we found run time issues
after super tenant id/domain re-factoring (for which we had sufficient time
to discover and fix).

Thanks,
Hasini.


>
>>
>> Can we do this after the planned chunk 2/chunk 3 products are released?
>>
>> Thanks,
>> Hasini.
>>
>> On Fri, Sep 14, 2012 at 5:03 PM, Nuwan Bandara  wrote:
>>
>>> Hi Pradeep,
>>>
>>> What did you mean by backward compatible, if we are to re-factor all
>>> these components ? Also the P2 story is a valid question.
>>>
>>> This is whole lot of components IMO. We should have done it bit earlier,
>>> else lets move to C5.
>>>
>>> Regards,
>>> /Nuwan
>>>
>>> On Fri, Sep 14, 2012 at 4:54 PM, Tharindu Mathew wrote:
>>>
>>>> All chunks will have to be re-released after this change to ensure
>>>> features can be installed on top.
>>>>
>>>> I thought this change was backwards compatible? Anyway, we shouldn't go
>>>> ahead with this.
>>>>
>>>>
>>>> On Fri, Sep 14, 2012 at 4:48 PM, Miyuru Wanninayaka wrote:
>>>>
>>>>> Doesn't breaking this much components during a release cycle will
>>>>> negatively affect release time line?
>>>>>
>>>>> Also we need to aware about what kind of changes need to done to
>>>>> components to fix once break.
>>>>>
>>>>> Also what happens to P2 story, after changing API, can already
>>>>> released chunk1 components install in a chunk2 product?
>>>>>
>>>>> On Fri, Sep 14, 2012 at 2:54 PM, Pradeep Fernando wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> we have completed the CarbonContext refactoring task within the
>>>>>> kernel. Now its time to refactor the platform/components. Soon I ll be
>>>>>> commiting the code to carbon-kernel.
>>>>>> The components listed below has to be modified. There you have to
>>>>>> refactor the code + move the components to new versions.
>>>>>>
>>>>>>
>>>>>> The modifications include API changes and will break the compatibility
>>>>>> between product minor versions. Please shout if you have any concerns
>>>>>> regarding this effort.
>>>>>>
>>>>>>
>>>>>> CarbonContextHolder refactoring. - use
>>>>>> CarbonContext/PrivilegedCarbonContext to access this.
>>>>>>
>>>>>> ./logging/org.wso2.carbon.logging.service/
>>>>>> ./rss-manager/org.wso2.carbon.rssmanager.core/
>>>>>> ./system-statistics/org.wso2.carbon.statistics.ui/
>>>>>> ./cg/org.wso2.carbon.cloud.gateway.agent/
>>>>>> ./webapp-mgt/org.wso2.carbon.webapp.mgt/
>>>>>> ./governance/org.wso2.carbon.governance.api/
>>>>>> ./business-processes/bpel/org.wso2.carbon.bpel/
>>>>>> ./business-processes/bpel/org.wso2.carbon.bpel.deployer/
>>>>>> ./business-processes/humantask/org.wso2.carbon.humantask/
>>>>>> ./proxy-admin/org.wso2.carbon.proxyadmin/
>>>>>> ./module-mgt/org.wso2.carbon.module.mgt/
>>>>>> ./registry/org.wso2.carbon.registry.extensions/
>>>>>> ./registry/org.wso2.carbon.registry.social.impl/
>>>>>> ./ws-discovery/org.wso2.carbon.discovery.core/
>>>>>> ./identity/org.wso2.carbon.identity.entitlement/
>>>>>> ./identity/org.wso2.carbon.identity.entitlement.mediator/
>>>>>> ./data-services/org.wso2.carbon.dataservices.core/
>>>>>> ./mediation-initializer/org.wso2.carbon.mediation.initializer/
>>>>>> ./service-mgt/org.wso2.carbon.service.mgt/
>>>>>> ./csg/org.wso2.carbon.cloud.csg.agent/
>>&

Re: [Dev] CarbonContext refactoring across the platform

[Hasini Gunasinghe]

I too think this will negatively affect the products in the queue to be
released which are being stabilized at the moment.

Can we do this after the planned chunk 2/chunk 3 products are released?

Thanks,
Hasini.

On Fri, Sep 14, 2012 at 5:03 PM, Nuwan Bandara  wrote:

> Hi Pradeep,
>
> What did you mean by backward compatible, if we are to re-factor all these
> components ? Also the P2 story is a valid question.
>
> This is whole lot of components IMO. We should have done it bit earlier,
> else lets move to C5.
>
> Regards,
> /Nuwan
>
> On Fri, Sep 14, 2012 at 4:54 PM, Tharindu Mathew wrote:
>
>> All chunks will have to be re-released after this change to ensure
>> features can be installed on top.
>>
>> I thought this change was backwards compatible? Anyway, we shouldn't go
>> ahead with this.
>>
>>
>> On Fri, Sep 14, 2012 at 4:48 PM, Miyuru Wanninayaka wrote:
>>
>>> Doesn't breaking this much components during a release cycle will
>>> negatively affect release time line?
>>>
>>> Also we need to aware about what kind of changes need to done to
>>> components to fix once break.
>>>
>>> Also what happens to P2 story, after changing API, can already released
>>> chunk1 components install in a chunk2 product?
>>>
>>> On Fri, Sep 14, 2012 at 2:54 PM, Pradeep Fernando wrote:
>>>
 Hi all,

 we have completed the CarbonContext refactoring task within the
 kernel. Now its time to refactor the platform/components. Soon I ll be
 commiting the code to carbon-kernel.
 The components listed below has to be modified. There you have to
 refactor the code + move the components to new versions.


 The modifications include API changes and will break the compatibility
 between product minor versions. Please shout if you have any concerns
 regarding this effort.


 CarbonContextHolder refactoring. - use
 CarbonContext/PrivilegedCarbonContext to access this.

 ./logging/org.wso2.carbon.logging.service/
 ./rss-manager/org.wso2.carbon.rssmanager.core/
 ./system-statistics/org.wso2.carbon.statistics.ui/
 ./cg/org.wso2.carbon.cloud.gateway.agent/
 ./webapp-mgt/org.wso2.carbon.webapp.mgt/
 ./governance/org.wso2.carbon.governance.api/
 ./business-processes/bpel/org.wso2.carbon.bpel/
 ./business-processes/bpel/org.wso2.carbon.bpel.deployer/
 ./business-processes/humantask/org.wso2.carbon.humantask/
 ./proxy-admin/org.wso2.carbon.proxyadmin/
 ./module-mgt/org.wso2.carbon.module.mgt/
 ./registry/org.wso2.carbon.registry.extensions/
 ./registry/org.wso2.carbon.registry.social.impl/
 ./ws-discovery/org.wso2.carbon.discovery.core/
 ./identity/org.wso2.carbon.identity.entitlement/
 ./identity/org.wso2.carbon.identity.entitlement.mediator/
 ./data-services/org.wso2.carbon.dataservices.core/
 ./mediation-initializer/org.wso2.carbon.mediation.initializer/
 ./service-mgt/org.wso2.carbon.service.mgt/
 ./csg/org.wso2.carbon.cloud.csg.agent/
 ./url-mapper/org.wso2.carbon.url.mapper.ui/
 ./data-sources/org.wso2.carbon.datasource/

 SuperTenantCarbonContext refactoring.  - use PrivilegedCarbonContext

 ./remote-usermgt/org.wso2.carbon.um.ws.service/
 ./mashup/org.wso2.carbon.mashup.javascript-hostobjects.registry/
 ./mashup/org.wso2.carbon.mashup.jsservices/
 ./mashup/org.wso2.carbon.mashup.javascript-hostobjects.system/
 ./rss-manager/org.wso2.carbon.rssmanager.core/
 ./system-statistics/org.wso2.carbon.statistics.ui/
 ./system-statistics/org.wso2.carbon.statistics/
 ./cep/org.wso2.carbon.cep.core/
 ./security/org.wso2.carbon.security.mgt/
 ./cg/org.wso2.carbon.cloud.gateway.agent/
 ./cg/org.wso2.carbon.cloud.gateway/

 ./authenticators/token-authenticator/org.wso2.carbon.identity.authenticator.token/
 ./analytics/org.wso2.carbon.analytics.hive/
 ./analytics/org.wso2.carbon.hive.data.source.access/
 ./webapp-mgt/org.wso2.carbon.webapp.deployer/
 ./ntask/org.wso2.carbon.ntask.core/
 ./event/org.wso2.carbon.event.core/
 ./event/org.wso2.carbon.event.ws/
 ./governance/org.wso2.carbon.governance.list/
 ./governance/org.wso2.carbon.governance.lcm/
 ./mediators/bam/org.wso2.carbon.mediator.bam/
 ./mediators/event/org.wso2.carbon.mediator.event/
 ./data-bridge/org.wso2.carbon.databridge.receiver.restapi/

 ./bam-data-publishers/org.wso2.carbon.bam.data.publisher.activity.mediation/

 ./bam-data-publishers/org.wso2.carbon.bam.data.publisher.activity.service/
 ./bam-data-publishers/org.wso2.carbon.bam.lwevent.core/
 ./bam-data-publishers/org.wso2.carbon.bam.data.publisher.servicestats/
 ./bam-data-publishers/org.wso2.carbon.bam.data.publisher.mediationstats/
 ./mediation/mediation-library/org.wso2.carbon.mediation.library/
 ./business-processes/attachment-mgt/org.wso2.carbon.attachment.mgt/
 ./business-processes/bpel/org.wso2.carbon.bpel/

 ./busin

Re: [Dev] [Commits] [Carbon-platform] svn commit r141667 - in carbon/platform/trunk/products/as/modules/samples/product/EntitlementFilter: . src/main/java/org/wso2/carbon/entitlement/filter/client src

[Hasini Gunasinghe]

Hi Pradeep,

What is the plan to sync the branch and trunk when we get back to trunk?

Thanks,
Hasini.

On Sun, Sep 9, 2012 at 7:27 PM, Pradeep Fernando  wrote:

> Hi johan,
>
> No point of commiting to trunk. waste of time. :)
>
> --Pradeep
> ___
> 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

Re: [Dev] Should I be able to login as "admin@carbon.super" as the username?

[Hasini Gunasinghe]

I took a check out from
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.core.services/4.0.1/and
checked applying the patch and the 4 files were patched without an
issue.
Could I know what is the error you got?

Thanks,
Hasini.

On Wed, Sep 5, 2012 at 2:51 PM, Afkham Azeez  wrote:

> I'm getting an error while applying the patch at
> the carbon/kernel/branches/4.0.0/core/org.wso2.carbon.core/4.0.1 level
>
>
> On Wed, Sep 5, 2012 at 2:27 PM, Hasini Gunasinghe  wrote:
>
>> Please find the attached patch with the fix.
>>
>> Thanks,
>> Hasini.
>>
>>
>>  On Wed, Sep 5, 2012 at 12:43 PM, Hasini Gunasinghe wrote:
>>
>>> +1. Will fix this.
>>>
>>> Thanks,
>>> Hasini.
>>>
>>> On Wed, Sep 5, 2012 at 12:33 PM, Prabath Siriwardena 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Sep 5, 2012 at 12:30 PM, Afkham Azeez  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 12:22 PM, Prabath Siriwardena >>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 5, 2012 at 12:22 PM, Hasini Gunasinghe 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 5, 2012 at 12:04 PM, Afkham Azeez wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Sep 5, 2012 at 2:13 AM, Senaka Fernando wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Right now I can log in as admin/admin and also 
>>>>>>>>> admin@carbon.super/admin.
>>>>>>>>> Is this proper behavior?
>>>>>>>>>
>>>>>>>>
>>>>>>>> :) You have discovered an easter egg in Carbon :) If a user tries
>>>>>>>> to login as admin@carbon.super we should throw an authentication
>>>>>>>> failure.
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Even with correct admin credentials?
>>>>>>>
>>>>>>
>>>>>> Yes.. what is the risk here..?
>>>>>>
>>>>>
>>>>> It can cause downstream logic to fail. Besides "carbon.super" & tenant
>>>>> ID of -1234 are internal details which we don't expose. We may decide to
>>>>> change super tenant name to "super.duper.dude" in the future because we
>>>>> came up with that as an internal implementation detail. But if some 
>>>>> clients
>>>>> start relying on "carbon.super" & -1234, then externals parties will get
>>>>> affected. So, we should not allow or encourage others to use these when
>>>>> they call into Carbon. So, we put a stop to it then and there by throwing
>>>>> an authentication exception.
>>>>>
>>>>
>>>> +1
>>>>
>>>> Thanks & regards,
>>>> -Prabath
>>>>
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks & regards,
>>>>>> -Prabath
>>>>>>
>>>>>>
>>>>>>> I too have tried this before and I do not see why we should throw an
>>>>>>> authentication failure.. May be I have missed some aspect.. Would
>>>>>>> appreciate more insight on what is the risk here...
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Hasini.
>>>>>>>
>>>>>>>> Can we get this fixed soon? Should be a simple fix.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> If it is proper, some UIs are not rendering properly when I log in
>>>>>>>>> as "admin@carbon.super". For example, half of "admin/index.jsp"
>>>>>>>>> is gone.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Senaka.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Senaka Fernando*
>>>>>>>>> M

Re: [Dev] Should I be able to login as "admin@carbon.super" as the username?

[Hasini Gunasinghe]

Please find the attached patch with the fix.

Thanks,
Hasini.

On Wed, Sep 5, 2012 at 12:43 PM, Hasini Gunasinghe  wrote:

> +1. Will fix this.
>
> Thanks,
> Hasini.
>
> On Wed, Sep 5, 2012 at 12:33 PM, Prabath Siriwardena wrote:
>
>>
>>
>> On Wed, Sep 5, 2012 at 12:30 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 12:22 PM, Prabath Siriwardena 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Sep 5, 2012 at 12:22 PM, Hasini Gunasinghe wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 12:04 PM, Afkham Azeez  wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 5, 2012 at 2:13 AM, Senaka Fernando wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Right now I can log in as admin/admin and also admin@carbon.super/admin.
>>>>>>> Is this proper behavior?
>>>>>>>
>>>>>>
>>>>>> :) You have discovered an easter egg in Carbon :) If a user tries to
>>>>>> login as admin@carbon.super we should throw an authentication
>>>>>> failure.
>>>>>>
>>>>>
>>>>
>>>>>
>>>>> Even with correct admin credentials?
>>>>>
>>>>
>>>> Yes.. what is the risk here..?
>>>>
>>>
>>> It can cause downstream logic to fail. Besides "carbon.super" & tenant
>>> ID of -1234 are internal details which we don't expose. We may decide to
>>> change super tenant name to "super.duper.dude" in the future because we
>>> came up with that as an internal implementation detail. But if some clients
>>> start relying on "carbon.super" & -1234, then externals parties will get
>>> affected. So, we should not allow or encourage others to use these when
>>> they call into Carbon. So, we put a stop to it then and there by throwing
>>> an authentication exception.
>>>
>>
>> +1
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>>>
>>>
>>>>
>>>> Thanks & regards,
>>>> -Prabath
>>>>
>>>>
>>>>> I too have tried this before and I do not see why we should throw an
>>>>> authentication failure.. May be I have missed some aspect.. Would
>>>>> appreciate more insight on what is the risk here...
>>>>>
>>>>> Thanks,
>>>>> Hasini.
>>>>>
>>>>>> Can we get this fixed soon? Should be a simple fix.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> If it is proper, some UIs are not rendering properly when I log in
>>>>>>> as "admin@carbon.super". For example, half of "admin/index.jsp" is
>>>>>>> gone.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Senaka.
>>>>>>>
>>>>>>> --
>>>>>>> *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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Afkham Azeez*
>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>> * <http://www.apache.org/>**
>>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>>> twitter: 
>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>> *
>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>>
>>>>>> *
>>>>>> *
>>>>>> *Lean . Enterprise . Middleware*
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>> Prabath
>>>>
>>>> Mobile : +94 71 809 6732
>>>>
>>>> http://blog.facilelogin.com
>>>> http://RampartFAQ.com
>>>>
>>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * <http://www.apache.org/>**
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>>
>


authentication.patch
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Should I be able to login as "admin@carbon.super" as the username?

[Hasini Gunasinghe]

+1. Will fix this.

Thanks,
Hasini.

On Wed, Sep 5, 2012 at 12:33 PM, Prabath Siriwardena wrote:

>
>
> On Wed, Sep 5, 2012 at 12:30 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Sep 5, 2012 at 12:22 PM, Prabath Siriwardena wrote:
>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 12:22 PM, Hasini Gunasinghe wrote:
>>>
>>>>
>>>>
>>>> On Wed, Sep 5, 2012 at 12:04 PM, Afkham Azeez  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 2:13 AM, Senaka Fernando wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Right now I can log in as admin/admin and also admin@carbon.super/admin.
>>>>>> Is this proper behavior?
>>>>>>
>>>>>
>>>>> :) You have discovered an easter egg in Carbon :) If a user tries to
>>>>> login as admin@carbon.super we should throw an authentication failure.
>>>>>
>>>>
>>>
>>>>
>>>> Even with correct admin credentials?
>>>>
>>>
>>> Yes.. what is the risk here..?
>>>
>>
>> It can cause downstream logic to fail. Besides "carbon.super" & tenant ID
>> of -1234 are internal details which we don't expose. We may decide to
>> change super tenant name to "super.duper.dude" in the future because we
>> came up with that as an internal implementation detail. But if some clients
>> start relying on "carbon.super" & -1234, then externals parties will get
>> affected. So, we should not allow or encourage others to use these when
>> they call into Carbon. So, we put a stop to it then and there by throwing
>> an authentication exception.
>>
>
> +1
>
> Thanks & regards,
> -Prabath
>
>
>>
>>
>>>
>>> Thanks & regards,
>>> -Prabath
>>>
>>>
>>>> I too have tried this before and I do not see why we should throw an
>>>> authentication failure.. May be I have missed some aspect.. Would
>>>> appreciate more insight on what is the risk here...
>>>>
>>>> Thanks,
>>>> Hasini.
>>>>
>>>>> Can we get this fixed soon? Should be a simple fix.
>>>>>
>>>>>
>>>>>>
>>>>>> If it is proper, some UIs are not rendering properly when I log in as
>>>>>> "admin@carbon.super". For example, half of "admin/index.jsp" is gone.
>>>>>>
>>>>>> Thanks,
>>>>>> Senaka.
>>>>>>
>>>>>> --
>>>>>> *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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Afkham Azeez*
>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>> * <http://www.apache.org/>**
>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>> twitter: 
>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>> *
>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>
>>>>> *
>>>>> *
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Prabath
>>>
>>> Mobile : +94 71 809 6732
>>>
>>> http://blog.facilelogin.com
>>> http://RampartFAQ.com
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Should I be able to login as "admin@carbon.super" as the username?

[Hasini Gunasinghe]

On Wed, Sep 5, 2012 at 12:04 PM, Afkham Azeez  wrote:

>
>
> On Wed, Sep 5, 2012 at 2:13 AM, Senaka Fernando  wrote:
>
>> Hi all,
>>
>> Right now I can log in as admin/admin and also admin@carbon.super/admin.
>> Is this proper behavior?
>>
>
> :) You have discovered an easter egg in Carbon :) If a user tries to login
> as admin@carbon.super we should throw an authentication failure.
>

Even with correct admin credentials?
I too have tried this before and I do not see why we should throw an
authentication failure.. May be I have missed some aspect.. Would
appreciate more insight on what is the risk here...

Thanks,
Hasini.

> Can we get this fixed soon? Should be a simple fix.
>
>
>>
>> If it is proper, some UIs are not rendering properly when I log in as
>> "admin@carbon.super". For example, half of "admin/index.jsp" is gone.
>>
>> Thanks,
>> Senaka.
>>
>> --
>> *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
>>
>>
>
>
> --
> *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*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Blocker] Rampart handlers consuming 8% time during an invocation even if security is not engaged

[Hasini Gunasinghe]

Hi Sagara,

Sure, will do.

Thanks,
Hasini.

On Wed, Sep 5, 2012 at 11:42 AM, Sagara Gunathunga  wrote:

> Hi Hasini,
>
> Can you please provide same patch for Rampart Apache trunk too ?
>
> Thanks !
>
> On Tue, Sep 4, 2012 at 11:47 PM, Hasini Gunasinghe wrote:
>
>> Attaching the modifications at Rampart handlers level which caused slight
>> improvement.
>> Please review and commit.
>>
>> We can also consider removing rampart module (i.e security phase) from
>> global phase in a future release so that rampart handlers will not be
>> invoked for each service call.
>>
>> Thanks,
>> Hasini.
>>
>>
>> On Tue, Sep 4, 2012 at 4:55 PM, Afkham Azeez  wrote:
>>
>>> Just by making the following change we were able to see a performance
>>> improvement of close to 20% !!!
>>>
>>> Index: src/org/apache/axis2/description/AxisModule.java
>>> ===
>>> --- src/org/apache/axis2/description/AxisModule.java (revision 141042)
>>> +++ src/org/apache/axis2/description/AxisModule.java (working copy)
>>> @@ -129,8 +129,17 @@
>>>   *
>>>   * @return the archive name of the module
>>>   */
>>> +private String archiveName;
>>> +
>>>  public String getArchiveName() {
>>> -return version == null ? name : (name + "-" + version);
>>> +if (archiveName == null){
>>> +if(version == null){
>>> +archiveName = name;
>>> +} else {
>>> +archiveName = name + "-" + version;
>>> +}
>>> +}
>>> +return archiveName;
>>>  }
>>>
>>> On Tue, Sep 4, 2012 at 2:27 PM, Afkham Azeez  wrote:
>>>
>>>> This is a simple echo service which has not been secured. In the in
>>>> flow, the overhead caused by the rampart handlers is 8% & in the out flow
>>>> the overhead is 12%. So, we can improve performance by 20% just by
>>>> optimizing this bit of code.
>>>>
>>>> Azeez
>>>>
>>>>
>>>> On Tue, Sep 4, 2012 at 2:23 PM, Prabath Siriwardena 
>>>> wrote:
>>>>
>>>>> What is the security policy you used here..?
>>>>>
>>>>> Thanks & regards,
>>>>> -Prabath
>>>>>
>>>>>
>>>>> On Tue, Sep 4, 2012 at 2:20 PM, Afkham Azeez  wrote:
>>>>>
>>>>>> Rampart handlers are causing much higher overhead in the outflow. See
>>>>>> attached screenshot.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 4, 2012 at 2:16 PM, Hasini Gunasinghe wrote:
>>>>>>
>>>>>>> Will look into this.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Hasini.
>>>>>>>
>>>>>>> On Tue, Sep 4, 2012 at 2:06 PM, Afkham Azeez  wrote:
>>>>>>>
>>>>>>>> See attached jprofiler screenshot.
>>>>>>>>
>>>>>>>> The main culprit seems to be the isEngaged method call which is
>>>>>>>> repeatedly building the module name. The fix should be simple, we could
>>>>>>>> remember the module name. Prabath et. al. please take this up urgently.
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Afkham Azeez*
>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>>> * <http://www.apache.org/>**
>>>>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>>>>> twitter: 
>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>>>> *
>>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>>>> *
>>>>>>>> *
>>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
&g

Re: [Dev] [Blocker] Rampart handlers consuming 8% time during an invocation even if security is not engaged

[Hasini Gunasinghe]

Attaching the modifications at Rampart handlers level which caused slight
improvement.
Please review and commit.

We can also consider removing rampart module (i.e security phase) from
global phase in a future release so that rampart handlers will not be
invoked for each service call.

Thanks,
Hasini.

On Tue, Sep 4, 2012 at 4:55 PM, Afkham Azeez  wrote:

> Just by making the following change we were able to see a performance
> improvement of close to 20% !!!
>
> Index: src/org/apache/axis2/description/AxisModule.java
> ===
> --- src/org/apache/axis2/description/AxisModule.java (revision 141042)
> +++ src/org/apache/axis2/description/AxisModule.java (working copy)
> @@ -129,8 +129,17 @@
>   *
>   * @return the archive name of the module
>   */
> +private String archiveName;
> +
>  public String getArchiveName() {
> -return version == null ? name : (name + "-" + version);
> +if (archiveName == null){
> +if(version == null){
> +archiveName = name;
> +} else {
> +archiveName = name + "-" + version;
> +}
> +}
> +return archiveName;
>  }
>
> On Tue, Sep 4, 2012 at 2:27 PM, Afkham Azeez  wrote:
>
>> This is a simple echo service which has not been secured. In the in flow,
>> the overhead caused by the rampart handlers is 8% & in the out flow the
>> overhead is 12%. So, we can improve performance by 20% just by optimizing
>> this bit of code.
>>
>> Azeez
>>
>>
>> On Tue, Sep 4, 2012 at 2:23 PM, Prabath Siriwardena wrote:
>>
>>> What is the security policy you used here..?
>>>
>>> Thanks & regards,
>>> -Prabath
>>>
>>>
>>> On Tue, Sep 4, 2012 at 2:20 PM, Afkham Azeez  wrote:
>>>
>>>> Rampart handlers are causing much higher overhead in the outflow. See
>>>> attached screenshot.
>>>>
>>>>
>>>>
>>>> On Tue, Sep 4, 2012 at 2:16 PM, Hasini Gunasinghe wrote:
>>>>
>>>>> Will look into this.
>>>>>
>>>>> Thanks,
>>>>> Hasini.
>>>>>
>>>>> On Tue, Sep 4, 2012 at 2:06 PM, Afkham Azeez  wrote:
>>>>>
>>>>>> See attached jprofiler screenshot.
>>>>>>
>>>>>> The main culprit seems to be the isEngaged method call which is
>>>>>> repeatedly building the module name. The fix should be simple, we could
>>>>>> remember the module name. Prabath et. al. please take this up urgently.
>>>>>>
>>>>>> --
>>>>>> *Afkham Azeez*
>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>> * <http://www.apache.org/>**
>>>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>>> twitter: 
>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>> *
>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>> *
>>>>>> *
>>>>>> *Lean . Enterprise . Middleware*
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Afkham Azeez*
>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> * <http://www.apache.org/>**
>>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>> twitter: 
>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>> *
>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>> *
>>>> *
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Prabath
>>>
>>> Mobile : +94 71 809 6732
>>>
>>> http://blog.facilelogin.com
>>> http://RampartFAQ.com
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


rapmart.patch
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Blocker] Rampart handlers consuming 8% time during an invocation even if security is not engaged

[Hasini Gunasinghe]

Will look into this.

Thanks,
Hasini.

On Tue, Sep 4, 2012 at 2:06 PM, Afkham Azeez  wrote:

> See attached jprofiler screenshot.
>
> The main culprit seems to be the isEngaged method call which is repeatedly
> building the module name. The fix should be simple, we could remember the
> module name. Prabath et. al. please take this up urgently.
>
> --
> *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*
>
>
> ___
> 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

Re: [Dev] Kernel build failed in clean repo.

[Hasini Gunasinghe]

Please take svn up in carbon.core.feature/4.0.1

Thanks,
Hasini.

On Fri, Aug 24, 2012 at 4:47 PM, Ajith Vitharana  wrote:

>
> [INFO] WSO2 Carbon - Carbon Feature .. FAILURE [6.826s]
> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon Core - Distribution ... SKIPPED
> [INFO] WSO2 Carbon - Integration . SKIPPED
> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
> [INFO] WSO2 Carbon - Integration Core  SKIPPED
> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
> [INFO] WSO2 Carbon - UI styles ... SKIPPED
> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
> [INFO] WSO2 Carbon - Distribution  SKIPPED
> [INFO] WSO2 Carbon - Patch releases - distribution - Aggregator Module
>  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1:24:18.987s
> [INFO] Finished at: Fri Aug 24 16:46:20 IST 2012
> [INFO] Final Memory: 462M/1410M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5:p2-feature-gen
> (4-p2-feature-generation) on project org.wso2.carbon.core.feature: ERROR:
> Could not find artifact
> org.wso2.carbon:org.wso2.carbon.core.server.feature:zip:4.0.1 in wso2-nexus
> (http://maven.wso2.org/nexus/content/groups/wso2-public/)
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.core.server.feature -Dversion=4.0.1
> -Dpackaging=zip -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.core.server.feature -Dversion=4.0.1
> -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR]
> [ERROR]
> [ERROR] org.wso2.carbon:org.wso2.carbon.core.server.feature:zip:4.0.1
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true,
> snapshots=true),
> [ERROR] central (http://repo1.maven.org/maven2, releases=true,
> snapshots=false)
> [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/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.core.feature
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>
> ___
> 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

Re: [Dev] Failure in building openid4java

[Hasini Gunasinghe]

Hi,

This was fixed yesterday morning as per r136982.
Please let us know if you are still getting this error.

Thanks,
Hasini.

On Thu, Aug 9, 2012 at 7:34 PM, Tharindu Mathew  wrote:

> Hi,
>
> I'm getting a build break in openid4java...
>
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : There are split packages, use directive
> -split-package:=(merge-first|merge-last) on instruction to get rid of this
> warning: org.openxri, classpath: [Jar:openid4java-nodeps,
> Jar:openxri-client, Jar:openxri-syntax, Jar:nekohtml] from:
> /Users/mackie/.m2/repository/org/openxri/openxri-syntax/1.2.0/openxri-syntax-1.2.0.jar
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : Instructions for Export-Package that are never used:
> org\.htmlparser\..*|org\.htmlparser
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: htmlparser.version
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : Superfluous export-package instructions: [org.htmlparser.*]
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [ERROR] Error building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : Invalid value for Bundle-Version, ${orbit.version.openid4java} does not
> match [0-9]+(\.[0-9]+(\.[0-9]+(\.[0-9A-Za-z_-]+)?)?)?
> [ERROR] Error(s) found in bundle configuration
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 3.980s
> [INFO] Finished at: Thu Aug 09 19:33:35 IST 2012
> [INFO] Final Memory: 6M/81M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.felix:maven-bundle-plugin:1.4.0:bundle (default-bundle) on
> project openid4java-nodeps: Error(s) found in bundle configuration -> [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/MojoExecutionException
>
> ___
> 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

Re: [Dev] Compilation failure : org.wso2.carbon.identity.provider

[Hasini Gunasinghe]

Hi Ajith,

On Thu, Aug 9, 2012 at 6:20 AM, Ajith Vitharana  wrote:

>
>
> On Wed, Aug 8, 2012 at 10:38 PM, Suresh Attanayaka wrote:
>
>> Hi Isuru,
>>
>> Take a svn up at the openid4java dependency and build both the dependency
>> and orbit.
>>
>>
> Hi Suresh ,
>
> You have committed to org.wso2.carbon.identity.provider/4.0.0 (r136764)
> after the AM release.
> That is wrong and should be revert.
>
These were added before the decision on releasing all the 4.0.0 components
was taken and was not wrong at the time they were added.
And we are in the process of creating 4.0.1 components and porting the
commits after r136764 into 4.0.1 components.

> And i'm getting following error while building  openid4java in a clean
> repo.
>
This is due to a missing orbit-version property. This is fixed now and
please take svn up in orbit/openid4java pom.xml.

Thanks,
Hasini.

> Please fix this  compilation error ASAP.
>
>
>
> [INFO]
> 
> [INFO] Building openid4java.wso2 ${orbit.version.openid4java}
> [INFO]
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> openid4java-nodeps ---
> [INFO] Deleting
> /home/ajithn/wso2/build/branches/release/platform/4.0.0/dependencies/orbit/openid4java/0.9.6.wso2v2/target
> [INFO]
> [INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
> openid4java-nodeps ---
> [INFO] Verifying module descriptor ...
> [INFO] Pom descriptor modification detected.
> [INFO] Deleting
> /home/ajithn/wso2/build/branches/release/platform/4.0.0/dependencies/orbit/openid4java/0.9.6.wso2v2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
> openid4java-nodeps ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/ajithn/wso2/build/branches/release/platform/4.0.0/dependencies/orbit/openid4java/0.9.6.wso2v2/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
> openid4java-nodeps ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources
> (default-testResources) @ openid4java-nodeps ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/ajithn/wso2/build/branches/release/platform/4.0.0/dependencies/orbit/openid4java/0.9.6.wso2v2/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @
> openid4java-nodeps ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.1:test (default-test) @
> openid4java-nodeps ---
> [INFO] No tests to run.
> [INFO] Surefire report directory:
> /home/ajithn/wso2/build/branches/release/platform/4.0.0/dependencies/orbit/openid4java/0.9.6.wso2v2/target/surefire-reports
>
> ---
>  T E S T S
> ---
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO] --- maven-bundle-plugin:1.4.0:bundle (default-bundle) @
> openid4java-nodeps ---
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: htmlparser.version
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : There are split packages, use directive
> -split-package:=(merge-first|merge-last) on instruction to get rid of this
> warning: org.openxri, classpath: [Jar:openid4java-nodeps,
> Jar:openxri-client, Jar:openxri-syntax, Jar:nekohtml] from:
> /home/ajithn/.m2/repository/org/openxri/openxri-syntax/1.2.0/openxri-syntax-1.2.0.jar
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : Instructions for Export-Package that are never used:
> org\.htmlparser\..*|org\.htmlparser
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: htmlparser.version
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : Superfluous export-package instructions: [org.htmlparser.*]
> [WARNING] Warning building bundle
> org.openid4java.wso2:openid4java-nodeps:bundle:${orbit.version.openid4java}
> : No translation found for macro: orbit.version.openid4java
> [WARNI

Re: [Dev] WSO2 Identity Server 4.0.0 - M2 Released.

[Hasini Gunasinghe]

Hi Samisa,

On Mon, Aug 6, 2012 at 8:00 AM, Samisa Abeysinghe  wrote:

> I have done an initial round of testing, predominately around the UI, but
> seems that there are some functional breaks too
>
> To make QA tasks easy, please make sure these UI aspects are fixed, plus
> the related functional issues are fixed.
>

Thanks for reporting these issues. We'll make sure these are fixed in the
future packs.

>
> More importantly, we need loads of samples to help users as well as
> testers.
>

Sure, We have plans to add more samples and more integration tests covering
the IS features in the upcoming milestone packs.

Thanks,
Hasini.

>
> On Fri, Aug 3, 2012 at 10:47 PM, Hasini Gunasinghe wrote:
>
>> Hi,
>>
>> Please find the link for Identity Server 4.0.0 - M2 build at
>> https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/m2/
>>
>> New features/improvements in M2:
>> 1. Improvements to OAuth feature.
>> 2. Improvements to OpenID feature.
>> 3. SCIM Integration with IS in M1 state.
>>
>> Issues fixed:
>> https://wso2.org/jira/browse/IDENTITY-265
>> https://wso2.org/jira/browse/IDENTITY-266
>> https://wso2.org/jira/browse/IDENTITY-267
>> https://wso2.org/jira/browse/IDENTITY-268
>>  https://wso2.org/jira/browse/IDENTITY-269
>> https://wso2.org/jira/browse/IDENTITY-270
>> https://wso2.org/jira/browse/IDENTITY-271
>> https://wso2.org/jira/browse/CARBON-13066
>> https://wso2.org/jira/browse/CARBON-13607
>>
>> Thanks,
>> Identity Server Team.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Identity Server 4.0.0 - M2 Released.

[Hasini Gunasinghe]

Hi,

Please find the link for Identity Server 4.0.0 - M2 build at
https://svn.wso2.org/repos/wso2/scratch/wso2is-4.0.0/m2/

New features/improvements in M2:
1. Improvements to OAuth feature.
2. Improvements to OpenID feature.
3. SCIM Integration with IS in M1 state.

Issues fixed:
https://wso2.org/jira/browse/IDENTITY-265
https://wso2.org/jira/browse/IDENTITY-266
https://wso2.org/jira/browse/IDENTITY-267
https://wso2.org/jira/browse/IDENTITY-268
https://wso2.org/jira/browse/IDENTITY-269
https://wso2.org/jira/browse/IDENTITY-270
https://wso2.org/jira/browse/IDENTITY-271
https://wso2.org/jira/browse/CARBON-13066
https://wso2.org/jira/browse/CARBON-13607

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

Re: [Dev] error while FE/BE separation

[Hasini Gunasinghe]

Hi Pradeep,

This message receiver is referenced only by BE components. So ideally it
should be in a core-BE component.

The correct fix for this FE-BE separation issue IMO, is to move user.mgt
component to core-server feature.

There is already a user.mgt.common component which is also included in
core-common feature.

I am not sure why user.mgt component was included in core-common feature so
far.

Thanks,
Hasini.

On Wed, Aug 1, 2012 at 8:47 PM, Pradeep Fernando  wrote:

> Hi,
>
> im getting the following error after restarting the server with the BE
> components. Came to know that user-mgt has a  reference to this CNF.
> the problem being,
>
> user-mgt is a common-feature
> carbon.server.admin is a server feature (priviledgedActionMR class resides
> in this bundle )
>
>
> need a solution asap. Carbon core L1.  Looks like we should move this
> class to some other place. (to a common component)
>
> --Pradeep
>
>
>
>
> org.apache.axis2.deployment.DeploymentException: A ClassNotFoundException
> error occurred in loading the message receiver
> org.wso2.carbon.server.admin.privilegedaction.PrivilegedActionMessageReceiver
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.org.apache.axis2.deployment.DeploymentException:
> A ClassNotFoundException error occurred in loading the message receiver
> org.wso2.carbon.server.admin.privilegedaction.PrivilegedActionMessageReceiver
> at
> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:471)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:217)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:64)
> 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.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:78)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:57)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:39)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:37)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java

Re: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #66 has FAILED. Change made by 22 authors.

[Hasini Gunasinghe]

Hi,

This has already been fixed yesterday.

Thanks,
Hasini,

On Tue, Jul 31, 2012 at 11:06 PM, Shammi Jayasinghe  wrote:

> Hi IS Team,
> Could you please check on following
>
> 31-Jul-2012 06:13:29 [INFO] BUILD FAILURE31-Jul-2012 06:13:29 [INFO]
> 31-Jul-2012
> 06:13:29 [INFO] Total time: 2:18:53.491s 31-Jul-2012 06:13:29[INFO]
> Finished at: Tue Jul 31 06:13:28 PDT 2012 31-Jul-2012 06:13:40[INFO]
> Final Memory: 2779M/3389M 31-Jul-2012 06:13:40[INFO]
>  
> 31-Jul-2012
> 06:13:40 [ERROR] Failed to execute goal on project
> org.wso2.carbon.identity.scim.provider.feature: Could not resolve
> dependencies for project
> org.wso2.carbon:org.wso2.carbon.identity.scim.provider.feature:pom:4.0.0:
> Could not find artifact org.wso2.charon:charon-core:jar:1.0.0-wso2v1 in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
> [Help 1] 31-Jul-2012 06:13:40 [ERROR] Thanks
> Shammi
>
> On Tue, Jul 31, 2012 at 6:44 PM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 Carbon 
>> BRANCH›
>> Platform_4.0.0  › 
>> #66
>> failed
>>
>> This build occurred because it is a dependant of 
>> WCB001-KER000-45
>> .
>>
>> No failed tests found, a possible compilation error.
>>Failing Jobs  Job
>> Duration Tests[image: Failed]  Default 
>> Job (Default
>> Stage)  139 minutes  No tests found  
>> Logs|
>> Artifacts  
>> Code
>> Changes   View
>> all 48 code changes
>> ramith 
>> removing tabs  135910isuruw
>> removing the data limitations in presentationSubject and presentationName
>> as a fix to the issue 
>> REGISTRY-1061
>> 135907lalaji 
>> Fixed 
>> APISTORE-567
>> 135906   45 more 
>> changes… 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
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Platform build failure (org.wso2.carbon.identity.scim.provider.feature)

[Hasini Gunasinghe]

Hi,

This is fixed. Please take svn update the pom file
of org.wso2.carbon.identity.scim.provider.feature.

Thanks,
Hasini.

On Tue, Jul 31, 2012 at 4:54 PM, Ranga Siriwardena  wrote:

> Hi,
>
> $Subject.
>
> -- Forwarded message --
> From: WSO2 Carbon 3.2.2 Builder (US1) 
> Date: Wed, Aug 1, 2012 at 12:11 AM
> Subject: "WSO2 Carbon Continuous Build has FAILED
> /home/builder/carbon/platform/4.0.0"
> To: ra...@wso2.com
>
>
> [INFO] WSO2 Carbon - Autoscaler Feature .. SKIPPED
> [INFO] Autoscaler Service Module . SKIPPED
> [INFO] WSO2 Carbon - Autoscaler Feature .. SKIPPED
> [INFO] Tenant Aware Load Balancer Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - Loadbalancer Endpoint Management Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Server Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation UI Feature  SKIPPED
> [INFO] WSO2 Carbon - Gadget Generation Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Feature Aggregator Module . SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer UI Feature ... SKIPPED
> [INFO] WSO2 Carbon - Cassandra Explorer Feature .. SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Cassandra Defn Storage Server Feature
>  SKIPPED
> [INFO] WSO2 Carbon - Data Bridge - Cassandra Defn Storage Aggregator
> Feature  SKIPPED
> [INFO] WSO2 Carbon - New Datasource Management Feature ... SKIPPED
> [INFO] WSO2 Jaggery Server - Features Aggregator Module .. SKIPPED
> [INFO] WSO2 Jaggery Server - Style Features .. SKIPPED
> [INFO] Jaggery Server Feature  SKIPPED
> [INFO] Jaggery Management UI Feature . SKIPPED
> [INFO] Jaggery aggregate Feature . SKIPPED
> [INFO] WSO2 Carbon - BAM Feature Aggregator Module ... SKIPPED
> [INFO] WSO2 Carbon - BAM Core Feature  SKIPPED
> [INFO] WSO2 Carbon - BAM Management UI Feature ... SKIPPED
> [INFO] WSO2 Carbon - Business Activity Monitoring Feature  SKIPPED
> [INFO] WSO2 Carbon - AppFactory Feature Aggregator Module  SKIPPED
> [INFO] WSO2 Carbon - AppFactory Server Feature ... SKIPPED
> [INFO] WSO2 Carbon - Platform Aggregator Pom . SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 1:22:44.880s
> [INFO] Finished at: Wed Aug 01 00:11:43 IST 2012
> [INFO] Final Memory: 1323M/1722M
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.identity.scim.provider.feature: Could not resolve
> dependencies for project
> org.wso2.carbon:org.wso2.carbon.identity.scim.provider.feature:pom:4.0.0:
> Could not find artifact org.wso2.charon:charon-core:jar:1.0.0-wso2v1 in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.identity.scim.provider.feature
>
>
> Thank You.
> Ranga.
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
>
> ___
> 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

Re: [Dev] Error: user core

[Hasini Gunasinghe]

Did you run the database scripts at server startup?
This happens when the relevant tables are not found in the UM database.

Thanks,
Hasini.

On Thu, Jul 26, 2012 at 4:46 PM, Pradeep Fernando  wrote:

> Hi,
>
> Im in the process of adding web-app mode support to carbon. Right now im
> facing the below error. Appreciate any help.
>
>
>
>
>
> Listening on port 0.0.0.0/0.0.0.0:19444 ...
> [2012-07-26 16:35:59,927]  INFO
> {org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
> Coordination service disabled.
> [2012-07-26 16:36:00,241]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2012-07-26 16:36:00,242]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 3.2.0-23-generic, amd64
> [2012-07-26 16:36:00,242]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/pradeep/installations/jdk1.6.0_33/jre
> [2012-07-26 16:36:00,243]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_33
> [2012-07-26 16:36:00,243]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 20.8-b03,Sun Microsystems Inc.
> [2012-07-26 16:36:00,243]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/pradeep/carbon-repo
> [2012-07-26 16:36:00,243]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/pradeep/installations/apache-tomcat-7.0.28/temp
> [2012-07-26 16:36:00,243]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> pradeep, en-US, Asia/Colombo
> [2012-07-26 16:36:00,581]  INFO
> {org.wso2.carbon.server.admin.internal.PrivilegedActionExtensionComponent}
> -  Privileged Actions Extension bundle activated successfuly.
> [2012-07-26 16:36:01,618] ERROR
> {org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Table
> "UM_DIALECT" not found; SQL statement:
> SELECT COUNT(UM_ID) FROM UM_DIALECT WHERE UM_TENANT_ID=? [42102-140]
> org.h2.jdbc.JdbcSQLException: Table "UM_DIALECT" not found; SQL statement:
> SELECT COUNT(UM_ID) FROM UM_DIALECT WHERE UM_TENANT_ID=? [42102-140]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
> at org.h2.message.DbException.get(DbException.java:167)
> at org.h2.message.DbException.get(DbException.java:144)
> at org.h2.command.Parser.readTableOrView(Parser.java:4498)
> at org.h2.command.Parser.readTableFilter(Parser.java:1011)
> at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1577)
> at org.h2.command.Parser.parseSelectSimple(Parser.java:1682)
> at org.h2.command.Parser.parseSelectSub(Parser.java:1571)
> at org.h2.command.Parser.parseSelectUnion(Parser.java:1416)
> at org.h2.command.Parser.parseSelect(Parser.java:1404)
> at org.h2.command.Parser.parsePrepared(Parser.java:392)
> at org.h2.command.Parser.parse(Parser.java:275)
> at org.h2.command.Parser.parse(Parser.java:247)
> at org.h2.command.Parser.prepare(Parser.java:201)
> at org.h2.command.Parser.prepareCommand(Parser.java:214)
> at org.h2.engine.Session.prepareLocal(Session.java:434)
> at org.h2.engine.Session.prepareCommand(Session.java:384)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1071)
> at
> org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:71)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
> at
> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)
> at
> org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51)
> at
> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)
> at
> org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:67)
> at
> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)
> at
> org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153)
> at
> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)
> at
> org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)
> at
> org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:99)
> at
> org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:63)
> at $Proxy14.prepareStatement(Unknown Source)
>  

Re: [Dev] Freezing trunk

[Hasini Gunasinghe]

Hi,

On Tue, Jul 24, 2012 at 5:20 PM, Amila Suriarachchi  wrote:

>
>
> On Tue, Jul 24, 2012 at 4:59 PM, Pradeep Fernando wrote:
>
>>
>>
>> On Tue, Jul 24, 2012 at 3:52 PM, Amila Suriarachchi wrote:
>>
>>> When cutting the branch can we avoid the components which are not
>>> released with the current set of products.
>>>
>>> For an example CEP component can be kept only in trunk and we will
>>> branch it when we ready to release the CEP. Since each and every component
>>> has branches this will be an viable option.
>>>
>>>
>>
>> No this is not possible. We have already created the branch. On the other
>> hand, there is no such thing as releasing from the trunk. So why don't you
>> do active development in the branch itself.
>>
>
> is there any reason to branch the components/products not release with the
> next batch of products? What we can do is to countine work on trunk and
> merge them to branch.
>

+1. For the features that are not yet completed on trunk, can we continue
working on them in trunk and branch them when we are have reached alpha
state wrt those features?

Thanks,
Hasini.

>
> thanks,
> Amila.
>
>
>
>>
>>
>> --pradeep
>>
>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
>
> ___
> 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

Re: [Dev] Identity database error while restarting the G-Reg server.

[Hasini Gunasinghe]

Fixed db scripts to match the table name used in the code - which has been
changed recently.
Please take svn up in identity/org.wso2.carbon.identity.core.

Thanks,
Hasini.

On Thu, Jul 19, 2012 at 4:45 PM, Ajith Vitharana  wrote:

> Hi All,
>
> I have mounted two registry instance and i got the following error while
> restarting the master node.
>
> chedulerServiceComponent
> *[2012-07-19 16:31:34,626] ERROR
> {org.wso2.carbon.identity.core.internal.IdentityCoreServiceComponent} -
>  Error occured while populating identity configuration properties*
> *java.lang.Exception: Error when creating the Identity database*
> at
> org.wso2.carbon.identity.core.persistence.JDBCPersistenceManager.initializeDatabase(JDBCPersistenceManager.java:98)
>  at
> org.wso2.carbon.identity.core.internal.IdentityCoreServiceComponent.activate(IdentityCoreServiceComponent.java:73)
> 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.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>  at
> org.wso2.carbon.security.internal.SecurityMgtServiceComponent.activate(SecurityMgtServiceComponent.java:62)
> 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(B

Re: [Dev] IS Build Fails in Profile Generation

[Hasini Gunasinghe]

Fixed the platform/trunk/products/pom.xml to have the correct jaxb version,
from where IS inherits the version.

The above issue should be fixed now.

Thanks,
Hasini.

On Mon, Jul 16, 2012 at 3:04 PM, Hasini Gunasinghe  wrote:

> Hi,
>
> We inherit those versions from platform/trunk/products/pom.xml.
>
> Will fix that.
>
> Thanks,
> Hasini.
>
> On Mon, Jul 16, 2012 at 2:57 PM, Ajith Vitharana  wrote:
>
>>
>>
>> On Mon, Jul 16, 2012 at 2:19 PM, Andun Gunawardena wrote:
>>
>>> Hi all,
>>>
>>> Getting this at the build of updated trunk.
>>>
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
>>> (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
>>>  Missing requirement: jaxb 2.1.7.wso2v1 (jaxb 2.1.7.wso2v1) requires
>>> 'package javax.activation 1.1.0' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
>>> (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
>>>   To: jaxb [2.1.7.wso2v1]
>>>
>>
>>
>> Hi All,
>>
>> We also noticed same error while building the AS profile.
>> Pradeep has already fixed that issue for AS (r132852).
>> Please use same fix for IS.
>>
>> Thanks
>> Ajith
>>
>>>
>>> Thanks
>>> AndunSLG
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94714631794
>>
>>
>>
>> ___
>> 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

Re: [Dev] IS Build Fails in Profile Generation

[Hasini Gunasinghe]

Hi,

We inherit those versions from platform/trunk/products/pom.xml.

Will fix that.

Thanks,
Hasini.

On Mon, Jul 16, 2012 at 2:57 PM, Ajith Vitharana  wrote:

>
>
> On Mon, Jul 16, 2012 at 2:19 PM, Andun Gunawardena  wrote:
>
>> Hi all,
>>
>> Getting this at the build of updated trunk.
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
>> (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
>>  Missing requirement: jaxb 2.1.7.wso2v1 (jaxb 2.1.7.wso2v1) requires
>> 'package javax.activation 1.1.0' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 IS - Utils Features 4.0.0.SNAPSHOT
>> (org.wso2.identity.utils.feature.group 4.0.0.SNAPSHOT)
>>   To: jaxb [2.1.7.wso2v1]
>>
>
>
> Hi All,
>
> We also noticed same error while building the AS profile.
> Pradeep has already fixed that issue for AS (r132852).
> Please use same fix for IS.
>
> Thanks
> Ajith
>
>>
>> Thanks
>> AndunSLG
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>
> ___
> 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

Re: [Dev] Invitation: User Management Code Review @ Fri Jul 13 1:30pm - 2:30pm (has...@wso2.com)

[Hasini Gunasinghe]

Hi,

Please find the notes from the code review below:
Participants: Miyuru, Asela, Dushan, Suresh, Hasini.
Reviewed components : ActiveDirectroyUserStoreManager and modified parts
of ReadOnlyLDAPUserStoreManager & ReadWriteLDAPUserStoreManager

Suggested improvements:
- Update the comments in the source code to adhere to new names
- Improve null check and empty string check
- Set default values if not configured
- Validate configuration parameter values if possible - such as ldap url
- Identify only the mandatory configuration parameters and halt server
startup if they are not provided in checkRequiredUserStoreConfigurations
method
- Give user account type as a configurable parameter - in
ActiveDirectoryUserStoreManager
- If user addition failed, send the relevant error code to UI along with
the custom error message
- Remove the user entry from AD if password modification step is failed in
addUser method.
- Format the code according to WSO2 code formatting.

Thanks,
Hasini.

On Thu, Jul 12, 2012 at 10:50 PM, Suresh Attanayaka  wrote:

> more details 
> »<https://www.google.com/calendar/event?action=VIEW&eid=cGhmZTIwbWUwcHRkaWdqYnVycDB1Zjl0MnMgaGFzaW5pQHdzbzIuY29t&tok=MTUjc3VyZXNoQHdzbzIuY29tY2RiMTIwOWUwZmM4NzI5NzE3NjZiNDRkMDRiY2Q4MTFhYzM5NGE0MQ&ctz=Asia/Colombo&hl=en>
> User Management Code Review
> *When*
> Fri Jul 13 1:30pm – 2:30pm Colombo
> *Where*
> 5th Floor , #58 (map<http://maps.google.lk/maps?q=5th+Floor+,+%2358&hl=en>
> )
> *Calendar*
> has...@wso2.com
> *Who*
> •
> Suresh Attanayaka - organizer
> •
> Asela Pathberiya
> •
> Prabath Siriwardana
> •
> Kasun Indrasiri
> •
> Thilina Buddhika
> •
> Johann Nallathamby
> •
> dev@wso2.org
> •
> Hasini Gunasinghe
>
> Going?   
> ***Yes<https://www.google.com/calendar/event?action=RESPOND&eid=cGhmZTIwbWUwcHRkaWdqYnVycDB1Zjl0MnMgaGFzaW5pQHdzbzIuY29t&rst=1&tok=MTUjc3VyZXNoQHdzbzIuY29tY2RiMTIwOWUwZmM4NzI5NzE3NjZiNDRkMDRiY2Q4MTFhYzM5NGE0MQ&ctz=Asia/Colombo&hl=en>-
> Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=cGhmZTIwbWUwcHRkaWdqYnVycDB1Zjl0MnMgaGFzaW5pQHdzbzIuY29t&rst=3&tok=MTUjc3VyZXNoQHdzbzIuY29tY2RiMTIwOWUwZmM4NzI5NzE3NjZiNDRkMDRiY2Q4MTFhYzM5NGE0MQ&ctz=Asia/Colombo&hl=en>-
> No<https://www.google.com/calendar/event?action=RESPOND&eid=cGhmZTIwbWUwcHRkaWdqYnVycDB1Zjl0MnMgaGFzaW5pQHdzbzIuY29t&rst=2&tok=MTUjc3VyZXNoQHdzbzIuY29tY2RiMTIwOWUwZmM4NzI5NzE3NjZiNDRkMDRiY2Q4MTFhYzM5NGE0MQ&ctz=Asia/Colombo&hl=en>
> ***more options 
> »<https://www.google.com/calendar/event?action=VIEW&eid=cGhmZTIwbWUwcHRkaWdqYnVycDB1Zjl0MnMgaGFzaW5pQHdzbzIuY29t&tok=MTUjc3VyZXNoQHdzbzIuY29tY2RiMTIwOWUwZmM4NzI5NzE3NjZiNDRkMDRiY2Q4MTFhYzM5NGE0MQ&ctz=Asia/Colombo&hl=en>
>
> Invitation from Google Calendar <https://www.google.com/calendar/>
>
> You are receiving this email at the account has...@wso2.com because you
> are subscribed for invitations on calendar has...@wso2.com.
>
> To stop receiving these notifications, please log in to
> https://www.google.com/calendar/ and change your notification settings
> for this calendar.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS identity-profile-gen is failing

[Hasini Gunasinghe]

Thanks Asela..

And sorry about the delay...
I was trying to take svn up under carbon/platform/trunk from yesterday
night and it has been failing multiple times due to the error : *svn:
REPORT of '/repos/wso2/!svn/vcc/default': Could not read response body:
Secure connection truncated (https://svn.wso2.org)*
It seems this svn issue has been reported several times earlier as well and
the solution proposed in those threads is to take svn up in small chunks..
If there is any better solution to avoid this, please let me know..

Thanks,
Hasini.

On Wed, Jul 11, 2012 at 11:53 AM, Thilina Buddhika wrote:

> Asela has the fixed this issue locally. Asela, please commit it.
>
> Thanks,
> Thilina
>
>
> On Wed, Jul 11, 2012 at 11:51 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> The same is failing in bamboo build [1]. Please fix this immediately, so
>> that we will have packs ready from next build onwards.
>>
>> Thanks,
>> Kishanthan.
>> [1]
>> http://wso2.org/bamboo/download/WSO2CARBON-PRODUCTS-JOB1/build_logs/WSO2CARBON-PRODUCTS-JOB1-293.log
>>
>>
>> On Tue, Jul 10, 2012 at 9:08 PM, Hasini Gunasinghe wrote:
>>
>>> Thanks for reporting.
>>> Will look into this.
>>>
>>> Thanks,
>>> Hasini.
>>>
>>> On Sun, Jul 8, 2012 at 5:56 PM, Andun Gunawardena wrote:
>>>
>>>> Hi all,
>>>>
>>>> I am getting this error in the IS identity-profile-gen,
>>>>
>>>> Cannot complete the install because one or more required items could
>>>> not be found.
>>>>  Software being installed: Identity XACML Feature 4.0.0.SNAPSHOT
>>>> (org.wso2.carbon.identity.xacml.feature.group 4.0.0.SNAPSHOT)
>>>>  Missing requirement: org.wso2.carbon.identity.thrift.authentication
>>>> 4.0.0.SNAPSHOT (org.wso2.carbon.identity.thrift.authentication
>>>> 4.0.0.SNAPSHOT) requires 'package org.slf4j 0.0.0' but it could not be 
>>>> found
>>>>  Cannot satisfy dependency:
>>>>   From: Identity XACML Feature 4.0.0.SNAPSHOT
>>>> (org.wso2.carbon.identity.xacml.feature.group 4.0.0.SNAPSHOT)
>>>>   To: org.wso2.carbon.identity.xacml.server.feature.group
>>>> [4.0.0.SNAPSHOT]
>>>>  Cannot satisfy dependency:
>>>>   From: Identity XACML Server Feature 4.0.0.SNAPSHOT
>>>> (org.wso2.carbon.identity.xacml.server.feature.group 4.0.0.SNAPSHOT)
>>>>   To: org.wso2.carbon.identity.thrift.authentication [4.0.0.SNAPSHOT]
>>>>
>>>> Please look in to this.
>>>>
>>>> Thanks
>>>> AndunSLG
>>>>
>>>> ___
>>>> 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
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Thilina Buddhika
> Associate Technical Lead
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 77 44 88 727
> blog : http://blog.thilinamb.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev