date:20141217

Re: [Dev] Waiting for required OSGiAxis2Service: While Creating Carbon Component

2014-12-17 Thread Ananthaneshan Elampooran

Hi,

Exact problem is, some JDK packages like sun.misc.* are not bundled in all
VMs. so we need to explicitly export JDK related packages in pom file using
'properties' tag.

>
> sun.misc.*
> 
> 


*E. Ananthaneshan*
Associate Software Engineer
WSO2, Inc: http://wso2.com
Mob: +94 712307125


On Mon, Dec 15, 2014 at 11:54 AM, Ananthaneshan Elampooran <
ananthanes...@wso2.com> wrote:
>
> added this element into 'maven-bundle-plugin's instructions' element to
> import dependencies.
>
>> *;resolution:=optional
>
>
> Solved this issue. Thank you Godwin
>
>
> *E. Ananthaneshan*
> Associate Software Engineer
> WSO2, Inc: http://wso2.com
> Mob: +94 712307125
>
>
> On Mon, Dec 15, 2014 at 11:04 AM, Ananthaneshan Elampooran <
> ananthanes...@wso2.com> wrote:
>>
>> Hi Team,
>>
>> I am creating a carbon back-end service component. I wrote the service
>> class and the 'services.xml' file. to make this as a OSGI bundle, I have
>> added following 'maven-bundle-plugin' configuration.
>>
>> 
>>> 
>>> 
>>> org.apache.felix
>>> maven-bundle-plugin
>>> true
>>> 
>>> 
>>>
>>> org.wso2.carbon.identity.fido.u2f
>>>
>>> org.wso2.carbon.identity.fido.u2f
>>>
>>> org.wso2.carbon.identity.fido.u2f
>>> *
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>
>>
>> I moved this jar to 'drop in' folder and started the server. I get this
>> message repeatedly.
>>
>> [2014-12-15 10:58:46,242]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
>>> delayed due to the following unsatisfied items:
>>> [2014-12-15 10:58:46,242]  WARN
>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>> OSGiAxis2Service: org.wso2.carbon.identity.fido.u2f-4.2.0
>>
>>
>> I tried adding all dependencies to 'lib' folder as well.
>>
>> How can I overcome this problem.
>>
>>
>>
>> Thanks and regards,
>> *E. Ananthaneshan*
>> Associate Software Engineer
>> WSO2, Inc: http://wso2.com
>> Mob: +94 712307125
>>
>>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 1.8.0 Released !

2014-12-17 Thread Vijayaratha Vijayasingam

The WSO2 API Manager 1.8.0 Released!

The WSO2 API Manager team is pleased to announce the release of version
1.8.0 of the Open Source API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API management challenges such as API provisioning, API governance, API
security and API monitoring. It combines some of the most powerful and
mature components of the WSO2's state-of-the-art Carbon platform to deliver
a smooth and end-to-end API management experience while catering to both
API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

   - *API Provider:* Define new APIs and manage them
   - *API Store:* Browse published APIs and subscribe to them
   - *API Gateway:* The underlying API runtime based on WSO2 ESB
   - *API Key Manager:* Performs Key Generation and Key Validation
   functionalities

WSO2 API Manager is developed on top of the revolutionary WSO2 Carbon
platform  (Middleware a' la carte), an
OSGi based framework that provides seamless modularity to your SOA via
componentization. This release also contains many new features and a range
of optional components (add-ons) that can be installed to customize the
behavior of the API Manager. Further, any existing features of the product
which are not required in your environment can be easily removed using the
underlying provisioning framework of Carbon. In brief, WSO2 API Manager can
be fully customized and tailored to meet your exact API management needs.

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also take a look at the online
product 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. Launch a web browser and navigate to https://localhost:9443/publisher to
   access the API provider webapp
   5. Navigate to https://localhost:9443/store to access the API store
   6. Navigate to https://localhost:9443/admin-dashboard to access Admin
   dashboard
   7. Use "admin", "admin" as the username and password to login as an admin

Improvements in 1.8.0

   - [APIMANAGER-637 ] -
   Provide means to search APIs 'starting with' / 'ending with' certain
   patterns
   - [APIMANAGER-702 ] - Time
   of subscription is not saved
   - [APIMANAGER-1347 ] -
   Published APIs shouldn't show details of proxied web services
   - [APIMANAGER-1368 ] - API
   Manager Publisher WSDL for API should change end point to gateway
   - [APIMANAGER-2142 ] -
   Better to have option to save the wsdl in registry or keep it as url
   - [APIMANAGER-2158 ] -
   Logging error when Single Logout is disabled
   - [APIMANAGER-2552 ] -
   Inactive tenants can still access resources exposed through NIO transport
   - [APIMANAGER-2557 ] -
   Configure Audit Log in log4j.properties
   - [APIMANAGER-2565 ] -
   Application is allowed to Delete when it is already in the Workflow
   Approval Process.
   - [APIMANAGER-2570 ] -
   Publisher's update API page's error Messages should be informative
   - [APIMANAGER-2593 ] -
   According to the making API changes, Existing WSDL docs on registry should
   be updated
   - [APIMANAGER-2635 ] -
   Case insensitive username comparison for APIM
   - [APIMANAGER-2650 ] - The
   publisher URL/API Console does not work out of the box if you set a port
   offset
   - [APIMANAGER-2652 ] -
   RestPeopleTestCase fails
   - [APIMANAGER-2694 ] -
   Make recently added API loading asynchronous
   - [APIMANAGER-2711 ] -
   Make JWTGenerator Extensible
   - [APIMANAGER-2755 ] -
   Migration tool to modify apis to migrate from 1.6 to 1.7
   - [APIMANAGER-2785 ] -
   Provide support for self signup for tenants' APIStores
   - [APIMANAGER-2788 ] -
   HTTP, HTTPS url redirection for login call in publisher
   - [APIMANAGER-2790 ] -
   Improvements for pr

[Dev] Configuring Local Authenticators on IS

2014-12-17 Thread Ananthaneshan Elampooran

Hi Team,

I tried to configure a new authenticator on IS Management Console, I could
not see the authenticator under Service Provider's "Local & Outbound
Authentication Configuration" to enable, only Basic and IWA is displayed.

I wrote a "Local Authenticator", it can be configured for second factor
authentication. The back-end service and authenticator components are
deployed in "dropins". The components are resolved and running.

The authenticator extends AbstractApplicationAuthenticator and
implements LocalApplicationAuthenticator as well. Do I need to make any
configuration changes to enable it in UI.

Thanks in advance,

*E. Ananthaneshan*
Associate Software Engineer
WSO2, Inc: http://wso2.com
Mob: +94 712307125
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot install Key Manager feature from the given repo.

2014-12-17 Thread Udara Liyanage

Hi,

To what product you are trying to install keys manager feature. Seems some
dependency features are already installed.



Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 17, 2014 12:20 PM, "Ayesha Dissanayaka"  wrote:

> Hi,
>
> When, I am trying to install key manager feature(APIM 1.7) from
> http://dist.wso2.org/p2/carbon/releases/turing/ [01] I am getting
> following error.
>
> "Your original install request has been modified.
> org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it
> is already installed.
> org.wso2.carbon.security.mgt.server.feature.group-4.2.5 will be ignored
> because a newer version is already installed.
> org.wso2.carbon.identity.oauth.common.feature.group-4.2.3 is already
> present because other installed software requires it. It will be added to
> the installed software list.
> org.wso2.carbon.identity.application.authentication.framework.server.feature.group-4.2.2
> is already installed, so an update will be performed instead.
> org.wso2.carbon.identity.self.registration.server.feature.group-4.2.2 will
> be ignored because it is already installed.
> org.wso2.carbon.webapp.mgt.server.feature.group-4.2.2 will be ignored
> because a newer version is already installed.
> org.wso2.carbon.idp.mgt.feature.group-4.2.3 is already installed, so an
> update will be performed instead.
> org.wso2.carbon.event.common.feature.group-4.2.0 is already present because
> other installed software requires it. It will be added to the installed
> software list. org.wso2.carbon.registry.contentsearch.feature.group-4.2.1
> is already installed, so an update will be performed instead. Cannot
> complete the install because of a conflicting dependency. Software being
> installed: Trusted Identity Provider Management Feature 4.2.4
> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) Software currently installed:
> WSO2 Stratos - Common Composite Feature 2.2.2
> (org.wso2.carbon.stratos.common.feature.group 2.2.2) Only one of the
> following can be installed at once: WSO2 Stratos - Common Core Feature
> 2.2.0 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.0) WSO2
> Stratos - Common Core Feature 2.3.0
> (org.wso2.carbon.stratos.common.server.feature.jar 2.3.0) WSO2 Stratos -
> Common Core Feature 2.2.1
> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.1) WSO2 Stratos -
> Common Core Feature 2.2.2
> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.2) Cannot satisfy
> dependency: From: Trusted Identity Provider Management Feature 4.2.4
> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) To:
> org.wso2.carbon.idp.mgt.server.feature.group [4.2.4] Cannot satisfy
> dependency: From: Identity Provider Management Server Feature 4.2.4
> (org.wso2.carbon.idp.mgt.server.feature.group 4.2.4) To:
> org.wso2.carbon.stratos.common.server.feature.group [2.3.0,2.4.0) Cannot
> satisfy dependency: From: WSO2 Stratos - Common Composite Feature 2.2.2
> (org.wso2.carbon.stratos.common.feature.group 2.2.2) To:
> org.wso2.carbon.stratos.common.server.feature.group [2.2.2] Cannot satisfy
> dependency: From: WSO2 Stratos - Common Core Feature 2.2.2
> (org.wso2.carbon.stratos.common.server.feature.group 2.2.2) To:
> org.wso2.carbon.stratos.common.server.feature.jar [2.2.2] Cannot satisfy
> dependency: From: WSO2 Stratos - Common Core Feature 2.3.0
> (org.wso2.carbon.stratos.common.server.feature.group 2.3.0) To:
> org.wso2.carbon.stratos.common.server.feature.jar [2.3.0]"
>
> [01]
> https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager
>
> Please have a look, and suggest a solution.
>
> Thanks!
> - Ayesha
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot install Key Manager feature from the given repo.

2014-12-17 Thread Ayesha Dissanayaka

To IS-5.0.0 fresh pack.

On Wed, Dec 17, 2014 at 2:43 PM, Udara Liyanage  wrote:
>
> Hi,
>
> To what product you are trying to install keys manager feature. Seems some
> dependency features are already installed.
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Dec 17, 2014 12:20 PM, "Ayesha Dissanayaka"  wrote:
>
>> Hi,
>>
>> When, I am trying to install key manager feature(APIM 1.7) from
>> http://dist.wso2.org/p2/carbon/releases/turing/ [01] I am getting
>> following error.
>>
>> "Your original install request has been modified.
>> org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it
>> is already installed.
>> org.wso2.carbon.security.mgt.server.feature.group-4.2.5 will be ignored
>> because a newer version is already installed.
>> org.wso2.carbon.identity.oauth.common.feature.group-4.2.3 is already
>> present because other installed software requires it. It will be added to
>> the installed software list.
>> org.wso2.carbon.identity.application.authentication.framework.server.feature.group-4.2.2
>> is already installed, so an update will be performed instead.
>> org.wso2.carbon.identity.self.registration.server.feature.group-4.2.2 will
>> be ignored because it is already installed.
>> org.wso2.carbon.webapp.mgt.server.feature.group-4.2.2 will be ignored
>> because a newer version is already installed.
>> org.wso2.carbon.idp.mgt.feature.group-4.2.3 is already installed, so an
>> update will be performed instead.
>> org.wso2.carbon.event.common.feature.group-4.2.0 is already present because
>> other installed software requires it. It will be added to the installed
>> software list. org.wso2.carbon.registry.contentsearch.feature.group-4.2.1
>> is already installed, so an update will be performed instead. Cannot
>> complete the install because of a conflicting dependency. Software being
>> installed: Trusted Identity Provider Management Feature 4.2.4
>> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) Software currently installed:
>> WSO2 Stratos - Common Composite Feature 2.2.2
>> (org.wso2.carbon.stratos.common.feature.group 2.2.2) Only one of the
>> following can be installed at once: WSO2 Stratos - Common Core Feature
>> 2.2.0 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.0) WSO2
>> Stratos - Common Core Feature 2.3.0
>> (org.wso2.carbon.stratos.common.server.feature.jar 2.3.0) WSO2 Stratos -
>> Common Core Feature 2.2.1
>> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.1) WSO2 Stratos -
>> Common Core Feature 2.2.2
>> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.2) Cannot satisfy
>> dependency: From: Trusted Identity Provider Management Feature 4.2.4
>> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) To:
>> org.wso2.carbon.idp.mgt.server.feature.group [4.2.4] Cannot satisfy
>> dependency: From: Identity Provider Management Server Feature 4.2.4
>> (org.wso2.carbon.idp.mgt.server.feature.group 4.2.4) To:
>> org.wso2.carbon.stratos.common.server.feature.group [2.3.0,2.4.0) Cannot
>> satisfy dependency: From: WSO2 Stratos - Common Composite Feature 2.2.2
>> (org.wso2.carbon.stratos.common.feature.group 2.2.2) To:
>> org.wso2.carbon.stratos.common.server.feature.group [2.2.2] Cannot satisfy
>> dependency: From: WSO2 Stratos - Common Core Feature 2.2.2
>> (org.wso2.carbon.stratos.common.server.feature.group 2.2.2) To:
>> org.wso2.carbon.stratos.common.server.feature.jar [2.2.2] Cannot satisfy
>> dependency: From: WSO2 Stratos - Common Core Feature 2.3.0
>> (org.wso2.carbon.stratos.common.server.feature.group 2.3.0) To:
>> org.wso2.carbon.stratos.common.server.feature.jar [2.3.0]"
>>
>> [01]
>> https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager
>>
>> Please have a look, and suggest a solution.
>>
>> Thanks!
>> - Ayesha
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>

-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot install Key Manager feature from the given repo.

2014-12-17 Thread Udara Liyanage

Hi,

Key manager feature uses some IS features such as oAuth which are already
present at IS. That may be the reason why it says some features are already
present.
May be you can try in installing existing duplicate features.



Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 17, 2014 2:50 PM, "Ayesha Dissanayaka"  wrote:

> To IS-5.0.0 fresh pack.
>
> On Wed, Dec 17, 2014 at 2:43 PM, Udara Liyanage  wrote:
>>
>> Hi,
>>
>> To what product you are trying to install keys manager feature. Seems
>> some dependency features are already installed.
>>
>>
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>> On Dec 17, 2014 12:20 PM, "Ayesha Dissanayaka"  wrote:
>>
>>> Hi,
>>>
>>> When, I am trying to install key manager feature(APIM 1.7) from
>>> http://dist.wso2.org/p2/carbon/releases/turing/ [01] I am getting
>>> following error.
>>>
>>> "Your original install request has been modified.
>>> org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it
>>> is already installed.
>>> org.wso2.carbon.security.mgt.server.feature.group-4.2.5 will be ignored
>>> because a newer version is already installed.
>>> org.wso2.carbon.identity.oauth.common.feature.group-4.2.3 is already
>>> present because other installed software requires it. It will be added to
>>> the installed software list.
>>> org.wso2.carbon.identity.application.authentication.framework.server.feature.group-4.2.2
>>> is already installed, so an update will be performed instead.
>>> org.wso2.carbon.identity.self.registration.server.feature.group-4.2.2 will
>>> be ignored because it is already installed.
>>> org.wso2.carbon.webapp.mgt.server.feature.group-4.2.2 will be ignored
>>> because a newer version is already installed.
>>> org.wso2.carbon.idp.mgt.feature.group-4.2.3 is already installed, so an
>>> update will be performed instead.
>>> org.wso2.carbon.event.common.feature.group-4.2.0 is already present because
>>> other installed software requires it. It will be added to the installed
>>> software list. org.wso2.carbon.registry.contentsearch.feature.group-4.2.1
>>> is already installed, so an update will be performed instead. Cannot
>>> complete the install because of a conflicting dependency. Software being
>>> installed: Trusted Identity Provider Management Feature 4.2.4
>>> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) Software currently installed:
>>> WSO2 Stratos - Common Composite Feature 2.2.2
>>> (org.wso2.carbon.stratos.common.feature.group 2.2.2) Only one of the
>>> following can be installed at once: WSO2 Stratos - Common Core Feature
>>> 2.2.0 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.0) WSO2
>>> Stratos - Common Core Feature 2.3.0
>>> (org.wso2.carbon.stratos.common.server.feature.jar 2.3.0) WSO2 Stratos -
>>> Common Core Feature 2.2.1
>>> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.1) WSO2 Stratos -
>>> Common Core Feature 2.2.2
>>> (org.wso2.carbon.stratos.common.server.feature.jar 2.2.2) Cannot satisfy
>>> dependency: From: Trusted Identity Provider Management Feature 4.2.4
>>> (org.wso2.carbon.idp.mgt.feature.group 4.2.4) To:
>>> org.wso2.carbon.idp.mgt.server.feature.group [4.2.4] Cannot satisfy
>>> dependency: From: Identity Provider Management Server Feature 4.2.4
>>> (org.wso2.carbon.idp.mgt.server.feature.group 4.2.4) To:
>>> org.wso2.carbon.stratos.common.server.feature.group [2.3.0,2.4.0) Cannot
>>> satisfy dependency: From: WSO2 Stratos - Common Composite Feature 2.2.2
>>> (org.wso2.carbon.stratos.common.feature.group 2.2.2) To:
>>> org.wso2.carbon.stratos.common.server.feature.group [2.2.2] Cannot satisfy
>>> dependency: From: WSO2 Stratos - Common Core Feature 2.2.2
>>> (org.wso2.carbon.stratos.common.server.feature.group 2.2.2) To:
>>> org.wso2.carbon.stratos.common.server.feature.jar [2.2.2] Cannot satisfy
>>> dependency: From: WSO2 Stratos - Common Core Feature 2.3.0
>>> (org.wso2.carbon.stratos.common.server.feature.group 2.3.0) To:
>>> org.wso2.carbon.stratos.common.server.feature.jar [2.3.0]"
>>>
>>> [01]
>>> https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager
>>>
>>> Please have a look, and suggest a solution.
>>>
>>> Thanks!
>>> - Ayesha
>>> --
>>> *Ayesha Dissanayaka*
>>> Software Engineer,
>>> WSO2, Inc : http://wso2.com
>>> 
>>> 20, Palmgrove Avenue, Colombo 3
>>> E-Mail: aye...@wso2.com 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listi

[Dev] Does it required to enable sticky sessions in a Identity Server 5.0 cluster?

2014-12-17 Thread Darshana Gunawardana

Hi folks,

What is our stand for $subject?

AFAIK, the new authentication framework doesn't depends on the tomcat
session, so it doesn't required to have sticky session enable in the load
balancer. (May be OpenID have a exception)

But for management console operations, its required enable sticky sessions..

What are the other concerns, if we disable sticky sessions in the load
balancer?

Thanks,
Darshana
-- 
Regards,


*Darshana Gunawardana*Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot install Key Manager feature from the given repo.

2014-12-17 Thread Nuwan Wimalasekara

Hi
This was working fine some time back and now it is not possible to install
Key Manager(AM 1.7.0) feature on IS 5.0.0 from the repo[1]. P2 repo has
been updated recently with the new releases. May be This issue come from
with the updation. This is a critical issue in the p2 repo and we need to
fix this soon.

[1] http://dist.wso2.org/p2/carbon/releases/turing/

Thanks,
Nuwanw

On Wed, Dec 17, 2014 at 3:00 PM, Udara Liyanage  wrote:
>
> Hi,
>
> Key manager feature uses some IS features such as oAuth which are already
> present at IS. That may be the reason why it says some features are already
> present.
> May be you can try in installing existing duplicate features.
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Dec 17, 2014 2:50 PM, "Ayesha Dissanayaka"  wrote:
>
>> To IS-5.0.0 fresh pack.
>>
>> On Wed, Dec 17, 2014 at 2:43 PM, Udara Liyanage  wrote:
>>>
>>> Hi,
>>>
>>> To what product you are trying to install keys manager feature. Seems
>>> some dependency features are already installed.
>>>
>>>
>>>
>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>> On Dec 17, 2014 12:20 PM, "Ayesha Dissanayaka"  wrote:
>>>
 Hi,

 When, I am trying to install key manager feature(APIM 1.7) from
 http://dist.wso2.org/p2/carbon/releases/turing/ [01] I am getting
 following error.

 "Your original install request has been modified.
 org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it
 is already installed.
 org.wso2.carbon.security.mgt.server.feature.group-4.2.5 will be ignored
 because a newer version is already installed.
 org.wso2.carbon.identity.oauth.common.feature.group-4.2.3 is already
 present because other installed software requires it. It will be added to
 the installed software list.
 org.wso2.carbon.identity.application.authentication.framework.server.feature.group-4.2.2
 is already installed, so an update will be performed instead.
 org.wso2.carbon.identity.self.registration.server.feature.group-4.2.2 will
 be ignored because it is already installed.
 org.wso2.carbon.webapp.mgt.server.feature.group-4.2.2 will be ignored
 because a newer version is already installed.
 org.wso2.carbon.idp.mgt.feature.group-4.2.3 is already installed, so an
 update will be performed instead.
 org.wso2.carbon.event.common.feature.group-4.2.0 is already present because
 other installed software requires it. It will be added to the installed
 software list. org.wso2.carbon.registry.contentsearch.feature.group-4.2.1
 is already installed, so an update will be performed instead. Cannot
 complete the install because of a conflicting dependency. Software being
 installed: Trusted Identity Provider Management Feature 4.2.4
 (org.wso2.carbon.idp.mgt.feature.group 4.2.4) Software currently installed:
 WSO2 Stratos - Common Composite Feature 2.2.2
 (org.wso2.carbon.stratos.common.feature.group 2.2.2) Only one of the
 following can be installed at once: WSO2 Stratos - Common Core Feature
 2.2.0 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.0) WSO2
 Stratos - Common Core Feature 2.3.0
 (org.wso2.carbon.stratos.common.server.feature.jar 2.3.0) WSO2 Stratos -
 Common Core Feature 2.2.1
 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.1) WSO2 Stratos -
 Common Core Feature 2.2.2
 (org.wso2.carbon.stratos.common.server.feature.jar 2.2.2) Cannot satisfy
 dependency: From: Trusted Identity Provider Management Feature 4.2.4
 (org.wso2.carbon.idp.mgt.feature.group 4.2.4) To:
 org.wso2.carbon.idp.mgt.server.feature.group [4.2.4] Cannot satisfy
 dependency: From: Identity Provider Management Server Feature 4.2.4
 (org.wso2.carbon.idp.mgt.server.feature.group 4.2.4) To:
 org.wso2.carbon.stratos.common.server.feature.group [2.3.0,2.4.0) Cannot
 satisfy dependency: From: WSO2 Stratos - Common Composite Feature 2.2.2
 (org.wso2.carbon.stratos.common.feature.group 2.2.2) To:
 org.wso2.carbon.stratos.common.server.feature.group [2.2.2] Cannot satisfy
 dependency: From: WSO2 Stratos - Common Core Feature 2.2.2
 (org.wso2.carbon.stratos.common.server.feature.group 2.2.2) To:
 org.wso2.carbon.stratos.common.server.feature.jar [2.2.2] Cannot satisfy
 dependency: From: WSO2 Stratos - Common Core Feature 2.3.0
 (org.wso2.carbon.stratos.common.server.feature.group 2.3.0) To:
 org.wso2.carbon.stratos.common.server.feature.jar [2.3.0]"

 [01]
 https://docs.wso2.com/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager

 Please have a look, and suggest a solution.

 Thanks!
 - Ayesha
 --
 *Ayesha Dissanayaka*
 Software Engineer,
 WSO2, Inc : http://wso2.com

 20, Palmgrove Avenue, Colombo 3
>>>

Re: [Dev] Does it required to enable sticky sessions in a Identity Server 5.0 cluster?

2014-12-17 Thread Asela Pathberiya

On Wed, Dec 17, 2014 at 3:09 PM, Darshana Gunawardana  wrote:
> Hi folks,
>
> What is our stand for $subject?
>
> AFAIK, the new authentication framework doesn't depends on the tomcat
> session, so it doesn't required to have sticky session enable in the load
> balancer. (May be OpenID have a exception)
>
> But for management console operations, its required enable sticky sessions..
>
> What are the other concerns, if we disable sticky sessions in the load
> balancer?

I guess,  Framework is working without sticky session as it replicates
all states data...   Sometime,  OpenId may maintains some state in
session...  we could avoid it using caching as well...?

Yes.. I think, sticky session is required when accessing console and
admin services (can you basic auth as well)  using LB.

Thanks,
Aseka

>
> Thanks,
> Darshana
> --
> Regards,
>
> Darshana Gunawardana
> Software Engineer
> WSO2 Inc.; http://wso2.com
> E-mail: darsh...@wso2.com
> Mobile: +94718566859
> Lean . Enterprise . Middleware



-- 
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933
 +358 449 228 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Does it required to enable sticky sessions in a Identity Server 5.0 cluster?

2014-12-17 Thread Johann Nallathamby

We've found that some of the cache operations like update and delete take
time to replicate. They eventually become consistent. Based on network
traffic and other parameters the time it takes to become consistent could
vary. Therefore it is recommended that sticky sessions are enabled.

On Wed, Dec 17, 2014 at 3:09 PM, Darshana Gunawardana 
wrote:
>
> Hi folks,
>
> What is our stand for $subject?
>
> AFAIK, the new authentication framework doesn't depends on the tomcat
> session, so it doesn't required to have sticky session enable in the load
> balancer. (May be OpenID have a exception)
>
> But for management console operations, its required enable sticky
> sessions..
>
> What are the other concerns, if we disable sticky sessions in the load
> balancer?
>
> Thanks,
> Darshana
> --
> Regards,
>
>
> *Darshana Gunawardana*Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>

-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Associate Technical Lead & Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] decompression error SVN IS checkout

2014-12-17 Thread Rajeev Sampath

On Wed, Dec 17, 2014 at 12:04 PM, Chamin Nalinda  wrote:
>
> Hi all,
>
> I got the following decompression error[1] after doing a svn checkout for
> WSO2 IS from[2]. Does any one know how to resolve this and the reason
> behind this ?
>
> [1] svn: E120104: ra_serf: An error occurred during decompression
>


Seems to be a problem with the svn client version. Try with a different
version.

http://stackoverflow.com/questions/21548042/cannot-svn-update-an-error-occurred-during-decompression


Thanks
Rajeev



> [2] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk11/
>
> Thanks in advance.
>
>
> --
> *Chamin Nalinda*
>
> Intern - Engineering
> WSO2 Inc. http://www.wso2.com
> lean.enterprise.middleware
>
> Mobile: (+94) 77 241 66 04
> Linkedin: https://www.linkedin.com/in/chaminnalinda
> Web: http://www.ckreativity.com
> Blog: http://techspiro.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Rajeev Sampath
Senior Software Engineer
WSO2, Inc.; http://www.wso2.com.

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

Re: [Dev] Tenant element to be included in the carbon.xml

2014-12-17 Thread Isuru Perera

With the new change, does it make sense to use "" as the element
name? I think it should be "Tenants" "TenantDomains".

On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:
>
> Modified config to use LDAP filter syntax
>
> 
> 
> 
> 
> 30
> 
> 
> *,!foo.com,!bar.com
> 
> 
> 
>
> On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez  wrote:
>>
>> 
>> 
>> 
>> 
>> 
>> 30
>> 
>> 
>> 
>> *
>> 
>> 
>> wso2.com
>> ibm.com
>> 
>> 
>> 
>> 
>>
>>
>> --
>> *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 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **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/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>
>

-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

[Dev] IS build error

2014-12-17 Thread Chamin Nalinda

Hi All,

I was doing a build on IS build according to the documentation[1]. I did
build all the patches before build the product. But after running maven
build command, I got build failure.

Error occurred:

[ERROR] Failed to execute goal on project org.wso2.identity.utils.feature:
Could not resolve dependencies for project
org.wso2.identity:org.wso2.identity.utils.feature:pom:5.0.0: Failed to
collect dependencies for [org.apache.derby.wso2:derby:jar:10.3.2.1wso2v1
(compile), org.hibernate.wso2:hibernate:jar:3.2.5.ga-wso2v1 (compile),
org.apache.bcel.wso2:bcel:jar:5.2.0.wso2v1 (compile),
asm.wso2:asm:jar:1.5.3.wso2v1 (compile), cglib.wso2:cglib:jar:2.2.wso2v1
(compile), org.apache.axis2.wso2:axis2-jibx:jar:1.6.1.wso2v1 (compile),
org.jibx.wso2:jibx:jar:1.2.1.wso2v1 (compile),
org.apache.axis2.wso2:axis2-jaxbri:jar:1.6.1.wso2v1 (compile),
com.sun.xml.bind.wso2:jaxb:jar:2.2.5.wso2v1 (compile),
bouncycastle:bcprov-jdk15:jar:132 (compile)]: Failed to read artifact
descriptor for org.apache.axis2.wso2:axis2-jibx:jar:1.6.1.wso2v1: Could not
find artifact org.wso2.carbon:carbon-parent:pom:4.0.0-SNAPSHOT in
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[Help 1]


Can someone suggest how to resolve this issue ? Thanks.

[1] https://docs.wso2.com/display/IS500/Building+from+Source


-- 
*Chamin Nalinda*

Intern - Engineering
WSO2 Inc. http://www.wso2.com
lean.enterprise.middleware

Mobile: (+94) 77 241 66 04
Linkedin: https://www.linkedin.com/in/chaminnalinda
Web: http://www.ckreativity.com
Blog: http://techspiro.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tenant element to be included in the carbon.xml

2014-12-17 Thread Afkham Azeez

Tenants is already implied.

On Wed, Dec 17, 2014 at 6:02 PM, Isuru Perera  wrote:
>
> With the new change, does it make sense to use "" as the element
> name? I think it should be "Tenants" "TenantDomains".
>
> On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:
>
>> Modified config to use LDAP filter syntax
>>
>> 
>> 
>> 
>> 
>> 30
>> 
>> 
>> *,!foo.com,!bar.com
>> 
>> 
>> 
>>
>> On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez  wrote:
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 30
>>> 
>>> 
>>> 
>>> *
>>> 
>>> 
>>> wso2.com
>>> ibm.com
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> --
>>> *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 <%2B94%2077%203320919>blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: **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/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>>
>>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>


-- 
*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 3320919blog: **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] Tenant element to be included in the carbon.xml

2014-12-17 Thread Isuru Perera

What I meant was, in the  we also specify the tenants to be
excluded from eager loading. So,  element might not make sense.
Anyway, I'm okay if you think that  is more suitable for the
config element.

Thanks!

On Wed, Dec 17, 2014 at 6:08 PM, Afkham Azeez  wrote:
>
> Tenants is already implied.
>
> On Wed, Dec 17, 2014 at 6:02 PM, Isuru Perera  wrote:
>>
>> With the new change, does it make sense to use "" as the element
>> name? I think it should be "Tenants" "TenantDomains".
>>
>> On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:
>>
>>> Modified config to use LDAP filter syntax
>>>
>>> 
>>> 
>>> 
>>> 
>>> 30
>>> 
>>> 
>>> *,!foo.com,!bar.com
>>> 
>>> 
>>> 
>>>
>>> On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez  wrote:

 
 
 
 
 
 30
 
 
 
 *
 
 
 wso2.com
 ibm.com
 
 
 
 


 --
 *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 <%2B94%2077%203320919>blog: *
 *http://blog.afkham.org* 
 *twitter: **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/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>>>
>>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
> --
> *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 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>


-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

Re: [Dev] Tenant element to be included in the carbon.xml

2014-12-17 Thread Afkham Azeez

Include - !foo.com = Exclude foo.com

On Wed, Dec 17, 2014 at 6:14 PM, Isuru Perera  wrote:
>
> What I meant was, in the  we also specify the tenants to be
> excluded from eager loading. So,  element might not make sense.
> Anyway, I'm okay if you think that  is more suitable for the
> config element.
>
> Thanks!
>
> On Wed, Dec 17, 2014 at 6:08 PM, Afkham Azeez  wrote:
>>
>> Tenants is already implied.
>>
>> On Wed, Dec 17, 2014 at 6:02 PM, Isuru Perera  wrote:
>>>
>>> With the new change, does it make sense to use "" as the
>>> element name? I think it should be "Tenants" "TenantDomains".
>>>
>>> On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:
>>>
 Modified config to use LDAP filter syntax

 
 
 
 
 30
 
 
 *,!foo.com,!bar.com
 
 
 

 On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez  wrote:
>
> 
> 
> 
> 
> 
> 30
> 
> 
> 
> *
> 
> 
> wso2.com
> ibm.com
> 
> 
> 
> 
>
>
> --
> *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 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **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/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919>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


>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>> --
>> *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 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>


-- 
*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 3320919blog: **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] Tenant element to be included in the carbon.xml

2014-12-17 Thread Isuru Perera

Yes. I understood. :) I was not thinking in that way. Thanks!

On Wed, Dec 17, 2014 at 6:17 PM, Afkham Azeez  wrote:
>
> Include - !foo.com = Exclude foo.com
>
> On Wed, Dec 17, 2014 at 6:14 PM, Isuru Perera  wrote:
>>
>> What I meant was, in the  we also specify the tenants to be
>> excluded from eager loading. So,  element might not make sense.
>> Anyway, I'm okay if you think that  is more suitable for the
>> config element.
>>
>> Thanks!
>>
>> On Wed, Dec 17, 2014 at 6:08 PM, Afkham Azeez  wrote:
>>>
>>> Tenants is already implied.
>>>
>>> On Wed, Dec 17, 2014 at 6:02 PM, Isuru Perera  wrote:

 With the new change, does it make sense to use "" as the
 element name? I think it should be "Tenants" "TenantDomains".

 On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:

> Modified config to use LDAP filter syntax
>
> 
> 
> 
> 
> 30
> 
> 
> *,!foo.com,!bar.com
> 
> 
> 
>
> On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez  wrote:
>>
>> 
>> 
>> 
>> 
>> 
>> 30
>> 
>> 
>> 
>> *
>> 
>> 
>> wso2.com
>> ibm.com
>> 
>> 
>> 
>> 
>>
>>
>> --
>> *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 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **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/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>
>

 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha

>>>
>>>
>>> --
>>> *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 <%2B94%2077%203320919>blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: **http://twitter.com/afkham_azeez*
>>> 
>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
> --
> *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 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>


-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

Re: [Dev] Tenant element to be included in the carbon.xml

2014-12-17 Thread Afkham Azeez

Nothing fancy here. Using LDAP filter syntax. Used in the Maven bundle
plugin package export/imports section as well.

On Wed, Dec 17, 2014 at 6:23 PM, Isuru Perera  wrote:
>
> Yes. I understood. :) I was not thinking in that way. Thanks!
>
> On Wed, Dec 17, 2014 at 6:17 PM, Afkham Azeez  wrote:
>>
>> Include - !foo.com = Exclude foo.com
>>
>> On Wed, Dec 17, 2014 at 6:14 PM, Isuru Perera  wrote:
>>>
>>> What I meant was, in the  we also specify the tenants to be
>>> excluded from eager loading. So,  element might not make sense.
>>> Anyway, I'm okay if you think that  is more suitable for the
>>> config element.
>>>
>>> Thanks!
>>>
>>> On Wed, Dec 17, 2014 at 6:08 PM, Afkham Azeez  wrote:

 Tenants is already implied.

 On Wed, Dec 17, 2014 at 6:02 PM, Isuru Perera  wrote:
>
> With the new change, does it make sense to use "" as the
> element name? I think it should be "Tenants" "TenantDomains".
>
> On Tue, Dec 16, 2014 at 1:01 PM, Afkham Azeez  wrote:
>
>> Modified config to use LDAP filter syntax
>>
>> 
>> 
>> 
>> 
>> 30
>> 
>> 
>> *,!foo.com,!bar.com
>> 
>> 
>> 
>>
>> On Tue, Dec 16, 2014 at 12:27 PM, Afkham Azeez 
>> wrote:
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 30
>>> 
>>> 
>>> 
>>> *
>>> 
>>> 
>>> wso2.com
>>> ibm.com
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> --
>>> *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 <%2B94%2077%203320919>blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: **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/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>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
>>
>>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>


 --
 *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 <%2B94%2077%203320919>blog: *
 *http://blog.afkham.org* 
 *twitter: **http://twitter.com/afkham_azeez*
 
 *linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

>>>
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>> --
>> *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 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>


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

[Dev] Build error in support chunk-11 branch

2014-12-17 Thread Indika Sampath

Hi All,

I am getting following build error when I tried to build support chunk-11
branch [1]. Please have a look into this.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project
org.wso2.carbon.identity.application.authentication.framework: Compilation
failure
[ERROR]
/home/indika/dev-zone/support/turing/platform/trunk/components/identity/org.wso2.carbon.identity.application.authentication.framework/4.2.2/src/main/java/org/wso2/carbon/identity/application/authentication/framework/internal/FrameworkServiceComponent.java:[100,32]
error: type ServiceTrackerCustomizer does not take parameters

[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/product-releases/chunk-11

Cheers!

-- 
Indika Sampath
Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Load a key store from registry or file system

2014-12-17 Thread Gayashan Amarasinghe

Hi all,

I want to load a key store to read a key for a given an alias. This key
store can be either in the registry or in the file system. Given the path
to this keystore what is the best way to figure out from where to load it?

I can see two options.

   1. Have the "file:" or "reg:" prefix in the key store path and filter
   based on that
   2. Try to load the file
   from the file system 
   first, if the file is not found in that location try to load it from the
   registry (or vice versa)

What would be the best approach to follow?

Thanks.
/Gayashan

-- 
*Gayashan Amarasinghe*
Software Engineer | Platform TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +94718314517
Blog : gayashan-a.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and commit : APPM-265

2014-12-17 Thread Lahiru Cooray

Hi,

Please merge the PR
https://github.com/wso2/app-manager/pull/94
-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Sandamal Weerasinghe

Hi all,

In a test case that I'm working on, I need to copy several files to
CARBON_HOME.

axis2.xml
carbon.xml
cipher-text.properties
master-datasources.xml
password-tmp
secret-conf.properties
wso2carbon.jks
wso2server.sh - has -Dkey.password=true environment variable

After copying these files I need to shut down the ESB instance and start it
again. (gracefully restarting won't work because of the wso2server.sh).

I tried the following to start a new ESB instance on a different port

Map startupParameterMap = new HashMap();
startupParameterMap.put("-DportOffset", "10");
CarbonTestServerManager carbonTestServerManager = new
CarbonTestServerManager(System.getProperty("carbon.zip"),
startupParameterMap);

carbonHome = carbonTestServerManager.startServer();
carbonTestServerManager.stopServer();

//copy files..

ServerUtils serverUtils = new ServerUtils();
serverUtils.startServerUsingCarbonHome(carbonHome,
FrameworkFactory.getFrameworkProperties("ESB"), startupParameterMap);

This part is working fine. But now I'm facing the following problems,

   1. When the server is shutting down, it tries to generate an emma
   coverage report, is there a way to skip that?
   2. How can I initialize an AdminServiceClient to work on the new ESB
   instance?

Thanks.

Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd

Mobile - +94-77-144-9640
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Load a key store from registry or file system

2014-12-17 Thread Danushka Fernando

AFAIR in proxy services we uses conf: for config registry and gov: for
governance registry. Can't we use that same convention?

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

On Wed, Dec 17, 2014 at 6:46 PM, Gayashan Amarasinghe 
wrote:
>
> Hi all,
>
> I want to load a key store to read a key for a given an alias. This key
> store can be either in the registry or in the file system. Given the path
> to this keystore what is the best way to figure out from where to load it?
>
> I can see two options.
>
>1. Have the "file:" or "reg:" prefix in the key store path and filter
>based on that
>2. Try to load the file
>from the file system 
>first, if the file is not found in that location try to load it from
>the registry (or vice versa)
>
> What would be the best approach to follow?
>
> Thanks.
> /Gayashan
>
> --
> *Gayashan Amarasinghe*
> Software Engineer | Platform TG
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94718314517
> Blog : gayashan-a.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Load a key store from registry or file system

2014-12-17 Thread Udara Liyanage

Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 17, 2014 6:47 PM, "Gayashan Amarasinghe"  wrote:
>
> Hi all,
>
> I want to load a key store to read a key for a given an alias. This key
store can be either in the registry or in the file system. Given the path
to this keystore what is the best way to figure out from where to load it?
>
> I can see two options.
> Have the "file:" or "reg:" prefix in the key store path and filter based
on that
This will be more readable.
> Try to load the file
> from the file system 
> first, if the file is not found in that location try to load it from the
registry (or vice versa)
> What would be the best approach to follow?
>
> Thanks.
> /Gayashan
>
> --
> Gayashan Amarasinghe
> Software Engineer | Platform TG
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94718314517
> Blog : gayashan-a.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Nuwan Wimalasekara

Hi Sandamal,


On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe 
wrote:
>
> Hi all,
>
> In a test case that I'm working on, I need to copy several files to
> CARBON_HOME.
>
> axis2.xml
> carbon.xml
> cipher-text.properties
> master-datasources.xml
> password-tmp
> secret-conf.properties
> wso2carbon.jks
> wso2server.sh - has -Dkey.password=true environment variable
>
> After copying these files I need to shut down the ESB instance and start
> it again. (gracefully restarting won't work because of the wso2server.sh).
>
> I tried the following to start a new ESB instance on a different port
>
> Map startupParameterMap = new HashMap();
> startupParameterMap.put("-DportOffset", "10");
> CarbonTestServerManager carbonTestServerManager = new
> CarbonTestServerManager(System.getProperty("carbon.zip"),
> startupParameterMap);
>
> carbonHome = carbonTestServerManager.startServer();
> carbonTestServerManager.stopServer();
>
> //copy files..
>
> ServerUtils serverUtils = new ServerUtils();
> serverUtils.startServerUsingCarbonHome(carbonHome,
> FrameworkFactory.getFrameworkProperties("ESB"), startupParameterMap);
>
> This part is working fine. But now I'm facing the following problems,
>
>1. When the server is shutting down, it tries to generate an emma
>coverage report, is there a way to skip that?
>
> Why do you need to skipp the emma coverage instrumentation from the server
you are starting?

>
>1. How can I initialize an AdminServiceClient to work on the new ESB
>instance?
>
> You can initialize an  AdminServiceClient by providing the backend url of
the server you have started. But you have to consider the offset when you
build the backend url.

We have already implemented this improvement in the framework
4.3.2-SNAPSHOT and you can make a server with any customisations and start,
stop and start again at ant time easily with TestServerManager. Since you
are using framework 4.2.x you have to follow above code to do this.

Thanks,
Nuwanw

> Thanks.
>
> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>
> Mobile - +94-77-144-9640
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MB][MQTT] Console Based Client

2014-12-17 Thread Pamod Sylvester

Hi All,

You could find a console based client which could be used for testing MQTT
brokers in [1]. The instructions could be found in the readme file.

Thanks,
Pamod
-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB][MQTT] Console Based Client

2014-12-17 Thread Pamod Sylvester

Sorry could add the link,
[1] https://svn.wso2.org/repos/wso2/scratch/pamod/mqtt/console_client

On Wed, Dec 17, 2014 at 8:11 PM, Pamod Sylvester  wrote:
>
> Hi All,
>
> You could find a console based client which could be used for testing MQTT
> brokers in [1]. The instructions could be found in the readme file.
>
> Thanks,
> Pamod
> --
> *Pamod Sylvester *
>  *Senior Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>


-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error in support chunk-11 branch

2014-12-17 Thread Prasad Tissera

Last build in Jenkins is successfu [1]. We don't have any changes to
org.wso2.carbon.identity.application.authentication.framework-4.2.2 (r29475).
Try to build whole chunk-11. Thanks.

[1]. https://supportbuild.wso2.com/jenkins/job/TURING-Chunk-11/659/changes

Regards,
Prasad.

On Wed, Dec 17, 2014 at 6:31 PM, Indika Sampath  wrote:
>
> Hi All,
>
> I am getting following build error when I tried to build support chunk-11
> branch [1]. Please have a look into this.
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project
> org.wso2.carbon.identity.application.authentication.framework: Compilation
> failure
> [ERROR]
> /home/indika/dev-zone/support/turing/platform/trunk/components/identity/org.wso2.carbon.identity.application.authentication.framework/4.2.2/src/main/java/org/wso2/carbon/identity/application/authentication/framework/internal/FrameworkServiceComponent.java:[100,32]
> error: type ServiceTrackerCustomizer does not take parameters
>
> [1]
> https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/product-releases/chunk-11
>
> Cheers!
>
> --
> Indika Sampath
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>

-- 
Prasad Tissera
Software Engineer.
Mobile : +94777223444
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.3.0 RC4

2014-12-17 Thread Manoj Kumara

[x] Stable go ahead and release

Following areas are covered during testing,


   1. Patching and Service Pack application process
   - patch verification
  - patch logging
   2. Artifact deployment with/without GD on both super tenant and tenants
  - webapps
  - services
  - CApps
   3. Deployment Synchronization for above artifacts on both super tenant
   and tenants
  - artifact add/remove/update

Thanks, Manoj


*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188

On Wed, Dec 17, 2014 at 10:39 AM, Pubudu Dissanayake 
wrote:
>
> [x] Stable - go ahead and release
>
> The following areas were covered with testing in both windows and Linux
> environments
>
> 1. Session Replication
>
>- Session replication with ELB (EC2 cluster) with and without Ghost
>Deployment
>- Session replication without ELB (directly accessing nodes)
>- performed kill -9 operation on both scenarios
>
>
> 2. Registry Core ( with a sample webapp)
>
>-  Test add, get and delete of Resources in super tenant
>-  Test add, get and delete of Resources in tenant
>-  Test add, get and delete of Collection in super tenant
>-  Test add, get and delete of Collection in tenant
>
>
>
> On Wed, Dec 17, 2014 at 2:01 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>>
>> [x] Stable - go ahead and release
>>
>> The following areas were covered with testing.
>>
>> 1. Carbon kernel samples (feature-management, p2-repo)
>> i. Installing sample features using pom
>> ii. Installing sample features using a p2-repo.
>> 2. Usage of caching (with a sample webapp)
>>  i. Simple cache accessing (random update and access)
>>  ii. Custom cache expiry value
>> 3. User management tests on
>>  i. Creating and managing roles, users (on both ST and Tenant and
>> also using a non-admin user)
>>  ii. Create new tenants and test above (i) again.
>>
>>
>> On Mon, Dec 15, 2014 at 9:28 AM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the *4th* release candidate of WSO2 Carbon Kernel 4.3.0.
>>>
>>> This release fixes the following issues :
>>> https://wso2.org/jira/issues/?filter=12088
>>>
>>> Please download, test and vote.
>>>
>>> *Binary distribution for Carbon, AS & ESB :*
>>> http://svn.wso2.org/repos/wso2/scratch/carbon/4.3.0-RC4/
>>>
>>> *Maven staging repository :*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-037/
>>>
>>> *The tag to be voted upon :*
>>> https://github.com/wso2/carbon4-kernel/releases/tag/4.3.0-RC4
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thanks,
>>> Carbon Team.
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Senior Software Engineer,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
> --
> *Pubudu Dissanayake*
>  Software Engineer
>
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> Mob: + 94 775 503 304
>
> Blog: http://geekdetected.wordpress.com/
> Linkedin: *http://lk.linkedin.com/in/pubududissanayake*
> 
> Flickr : https://www.flickr.com/photos/pubudufx/
> Twitter: https://twitter.com/GeekInAction
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Krishantha Samaraweera

Hi Sandamal,

On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe 
wrote:
>
> Hi all,
>
> In a test case that I'm working on, I need to copy several files to
> CARBON_HOME.
>
> axis2.xml
> carbon.xml
> cipher-text.properties
> master-datasources.xml
> password-tmp
> secret-conf.properties
> wso2carbon.jks
> wso2server.sh - has -Dkey.password=true environment variable
>
> After copying these files I need to shut down the ESB instance and start
> it again. (gracefully restarting won't work because of the wso2server.sh).
>
> I tried the following to start a new ESB instance on a different port
>
> Map startupParameterMap = new HashMap();
> startupParameterMap.put("-DportOffset", "10");
> CarbonTestServerManager carbonTestServerManager = new
> CarbonTestServerManager(System.getProperty("carbon.zip"),
> startupParameterMap);
>
> carbonHome = carbonTestServerManager.startServer();
> carbonTestServerManager.stopServer();
>
> //copy files..
>
> ServerUtils serverUtils = new ServerUtils();
> serverUtils.startServerUsingCarbonHome(carbonHome,
> FrameworkFactory.getFrameworkProperties("ESB"), startupParameterMap);
>
> This part is working fine. But now I'm facing the following problems,
>
>1. When the server is shutting down, it tries to generate an emma
>coverage report, is there a way to skip that?
>
> You can disable coverage generation by setting coverage.enable property
value to false in automation.properties file.
>
>
>1. How can I initialize an AdminServiceClient to work on the new ESB
>instance?
>
> Older test framework doesn't support for multiple configurations. So you
need to hard code backend URL bases on your port off set value. And use
LoginLogoutClient to get session cookie.

In latest test framework release - TAF 4.3.1, you can specify multiple
instance configurations in automation.xml file, and retrieve values though
AutomationContext.

Thanks,
Krishantha.


> Thanks.
>
> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>
> Mobile - +94-77-144-9640
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Nuwan Wimalasekara

On Wed, Dec 17, 2014 at 10:56 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:
>
> Hi Sandamal,
>
> On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe 
> wrote:
>>
>> Hi all,
>>
>> In a test case that I'm working on, I need to copy several files to
>> CARBON_HOME.
>>
>> axis2.xml
>> carbon.xml
>> cipher-text.properties
>> master-datasources.xml
>> password-tmp
>> secret-conf.properties
>> wso2carbon.jks
>> wso2server.sh - has -Dkey.password=true environment variable
>>
>> After copying these files I need to shut down the ESB instance and start
>> it again. (gracefully restarting won't work because of the wso2server.sh).
>>
>> I tried the following to start a new ESB instance on a different port
>>
>> Map startupParameterMap = new HashMap();
>> startupParameterMap.put("-DportOffset", "10");
>> CarbonTestServerManager carbonTestServerManager = new
>> CarbonTestServerManager(System.getProperty("carbon.zip"),
>> startupParameterMap);
>>
>> carbonHome = carbonTestServerManager.startServer();
>> carbonTestServerManager.stopServer();
>>
>> //copy files..
>>
>> ServerUtils serverUtils = new ServerUtils();
>> serverUtils.startServerUsingCarbonHome(carbonHome,
>> FrameworkFactory.getFrameworkProperties("ESB"), startupParameterMap);
>>
>> This part is working fine. But now I'm facing the following problems,
>>
>>1. When the server is shutting down, it tries to generate an emma
>>coverage report, is there a way to skip that?
>>
>> You can disable coverage generation by setting coverage.enable property
> value to false in automation.properties file.
>
if we disable the coverage by setting the coverage.enable value, It will
disable coverage from whole test module. if so  we can not collect the
coverage statistics.

>
>>1. How can I initialize an AdminServiceClient to work on the new ESB
>>instance?
>>
>> Older test framework doesn't support for multiple configurations. So you
> need to hard code backend URL bases on your port off set value. And use
> LoginLogoutClient to get session cookie.
>
> In latest test framework release - TAF 4.3.1, you can specify multiple
> instance configurations in automation.xml file, and retrieve values though
> AutomationContext.
>
> Thanks,
> Krishantha.
>
>
>> Thanks.
>>
>> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>>
>> Mobile - +94-77-144-9640
>>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middlewear.
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] RPCMessageReceiver Exception occurred while an unauthorized user tries to access a web application in EAM

2014-12-17 Thread Prasad Tissera

Hi Thilini,

This will be fixed in the IS Service Pack and will be merged to the public
branch. Thanks for reporting.

Regards,
Prasad.

On Tue, Sep 23, 2014 at 11:06 PM, Thilini Shanika  wrote:
>
> Hi,
>
> RPCMessageReceiver exceptions are occurred in EAM while an unauthorized
> user tries to access an webapp from EAM store [1] or browse an webapp
> resource from admin console [2]. These exceptions are triggered from
> org.wso2.carbon.identity.application.mgt/4.2.1 component and the root cause
> for this unexpected behavior is  using 'CarbonContext.getCurrentContext()'
> instead of 'CarbonContext.getThreadLocalCarbonContext()', inside some
> methods of ApplicationManagementService
> and ApplicationManagementOSGIService classes. Can you please provide a fix
> for this issue?
>
>
> [1] - https://wso2.org/jira/browse/APPM-184
> [2] - https://wso2.org/jira/browse/APPM-186
>
> Thanks !
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Prasad Tissera
Software Engineer.
Mobile : +94777223444
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ES] Uploading Zip Files with Assets

2014-12-17 Thread Shiva Balachandran

Hi All,

I have a requirement to add zip file (size could vary from 2 mb- 10 mb)
along with an asset. Basically our asset will have its properties filled
and the user will have to attached a zip file. This zip file should not be
stored in the registry due to the large size of the zip file

Does ES support this type of functionality? How can we achieve this?

It would be great if you could clarify how the thumbnails and banners are
currently stored in the ES model?

If we are able to store the zip file in a local location, not in the
registry, how are we to access the file in a clustered environment?

Thank you.

Regards
-- 
Shiva Balachandran
Software Engineer
WSO2 Inc.

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

[Dev] Base64 encoding for the attachment

2014-12-17 Thread Kathees Rajendram

Hi,

I tried to get the attachment from the axis2 message context and converted
to base64 encoding. The base64 encoding  is different compared with
original image base64 encoding. Suggestion please?

try {

Axis2MessageContext axisMsgContext = (Axis2MessageContext) synCtx;
org.apache.axis2.context.MessageContext msgContext = axisMsgContext
.getAxis2MessageContext();

Attachments attachment = msgContext.getAttachmentMap();

InputStream inputStream =
attachment.getIncomingAttachmentsAsSingleStream();

byte[] bytes = IOUtils.toByteArray(inputStream);

String byteArray = Base64.encodeBytes(bytes);

String encodedString = new String(byteArray);

synCtx.setProperty("attachmentObject", encodedString);

}

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Base64 encoding for the attachment

2014-12-17 Thread Prabath Ariyarathna

HI Kathees.

Please try to *Base64.encodeBase64URLSafeString(bytes)* instead of
*Base64.encodeBytes(bytes)*

On Thu, Dec 18, 2014 at 7:46 AM, Kathees Rajendram  wrote:
>
> Hi,
>
> I tried to get the attachment from the axis2 message context and converted
> to base64 encoding. The base64 encoding  is different compared with
> original image base64 encoding. Suggestion please?
>
> try {
>
> Axis2MessageContext axisMsgContext = (Axis2MessageContext) synCtx;
> org.apache.axis2.context.MessageContext msgContext = axisMsgContext
> .getAxis2MessageContext();
>
> Attachments attachment = msgContext.getAttachmentMap();
>
> InputStream inputStream =
> attachment.getIncomingAttachmentsAsSingleStream();
>
> byte[] bytes = IOUtils.toByteArray(inputStream);
>
> String byteArray = Base64.encodeBytes(bytes);
>
> String encodedString = new String(byteArray);
>
> synCtx.setProperty("attachmentObject", encodedString);
>
> }
>
> Thanks,
> Kathees
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 

*Prabath Ariyarathna*

*Associate Technical Lead*

*WSO2, Inc. *

*lean . enterprise . middleware *


*Email: prabat...@wso2.com *

*Blog: http://prabu-lk.blogspot.com *

*Flicker : https://www.flickr.com/photos/47759189@N08
*

*Mobile: +94 77 699 4730 *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Why we keep commented out in api-manager.xml's usage stat section?

2014-12-17 Thread Amila Maha Arachchi

APIM Team,

Currently, if I want to publish API usage stats to BAM, we need to set
APIUsageTracking.Enabled to  true. Then this starts publishing usage data.

But, until we enable  at the bottom, stats does not appear
in the UI. It gives a funny message saying, "Stat publishing is enabled,
generate some traffic" :)

IMO, there is no valid reason to keep this data source name commented out.
Because, you guys have added the datasource to master-datasource.xml when
shipping the product.

So, I suggest to keep it uncommented and make the life easier for the user.
Otherwise, he/she will spend quite a lot of time troubleshooting. This is a
usability improvement.





true

...






Regards,
Amila.

-- 
*Amila Maharachchi*
Senior Technical Lead
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] [APPM] General code review of patches provided

2014-12-17 Thread Ruwan Yatawara

General

   -

   Make the log parameters in debug logs, context aware and releavent.
   -

   Add null checks in all host object methods added.
   -

   Add description for parameters, in code comments.
   -

   Remove all log.info from jaggery code
   -

   Get rid of unused imports
   -

   Use standard variable names for parameters like synapse context


ProviderHostObject

   -

   change method name from getAssociatedAppsName to getAssociatedAppNames



   -

   in iswebappExist method, string comparison need to be done against the
   constant, not the other way around.



   -

   saveEntitlementPolicyPartials / saveEntitlementPolicyPartials
   -

  Add null checks to arguments recieved from native array as it will be
  problematic when these functions are used as APIs
  -

  Fix length to 120



AppMgtDao

   -

   SaveEntitlementPolicyPartials / UpdateEntitlementPolicyPartials /
   DeleteEntitlementPolicyPartials
   -

  Use Integer.parseInt instead of complex value of statement, then
  throw a parseException
  -

  Throw exception E1 instead of E in the catch block



   -

   getSharedEntitlementPolicyPartialsList
   -

  Get rid of connection.commit as it is a select query that is executed



   -

   Check if validationResult function is really needed
   - addApplication  method, replace == with equals



Entitlement JS

   -

   In update scenario, include a comment for the section when building
   associated app list
   -

   When getting the policy partials, get the policy partials per app in
   single db call from db instead compiling a list in UI



APPM-222

   -

   change method name getAPISubscriptionCountByApp to
   getSubscriptionCountByApp
   -

   define return parameter in the java doc comment and list what is
   returned in the map
   -

   The loop to populate subscriptions does not seem to run when the sql is
   executed so get rid of that section after checking
   -

   Get rid of the UI specific formatting logic executed at the backend
   (Adding spaces and formatting) and handle said logic in the UI.
   -

   getAllWebapps method instantiate all the variables before starting the
   while loop
   -

   In the DB query get rid of CURRENT_TIMESTAMP as it not a standard ANSI
   sql



APPM-247

   -

   api.getPolicyPartiallist() is not a list so change the variable name to
   something else.



APPM-167

   -

   addURITemplate : get rid of the byte i =0 section and the logic to
   increment same add regular, create the prepared statement by inserting the
   values as 1,2,3
   -

   AppID you do not have to cast to string again
   -

   In the EntitlemntPolicy Class get rid of the generic exceptions and Add
   all the java doc comments


AppMgtDao

   -

   For the delete app method, get rid of the call made from DAO layer to
   Impl, introduce a hostobject method and call the impl instead



APPM-206

   -

   AppManagerConfigurationServiceComponent, introduce isDebug enabled blocks
   -

   Add useful error messages.





Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://thoughts.ruwan-ace.com/
www: :http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Load a key store from registry or file system

2014-12-17 Thread Gayashan Amarasinghe

Thanks Danushka and Udara. I'll follow the existing approach where the path
is prefixed by gov, config or local if it is in the registry and "file" if
it is in the filesystem.

Thanks.
/Gayashan

On Wed, Dec 17, 2014 at 8:06 PM, Udara Liyanage  wrote:
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Dec 17, 2014 6:47 PM, "Gayashan Amarasinghe"  wrote:
> >
> > Hi all,
> >
> > I want to load a key store to read a key for a given an alias. This key
> store can be either in the registry or in the file system. Given the path
> to this keystore what is the best way to figure out from where to load it?
> >
> > I can see two options.
> > Have the "file:" or "reg:" prefix in the key store path and filter based
> on that
> This will be more readable.
> > Try to load the file
> > from the file system 
> > first, if the file is not found in that location try to load it from the
> registry (or vice versa)
> > What would be the best approach to follow?
> >
> > Thanks.
> > /Gayashan
> >
> > --
> > Gayashan Amarasinghe
> > Software Engineer | Platform TG
> > WSO2, Inc. | http://wso2.com
> > lean. enterprise. middleware
> >
> > Mobile : +94718314517
> > Blog : gayashan-a.blogspot.com
> >
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
> >
>


-- 
*Gayashan Amarasinghe*
Software Engineer | Platform TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +94718314517
Blog : gayashan-a.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Session Cookies in Platform and Products.

2014-12-17 Thread Hasintha Indrajee

Hi all,

In our platform or any application, do we use any custom cookies other than
JSESSIONID cookies for maintaining sessions ?. Can somebody point out the
places where we use those custom cookies for maintaining sessions.

For an example we use CommonAuthID cookie for maintaining sessions in
Authentication Framework.

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

Re: [Dev] Base64 encoding for the attachment

2014-12-17 Thread Malaka Silva

Hi,

You can also try [1] for encoding.

[1]
http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0001/dependencies/axiom/modules/axiom-api/src/main/java/org/apache/axiom/util/base64/Base64Utils.java

On Thu, Dec 18, 2014 at 8:09 AM, Prabath Ariyarathna 
wrote:
>
> HI Kathees.
>
> Please try to *Base64.encodeBase64URLSafeString(bytes)* instead of
> *Base64.encodeBytes(bytes)*
>
> On Thu, Dec 18, 2014 at 7:46 AM, Kathees Rajendram 
> wrote:
>
>> Hi,
>>
>> I tried to get the attachment from the axis2 message context and
>> converted to base64 encoding. The base64 encoding  is different compared
>> with original image base64 encoding. Suggestion please?
>>
>> try {
>>
>> Axis2MessageContext axisMsgContext = (Axis2MessageContext) synCtx;
>> org.apache.axis2.context.MessageContext msgContext = axisMsgContext
>> .getAxis2MessageContext();
>>
>> Attachments attachment = msgContext.getAttachmentMap();
>>
>> InputStream inputStream =
>> attachment.getIncomingAttachmentsAsSingleStream();
>>
>> byte[] bytes = IOUtils.toByteArray(inputStream);
>>
>> String byteArray = Base64.encodeBytes(bytes);
>>
>> String encodedString = new String(byteArray);
>>
>> synCtx.setProperty("attachmentObject", encodedString);
>>
>> }
>>
>> Thanks,
>> Kathees
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> --
>
> *Prabath Ariyarathna*
>
> *Associate Technical Lead*
>
> *WSO2, Inc. *
>
> *lean . enterprise . middleware *
>
>
> *Email: prabat...@wso2.com *
>
> *Blog: http://prabu-lk.blogspot.com *
>
> *Flicker : https://www.flickr.com/photos/47759189@N08
> *
>
> *Mobile: +94 77 699 4730 *
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/


Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.3.0 RC4

2014-12-17 Thread Sameera Jayasoma

Hi Devs,

Thanks for testing and verifying the Carbon kernel RC4. We are closing this
vote now. This vote has passed with 7 +1s and 0 -1s. Therefore we will
proceed with the Carbon kernel 4.3.0 release.

7 +1s
0  -1s

Carbon Team.


On Wed, Dec 17, 2014 at 10:20 PM, Manoj Kumara  wrote:
>
> [x] Stable go ahead and release
>
> Following areas are covered during testing,
>
>
>1. Patching and Service Pack application process
>- patch verification
>   - patch logging
>2. Artifact deployment with/without GD on both super tenant and tenants
>   - webapps
>   - services
>   - CApps
>3. Deployment Synchronization for above artifacts on both super tenant
>and tenants
>   - artifact add/remove/update
>
> Thanks, Manoj
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
> On Wed, Dec 17, 2014 at 10:39 AM, Pubudu Dissanayake 
> wrote:
>>
>> [x] Stable - go ahead and release
>>
>> The following areas were covered with testing in both windows and Linux
>> environments
>>
>> 1. Session Replication
>>
>>- Session replication with ELB (EC2 cluster) with and without Ghost
>>Deployment
>>- Session replication without ELB (directly accessing nodes)
>>- performed kill -9 operation on both scenarios
>>
>>
>> 2. Registry Core ( with a sample webapp)
>>
>>-  Test add, get and delete of Resources in super tenant
>>-  Test add, get and delete of Resources in tenant
>>-  Test add, get and delete of Collection in super tenant
>>-  Test add, get and delete of Collection in tenant
>>
>>
>>
>> On Wed, Dec 17, 2014 at 2:01 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>>
>>> [x] Stable - go ahead and release
>>>
>>> The following areas were covered with testing.
>>>
>>> 1. Carbon kernel samples (feature-management, p2-repo)
>>> i. Installing sample features using pom
>>> ii. Installing sample features using a p2-repo.
>>> 2. Usage of caching (with a sample webapp)
>>>  i. Simple cache accessing (random update and access)
>>>  ii. Custom cache expiry value
>>> 3. User management tests on
>>>  i. Creating and managing roles, users (on both ST and Tenant and
>>> also using a non-admin user)
>>>  ii. Create new tenants and test above (i) again.
>>>
>>>
>>> On Mon, Dec 15, 2014 at 9:28 AM, Sameera Jayasoma 
>>> wrote:
>>>
 Hi Devs,

 This is the *4th* release candidate of WSO2 Carbon Kernel 4.3.0.

 This release fixes the following issues :
 https://wso2.org/jira/issues/?filter=12088

 Please download, test and vote.

 *Binary distribution for Carbon, AS & ESB :*
 http://svn.wso2.org/repos/wso2/scratch/carbon/4.3.0-RC4/

 *Maven staging repository :*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-037/

 *The tag to be voted upon :*
 https://github.com/wso2/carbon4-kernel/releases/tag/4.3.0-RC4


 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release

 Thanks,
 Carbon Team.

 --
 Sameera Jayasoma,
 Software Architect,

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://sameera.adahas.org
 twitter: https://twitter.com/sameerajayasoma
 flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
 Mobile: 0094776364456

 Lean . Enterprise . Middleware


>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Senior Software Engineer,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> *
>>>
>>
>>
>> --
>> *Pubudu Dissanayake*
>>  Software Engineer
>>
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> Mob: + 94 775 503 304
>>
>> Blog: http://geekdetected.wordpress.com/
>> Linkedin: *http://lk.linkedin.com/in/pubududissanayake*
>> 
>> Flickr : https://www.flickr.com/photos/pubudufx/
>> Twitter: https://twitter.com/GeekInAction
>>
>>

-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] Base64 encoding for the attachment

2014-12-17 Thread Firzhan Naqash

Hi Kathees,

You can use the following code snippet to encode the byte array.

String encodedRequestMessage =
Base64.encodeBytes(byteArrayOutputStream.toByteArray(),
Base64.DONT_BREAK_LINES);



Regards,
Firzhan

On Thu, Dec 18, 2014 at 11:00 AM, Malaka Silva  wrote:
>
> Hi,
>
> You can also try [1] for encoding.
>
> [1]
> http://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0001/dependencies/axiom/modules/axiom-api/src/main/java/org/apache/axiom/util/base64/Base64Utils.java
>
> On Thu, Dec 18, 2014 at 8:09 AM, Prabath Ariyarathna 
> wrote:
>>
>> HI Kathees.
>>
>> Please try to *Base64.encodeBase64URLSafeString(bytes)* instead of
>> *Base64.encodeBytes(bytes)*
>>
>> On Thu, Dec 18, 2014 at 7:46 AM, Kathees Rajendram 
>> wrote:
>>
>>> Hi,
>>>
>>> I tried to get the attachment from the axis2 message context and
>>> converted to base64 encoding. The base64 encoding  is different compared
>>> with original image base64 encoding. Suggestion please?
>>>
>>> try {
>>>
>>> Axis2MessageContext axisMsgContext = (Axis2MessageContext) synCtx;
>>> org.apache.axis2.context.MessageContext msgContext = axisMsgContext
>>> .getAxis2MessageContext();
>>>
>>> Attachments attachment = msgContext.getAttachmentMap();
>>>
>>> InputStream inputStream =
>>> attachment.getIncomingAttachmentsAsSingleStream();
>>>
>>> byte[] bytes = IOUtils.toByteArray(inputStream);
>>>
>>> String byteArray = Base64.encodeBytes(bytes);
>>>
>>> String encodedString = new String(byteArray);
>>>
>>> synCtx.setProperty("attachmentObject", encodedString);
>>>
>>> }
>>>
>>> Thanks,
>>> Kathees
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> --
>>
>> *Prabath Ariyarathna*
>>
>> *Associate Technical Lead*
>>
>> *WSO2, Inc. *
>>
>> *lean . enterprise . middleware *
>>
>>
>> *Email: prabat...@wso2.com *
>>
>> *Blog: http://prabu-lk.blogspot.com *
>>
>> *Flicker : https://www.flickr.com/photos/47759189@N08
>> *
>>
>> *Mobile: +94 77 699 4730 *
>>
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>
> ___
> 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] [ES] Uploading Zip Files with Assets

2014-12-17 Thread Ayesha Dissanayaka

hi Shiva,

Currently thumbnails and banners comes with default assets in ES are stored
in the below datasource mentioned in the master-datasources.xml config
file. So they are not saved in registry.


JAGH2
The datasource used for by the Jaggery Storage
Manager

jdbc/test




jdbc:h2:repository/database/ES_STORAGE;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6
sa

org.h2.Driver
50
6




In a clustered environment pointing to the same datasource by all the nodes
will enable accessing files without any issue.

Thanks!
- Ayesha


On Thu, Dec 18, 2014 at 1:16 AM, Shiva Balachandran  wrote:
>
> Hi All,
>
> I have a requirement to add zip file (size could vary from 2 mb- 10 mb)
> along with an asset. Basically our asset will have its properties filled
> and the user will have to attached a zip file. This zip file should not be
> stored in the registry due to the large size of the zip file
>
> Does ES support this type of functionality? How can we achieve this?
>
> It would be great if you could clarify how the thumbnails and banners are
> currently stored in the ES model?
>
> If we are able to store the zip file in a local location, not in the
> registry, how are we to access the file in a clustered environment?
>
> Thank you.
>
> Regards
> --
> Shiva Balachandran
> Software Engineer
> WSO2 Inc.
>
> Mobile - +94 774445788
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error in support chunk-11 branch

2014-12-17 Thread Rajeev Sampath

AFAIK, this error occurs when building with JDK 7+, try using JDK 6.


Thanks
Rajeev

On Wed, Dec 17, 2014 at 9:21 PM, Prasad Tissera  wrote:
>
> Last build in Jenkins is successfu [1]. We don't have any changes to
> org.wso2.carbon.identity.application.authentication.framework-4.2.2 (r29475).
> Try to build whole chunk-11. Thanks.
>
> [1]. https://supportbuild.wso2.com/jenkins/job/TURING-Chunk-11/659/changes
>
> Regards,
> Prasad.
>
> On Wed, Dec 17, 2014 at 6:31 PM, Indika Sampath  wrote:
>>
>> Hi All,
>>
>> I am getting following build error when I tried to build support chunk-11
>> branch [1]. Please have a look into this.
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project
>> org.wso2.carbon.identity.application.authentication.framework: Compilation
>> failure
>> [ERROR]
>> /home/indika/dev-zone/support/turing/platform/trunk/components/identity/org.wso2.carbon.identity.application.authentication.framework/4.2.2/src/main/java/org/wso2/carbon/identity/application/authentication/framework/internal/FrameworkServiceComponent.java:[100,32]
>> error: type ServiceTrackerCustomizer does not take parameters
>>
>> [1]
>> https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/product-releases/chunk-11
>>
>> Cheers!
>>
>> --
>> Indika Sampath
>> Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>
> --
> Prasad Tissera
> Software Engineer.
> Mobile : +94777223444
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Rajeev Sampath
Senior Software Engineer
WSO2, Inc.; http://www.wso2.com.

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

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Sandamal Weerasinghe

The reason why I wanted to disable emma test coverage is because it throws
the following error. But I can leave that as it is. I will use the above
solution for (2) to access the adminServiceClients.

Thanks.

com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
version of class
[org.wso2.carbon.core.services.util.CarbonAuthenticationUtil] in the
coverage data is not consistent with the version of this class in the
metadata, possibly because stale metadata is being used for report
generation.
at com.vladium.emma.report.ReportDataModel.getView(ReportDataModel.java:95)
at
com.vladium.emma.report.AbstractReportGenerator.initialize(AbstractReportGenerator.java:210)
at
com.vladium.emma.report.html.ReportGenerator.process(ReportGenerator.java:85)
at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:255)
at com.vladium.emma.Processor.run(Processor.java:88)
at com.vladium.emma.report.reportCommand.run(reportCommand.java:139)
at
org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils.generateReports(CodeCoverageUtils.java:310)
at
org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.shutdown(ServerUtils.java:214)
at
org.wso2.carbon.automation.core.TestServerManager.stopServer(TestServerManager.java:113)
at
org.wso2.carbon.automation.core.tests.utils.CarbonTestServerManager.stopServer(CarbonTestServerManager.java:46)
at
org.wso2.carbon.esb.security.basic.ESBJAVA3424TestCase.init(ESBJAVA3424TestCase.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
[2014-12-18 11:39:44,149]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils} -  Emma
report generation completed

Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd

Mobile - +94-77-144-9640

On Wed, Dec 17, 2014 at 11:07 PM, Nuwan Wimalasekara 
wrote:
>
>
>
> On Wed, Dec 17, 2014 at 10:56 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>>
>> Hi Sandamal,
>>
>> On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe 
>> wrote:
>>>
>>> Hi all,
>>>
>>> In a test case that I'm working on, I need to copy several files to
>>> CARBON_HOME.
>>>
>>> axis2.xml
>>> carbon.xml
>>> cipher-text.properties
>>> master-datasources.xml
>>> password-tmp
>>> secret-conf.properties
>>> wso2carbon.jks
>>> wso2server.sh - has -Dkey.password=true environment variable
>>>
>>> After copying these files I need to shut down the ESB instance and start
>>> it again. (gracefully restarting won't work because of the wso2server.sh).
>>>
>>> I tried the following to start a new ESB instance on a different port
>>>
>>> Map startupParameterMap = new HashMap();
>>> s

Re: [Dev] [ES] input type 'file' not retrieved

2014-12-17 Thread Sameera Medagammaddegedara

Hi Denuwanthi,

The ES will first scan for any file fields and put them in the ES
storage.After which the options object is augmented with the name of the
field and a storage UUID before being passed to the asset create method.if
the file field is not found in the RXT definition it is ignored.In this
case the wsdl_zip field is not defined in the RXT definition and is a file
field.

In order to by pass this behaviour you will need to implement a custom API
endpoint and invoke your asset create logic.

Thank You,
Sameera


On Tue, Dec 16, 2014 at 11:55 PM, Denuwanthi De Silva 
wrote:
>
> Hi,
>
> In the custom asset extension I'm working on, I have a requirement to
> support file upload.
>
> Thus, in my overridden partial (create_form.hbs) I use
> 
> to get the html view of the file uploader.
>
> Then, in my extension's asset.js inside 'create' method, I try to access
> the value taken by that html element by using,
>
> *options.wsdl_zip*
>
> But, when I actually browse file and log the above value, it prints 'null'
> and the 'options' json object does not even contain 'wsdl_zip' attribute.
>
> If I use a text field instead of using type 'file',
>
> 
>
>
> options.wsdl_zip returns the value I entered in the text field.
>
> So, what could be the reason for not retrieving 'file' type inputs ?
> Any other configurations need to be done?
>
> Thanks,
> --
> Denuwanthi De Silva
> Software Engineer;
> WSO2 Inc.; http://wso2.com,
> Email: denuwan...@wso2.com
>
>
>

-- 
Sameera Medagammaddegedara
Software Engineer

Contact:
Email: samee...@wso2.com
Mobile: + 94 077 255 3005
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][Test-Automation] What is the exception object that should be thrown from a Test-Automation-Extension

2014-12-17 Thread Ayesha Dissanayaka

Hi ,

I have introduced an extentionClass extending ExecutionListenerExtension. I
if I am to throw a exception such as *IOException* and
*MalformedURLException* caught in this implementation to upper level, what
should be the specific higher level exception instance I should throw?

Thanks!
-Ayesha

-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error in support chunk-11 branch

2014-12-17 Thread Hasintha Indrajee

Hi Indika,

On Thu, Dec 18, 2014 at 11:36 AM, Rajeev Sampath  wrote:
>
>
> AFAIK, this error occurs when building with JDK 7+, try using JDK 6.
>
> Yes, the issue should be with your java version. Created a jira for this
[1]. Service tracker should be removed from Authentication Framework.

[1] https://wso2.org/jira/browse/IDENTITY-2953

>
> Thanks
> Rajeev
>
> On Wed, Dec 17, 2014 at 9:21 PM, Prasad Tissera  wrote:
>
>> Last build in Jenkins is successfu [1]. We don't have any changes to
>> org.wso2.carbon.identity.application.authentication.framework-4.2.2 (r29475).
>> Try to build whole chunk-11. Thanks.
>>
>> [1].
>> https://supportbuild.wso2.com/jenkins/job/TURING-Chunk-11/659/changes
>>
>> Regards,
>> Prasad.
>>
>> On Wed, Dec 17, 2014 at 6:31 PM, Indika Sampath  wrote:
>>>
>>> Hi All,
>>>
>>> I am getting following build error when I tried to build support
>>> chunk-11 branch [1]. Please have a look into this.
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project
>>> org.wso2.carbon.identity.application.authentication.framework: Compilation
>>> failure
>>> [ERROR]
>>> /home/indika/dev-zone/support/turing/platform/trunk/components/identity/org.wso2.carbon.identity.application.authentication.framework/4.2.2/src/main/java/org/wso2/carbon/identity/application/authentication/framework/internal/FrameworkServiceComponent.java:[100,32]
>>> error: type ServiceTrackerCustomizer does not take parameters
>>>
>>> [1]
>>> https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/platform/trunk/product-releases/chunk-11
>>>
>>> Cheers!
>>>
>>> --
>>> Indika Sampath
>>> Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Phone: +94 716 424 744
>>> Blog: http://indikasampath.blogspot.com/
>>>
>>>
>>
>> --
>> Prasad Tissera
>> Software Engineer.
>> Mobile : +94777223444
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> --
> Rajeev Sampath
> Senior Software Engineer
> WSO2, Inc.; http://www.wso2.com.
>
> Mobile:
> * +94716265766 <%2B94716265766>*
>
> ___
> 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] [AF] If Auto Deploy fails for some reason Then we cannot promote that branch after that.

2014-12-17 Thread Danushka Fernando

Hi all,
According to current implementation, We pass a different deploy action to
Auto Deploy which will label the artifact to promote. But for some reason
if it fails and say user decided to disable auto deploy, user cannot
promote that branch after that since label hasn't been created. And another
down side is that if some one disable auto deploy and do manual deploy some
of the changes are not going to be in the labeled artifact.

IMO this should get fixed. WDYT?

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Dharshana Warusavitharana

Hi Sandamal,

This happens because there are inconsistencies between coverage.ec and .em
files created during the instrumentation.

Could you try to exclude
[org.wso2.carbon.core.services.util.CarbonAuthenticationUtil]
from filter.txt file and see.

Anyway ESB does not want this class instrumented for coverage.

Thank You,
Dharshana.


On Thu, Dec 18, 2014 at 11:43 AM, Sandamal Weerasinghe 
wrote:
>
> The reason why I wanted to disable emma test coverage is because it throws
> the following error. But I can leave that as it is. I will use the above
> solution for (2) to access the adminServiceClients.
>
> Thanks.
>
> com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
> version of class
> [org.wso2.carbon.core.services.util.CarbonAuthenticationUtil] in the
> coverage data is not consistent with the version of this class in the
> metadata, possibly because stale metadata is being used for report
> generation.
> at com.vladium.emma.report.ReportDataModel.getView(ReportDataModel.java:95)
> at
> com.vladium.emma.report.AbstractReportGenerator.initialize(AbstractReportGenerator.java:210)
> at
> com.vladium.emma.report.html.ReportGenerator.process(ReportGenerator.java:85)
> at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:255)
> at com.vladium.emma.Processor.run(Processor.java:88)
> at com.vladium.emma.report.reportCommand.run(reportCommand.java:139)
> at
> org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils.generateReports(CodeCoverageUtils.java:310)
> at
> org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.shutdown(ServerUtils.java:214)
> at
> org.wso2.carbon.automation.core.TestServerManager.stopServer(TestServerManager.java:113)
> at
> org.wso2.carbon.automation.core.tests.utils.CarbonTestServerManager.stopServer(CarbonTestServerManager.java:46)
> at
> org.wso2.carbon.esb.security.basic.ESBJAVA3424TestCase.init(ESBJAVA3424TestCase.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
> at
> org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> at org.testng.TestNG.run(TestNG.java:999)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> [2014-12-18 11:39:44,149]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils} -  Emma
> report generation completed
>
>
> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>
> Mobile - +94-77-144-9640
>
> On Wed, Dec 17, 2014 at 11:07 PM, Nuwan Wimalasekara 
> wrote:
>>
>>
>>
>> On Wed, Dec 17, 2014 at 10:56 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>>
>>> Hi Sandamal,
>>>
>>> On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe >> > wrote:

 Hi all,

 In a

Re: [Dev] [DEV][Test-Automation] What is the exception object that should be thrown from a Test-Automation-Extension

2014-12-17 Thread Ayesha Dissanayaka

Can I throw http://testng.org/javadoc/org/testng/TestNGException.html for
$subject?

On Thu, Dec 18, 2014 at 11:57 AM, Ayesha Dissanayaka 
wrote:
>
> Hi ,
>
> I have introduced an extentionClass extending ExecutionListenerExtension.
> I if I am to throw a exception such as *IOException* and
> *MalformedURLException* caught in this implementation to upper level,
> what should be the specific higher level exception instance I should throw?
>
> Thanks!
> -Ayesha
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Disabling of ESB script mediator - JSON payloads related integration test cases

2014-12-17 Thread Dimuthu De Lanerolle

We have automated ESB script mediator related test scenarios for JSON
payloads (pls refer  'Script mediator' section of the doc  [1]) and below
mentioned test cases are *disabled* due to ESB 4.9.0-SANPSHOT related
script mediator known issue [2] .

[1] https://docs.wso2.com/display/ESB490/JSON+Support
[2] https://wso2.org/jira/browse/ESBJAVA-3423

Exception:
com.sun.phobos.script.util.ExtendedScriptException:
org.mozilla.javascript.EcmaError: ReferenceError: "JSON" is not defined.
(#1) in  at line number 1
at
com.sun.phobos.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:184)
at
com.sun.phobos.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:198)
at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:264)
at
org.apache.synapse.mediators.bsf.ScriptMediator.processJSONPayload(ScriptMediator.java:325)
at
org.apache.synapse.mediators.bsf.ScriptMediator.mediateForInlineScript(ScriptMediator.java:285)
at
org.apache.synapse.mediators.bsf.ScriptMediator.invokeScript(ScriptMediator.java:235)
at
org.apache.synapse.mediators.bsf.ScriptMediator.mediate(ScriptMediator.java:203)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:80)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:135)
at org.apache.synapse.rest.Resource.process(Resource.java:297)
at org.apache.synapse.rest.API.process(API.java:297)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:93)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:50)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:220)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:501)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:171)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:229)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.mozilla.javascript.EcmaError: ReferenceError: "JSON" is not
defined. (#1)
at
org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3350)


Therefore pls enable these test cases once mentioned JIRA issue is fixed.

Test cases :

* /tests-other/
  1. JSONWithScriptMediatorXMLResponseTestCase
  2. JSONWithScriptMediatorJsonResponseTestCase
  3. JSONWithScriptMediatorJsonOperationsTestCase
  4. JSONWithScriptMediatorBuildingXMLPayloadIterativelyTestCase


Regards








-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stopping and starting an ESB instance from a test case

2014-12-17 Thread Krishantha Samaraweera

Hi Sandamal,

On Thu, Dec 18, 2014 at 11:43 AM, Sandamal Weerasinghe 
wrote:
>
> The reason why I wanted to disable emma test coverage is because it throws
> the following error. But I can leave that as it is. I will use the above
> solution for (2) to access the adminServiceClients.
>
> Thanks.
>
> com.vladium.emma.EMMARuntimeException: [CLASS_STAMP_MISMATCH] runtime
> version of class
> [org.wso2.carbon.core.services.util.CarbonAuthenticationUtil] in the
> coverage data is not consistent with the version of this class in the
> metadata, possibly because stale metadata is being used for report
> generation.
> at com.vladium.emma.report.ReportDataModel.getView(ReportDataModel.java:95)
> at
> com.vladium.emma.report.AbstractReportGenerator.initialize(AbstractReportGenerator.java:210)
> at
> com.vladium.emma.report.html.ReportGenerator.process(ReportGenerator.java:85)
> at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:255)
> at com.vladium.emma.Processor.run(Processor.java:88)
> at com.vladium.emma.report.reportCommand.run(reportCommand.java:139)
> at
> org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils.generateReports(CodeCoverageUtils.java:310)
> at
> org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.shutdown(ServerUtils.java:214)
> at
> org.wso2.carbon.automation.core.TestServerManager.stopServer(TestServerManager.java:113)
> at
> org.wso2.carbon.automation.core.tests.utils.CarbonTestServerManager.stopServer(CarbonTestServerManager.java:46)
> at
> org.wso2.carbon.esb.security.basic.ESBJAVA3424TestCase.init(ESBJAVA3424TestCase.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
> at
> org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> at org.testng.TestNG.run(TestNG.java:999)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> [2014-12-18 11:39:44,149]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils} -  Emma
> report generation completed
>


I've seen this error when there are multiple jar versions in plugins dir.
Can you please check.


Thanks,
Krishantha.

>
>
> Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
>
> Mobile - +94-77-144-9640
>
> On Wed, Dec 17, 2014 at 11:07 PM, Nuwan Wimalasekara 
> wrote:
>>
>>
>>
>> On Wed, Dec 17, 2014 at 10:56 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>>
>>> Hi Sandamal,
>>>
>>> On Wed, Dec 17, 2014 at 7:07 PM, Sandamal Weerasinghe >> > wrote:

 Hi all,

 In a test case that I'm working on, I need to copy several files to
 CARBON_HOME.

 axis2.xml
 carbon.xml
 cipher-text.properties
 master-datasources.xml
 password-tmp
 secre

Re: [Dev] Contributing to IS - where is the current development source

2014-12-17 Thread Dulitha Wijewantha

Thanks Darshana and Dulanja. I'll send another mail about the changes to
@dev.

On Tue, Dec 16, 2014 at 7:26 PM, Dulanja Liyanage  wrote:
>
> And this new code should be reviewed. Also, better to discuss what it
> provides in a public list like @dev or @architecture.
>
> Thanks
> Dulanja
>
> On Wed, Dec 17, 2014 at 8:51 AM, Darshana Gunawardana 
> wrote:
>>
>> Hi Dulitha,
>>
>> Thanks for the contribution. Development source is available at [1]. And
>> there is ongoing processes on moving to GIT. Until these migration get
>> complete we kept sync svn and git. So you need to send a PR to [2] as
>> well..
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/identity/org.wso2.carbon.identity.mgt/4.2.3/
>>
>> [2] https://github.com/wso2-dev/carbon-identity
>>
>> Regards,
>> Darshana
>>
>> On Wed, Dec 17, 2014 at 6:23 AM, Dulitha Wijewantha 
>> wrote:
>>
>>> Hi guys,
>>> I would like to contribute some code I wrote to identity.mgt component.
>>> Where is the development source of this available? Is it in SVN [1] or in
>>> Github?
>>>
>>> [1] -
>>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/identity/org.wso2.carbon.identity.mgt/
>>> Cheers~
>>>
>>> --
>>> Dulitha Wijewantha (Chan)
>>> Software Engineer - Mobile Development
>>> WSO2 Inc
>>> Lean.Enterprise.Mobileware
>>>  * ~Email   duli...@wso2.com*
>>> *  ~Mobile +94712112165 <%2B94712112165>*
>>> *  ~Website   dulitha.me *
>>> *  ~Twitter @dulitharw *
>>>   *~Github @dulichan *
>>>   *~SO @chan *
>>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com*
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>>
>
> --
> Dulanja Liyanage
> WSO2 Inc.
> M: +94776764717
>


-- 
Dulitha Wijewantha (Chan)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~Github @dulichan *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

54 matches

Mail list logo