Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC4

2018-06-22 Thread Chamalee De Silva
Hi,
I tested following in API Manager RC4.

1. Basic API flow
- API creation, publishing, invocation etc.
2. Creating users and roles, and user permissions.
3. API documentation
4. Forums in API Store

5. Single Sign On with WSO2 Idnetity Server (WSO2 IS 5.6.0 RC3)
 - SP init and IDP init SSO
 - Assertion Encryption
 - Single logout on/off
 -  SAML request singning in store and publisher.

6. Installing SCIM identity feature in API Manager 2.5.0
7. API Properties
8. SDK generation feature


[+] -  Stable - go ahead and release


Thanks,
Chamalee


On Fri, Jun 22, 2018 at 12:16 PM, Chamin Dias  wrote:

> Hi,
>
> Tested following (for both super tenat and tenat) and no issues found.
>
> a) Label creation/update
> b) Attaching/removing labels to/from APIs
> c) Displaying label information in Publisher and Store
>
> [+] Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jun 22, 2018 at 12:15 PM, Krishan Wijesena 
> wrote:
>
>> Hi,
>> I have tested following and no issues found.
>>
>> 1. Basic API flow
>> - API creation, publishing, invocation.
>> 2. Admin REST API
>> 3. Adding new Throttling policies
>> - Advanced policies
>> - Subscription policies
>> - Application policies
>> - Block list policies
>> 4. Microgateway label add/update REST API
>> 5. Test with browser IE 11
>>  - basic flow (Super tenant/tenant)
>>  - Label add/update
>>
>> [+]Stable - go ahead and release
>>
>> Thanks,
>> krishan.
>>
>>
>>
>> On Thu, Jun 21, 2018 at 10:36 PM, Chamin Dias  wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the fourth release candidate of WSO2 API
>>> Manager 2.5.0.
>>>
>>> This release fixes the following issues.
>>> Fixes : carbon-apimgt
>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-03-16..2018-06-21+-label%3A%22APIM+3.0.0%22>
>>> Fixes : product-apim
>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-03-16..2018-06-21+-label%3A3.0.0>
>>> Fixes : analytics-apim
>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=closed%3A2018-03-16..2018-06-21+is%3Aclosed>
>>>
>>> Source and distribution,
>>> Runtime : https://github.com/wso2/produc
>>> t-apim/releases/tag/v2.5.0-rc4
>>> Analytics : https://github.com/wso2/analyt
>>> ics-apim/releases/tag/v2.5.0-rc1
>>>
>>> Please download, test the product and vote.
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> *Note : We can still use APIM-Analytics 2.5.0-rc1 for analytics (no
>>> issues reported so far).*
>>>
>>> Thanks,
>>> WSO2 API Manager Team.
>>>
>>> --
>>> Chamin Dias
>>> Mobile : 0716097455
>>> Email : cham...@wso2.com
>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Krishan Wijesena*
>> Software Engineer | WSO2
>>
>> Email : krish...@wso2.com
>> Mobile : +94776219923
>> WSO2 Inc : http://wso2.com
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>
>
>
> --
> Chamin Dias
> Mobile : 0716097455
> Email : cham...@wso2.com
> LinkedIn : https://www.linkedin.com/in/chamindias
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Senior Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] How to write unit tests for custom password grant handler.

2018-06-18 Thread Chamalee De Silva
Hi Shiva,
The following unit tests written to test WSO2 grant handlers will be
helpful for you.


[1]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/de2ffd59d1b5197aea8ecde671677578d699f7f7/components/org.wso2.carbon.identity.oauth/src/test/java/org/wso2/carbon/identity/oauth2/token/handlers/grant


Thanks,
Chamalee

On Tue, Jun 19, 2018 at 10:21 AM, Shiva Kumar 
wrote:

> Hi All,
>
> I have written a custom password grant handler, How I can write unit tests
> for that, please provide a hint.
>
> Thanks,
>
> Shiva
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Senior Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC3

2018-06-18 Thread Chamalee De Silva
Hi,
I have tested following and no issues found.

1. Basic API flow
- API creation, publishing, invocation etc.
2. Creating users and roles, and user permissions.

3. Single Sign On with WSO2 Idnetity Server (WSO2 IS 5.6.0 RC3)
 - SP init and IDP init SSO
 - Assertion Encryption
 - Single logout on/off
 -  SAML request singning in store and publisher.

4. Installing SCIM identity feature in API Manager 2.5.0

5. API Properties

6. SDK generation feature


[+]Stable - go ahead and release


Thanks,
Chamalee



On Tue, Jun 19, 2018 at 12:07 AM, Chamin Dias  wrote:

> Hi all,
>
> We are pleased to announce the third release candidate of WSO2 API Manager
> 2.5.0.
>
> This release fixes the following issues.
> Fixes : carbon-apimgt
> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-03-16..2018-06-18+-label%3A%22APIM+3.0.0%22+>
> Fixes : product-apim
> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-03-16..2018-06-18+-label%3A3.0.0>
> Fixes : analytics-apim
> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=closed%3A2018-03-16..2018-06-18+is%3Aclosed>
>
> Source and distribution,
> Runtime : https://github.com/wso2/product-apim/releases/tag/v2.5.0-rc3
> Analytics : https://github.com/wso2/analytics-apim/releases/tag/
> v2.5.0-rc1
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Note : We can still use APIM-Analytics 2.5.0-rc1 for analytics (no issues
> reported so far).
>
> Thanks,
> WSO2 API Manager Team
>
> --
> Chamin Dias
> Mobile : 0716097455
> Email : cham...@wso2.com
> LinkedIn : https://www.linkedin.com/in/chamindias
>
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Senior Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Writing and calling custom admin services for WSO2IS 5.5.0

2018-06-05 Thread Chamalee De Silva
Hi Shiva,

You can refer documentation [1] for calling admin services.
There is no such documentation available on how to write admin services as
they are internally built in WSO2 products,
You can refer the iWSO2 Identity Server source code in github on how they
have constructed.


[1] hhttps://docs.wso2.com/display/IS550/Calling+Admin+Services

On Tue, Jun 5, 2018 at 6:12 PM, Shiva Kumar K R 
wrote:

> Hi All,
> Is there any sources available to write and deploy admin services and
> calling them.
>
> Thank you,
> Shiva
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Senior Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Test failure in axis2 transport when the axis2 version is upgraded

2018-03-13 Thread Chamalee De Silva
Hi Chanika,
Does it mean that the a downgrade to 1.6.1-wso2v23 or going for a newer
version ?





On Wed, Mar 7, 2018 at 5:24 PM, Chanika Geeganage <chan...@wso2.com> wrote:

> Hi,
>
> I tried to upgrade the axis2 version (1.6.1-wso2v24) in
> wso2-axis2-transport repo. I'm getting the following test failures in the
> JMS transport test cases.
>
> org.apache.axis2.AxisFault: Did not receive a JMS response within 3 ms
> to destination : direct://amq.direct/TempQueue3347121a-c9c8-44dc-b1c6-
> 1df603d7d02c/tmp_8af87fef-ddef-4eb9-9655-945482ad6941?
> exclusive='true'='true' with JMS correlation ID :
> ID:94912946-a240-4c95-b21b-f886c0aa9437
> at org.apache.axis2.transport.base.AbstractTransportSender.hand
> leException(AbstractTransportSender.java:234)
> at org.apache.axis2.transport.jms.JMSSender.waitForResponseAndP
> rocess(JMSSender.java:415)
> at org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSend
> er.java:349)
> at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSend
> er.java:205)
> at org.apache.axis2.transport.base.AbstractTransportSender.invo
> ke(AbstractTransportSender.java:119)
> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:525)
> at org.apache.axis2.transport.base.AbstractTransportListener.ha
> ndleIncomingMessage(AbstractTransportListener.java:336)
> at org.apache.axis2.transport.jms.JMSMessageReceiver.processTho
> ughEngine(JMSMessageReceiver.java:214)
> at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(
> JMSMessageReceiver.java:124)
> at org.apache.axis2.transport.jms.ServiceTaskManager$MessageLis
> tenerTask.handleMessage(ServiceTaskManager.java:645)
> at org.apache.axis2.transport.jms.ServiceTaskManager$MessageLis
> tenerTask.run(ServiceTaskManager.java:526)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
> run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> Only the following PRs were merged after 1.6.1-wso2v23 release in axis2.
> If I reverted the fix [1] and tests were passed.
>
> [1] https://github.com/wso2/wso2-axis2/pull/127/files
> [2] https://github.com/wso2/wso2-axis2/pull/132/files
>
> --
> Best Regards..
>
> Chanika Geeganage
> +94773522586 <+94%2077%20352%202586>
> WSO2, Inc.; http://wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Senior Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] WSO2 API Manager 2.1.0-update12 Released !

2018-02-22 Thread Chamalee De Silva
*The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update12 of 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- API Traffic Manager: Performs Rate Limiting of API
RequestsFor more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager
. Also, take a look at the online
product documentation
.
Distributionswso2am-2.1.0-update12.zip
wso2am-analytics-2.1.0-update7.zip

How to Run 1. Extract the downloaded zip2. Go to the bin directory in the
extracted folder3. Run the wso2server.sh or wso2server.bat as appropriate4.
Launch a web browser and navigate to https://localhost:9443/publisher
 to access the API publisher webapp5.
Navigate to https://localhost:9443/store  to
access the API store6. Navigate to https://localhost:9443/admin
 to access Admin Portal7. Use "admin",
"admin" as the username and password to login as an admin Bug Fixes And
Improvements in 2.1.0-update12 - JIRA
- GitHub (Product-apim
),
(Carbon-apimgt
),
(analytics-apim
)
Known IssuesAll the open issues pertaining to WSO2 API Manager are reported
at the following location: - JIRA
- GitHub (Product-apim
),
(Carbon-apimgt
),
(analytics-apim
) How
You Can ContributeMailing ListsJoin our mailing list and correspond with
the developers directly. - Developer List: dev@wso2.org  |
Subscribe | Mail Archive- User List: u...@wso2.org  |
Subscribe | Mail ArchiveReporting IssuesWe encourage you to report issues,
documentation faults, and feature requests regarding WSO2 API Manager
through the public API Manager Git Repo
. -- The WSO2 API Manager Team
--*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] WSO2 API Manager 2.1.0-update11 Released !

2018-02-16 Thread Chamalee De Silva
The WSO2 API Manager team is pleased to announce the release of version
2.1.0-update11 of 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
   -

   API Traffic Manager: Performs Rate Limiting of API Requests

For more information on WSO2 API Manager please visit
http://wso2.com/products/api-manager. Also, take a look at the online
product documentation
.

DistributionWSO2 APIM 2.1.0-update11.zip


WSO2 APIM Analytics 2.1.0-update6.zip

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 publisher webapp
   5.

   Navigate to https://localhost:9443/store to access the API store
   6.

   Navigate to https://localhost:9443/admin to access Admin Portal
   7.

   Use "admin", "admin" as the username and password to login as an admin

Bug Fixes And Improvements in 2.1.0-update11

Please refer following locations for WSO2 API Manager 2.1.0-update11 Bug
fixes and Improvements.


   -

   JIRA 
   -

   GitHub (Product-apim
   
,
   Carbon-apimgt
   

   )

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   -

   JIRA 
   -

   GitHub (Product-apim
   
,
   Carbon-apimgt
   

   )

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List: dev@wso2.org | Subscribe | Mail Archive
   -

   User List: u...@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo
.
 -- The WSO2 API Manager Team --
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM][210][2xx] Fixing Puppet Configuration with missing datasource configuration for MySQL stat database

2018-01-23 Thread Chamalee De Silva
Hi Pubudu,
This is a fix done in order to override the existing common statdb
configuration which comes with the common.yaml of each pattern (3,4,5,6) as
by default that comes with H2.
When we are configuring analytics for a clustered environment, we need to
enable stats for gateway worker and events are published to it as well.

Publisher/store node already have statdb config in each pattern.

What do you mean is it is not required to do the datasource configuration
in gateway worker nodes ?

@Samitha, appreciate your opinion as well on this.



Thanks,
Chamalee

On Tue, Jan 23, 2018 at 10:28 PM, Pubudu Gunatilaka <pubu...@wso2.com>
wrote:

> Hi Chamalee,
>
> Based on your PR you have added stat db for gateway profiles. We don't
> configure stat db for gateways. Normally we don't specify any databases for
> gateways unless we have multi-tenancy and google analytics is enabled.
>
> Thank you!
>
> On Tue, Jan 23, 2018 at 9:52 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> [+dev]
>>
>> On Tue, Jan 23, 2018 at 6:37 PM, Chamalee De Silva <chama...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>> While working on the documentation issue raised in [1]  I could find out
>>> that there is a inconsistency in the data-source URL appeared for
>>> WSO2AM_STATS_DB master datasource configuration in puppet-apim patterns.
>>> (In default configuration it appears as WSO2AM_STAT_DB as the db name and
>>> in mysql configuration of analytics product, it appears as statdb in [2]).
>>>
>>> Other than that for the patterns where the APIM Analytics is configured
>>> (patern 3.4.5 and 6), we haven't added the MySQL master datasource
>>> configuration in API Manager side though it is added to the analytics
>>> product configuration in [3].
>>>
>>> As per the offline discussion had with Samitha, I have fixed this by
>>> adding the master datasource configuration for the gateway-workers in the
>>> patterns where analytics is enabled so that the datasource configuration
>>> will be overridden with mysql configuration.
>>>
>>> Fix is available in PR [4] and [5] for v2.1.0 branch and for the master
>>> branch respectively.
>>>
>>>
>>>
>>> [1] https://github.com/wso2/product-apim/issues/2340
>>> [2] https://github.com/wso2/puppet-apim/tree/master/wso2am_runtime
>>> [3] https://github.com/wso2/puppet-apim/blob/master/wso2am_a
>>> nalytics/hieradata/dev/wso2/wso2am_analytics/pattern-1/default.yaml
>>>
>>> [4] https://github.com/wso2/puppet-apim/pull/59
>>> [5] https://github.com/wso2/puppet-apim/pull/60
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Chamalee De Silva*
>>> Software Engineer
>>> *WS**O2* Inc. :http://wso2.com/
>>>
>>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM][210][2xx] Fixing Puppet Configuration with missing datasource configuration for MySQL stat database

2018-01-23 Thread Chamalee De Silva
[+dev]

On Tue, Jan 23, 2018 at 6:37 PM, Chamalee De Silva <chama...@wso2.com>
wrote:

> Hi all,
> While working on the documentation issue raised in [1]  I could find out
> that there is a inconsistency in the data-source URL appeared for
> WSO2AM_STATS_DB master datasource configuration in puppet-apim patterns.
> (In default configuration it appears as WSO2AM_STAT_DB as the db name and
> in mysql configuration of analytics product, it appears as statdb in [2]).
>
> Other than that for the patterns where the APIM Analytics is configured
> (patern 3.4.5 and 6), we haven't added the MySQL master datasource
> configuration in API Manager side though it is added to the analytics
> product configuration in [3].
>
> As per the offline discussion had with Samitha, I have fixed this by
> adding the master datasource configuration for the gateway-workers in the
> patterns where analytics is enabled so that the datasource configuration
> will be overridden with mysql configuration.
>
> Fix is available in PR [4] and [5] for v2.1.0 branch and for the master
> branch respectively.
>
>
>
> [1] https://github.com/wso2/product-apim/issues/2340
> [2] https://github.com/wso2/puppet-apim/tree/master/wso2am_runtime
> [3] https://github.com/wso2/puppet-apim/blob/master/
> wso2am_analytics/hieradata/dev/wso2/wso2am_analytics/
> pattern-1/default.yaml
>
> [4] https://github.com/wso2/puppet-apim/pull/59
> [5] https://github.com/wso2/puppet-apim/pull/60
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Building XACML-APIManager repository

2018-01-11 Thread Chamalee De Silva
Thanks a lot Nadeesha.

We are going to maintain the entitlement JAR source within the API Manager
from 2.2.0 onwards.
Uvindra is working on it.

I have tested the dependency fixed jar given by Uvindra and it is working
without an issue when we are using Identity Server as PDP as described in
the Documentation [1].
Docs are updated with the fixed jar now.


[1] https://docs.wso2.com/display/AM210/Enabling+Role-
Based+Access+Control+Using+XACML


Thanks,
Chamalee

On Thu, Jan 11, 2018 at 10:29 AM, Nadeesha Gamage <nadee...@wso2.com> wrote:

> Hi Charmalee,
> I have updated the maven file in Git repo to get the latest dependencies
> and the jar is build successfully, however I am unable to test this with
> API M 2.1.0 as XACML features cannot be installed in API Manager 2.1.0.
>
> Thank you,
> Nadeesha
>
> On Thu, Jan 4, 2018 at 3:22 PM, Nadeesha Gamage <nadee...@wso2.com> wrote:
>
>> Hi Chamalee,
>> This was done for API Manager 1.8 or 1.9, I will check on this and get
>> back to you.
>>
>> Nadeesha
>>
>> On Thu, Jan 4, 2018 at 3:15 PM, Chamalee De Silva <chama...@wso2.com>
>> wrote:
>>
>>> Hi Nadeesha,
>>>
>>> This is regarding mail thread [1].
>>> Documentation [2]
>>> <https://docs.wso2.com/display/AM210/Enabling+Role-Based+Access+Control+Using+XACML>
>>> has provided the source of the entitlement-1.0-SNAPSHOT JAR
>>> <https://docs.wso2.com/download/attachments/48269310/entitlement-1.0-SNAPSHOT.jar?version=1=1461127204000=v2>
>>>  as
>>> [3] <https://github.com/nadeesha5814/XACML-APIManager> and when
>>> building it, it fails with following.
>>>
>>> I could reproduce the same which is mentioned in [1].
>>>
>>> Can I know what are the other repositories that need to build to get
>>> this jar built successfully and is this compatible with API Manager 2.1.0 ?
>>>
>>>
>>>
>>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>> MaxPermSize=2048m; support was removed in 8.0
>>> [INFO] Scanning for projects...
>>> [INFO]
>>>
>>> [INFO] 
>>> 
>>> [INFO] Building entitlement 1.0-SNAPSHOT
>>> [INFO] 
>>> 
>>> Downloading: https://server.oosnmp.net/dist
>>> /release/org/apache/bsf/bsf-all/3.0/bsf-all-3.0.pom
>>> [WARNING] The POM for org.eclipse.osgi:org.eclipse.o
>>> sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:javax.serv
>>> let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information
>>> available
>>> [WARNING] The POM for org.eclipse.equinox:org.apache
>>> .jasper:jar:5.5.17.v200806031609 is missing, no dependency information
>>> available
>>> [WARNING] The POM for org.eclipse.equinox:org.apache
>>> .commons.el:jar:1.0.0.v200806031608 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing,
>>> no dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.artifact.repository:ja

[Dev] Building XACML-APIManager repository

2018-01-04 Thread Chamalee De Silva
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.repository.tools:jar:1.0.0.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.repository:jar:1.0.0.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.touchpoint.natives:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.updatechecker:jar:1.1.0.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.preferences:jar:3.2.300.v20090520-1800
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.security:jar:1.0.100.v20090520-1800
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.simpleconfigurator.manipulator:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.updatesite:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.core:org.eclipse.core.commands:jar:3.5.0.I20090429-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.core:org.eclipse.core.contenttype:jar:3.4.0.v20090429-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.core:org.eclipse.core.expressions:jar:3.4.100.v20090429-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.core:org.eclipse.core.net:jar:1.2.0.I20090522-1010
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.core:org.eclipse.core.runtime.compatibility.auth:jar:3.2.100.v20090413
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.ecf:org.eclipse.ecf:jar:3.0.0.v20090520-0800 is missing, no
dependency information available
[WARNING] The POM for
org.eclipse.ecf:org.eclipse.ecf.filetransfer:jar:3.0.0.v20090520-0800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.ecf:org.eclipse.ecf.identity:jar:3.0.0.v20090520-0800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.ecf:org.eclipse.ecf.provider.filetransfer:jar:3.0.0.v20090520-0800
is missing, no dependency information available
[WARNING] The POM for org.eclipse:org.sat4j.core:jar:2.1.0.v20090520 is
missing, no dependency information available
[WARNING] The POM for org.eclipse:org.sat4j.pb:jar:2.1.0.v20090520 is
missing, no dependency information available
[WARNING] The POM for org.eclipse:com.ibm.icu:jar:4.0.1.v20090415 is
missing, no dependency information available
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.534 s
[INFO] Finished at: 2018-01-04T15:05:31+05:30
[INFO] Final Memory: 24M/546M
[INFO]

[ERROR] Failed to execute goal on project entitlement: Could not resolve
dependencies for project
org.wso2.sample.callback:entitlement:jar:1.0-SNAPSHOT: Failed to collect
dependencies at org.wso2.carbon:org.wso2.carbon.apimgt.gateway:jar:1.0.5 ->
org.wso2.carbon:org.wso2.carbon.mediation.initializer:jar:4.0.2 ->
org.wso2.carbon:org.wso2.carbon.mediation.dependency.mgt:jar:4.0.0 ->
org.apache.synapse:synapse-extensions:jar:2.1.0-wso2v6 ->
org.apache.bsf:bsf-all:jar:3.0: Failed to read artifact descriptor for
org.apache.bsf:bsf-all:jar:3.0: Could not transfer artifact
org.apache.bsf:bsf-all:pom:3.0 from/to snmp4j-repo (
https://server.oosnmp.net/dist/release/): hostname in certificate didn't
match:  !=  OR  OR <
oosnmp.net> -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException






[1] XACML jar source
[2]
https://docs.wso2.com/display/AM210/Enabling+Role-Based+Access+Control+Using+XACML
[3] https://github.com/nadeesha5814/XACML-APIManager



Thanks,
Chamalee
-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [IS]Error while running IS

2017-12-18 Thread Chamalee De Silva
eering,
> University of Moratuwa.
>
> *Mobile*: +94776099594 <+94%2077%20609%209594>
> *E-mail*: piraveena...@cse.mrt.ac.lk
> *Blog:* https://medium.com/@piraveenaparalogarajah
> *LinkedIn*: https://www.linkedin.com/in/piraveena-paralogarajah
> <https://www.linkedin.com/in/piraveena-paralogarajah>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Store page is not responding when Add-API call using Jaggery APP.

2017-12-18 Thread Chamalee De Silva
Hi Thivya,

Yes, it is reproducible when you have created an API with using jaggery API
[1] and then publish it (I used UI operations to publish) and even after
login to the API store

And this happens only for the APIs created through Jaggery API directly.
(not for the APIs created through UI or new REST API).

Since we have deprecated  the old REST APIs (Jaggery APIs) [2] in 2.1.0,
can you use the new REST API [3] to continue your task ?

And you can open up a git issue in [4] to get this fixed.



[1]https://docs.wso2.com/display/AM210/publisher+APIs#PublisherAPIs-AddAPI
[2] https://docs.wso2.com/display/AM210/Deprecated+APIs
[3] https://docs.wso2.com/display/AM210/RESTful+APIs
[4] https://github.com/wso2/product-apim/issues


Thanks,
Chamalee

On Mon, Dec 18, 2017 at 1:57 PM, Chamalee De Silva <chama...@wso2.com>
wrote:

> Hi Thivya,
> How did you publish the API ?
> (Since the doc[1] creates an API which is in the created state)
>
>
>
>
>
> [1]https://docs.wso2.com/display/AM210/publisher+APIs#PublisherAPIs-AddAPI
>
> On Mon, Dec 18, 2017 at 1:36 PM, Thivya Mahenthirarasa <thi...@wso2.com>
> wrote:
>
>> Hi Chamalee,
>>
>> This is reproducible even after login to the API Store when you are
>> trying to open the API Console.
>>
>>
>>
>> *Regards,*
>> *THivya*
>>
>> On Mon, Dec 18, 2017 at 1:33 PM, Thivya Mahenthirarasa <thi...@wso2.com>
>> wrote:
>>
>>> Hi Irham,
>>>
>>>
>>>
>>> *Add API [1] is showing the mentioned issue.**Add API with Path
>>> Parameter[2] works fine.*
>>>
>>> The only difference in both is resource
>>>
>>>
>>>- In Add API the resources are added directly.
>>>
>>>
>>> resourceCount=0=GET
>>> 0=Application=Unlimited
>>>
>>>
>>>- In AddAPIWith Parameter the resources are added as swagger
>>>
>>> eg:-
>>> swagger={"paths" : {"/CheckPhoneNumber" : {"post" : {"x-auth-type" :
>>> "Application%20%26%20Application%20User", "x-scope" : "read_number",
>>> "x-throttling-tier" : "Unlimited", "responses" : {"200" : {}}}, "get" :
>>> {"x-auth-type" : "Application%20%26%20Application%20User",
>>> "x-throttling-tier" : "Unlimited", "responses" : {"200" : {}},
>>> "parameters" : [{"name" : "PhoneNumber", "paramType" : "query",
>>> "required" : false, "type" : "string", "description" : "Phone Number",
>>> "in" : "query"}, {"name" : "LicenseKey", "paramType" : "query",
>>> "required" : false, "type" : "string", "description" : "License Key",
>>> "in" : "query"}]}}, "/" : {"put" : {"responses" : {"200" : {}}}, "get" :
>>> {"responses" : {"200" : {}, "swagger" : "2.0", "x-wso2-security" : {
>>> "apim" : {"x-wso2-scopes" : [{"description" : "", "name" : "read_number",
>>> "roles" : "admin", "key" : "read_number"}]}}, "info" : {"title" :
>>> "PhoneVerification", "version" : "1.0.0"}}
>>>
>>>
>>>
>>>
>>> [1]https://docs.wso2.com/display/AM210/publisher+APIs#Publis
>>> herAPIs-AddAPI
>>>
>>> [2] https://docs.wso2.com/display/AM210/publisher+APIs#Publisher
>>> APIs-AddAPIwithPathParameter
>>>
>>> *Regards,*
>>> *Thivya*
>>>
>>> On Mon, Dec 18, 2017 at 12:01 PM, Chamalee De Silva <chama...@wso2.com>
>>> wrote:
>>>
>>>> Hi Thivya,
>>>>
>>>> This is reproducible when you are trying to open the API Console
>>>> without login to the API Store.
>>>> Login to the API so that this "fetching resource list:
>>>> https://10.100.5.39:9443/store/api-docs/admin/PhoneVer
>>>> ification/1.0.0?envName=undefined; Please wait." will go out.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> Chamalee
>>>>
>>>> On Mon, Dec 18, 2017 at 11:53 AM, Irham Iqbal <iq...@wso2.com> wrote:
>>>>
>>>>> Hi Thivya,

Re: [Dev] Store page is not responding when Add-API call using Jaggery APP.

2017-12-18 Thread Chamalee De Silva
Hi Thivya,
How did you publish the API ?
(Since the doc[1] creates an API which is in the created state)





[1]https://docs.wso2.com/display/AM210/publisher+APIs#PublisherAPIs-AddAPI

On Mon, Dec 18, 2017 at 1:36 PM, Thivya Mahenthirarasa <thi...@wso2.com>
wrote:

> Hi Chamalee,
>
> This is reproducible even after login to the API Store when you are trying
> to open the API Console.
>
>
>
> *Regards,*
> *THivya*
>
> On Mon, Dec 18, 2017 at 1:33 PM, Thivya Mahenthirarasa <thi...@wso2.com>
> wrote:
>
>> Hi Irham,
>>
>>
>>
>> *Add API [1] is showing the mentioned issue.**Add API with Path
>> Parameter[2] works fine.*
>>
>> The only difference in both is resource
>>
>>
>>- In Add API the resources are added directly.
>>
>>
>> resourceCount=0=GET
>> 0=Application=Unlimited
>>
>>
>>- In AddAPIWith Parameter the resources are added as swagger
>>
>> eg:-
>> swagger={"paths" : {"/CheckPhoneNumber" : {"post" : {"x-auth-type" :
>> "Application%20%26%20Application%20User", "x-scope" : "read_number",
>> "x-throttling-tier" : "Unlimited", "responses" : {"200" : {}}}, "get" : {
>> "x-auth-type" : "Application%20%26%20Application%20User",
>> "x-throttling-tier" : "Unlimited", "responses" : {"200" : {}},
>> "parameters" : [{"name" : "PhoneNumber", "paramType" : "query",
>> "required" : false, "type" : "string", "description" : "Phone Number",
>> "in" : "query"}, {"name" : "LicenseKey", "paramType" : "query",
>> "required" : false, "type" : "string", "description" : "License Key",
>> "in" : "query"}]}}, "/" : {"put" : {"responses" : {"200" : {}}}, "get" :
>> {"responses" : {"200" : {}, "swagger" : "2.0", "x-wso2-security" : {
>> "apim" : {"x-wso2-scopes" : [{"description" : "", "name" : "read_number",
>> "roles" : "admin", "key" : "read_number"}]}}, "info" : {"title" :
>> "PhoneVerification", "version" : "1.0.0"}}
>>
>>
>>
>>
>> [1]https://docs.wso2.com/display/AM210/publisher+APIs#Publis
>> herAPIs-AddAPI
>>
>> [2] https://docs.wso2.com/display/AM210/publisher+APIs#Publisher
>> APIs-AddAPIwithPathParameter
>>
>> *Regards,*
>> *Thivya*
>>
>> On Mon, Dec 18, 2017 at 12:01 PM, Chamalee De Silva <chama...@wso2.com>
>> wrote:
>>
>>> Hi Thivya,
>>>
>>> This is reproducible when you are trying to open the API Console without
>>> login to the API Store.
>>> Login to the API so that this "fetching resource list:
>>> https://10.100.5.39:9443/store/api-docs/admin/PhoneVer
>>> ification/1.0.0?envName=undefined; Please wait." will go out.
>>>
>>>
>>>
>>> Thanks,
>>> Chamalee
>>>
>>> On Mon, Dec 18, 2017 at 11:53 AM, Irham Iqbal <iq...@wso2.com> wrote:
>>>
>>>> Hi Thivya,
>>>>
>>>> Please share the API request you're sending to add API.
>>>> In addition to that you can create another API from the UI and compare
>>>> the swagger.json and api.json in the registry and find out whats wrong with
>>>> your request.
>>>> Also if your using the sample API request as it is in the doc, which
>>>> one your trying "Add API" or "Add API with Path Parameter"
>>>>
>>>> Thanks,
>>>> Iqbal
>>>>
>>>> On Mon, Dec 18, 2017 at 11:18 AM, Thivya Mahenthirarasa <
>>>> thi...@wso2.com> wrote:
>>>>
>>>>> Hi Team,
>>>>>
>>>>> I'm observing the below line in store only when I created API by using
>>>>> jaggery app in APIM210. I have followed the publicherAPIs Documentaion[1].
>>>>>
>>>>> "fetching resource list: https://10.100.5.39:9443/store
>>>>> /api-docs/admin/PhoneVerification/1.0.0?envName=undefined; Please
>>>>> wait."
>>>>>
>>>>> Steps

Re: [Dev] Store page is not responding when Add-API call using Jaggery APP.

2017-12-17 Thread Chamalee De Silva
Hi Thivya,

This is reproducible when you are trying to open the API Console without
login to the API Store.
Login to the API so that this "fetching resource list:
https://10.100.5.39:9443/store/api-docs/admin/PhoneVerification/1.0.0?
envName=undefined; Please wait." will go out.



Thanks,
Chamalee

On Mon, Dec 18, 2017 at 11:53 AM, Irham Iqbal <iq...@wso2.com> wrote:

> Hi Thivya,
>
> Please share the API request you're sending to add API.
> In addition to that you can create another API from the UI and compare the
> swagger.json and api.json in the registry and find out whats wrong with
> your request.
> Also if your using the sample API request as it is in the doc, which one
> your trying "Add API" or "Add API with Path Parameter"
>
> Thanks,
> Iqbal
>
> On Mon, Dec 18, 2017 at 11:18 AM, Thivya Mahenthirarasa <thi...@wso2.com>
> wrote:
>
>> Hi Team,
>>
>> I'm observing the below line in store only when I created API by using
>> jaggery app in APIM210. I have followed the publicherAPIs Documentaion[1].
>>
>> "fetching resource list: https://10.100.5.39:9443/store
>> /api-docs/admin/PhoneVerification/1.0.0?envName=undefined; Please wait."
>>
>> Steps to reproduce
>> 1. Add an API using jaggery app.
>> 2. Log in to store and click API console
>>
>> Attaching the screenshot.
>>
>>
>> *Highly appreciate your suggestions and responses on this.*
>>
>>
>> [1] https://docs.wso2.com/display/AM210/publisher+APIs#Publisher
>> APIs-AddAPI
>>
>>
>> *Regards,*
>> *Thivya*
>> --
>>
>> *Thivya Mahenthirarasa*
>>
>> *Software Engineer -Support Team | WSO2*
>>
>>
>> *Email: thi...@wso2.com <thi...@wso2.com>*
>>
>> *Mobile: +94766461966 <+94%2076%20646%201966> <http://wso2.com/signature>*
>> *Web: http://wso2.com <http://wso2.com>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer
> WSO2
> phone: +94 777888452
> <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Get geolocation based on ip returns null country

2017-12-05 Thread Chamalee De Silva
t;> ion+Based+Statistics
>>>>> [3] http://blog.rukspot.com/2016/10/configure-wso2-das-310-for-w
>>>>> so2-apim.html
>>>>>
>>>>> Thanks,
>>>>> Lakshman.
>>>>>
>>>>> --
>>>>> Lakshman Udayakantha
>>>>> WSO2 Inc. www.wso2.com
>>>>> lean.enterprise.middleware
>>>>> Mobile: *0717429601*
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Megala Uthayakumar
>>>>
>>>> Software Engineer
>>>> Mobile : 0779967122
>>>>
>>>
>>>
>>>
>>> --
>>> Lakshman Udayakantha
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>> Mobile: *0717429601*
>>>
>>>
>>
>>
>> --
>> Lakshman Udayakantha
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>> Mobile: *0717429601*
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> Thanks & Best Regards,
> *Praneesha Chandrasiri*
> *Technical Writer*
> *WSO2 Inc. *
> *Mobile: +(94) 718156888 <+94%2071%20815%206888>*
> *E-mail: pranee...@wso2.com <pranee...@wso2.com>*
> <http://wso2.com/signature>
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM][2.1.0] "Controlled" visibility Level in API visibility

2017-11-27 Thread Chamalee De Silva
Thanks Praminda.
Merged the changes.



Thanks
Chamalee

On Tue, Nov 28, 2017 at 12:28 PM, Praminda Jayawardana <prami...@wso2.com>
wrote:

> Approved
>
> On Tue, Nov 28, 2017 at 12:14 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi,
>> It seems we have added this up to C5  API definition as well though it is
>> not used.
>> Removed the CONTROLLED visibility from API definition of C5 with PR [1].
>> Please review and approve.
>>
>>
>> [1] https://github.com/wso2/carbon-apimgt/pull/4767
>>
>>
>> On Mon, Nov 27, 2017 at 6:46 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
>> wrote:
>>
>>> Sometimes back we had this feature with API Manager and later we removed
>>> that. With that we can select set of tenants we need to expose our API.
>>> I do not think we have usages of this feature. It was there in APIM
>>> 1.4.0 as remember and removed in 1.6.0 or later version.
>>>
>>> [1]https://docs.wso2.com/display/AM140/API+Visibility
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Mon, Nov 27, 2017 at 5:34 PM, Chamalee De Silva <chama...@wso2.com>
>>> wrote:
>>>
>>>> Hi team,
>>>>
>>>> In our visibility model of API in C4, we have following three types of
>>>> visibility which are documented.
>>>>
>>>>
>>>>- Public:
>>>>-
>>>>
>>>>Restricted by Roles (restrcted)
>>>>-
>>>>
>>>>Visible to my domain: (private)
>>>>
>>>>
>>>> But when checking with the code (I am refering to the C4 code), I could
>>>> found that there is another visibility level called *controlled.*
>>>>
>>>> This *controlled* visibility level goes with a list of
>>>> "visibleTenants", but could not find any usage of it.
>>>> When adding or updating an API as well as when retrieving the API this
>>>> "visibleTenants" is added if available [1].
>>>>
>>>> Can anyone point out what is the use of this controlled visibility
>>>> level and is there a way to control visibility for specific tenants through
>>>> this without UI ?
>>>>
>>>>
>>>> When it comes to subscription availability, there is a
>>>> separate property "subscriptionTenants" for the API, so this
>>>> "visibleTenants" is not related to that.
>>>>
>>>> Any reason for keeping this *controlled* visibility level ?
>>>> Even in the REST API we have added this though it seems not used.
>>>>
>>>>
>>>>
>>>>
>>>> [1] https://github.com/wso2/carbon-apimgt/blob/6.1.x/components/
>>>> apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/
>>>> wso2/carbon/apimgt/hostobjects/APIProviderHostObject.java#L1737
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> *Chamalee De Silva*
>>>> Software Engineer
>>>> *WS**O2* Inc. :http://wso2.com/
>>>>
>>>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>>>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779 <+94%2071%20306%208779>
>>>
>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> <http://sanjeewamalalgoda.blogspot.com/>
>>>
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM][2.1.0] "Controlled" visibility Level in API visibility

2017-11-27 Thread Chamalee De Silva
Hi,
It seems we have added this up to C5  API definition as well though it is
not used.
Removed the CONTROLLED visibility from API definition of C5 with PR [1].
Please review and approve.


[1] https://github.com/wso2/carbon-apimgt/pull/4767


On Mon, Nov 27, 2017 at 6:46 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
wrote:

> Sometimes back we had this feature with API Manager and later we removed
> that. With that we can select set of tenants we need to expose our API.
> I do not think we have usages of this feature. It was there in APIM 1.4.0
> as remember and removed in 1.6.0 or later version.
>
> [1]https://docs.wso2.com/display/AM140/API+Visibility
>
> Thanks,
> sanjeewa.
>
> On Mon, Nov 27, 2017 at 5:34 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi team,
>>
>> In our visibility model of API in C4, we have following three types of
>> visibility which are documented.
>>
>>
>>- Public:
>>-
>>
>>Restricted by Roles (restrcted)
>>-
>>
>>Visible to my domain: (private)
>>
>>
>> But when checking with the code (I am refering to the C4 code), I could
>> found that there is another visibility level called *controlled.*
>>
>> This *controlled* visibility level goes with a list of "visibleTenants",
>> but could not find any usage of it.
>> When adding or updating an API as well as when retrieving the API this
>> "visibleTenants" is added if available [1].
>>
>> Can anyone point out what is the use of this controlled visibility level
>> and is there a way to control visibility for specific tenants through this
>> without UI ?
>>
>>
>> When it comes to subscription availability, there is a separate property
>> "subscriptionTenants" for the API, so this "visibleTenants" is not related
>> to that.
>>
>> Any reason for keeping this *controlled* visibility level ?
>> Even in the REST API we have added this though it seems not used.
>>
>>
>>
>>
>> [1] https://github.com/wso2/carbon-apimgt/blob/6.1.x/components/
>> apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/
>> wso2/carbon/apimgt/hostobjects/APIProviderHostObject.java#L1737
>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779 <+94%2071%20306%208779>
>
> <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.
> blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
>
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [APIM][2.1.0] "Controlled" visibility Level in API visibility

2017-11-27 Thread Chamalee De Silva
Hi team,

In our visibility model of API in C4, we have following three types of
visibility which are documented.


   - Public:
   -

   Restricted by Roles (restrcted)
   -

   Visible to my domain: (private)


But when checking with the code (I am refering to the C4 code), I could
found that there is another visibility level called *controlled.*

This *controlled* visibility level goes with a list of "visibleTenants",
but could not find any usage of it.
When adding or updating an API as well as when retrieving the API this
"visibleTenants" is added if available [1].

Can anyone point out what is the use of this controlled visibility level
and is there a way to control visibility for specific tenants through this
without UI ?


When it comes to subscription availability, there is a separate property
"subscriptionTenants" for the API, so this "visibleTenants" is not related
to that.

Any reason for keeping this *controlled* visibility level ?
Even in the REST API we have added this though it seems not used.




[1]
https://github.com/wso2/carbon-apimgt/blob/6.1.x/components/apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/wso2/carbon/apimgt/hostobjects/APIProviderHostObject.java#L1737




-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

2017-11-24 Thread Chamalee De Silva
[1] Port offsetting the Thrift port in APIM

On Fri, Nov 24, 2017 at 7:01 PM, Chamalee De Silva <chama...@wso2.com>
wrote:

> hi Dushantha,
>
> For API Manager 2.0.0 and later versions, we do not need to configure the
> ThriftClient and ThriftServer ports as they get incremented according to
> the offset.
>
> For API Manager versions prior to APIM 2.0.0 we need to modify these ports
> according to the port offset.
>
> Please refer mail thread [1] for more information.
>
>
>
> Thanks,
> Chamalee
>
> On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga <sami...@wso2.com>
> wrote:
>
>> Hi Dushantha,
>>
>> The point is that by default those thrift port values are commented out.
>> (if they are commented-out the all the port values are changed by the
>> offset value ) If you uncomment them, you have to configure them correctly.
>> By the way in the doc [1] you mentioned, note the below section, under the
>> 3rd point under the topic "Installing and configuring API Manager".
>>
>> [image: Inline image 1]
>>
>> So the doc has been written not considering that optional step of port
>> offsetting. So all ports mentioned in the doc are considering that there
>> are no offsets.
>>
>> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Mana
>> ger+2.0.0
>>
>> Regards,
>> Samitha
>>
>> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne <vidura...@wso2.com
>> > wrote:
>>
>>> Hi Dushantha,
>>>
>>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>>> nodes, then the default Thrift port (10397) in both the nodes will get
>>> offset by the specified offset value.
>>> Eg:
>>> Gateway offset = 2,
>>> Then  will be 10399
>>>
>>> KeyManager offset = 3,
>>> Then  will be 10400
>>>
>>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>>> the Gateway as the Thrift client. Hence the Gateway uses the
>>>  to send a request to the KeyManager where the request is
>>> handled at the . For the communication to happen, both
>>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>>> Gateway) should be of the same value. Unless the port offset of both the
>>> Gateway and the KeyManager is the same, you will have to manually set the
>>> two values.
>>>
>>> Thanks,
>>> Viduranga.
>>>
>>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva <cham...@wso2.com> wrote:
>>>
>>>> This already in the public documentation. Please refer "Changing the
>>>> Thrift client and server ports" section.
>>>>
>>>>
>>>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>>>> +Ports+with+Offset
>>>>
>>>> Thanks,
>>>> Chamara Silva
>>>>
>>>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita <dushan...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi
>>>>> I'm involved in a gateway cluster set up in the local machine where
>>>>> the architecture is explained as follows
>>>>>
>>>>>1. IS 5.3.0 as KM offset 0
>>>>>2. Publisher/store/TM  offset 1
>>>>>3. Gateway worker   offset 3
>>>>>4. GatewayWorkerManger  offset 2
>>>>>
>>>>> I'm following the [1] Clustering API Manager document where it
>>>>> explains
>>>>> Configuring the Gateway > Configure key management related
>>>>> communication. >  c.  Specify the ThriftClientPort and Thrif
>>>>> tServerPort values. 10397 is the default.
>>>>> 10397
>>>>> 10397
>>>>> My query is should this port values be incremented according to the
>>>>> given offset values
>>>>>
>>>>>
>>>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
>>>>> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>>>>>
>>>>>
>>>>> many thanks
>>>>> --
>>>>> *Dushantha Nayanajith Chandima Batuwita*
>>>>> Software Engineer Support | WSO2
>>>>> dushan...@wso2.com
>>>>> mobile : 0094777453010 <077%20745%203010>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Suminda Chamara Silva
>>>> Technical Lead
>

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

2017-11-24 Thread Chamalee De Silva
hi Dushantha,

For API Manager 2.0.0 and later versions, we do not need to configure the
ThriftClient and ThriftServer ports as they get incremented according to
the offset.

For API Manager versions prior to APIM 2.0.0 we need to modify these ports
according to the port offset.

Please refer mail thread [1] for more information.



Thanks,
Chamalee

On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga <sami...@wso2.com>
wrote:

> Hi Dushantha,
>
> The point is that by default those thrift port values are commented out.
> (if they are commented-out the all the port values are changed by the
> offset value ) If you uncomment them, you have to configure them correctly.
> By the way in the doc [1] you mentioned, note the below section, under the
> 3rd point under the topic "Installing and configuring API Manager".
>
> [image: Inline image 1]
>
> So the doc has been written not considering that optional step of port
> offsetting. So all ports mentioned in the doc are considering that there
> are no offsets.
>
> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
> Manager+2.0.0
>
> Regards,
> Samitha
>
> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne <vidura...@wso2.com>
> wrote:
>
>> Hi Dushantha,
>>
>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>> nodes, then the default Thrift port (10397) in both the nodes will get
>> offset by the specified offset value.
>> Eg:
>> Gateway offset = 2,
>> Then  will be 10399
>>
>> KeyManager offset = 3,
>> Then  will be 10400
>>
>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>> the Gateway as the Thrift client. Hence the Gateway uses the
>>  to send a request to the KeyManager where the request is
>> handled at the . For the communication to happen, both
>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>> Gateway) should be of the same value. Unless the port offset of both the
>> Gateway and the KeyManager is the same, you will have to manually set the
>> two values.
>>
>> Thanks,
>> Viduranga.
>>
>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva <cham...@wso2.com> wrote:
>>
>>> This already in the public documentation. Please refer "Changing the
>>> Thrift client and server ports" section.
>>>
>>>
>>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>>> +Ports+with+Offset
>>>
>>> Thanks,
>>> Chamara Silva
>>>
>>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita <dushan...@wso2.com>
>>> wrote:
>>>
>>>> Hi
>>>> I'm involved in a gateway cluster set up in the local machine where the
>>>> architecture is explained as follows
>>>>
>>>>1. IS 5.3.0 as KM offset 0
>>>>2. Publisher/store/TM  offset 1
>>>>3. Gateway worker   offset 3
>>>>4. GatewayWorkerManger  offset 2
>>>>
>>>> I'm following the [1] Clustering API Manager document where it explains
>>>> Configuring the Gateway > Configure key management related
>>>> communication. >  c.  Specify the ThriftClientPort and ThriftServerPort
>>>>  values. 10397 is the default.
>>>> 10397
>>>> 10397
>>>> My query is should this port values be incremented according to the
>>>> given offset values
>>>>
>>>>
>>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
>>>> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>>>>
>>>>
>>>> many thanks
>>>> --
>>>> *Dushantha Nayanajith Chandima Batuwita*
>>>> Software Engineer Support | WSO2
>>>> dushan...@wso2.com
>>>> mobile : 0094777453010 <077%20745%203010>
>>>>
>>>
>>>
>>>
>>> --
>>> Suminda Chamara Silva
>>> Technical Lead
>>> WSO2 Inc.
>>> Mobile: +94718302858 <+94%2071%20830%202858>
>>> blog: http://chamaras.blogspot.com
>>>
>>>
>>> _______
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> *Viduranga Gunarathne*
>>
>> *Software Engineer Intern*
>>
>>
>> *WSO2*
>> Email : vidura...@wso2.com
>> Mobile : +94712437484 <+94%2071%20243%207484>
>> Web : http://wso2.com
>> [image: https://wso2.com/signature] <https://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Samitha Chathuranga
> Software Engineer, WSO2 Inc.
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM 2.1.0] Class not found org.wso2.carbon.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v20

2017-11-22 Thread Chamalee De Silva
 at org.apache.catalina.util.LifecycleBase.start(
> LifecycleBase.java:145)
> at org.apache.catalina.core.ContainerBase$StartChild.call(
> ContainerBase.java:1571)
> at org.apache.catalina.core.ContainerBase$StartChild.call(
> ContainerBase.java:1561)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.wso2.carbon.transport.passthru.PassThroughHttpSender cannot be found
> by axis2_1.6.1.wso2v20
> at org.apache.axis2.deployment.AxisConfigBuilder.
> processTransportSenders(AxisConfigBuilder.java:712)
> at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(
> AxisConfigBuilder.java:124)
> at org.wso2.carbon.core.CarbonAxisConfigurator.
> populateAxisConfiguration(CarbonAxisConfigurator.java:341)
> at org.wso2.carbon.core.CarbonAxisConfigurator.
> getAxisConfiguration(CarbonAxisConfigurator.java:192)
> ... 41 more
> Caused by: java.lang.ClassNotFoundException: 
> org.wso2.carbon.transport.passthru.PassThroughHttpSender
> cannot be found by axis2_1.6.1.wso2v20
> at org.eclipse.osgi.internal.loader.BundleLoader.
> findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.
> DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.axis2.util.Loader.loadClass(Loader.java:261)
> at org.apache.axis2.deployment.AxisConfigBuilder.
> processTransportSenders(AxisConfigBuilder.java:686)
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Enable JWT in gateway node

2017-11-20 Thread Chamalee De Silva
Hi Pubudu,

In a fully distributed set up we can decide in which component (Key Manager
or  Gateway) we need to keep key validation information cache.
Therefore having JWT enabled in Key Manager node only is enough IMO.

To check the values passing to the backend we can use debug logs.



Thanks,
Chamalee

On Mon, Nov 20, 2017 at 8:16 AM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:

> Hi,
>
> Do we need to enable JWT in gateway node [1] in a fully distributed
> deployment where KM/IS is hosted separately?
>
> I can see the JWT is passed to the backend.
>
> *TID: [-1] [] [2017-11-20 10:37:31,347] DEBUG
>> {org.apache.synapse.transport.http.headers} -  http-outgoing-1 >>
>> X-JWT-Assertion: *eyJ0eXAiOiJKV1QiLCJhbGciOiJSUz
>> I1NiIsIng1dCI6ImFfamhOdXMyMUtWdW9GeDY1TG1rVzJPX2wxMCJ9.
>> eyJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1zXC9yb2xlIjpbIkludGVybmFs
>> XC9zdWJzY3JpYmVyIiwiSW50ZXJuYWxcL2NyZWF0b3IiLCJBcHBsaWNhdGlv
>> blwvYWRtaW5fRGVmYXVsdEFwcGxpY2F0aW9uX1BST0RVQ1RJT04iLCJJbnRl
>> cm5hbFwvcHVibGlzaGVyIiwiSW50ZXJuYWxcL2V2ZXJ5b25lIiwiYWRtaW4i
>> XSwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvYXBwbGljYXRpb250aWVy
>> IjoiVW5saW1pdGVkIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wva2V5
>> dHlwZSI6IlBST0RVQ1RJT04iLCJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1z
>> XC92ZXJzaW9uIjoidjEiLCJpc3MiOiJ3c28yLm9yZ1wvcHJvZHVjdHNcL2Ft
>> IiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvYXBwbGljYXRpb25uYW1l
>> IjoiRGVmYXVsdEFwcGxpY2F0aW9uIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2Ns
>> YWltc1wvZW5kdXNlciI6ImFkbWluQGNhcmJvbi5zdXBlciIsImh0dHA6XC9c
>> L3dzbzIub3JnXC9jbGFpbXNcL2VuZHVzZXJUZW5hbnRJZCI6Ii0xMjM0Iiwi
>> aHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvc3Vic2NyaWJlciI6ImFkbWlu
>> IiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvdGllciI6IlVubGltaXRl
>> ZCIsImh0dHA6XC9cL3dzbzIub3JnXC9jbGFpbXNcL2FwcGxpY2F0aW9uaWQi
>> OiIxIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvdXNlcnR5cGUiOiJB
>> UFBMSUNBVElPTiIsImV4cCI6MTUxMTE0NTQ0OSwiaHR0cDpcL1wvd3NvMi5v
>> cmdcL2NsYWltc1wvYXBpY29udGV4dCI6IlwvZmRzYVwvdjEifQ==.
>> ADG30dcwlxBaN7Wxtixc5Wq/gZRj7nZrGHExn0E+7O4pZ6xTSjeVx7UrWSwj31vm7DjL+
>> CvK07popxJqchT8+ACt303BkRxOKgfW66h/XmOxleUlXohQByUe6/
>> 7FTpnFRfyZ7jzttjZct39sBzHcNcyUAEqcl/HEt+eR62/dksM=
>> {org.apache.synapse.transport.http.headers}
>> *TID: [-1] [] [2017-11-20 10:37:31,348] DEBUG
>> {org.apache.synapse.transport.http.wire} -  HTTP-Sender I/O dispatcher-1 <<
>> "X-JWT-Assertion: *eyJ0eXAiOiJKV1QiLCJhbGciOiJSUz
>> I1NiIsIng1dCI6ImFfamhOdXMyMUtWdW9GeDY1TG1rVzJPX2wxMCJ9.
>> eyJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1zXC9yb2xlIjpbIkludGVybmFs
>> XC9zdWJzY3JpYmVyIiwiSW50ZXJuYWxcL2NyZWF0b3IiLCJBcHBsaWNhdGlv
>> blwvYWRtaW5fRGVmYXVsdEFwcGxpY2F0aW9uX1BST0RVQ1RJT04iLCJJbnRl
>> cm5hbFwvcHVibGlzaGVyIiwiSW50ZXJuYWxcL2V2ZXJ5b25lIiwiYWRtaW4i
>> XSwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvYXBwbGljYXRpb250aWVy
>> IjoiVW5saW1pdGVkIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wva2V5
>> dHlwZSI6IlBST0RVQ1RJT04iLCJodHRwOlwvXC93c28yLm9yZ1wvY2xhaW1z
>> XC92ZXJzaW9uIjoidjEiLCJpc3MiOiJ3c28yLm9yZ1wvcHJvZHVjdHNcL2Ft
>> IiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvYXBwbGljYXRpb25uYW1l
>> IjoiRGVmYXVsdEFwcGxpY2F0aW9uIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2Ns
>> YWltc1wvZW5kdXNlciI6ImFkbWluQGNhcmJvbi5zdXBlciIsImh0dHA6XC9c
>> L3dzbzIub3JnXC9jbGFpbXNcL2VuZHVzZXJUZW5hbnRJZCI6Ii0xMjM0Iiwi
>> aHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvc3Vic2NyaWJlciI6ImFkbWlu
>> IiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvdGllciI6IlVubGltaXRl
>> ZCIsImh0dHA6XC9cL3dzbzIub3JnXC9jbGFpbXNcL2FwcGxpY2F0aW9uaWQi
>> OiIxIiwiaHR0cDpcL1wvd3NvMi5vcmdcL2NsYWltc1wvdXNlcnR5cGUiOiJB
>> UFBMSUNBVElPTiIsImV4cCI6MTUxMTE0NTQ0OSwiaHR0cDpcL1wvd3NvMi5v
>> cmdcL2NsYWltc1wvYXBpY29udGV4dCI6IlwvZmRzYVwvdjEifQ==.
>> ADG30dcwlxBaN7Wxtixc5Wq/gZRj7nZrGHExn0E+7O4pZ6xTSjeVx7UrWSwj31vm7DjL+
>> CvK07popxJqchT8+ACt303BkRxOKgfW66h/XmOxleUlXohQByUe6/
>> 7FTpnFRfyZ7jzttjZct39sBzHcNcyUAEqcl/HEt+eR62/dksM=[\r][\n]"
>> {org.apache.synapse.transport.http.wire}
>
>
>
> What is the need to enable JWT in gateway node?
>
> [1] - https://docs.wso2.com/display/AM210/Distributed+
> Deployment+of+API+Manager#DistributedDeploymentofAPIManager-Step3.5-
> ConfiguretheGateway
>
> Thank you!
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Newly created API does not appear in the API manager with the pre-packaged Identity Server as a Key Manager

2017-11-07 Thread Chamalee De Silva
Hi Thomas,

Can you clear out the H2 database and clear the registry mount path once
and try again ?
This might be an issue due to intermediate incorrect mounting
configurations as described in [1].


[1] https://wso2.org/jira/browse/APIMANAGER-2174

On Tue, Nov 7, 2017 at 9:43 PM, Thomas LEGRAND <thomas.legr...@versusmind.eu
> wrote:

> Hello,
>
> I have my API manager which is configured to use the Identity Server as
> Key Manager. But, on the API manager publisher, when I create a new API
> from a swagger file or using the assistant (for the worldbank tuto), I
> don't see any of my API in the list. However, I can see that XML files are
> created via the log of the API manager :
>
> TID: [-1234] [] [2017-11-07 17:04:39,159]  INFO
>> {org.apache.synapse.rest.API} -  Initializing API: admin--WorldBank:v1.0.0
>> {org.apache.synapse.rest.API}
>>
>
> But nothing on my screen:
>
> [image: Images intégrées 1]
>
> I am connected as admin (the default user) and I can't even bind my API to
> an application on the API manager store :/
>
> I double-checked the configuration but I can see an error at the startup
> of the API manager :
>
> TID: [-1234] [] [2017-11-07 17:04:02,197] ERROR {org.wso2.carbon.registry.
> core.internal.RegistryCoreServiceComponent} -  Unable to create fixed
> remote mounts. {org.wso2.carbon.regi
> stry.core.internal.RegistryCoreServiceComponent}
> org.wso2.carbon.registry.core.exceptions.RegistryException: An exception
> occurred while executing handler chain. null
> at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.
> delete(HandlerManager.java:2649)
> at org.wso2.carbon.registry.core.jdbc.handlers.
> UserDefinedHandlerManager.delete(UserDefinedHandlerManager.java:215)
> Caused by: java.lang.NullPointerException
> at org.wso2.carbon.registry.core.jdbc.handlers.builtin.
> MountHandler.delete(MountHandler.java:490)
> at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.
> delete(HandlerManager.java:2627)
> ... 50 more
>
> - Do you have any idea why this error occurs?
> - Is this error linked to the fact I can't see my newly created APIs?
> - CAn you help me, please?
>
> Regards,
>
> Thomas
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Issue when running mysql db script - APIM analytics HA setup

2017-11-07 Thread Chamalee De Silva
Hi Damith,

mysql5.7.sql script has been added for MySQL 5.7 and later versions of
databases.
This is clearly described in the documentation on setting up MySQL
documentation in [1].

If we are going to add this special note, we may have to add this
everywhere where mysql is used.

@team, What is the best option ?


[1] https://docs.wso2.com/display/AM200/Setting+up+MySQL


On Tue, Nov 7, 2017 at 2:20 PM, Damith Wickramasinghe <dami...@wso2.com>
wrote:

> Hi all,
>
> I'm using mysql version 5.7.20. In order to populate userdb and regdb i
> need to run mysql scripts and i have used the scripts in APIM analytics
> pack(mysql.sql). When run below issue arises,
>
> ERROR 1067 (42000): Invalid default value for 'REG_CREATED_TIME'
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
> ERROR 1067 (42000): Invalid default value for 'REG_LAST_UPDATED_TIME'
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>
> Searching the issue found out i need to run NOT mysql.sql but
> mysql5.7.sql. So for wt version does the mysql.sql works ? versions other
> than  5.7 ? IF so we need to mention this clearly in the
> docs . I found the same issue has been occurred for a customer as well.  I
> followed [1].
>
> [1] - https://docs.wso2.com/display/AM210/Minimum+High+
> Availability+Deployment+for+WSO2+APIM+Analytics
>
> Regards,
> Damith.
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> lean.enterprise.middleware
>
> mobile: *+94728671315 <+94%2072%20867%201315>*
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Backend Returning 503 HTTP Status Code

2017-10-06 Thread Chamalee De Silva
Hi Francisco,

I tested this scenario.
To direct this response to the fault-sequence,
You can filter the response from the out-sequence of your proxy service,
and call the fault-sequence you want to invoke inside the out-equence using
a filter mediator.

As a simple example it is like this.


 

   


 
 


Then you can modify the error message as you want in the fault sequence
using a payload factory mediator.






Thanks,
Chamalee



On Thu, Oct 5, 2017 at 11:51 PM, Júnior <fjunio...@gmail.com> wrote:

> Hi,
>
> I have a ESB Proxy that calls a DSS endpoint. This DSS endpoint is under a
> Load Balancer. When the DSS server is down, the Load Balancer returns a 503
> HTTP Error.
>
> It seems strange to me that the flow is going to the outSequence and not
> to the faultSequence.
>
> Is this the expected behavior?
>
> Is it possible to make such case goes to the faultSequence?
>
> The code to send the request is like below:
>
> 
> 
> 
>
> Thanks,
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

2017-09-14 Thread Chamalee De Silva
Thanks for the information Vijitha.




Thanks,
Chamalee





On Thu, Sep 14, 2017 at 5:28 PM, Vijitha Ekanayake <vijit...@wso2.com>
wrote:

> Hi Chamalee,
>
> This feature has been implemented after the ESB 500 release and it should
> be available in EI.
>  You need to add following processors under HttpGetRequestProcessors in
> carbon.xml to get feature to work.
>
> 
> swagger.json
>org.wso2.carbon.mediat
> ion.transport.handlers.requestprocessors.swagger.format.
> SwaggerJsonProcessor
> 
> 
> swagger.yaml
> org.wso2.carbon.mediation.transport.handlers.requestp
> rocessors.swagger.format.SwaggerYamlProcessor
> 
>
>
> Please refer JIRA[1] for more information.
>
>
>
>
> [1]. https://wso2.org/jira/browse/ESBJAVA-4936
>
>
> Thanks,
> Vijitha.
>
> On Thu, Sep 14, 2017 at 4:49 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi Maheeka and ESB team,
>>
>> Is $Subject available in ESB 5.0.0 ?
>> Do we have any documentation on $Subject that we can use to try swagger
>> support on ESB REST APIs ?
>> I found mail thread [1] and JIRA [2] related to this.
>>
>> Appreciate your help.
>>
>> [1] Integration Cloud - ESB on Cloud
>> [2] https://wso2.org/jira/browse/ESBJAVA-3709
>>
>>
>>
>> Thanks,
>> Chamalee
>>
>> On Thu, Sep 29, 2016 at 11:21 AM, Joseph Fonseka <jos...@wso2.com> wrote:
>>
>>> Hi Jagath
>>>
>>> It is the same case weather we provide users to add swagger
>>> annotations/notes to define additional parameters in synapse. If we have
>>> such approch we can use it to define the path parameter type.
>>>
>>> Since we are supporting above in the next iteration we could resolve to
>>> create the path parameter with a default type preferably *string* since it
>>> is less restrictive.
>>>
>>> Also please note swagger spec do not support full URI template
>>> specification.
>>>
>>> Thanks
>>> Jo
>>>
>>> On Tue, Sep 27, 2016 at 11:12 AM, Jagath Sisirakumara Ariyarathne <
>>> jaga...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> While implementing swagger definition for uri-template based APIs, we
>>>> have following problem.
>>>>
>>>> If we have a template like "/view/{symbol}", we need to define "symbol"
>>>> as a parameter in swagger definition. According to the swagger spec for
>>>> parameters[1], if it is a query or path parameter, then it is required to
>>>> have a type (string, number etc) for this parameter. But this information
>>>> is not available in existing synapse configurations of APIs. The possible
>>>> option is to provide all parameters as "string" as Maheeka mentioned
>>>> earlier.
>>>>
>>>> Appreciate any thoughts on this.
>>>>
>>>> [1] - http://swagger.io/specification/#parameterObject
>>>>
>>>> Thanks.
>>>>
>>>> On Tue, Sep 27, 2016 at 5:38 AM, Jagath Sisirakumara Ariyarathne <
>>>> jaga...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I have completed initial implementation for url-mapping based APIs.
>>>>> Attached sample API and its definitions. I am further working on 
>>>>> supporting
>>>>> uri-templates based definitions.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Thu, Sep 22, 2016 at 2:09 PM, Jagath Sisirakumara Ariyarathne <
>>>>> jaga...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> In this particular implementation for Integration Cloud, we planned
>>>>>> to go with an extension which uses existing information in synapse
>>>>>> configurations without updating synapse code base. Therefore as Maheeka
>>>>>> mentioned in [1], we are going to provide limited information at initial
>>>>>> phase. But in long run, we need to extend this to store all required API
>>>>>> definitions in synapse configurations.
>>>>>>
>>>>>> [1] - https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f2
>>>>>> 33f2
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Thu, Sep 22, 2016 at 8:23 AM, Josep

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

2017-09-14 Thread Chamalee De Silva
est API configuration we
>>>>>> can invoke RestApiAdminServices's getApiByName operation which returns 
>>>>>> the
>>>>>> following response [5] for an API created that has the PetStore 
>>>>>> resources.
>>>>>> We can identify the methods and uri-template and mappings from this
>>>>>> response.
>>>>>>
>>>>>> Please let know your thoughts.
>>>>>>
>>>>>> Thanks,
>>>>>> Maheeka
>>>>>>
>>>>>> [1] http://petstore.swagger.io/#/pet
>>>>>> [2] https://gist.github.com/maheeka/4eaedd2e2e0765959a4166865bf9adf9
>>>>>> [3] https://gist.github.com/maheeka/ec23751f21d8d7d5abaa4f9130f233f2
>>>>>> [4] https://www.diffchecker.com/xEu0NSNz
>>>>>> [5] http://schemas.
>>>>>> xmlsoap.org/soap/envelope/">
>>>>>>
>>>>>>   http://org.apache.axis2/xsd
>>>>>> ">
>>>>>>  http://api.rest.carbon.wso2.org/xsd; xmlns:xsi="http://www.w3.org/2
>>>>>> 001/XMLSchema-instance">
>>>>>> 
>>>>>> /pet
>>>>>> PetstoreAPI.xml
>>>>>> 
>>>>>> false
>>>>>> PetstoreAPI
>>>>>> -1
>>>>>> 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>POST
>>>>>>PUT
>>>>>>
>>>>>>
>>>>>>0
>>>>>>
>>>>>>/
>>>>>>
>>>>>> 
>>>>>> 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>POST
>>>>>>DELETE
>>>>>>GET
>>>>>>
>>>>>>
>>>>>>0
>>>>>>/{petId}
>>>>>>
>>>>>>
>>>>>> 
>>>>>> false
>>>>>> false
>>>>>>  
>>>>>>   
>>>>>>
>>>>>> 
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Maheeka Jayasuriya
>>>>>> Senior Software Engineer
>>>>>> Mobile : +9450661
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> --
>>>>> *Joseph Fonseka*
>>>>> WSO2 Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> mobile: +94 772 512 430
>>>>> skype: jpfonseka
>>>>>
>>>>> * <http://lk.linkedin.com/in/rumeshbandara>*
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jagath Ariyarathne
>>>> Technical Lead
>>>> WSO2 Inc.  http://wso2.com/
>>>> Email: jaga...@wso2.com
>>>> Mob  : +94 77 386 7048
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: jaga...@wso2.com
>>> Mob  : +94 77 386 7048
>>> <http://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>> <http://wso2.com/signature>
>>
>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * <http://lk.linkedin.com/in/rumeshbandara>*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Yasima Dewmini

2017-06-30 Thread Chamalee De Silva
Congratulations Yasima 




On Fri, Jun 30, 2017 at 3:03 PM, Harsha Kumara <hars...@wso2.com> wrote:

> Congratulations!
>
> On Fri, Jun 30, 2017 at 1:41 PM, Tharindu Dharmarathna <tharin...@wso2.com
> > wrote:
>
>> Congratulations Yasima!
>>
>>
>> On Fri, Jun 30, 2017 at 1:31 PM, Roshan Wijesena <ros...@wso2.com> wrote:
>>
>>> Congratulations Yasima!
>>>
>>> On Fri, Jun 30, 2017 at 1:20 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>> It's my pleasure to welcome  Yasima Dewmini  as a WSO2 Committer.
>>>>
>>>> Yasima  has been a valuable contributor to the WSO2 API Manager team.
>>>> In recognition of her contribution, dedication, and commitment she has been
>>>> voted as a WSO2 committer.
>>>>
>>>> Yasima, Congratulations and keep up the good work!
>>>>
>>>> Thank You,
>>>> sanjeewa.
>>>> --
>>>>
>>>> *Sanjeewa Malalgoda*
>>>> WSO2 Inc.
>>>> Mobile : +94713068779 <+94%2071%20306%208779>
>>>>
>>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>>> :http://sanjeewamalalgoda.blogspot.com/
>>>> <http://sanjeewamalalgoda.blogspot.com/>
>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: *+94719154640 <+94%2071%20915%204640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>> lean.enterprise.middleware.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Preventing API Developers from updating an API once its Published

2017-03-30 Thread Chamalee De Silva
o the API.
>> 3. Publisher makes the API Created state (or some new state).
>>
>> Now the API is not visible on Store, but existing subscriptions are still
>> valid.
>>
>> The previous API is available on GW, so existing invocations are working
>> without any issue. (This, we did not allow in CREATED state in C4)
>>
>> 4. Developer makes changes to the API
>> 5. Publisher accepts the changes (which means the API's lifecycle is
>> changed to Published)
>> 6. New changes are updated on the GW.
>>
>>
>> Thanks!
>> Malintha
>>
>>
>> Thanks,
>> NuwanD.
>>
>> On Thu, Mar 30, 2017 at 11:52 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>> Hi Nuwan,
>>
>> AFAIU, in this case, we are not addressing the original issue. Original
>> issue here is changes made by API developers should not be reflected in
>> Store and Gateway unless the API publisher publishes the API again. Please
>> correct me if I am wrong.
>>
>> I don't think temporarily removing the API is the best solution if it is
>> already serving requests.
>>
>> What if we introduce another life cycle state and transfer the API to
>> that state until API publisher re-publishes the API. In this way, there is
>> no effect to the existing API.
>>
>> Thank you!
>>
>> On Thu, Mar 30, 2017 at 11:41 PM, Rukshan Premathunga <ruks...@wso2.com>
>> wrote:
>>
>> Hi Nuwan,
>>
>> If we demote API back to create, state how we are going to handle
>> subscription already have? Are we going to disable them till the API get
>> publish again?
>>
>> Also can we introduce or use the existing state to allow the API to be
>> update without un-publishing it. once it is done we can publish it again
>> with the changes. Because in if we demote to create state, we cannot have
>> subscription information right?
>>
>> Thanks and Regards
>>
>> On Thu, Mar 30, 2017 at 11:15 PM, Nuwan Dias <nuw...@wso2.com> wrote:
>>
>> Hi,
>>
>> On API Manager, API Developers (!= publishers) aren't able to publish an
>> API to the Store or Gateway. But on API Manager version 2.1.0 and before,
>> if an API Developer makes an update to an API that is already published,
>> the changes made by the developer are immediately reflected on the Store
>> and Gateway. This kind of beats the purpose of preventing API Developers
>> from publishing APIs to the Store and Gateway directly.
>>
>> For API Manager 3.0.0, I suggest that we prevent the API being updated by
>> API Developers after the API has gone beyond the "CREATED" state. API
>> Publishers should still be allowed to make updates to the fields they are
>> eligible for (non technical information). If someone badly needs to update
>> technical information of a published API, they should first bring the API
>> to the "CREATED" state, which will make the API disappear temporarily and
>> bring it back to "PUBLISHED" once the changes are saved.
>>
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>
>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Senior Software Engineer, WSO2
>
> LinkedIn: https://lk.linkedin.com/in/rajuu
> Mobile: +1 408 791 7640 <(408)%20791-7640>
> Blogs: http://wso2tech.blogspot.com/ | https://medium.com/@wso2tech
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Lakshani Gamage

2017-03-14 Thread Chamalee De Silva
Congrats Lakshani !!!

On Tue, Mar 14, 2017 at 12:32 PM, Harshan Liyanage <hars...@wso2.com> wrote:

> Congratz Lakshani 
>
> Harshan Liyanage
> EMM/IoT TG
> Mobile: *+94765672894*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
> lean.enterprise.middleware.
>
> On Tue, Mar 14, 2017 at 11:43 AM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Congratz Lakshani!
>>
>> On Tue, Mar 14, 2017 at 9:42 AM, Rushmin Fernando <rush...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to welcome Lakshani Gamage as a WSO2 Committer.
>>>
>>> Lakshani had been a valuable contributor to the App Manager team and
>>> she is currently a member of the IoT team. In recognition of her
>>> contribution, dedication, and commitment she has been voted as a WSO2
>>> committer.
>>>
>>> Lakshani, welcome aboard and keep up the good work!
>>>
>>> Regards,
>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>>
>>> mobile : +94775615183
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Menaka Jayawardena*
>> *Software Engineer - WSO2 Inc*
>> *Tel : 071 350 5470*
>> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>*
>> *Blog: https://menakamadushanka.wordpress.com/
>> <https://menakamadushanka.wordpress.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
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Identity Server 5.3.0 as a Key Manager with API Manager 2.1.0

2017-02-15 Thread Chamalee De Silva
hi Gottfried,


The new documentation are ready and please refer [1] or [2] according to
your requirement.

@Darshana,
Yes, It is available at [3].



[1] https://docs.wso2.com/display/AM210/Configuring+
WSO2+Identity+Server+as+a+Key+Manager
[2] https://docs.wso2.com/display/AM210/Configuring+the+
Pre-Packaged+Identity+Server+with+API+Manager
[3]  http://product-dist.wso2.com/downloads/api-manager/2.1.0/
identity-server/wso2is-5.3.0.zip



hi Go

On Wed, Feb 15, 2017 at 6:20 PM, Darshana Gunawardana <darsh...@wso2.com>
wrote:

>
>
> On Tue, Feb 14, 2017 at 11:00 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Now it is possible to use IS as KM with API Manager 2.1.0.
>> The P2 repo [1] is updated with the Key Manager features and by
>> installing Key Manager version 6.1.66 in WSO2 IS 5.3.0 you will be able to
>> use IS as Key Manager for API Manager 2.1.0.
>> The configuration steps are almost same as in the documentation [2].
>>
>> We are in the process of updating the documentation for Configuring WSO2
>> IS 5.3.0 as Key Manager for WSO2 API Manager 2.1.0 and the new
>> documentation will be available soon.
>>
>
> Thanks Chamalee for the response. Will there be a pre configured IS as Key
> Manager for IS 5.3.0 + APIM 2.1.0 for download?
>
> Regards,
>
>>
>> We will update this thread when the documentation is available.
>>
>>
>> [1] http://product-dist.wso2.com/p2/carbon/releases/wilkes/
>> [2] https://docs.wso2.com/display/CLUSTER44x/Configuring+the
>> +Identity+Server+5.2.0+as+a+Key+Manager+with+API+Manager+2.0.0
>>
>>
>> Thanks,
>> Chamalee
>>
>> On Tue, Feb 14, 2017 at 9:18 PM, Darshana Gunawardana <darsh...@wso2.com>
>> wrote:
>>
>>> Hi Chamalee,
>>>
>>> Do you know the timelines of this?
>>>
>>> Thanks,
>>>
>>> On Tue, Feb 14, 2017 at 7:13 PM, Gottfried Szing <gottfr...@szing.eu>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> Is there a timeline when it is possible to use Identity Server 5.3.0 as
>>>> a Key Manager with API Manager 2.1.0?
>>>>
>>>> Following the documentation for IS 5.2.0/AM 2.0.0 at
>>>> https://docs.wso2.com/x/CKJlAw for the above setup always fails, no
>>>> matter which version (5.0.3, 6.0.4, 6.1.66) of the keymanager is chosen.
>>>> And a newer documenation is not available.
>>>>
>>>> Br,
>>>>   Gottfried
>>>> _______
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com <darsh...@wso2.com>*
>>> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
>>> Middleware
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com <darsh...@wso2.com>*
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Identity Server 5.3.0 as a Key Manager with API Manager 2.1.0

2017-02-14 Thread Chamalee De Silva
hi Gottfried,

I confirm Farasath's and Abimaran's comments.
As they have pointed out, this error is harmless and can be ignored.




Thanks,
Chamalee.


On Wed, Feb 15, 2017 at 7:44 AM, Abimaran Kugathasan <abima...@wso2.com>
wrote:

>
>
> On Wed, Feb 15, 2017 at 1:50 AM, Gottfried Szing <gottfr...@szing.eu>
> wrote:
>
>> Hi Chamalee,
>>
>> Now it is possible to use IS as KM with API Manager 2.1.0. The P2 repo
>>> [1] is updated with the Key Manager
>>> features and by installing Key Manager version 6.1.66 in WSO2 IS 5.3.0
>>> you will be able to use IS as Key
>>> Manager for API Manager 2.1.0. The configuration steps are almost same
>>> as in the documentation [2].
>>>
>>> We are in the process of updating the documentation for Configuring WSO2
>>> IS 5.3.0 as Key Manager for WSO2
>>> API Manager 2.1.0 and the new documentation will be available soon.
>>>
>>> We will update this thread when the documentation is available.
>>>
>>
>> Thanks for your response and I have already tried the version 6.1.66 from
>> the repository. In the UI the installation works without any message, but
>> in the logs an error shows up immediately after installing the feature. So,
>> this error is logged before doing the restart.
>>
>> [2017-02-14 21:04:20,564]  INFO {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -
>> 'admin@carbon.super [-1234]' logged in at [2017-02-14 21:04:20,564+0100]
>> java.io.FileNotFoundException:
>> /build/release-builds/pulasthim/product-is/target/checkout/m
>> odules/p2-profile-gen/target/wso2carbon-core-4.4.11/reposito
>> ry/components/artifacts.xml
>> (No such file or directory)
>> at java.io.FileOutputStream.open0(Native Method)
>> at java.io.FileOutputStream.open(FileOutputStream.java:270)
>> at java.io.FileOutputStream.(FileOutputStream.java:213)
>> at java.io.FileOutputStream.(FileOutputStream.java:162)
>>
>>
>> And during restart of the server itself, three different error messages
>> shows up.
>>
>> [2017-02-14 21:15:40,358] ERROR {org.wso2.carbon.apimgt.impl.utils.APIUtil}
>> -  Custom sequence template location unavailable for custom sequence type
>> in : repository/resources/customsequences/in
>> [2017-02-14 21:15:40,358] ERROR {org.wso2.carbon.apimgt.impl.utils.APIUtil}
>> -  Custom sequence template location unavailable for custom sequence type
>> out : repository/resources/customsequences/out
>> [2017-02-14 21:15:40,358] ERROR {org.wso2.carbon.apimgt.impl.utils.APIUtil}
>> -  Custom sequence template location unavailable for custom sequence type
>> fault : repository/resources/customsequences/fault
>>
>> None of this happened with the IS 5.2 + AM 2.0, so I am not sure if this
>> can be ignored or if this is a serious issue.
>>
>
> These were there in IS 5.2 + AM 2.0 (if you have installed the feature
> rather than using Pre-Packaged IS) too and can be ignored.
>
>
>>
>> Br & Thanks,
>>   Gottfried
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <+94%2077%20392%202820>
>
> <http://stackoverflow.com/users/515034>
> <http://lk.linkedin.com/in/abimaran>
> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
> <https://twitter.com/abimaran>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Identity Server 5.3.0 as a Key Manager with API Manager 2.1.0

2017-02-14 Thread Chamalee De Silva
Hi,

Now it is possible to use IS as KM with API Manager 2.1.0.
The P2 repo [1] is updated with the Key Manager features and by installing
Key Manager version 6.1.66 in WSO2 IS 5.3.0 you will be able to use IS as
Key Manager for API Manager 2.1.0.
The configuration steps are almost same as in the documentation [2].

We are in the process of updating the documentation for Configuring WSO2 IS
5.3.0 as Key Manager for WSO2 API Manager 2.1.0 and the new documentation
will be available soon.

We will update this thread when the documentation is available.


[1] http://product-dist.wso2.com/p2/carbon/releases/wilkes/
[2] https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Identity+
Server+5.2.0+as+a+Key+Manager+with+API+Manager+2.0.0


Thanks,
Chamalee

On Tue, Feb 14, 2017 at 9:18 PM, Darshana Gunawardana <darsh...@wso2.com>
wrote:

> Hi Chamalee,
>
> Do you know the timelines of this?
>
> Thanks,
>
> On Tue, Feb 14, 2017 at 7:13 PM, Gottfried Szing <gottfr...@szing.eu>
> wrote:
>
>> Hi
>>
>> Is there a timeline when it is possible to use Identity Server 5.3.0 as a
>> Key Manager with API Manager 2.1.0?
>>
>> Following the documentation for IS 5.2.0/AM 2.0.0 at
>> https://docs.wso2.com/x/CKJlAw for the above setup always fails, no
>> matter which version (5.0.3, 6.0.4, 6.1.66) of the keymanager is chosen.
>> And a newer documenation is not available.
>>
>> Br,
>>   Gottfried
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Associate Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com <darsh...@wso2.com>*
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 API Manager 2.1.0 RC5

2017-02-03 Thread Chamalee De Silva
Tested following.

1. Response caching
2. IS as KM with WSO2 IS 5.3.0
3. Single Sign On with WSO2 IS 5.3.0 (SP initiated SSO) with and without
Single Logout.
4 Publishing to multiple in ST and Tenant external Stores
5. Provisioning out of band auth Clients
6. Installing as a windows Service
7. Analytics for Publisher, Store and admin Portal on Windows
8. SDK generation Feature
9. Database functionalities with following databases.

   -  mysql 5.6, 5.7
   -  DB2
   -  PostgreSQL 9.3
   -  MSSQL
   -  Oracle 11g






No issues found

[+] Stable   -   go ahead and release



Thanks,
Chamalee





On Thu, Feb 2, 2017 at 11:32 PM, Malintha Amarasinghe <malint...@wso2.com>
wrote:

> Hi All,
>
> This is the 5th Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-apim/releases/
> download/v2.1.0-rc5/wso2am-2.1.0-RC5.zip
> Analytics : https://github.com/wso2/analytics-apim/releases/download/v
> 2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
> g/v2.1.0-rc2
>
>
> This release fixes the following issues:
> Runtime : https://wso2.org/jira/issues/?filter=13623
> Analytics : https://wso2.org/jira/issues/?filter=13624
> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 API Manager Team -
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306 <+94%2071%20238%203306>
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Chamalee De Silva
Tested following.

1. Basic API functionalities and API documentation functionalities.
2. Single Sign On with WSO2 IS 5.3.0 ( Publisher/Store/admin/carbon) - [ SP
initiated SSO ] with and without Single Logout.
3. IS as Key Manager with WSO2 IS 5.3.0
4. Database functionalities with following databases
MySQL 5.6, 5,7
Oracle 11g
PostgreSQL 9.3
MSSQL
DB2
5. Publishing APIs for External Stores in both tenant and super tenant
6. Provisioning out of band auth Clients
7. Analytics for Publisher and Store (for Linux and Windows)
8. SDK generation feature (for admin, non admin, self signup users in both
super tenant & tenant)
9. Account Recovery and Credential Management feature installation

No issues found.

[+]   Stable   - go ahead and release.




Thanks,
Chamalee

On Tue, Jan 31, 2017 at 11:00 AM, Tharindu Dharmarathna <tharin...@wso2.com>
wrote:

> Tested Subscription level throttling in tenant and super tenant.
>
> [+]   Stable   - go ahead and release
>
> On Tue, Jan 31, 2017 at 10:47 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:
>
>> Hi,
>>
>> Tested following.
>>
>>-
>>- Alert generation
>>- Alert subscription
>>
>> [+]   Stable   - go ahead and release
>>
>> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe <
>> malint...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>>
>>> Please download, test the product and vote. The vote will be open for 72
>>> hours or as needed.
>>>
>>> Source and distribution
>>>
>>> Run-time : https://github.com/wso2/prod
>>> uct-apim/releases/download/v2.1.0-rc4/wso2am-2.1.0-RC4.zip
>>> Analytics : https://github.com/wso2/anal
>>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>>> g/v2.1.0-rc2
>>>
>>>
>>> This release fixes the following issues:
>>> Runtime : https://wso2.org/jira/issues/?filter=13623
>>> Analytics : https://wso2.org/jira/issues/?filter=13624
>>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>>
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 API Manager Team -
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> Fazlan Nazeem
>>
>> *Software Engineer*
>>
>> *WSO2 Inc*
>> Mobile : +94772338839
>> <%2B94%20%280%29%20773%20451194>
>> fazl...@wso2.com
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <+94%2077%20910%209091>*
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC3

2017-01-15 Thread Chamalee De Silva
Hi all,

We are calling off the vote due to an L1 issue [1] found in SSO flow in
tenant mode.
We will do an RC4 soon.



[1] https://wso2.org/jira/browse/APIMANAGER-5579



Thanks,
Chamalee

On Mon, Jan 16, 2017 at 11:04 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:

> Hi,
>
> I have tested the following.
>
>- Alert generation
>- Alert configuration changes
>- Alert deactivation/activation
>
> [+] Stable - go ahead and release
>
>
> On Mon, Jan 16, 2017 at 10:55 AM, Rukshan Premathunga <ruks...@wso2.com>
> wrote:
>
>> Tested Analytics for tenant and super tenant. No issues found.
>>
>> [+] Stable - go ahead and release
>>
>> Thanks and Regards.
>>
>> On Mon, Jan 16, 2017 at 10:49 AM, Praminda Jayawardana <prami...@wso2.com
>> > wrote:
>>
>>> Tested client SDK generation for super tenant, non admin, tenant and
>>> self signup users.
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> Praminda
>>>
>>> On Mon, Jan 16, 2017 at 10:08 AM, Arshardh Ifthikar <arsha...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Tested Websocket API feature.
>>>>
>>>> [+] Stable - go ahead and release
>>>>
>>>> On Mon, Jan 16, 2017 at 10:01 AM, Chamila Adhikarinayake <
>>>> chami...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Tested workflows for API lifecycle state change feature.
>>>>>
>>>>> [+] Stable - go ahead and release
>>>>>
>>>>> On Fri, Jan 13, 2017 at 6:23 PM, Malintha Amarasinghe <
>>>>> malint...@wso2.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> This is the 3rd Release Candidate of WSO2 API Manager 2.1.0
>>>>>>
>>>>>> Please download, test the product and vote. The vote will be open for
>>>>>> 72 hours or as needed.
>>>>>>
>>>>>> Source and distribution
>>>>>>
>>>>>> Run-time : https://github.com/wso2/prod
>>>>>> uct-apim/releases/download/v2.1.0-rc3/wso2am-2.1.0-RC3.zip
>>>>>> Analytics : https://github.com/wso2/anal
>>>>>> ytics-apim/releases/download/v2.1.0-rc2/wso2am-analytics-2.1
>>>>>> .0-RC2.zip
>>>>>> Tooling : https://github.com/wso2/devs
>>>>>> tudio-tooling-apim/releases/tag/v2.1.0-rc2
>>>>>>
>>>>>>
>>>>>> This release fixes the following issues:
>>>>>> Runtime : https://wso2.org/jira/issues/?filter=13623
>>>>>> Analytics : https://wso2.org/jira/issues/?filter=13624
>>>>>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>>>>>
>>>>>>
>>>>>> Please vote as follows.
>>>>>> [+] Stable - go ahead and release
>>>>>> [-] Broken - do not release (explain why)
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> - WSO2 API Manager Team -
>>>>>>
>>>>>> --
>>>>>> Malintha Amarasinghe
>>>>>> Software Engineer
>>>>>> *WSO2, Inc. - lean | enterprise | middleware*
>>>>>> http://wso2.com/
>>>>>>
>>>>>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>>>>>
>>>>>> ___
>>>>>> Architecture mailing list
>>>>>> architect...@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Chamila Adhikarinayake
>>>>> Software Engineer
>>>>> WSO2, Inc.
>>>>> Mobile - +94712346437 <+94%2071%20234%206437>
>>>>> Email  - chami...@wso2.com
>>>>> Blog  -  http://helpfromadhi.blogspot.com/
>>>>>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Arshardh Ifthikar*
>>>> Trainee Software Engineer
>>>> WSO2, Inc.
>>>> Mobile: +94719806525 <+94%2071%20980%206525>
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Praminda Jayawardana*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC3

2017-01-14 Thread Chamalee De Silva
Hi,

Tested the following for both tenant and super tenant users.

   - Database functionalities with following databases.

  -  MySQL 5.6, 5.7
  -  Oracle 11g
  -  PostgreSQL  9.3
  -  MSSQL

   - API Invocation scenarios for new REST APIs including sample API.
   - API documentation functionalities
   - API visibility and versioning


[+]  Stable   -   go ahead and release


On Sun, Jan 15, 2017 at 9:33 AM, Nuwandi Wickramasinghe <nuwan...@wso2.com>
wrote:

> Tested following.
>
>- 3rd party key management for super tenant and tenant users
>- APIMANAGER-5530
>- APIMANAGER-5510
>- APIMANAGER-5370
>
> [+] Stable - go ahead and release
>
> On Fri, Jan 13, 2017 at 6:23 PM, Malintha Amarasinghe <malint...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc3/wso2am-2.1.0-RC3.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc2/wso2am-analytics-2.1.0-RC2.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> Mobile : 0719214873
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Ldap UserStore Configuration: Use of Auxiliary Object Classes

2017-01-13 Thread Chamalee De Silva
Hi Kawas,

Please refer [1] for creating auxiliary object Classes in WSo2 Identity
Server to be used with LDAP servers.
This may answer your question.


[1]
http://hasini-gunasinghe.blogspot.com/2011/02/how-to-introduce-custom-attributes-to.html


Thanks,
Chamalee

On Wed, Jan 11, 2017 at 7:21 PM, kawas <kawa...@gmail.com> wrote:

> Hello,
>
> Using Ldap as a UserStore, I want to use custom attributes for my users
> mainly in claims mapping.
>
> I don't really like the idea of creating a new objectClass in Ldap and
> configure WSO2 IS accordingly,
> - Would it be possible to specify optional auxiliary objectClasses in
> UserStore configuration ?
>
>
> Regards,
>
> Kawas
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.11 RC1

2016-12-21 Thread Chamalee De Silva
Tested with API Manager database functionalities for following databases.

   -  Oracle 11g
   -  MySQL 5.6
   - PostgreSQL 9.3


No issues found.

[x] Stable  -  Go ahead and release



On Wed, Dec 21, 2016 at 3:26 PM, Praminda Jayawardana <prami...@wso2.com>
wrote:

> Tested with APIM (basic functionality testing and integration tests). No
> issues found.
>
>  [x] Stable -Go ahead and release
>
>
> On Wed, Dec 21, 2016 at 3:19 PM, Vindula Jayawardana <vind...@wso2.com>
> wrote:
>
>>
>> Built IS 5.3.0 SNAPSHOT and found no issues in identity provisioning.
>>
>>
>>> [x] Stable  - Go ahead and release
>>>
>>> --
>> *Vindula Jayawardana*
>> Trainee Software Engineer
>> Mobile : +94 713 462554 <+94%2071%20346%202554>
>> Email : vind...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Chamalee De Silva
Hi,
I have done following tests.

 Basic API Flow
 SAML2 Grant type with IS 5.2.0 beta2


No issues found.

[+] Stable - go ahead and release
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

2016-07-22 Thread Chamalee De Silva
Tested


   - basic API flow
   - SSO with IS 5.2.0 beta2
   - Reverse Proxy with SSO with IS 5.2.0 beta2


and no issues found.


[x] - Stable - Go ahead and release.




On Fri, Jul 22, 2016 at 11:28 AM, Rukshan Premathunga <ruks...@wso2.com>
wrote:

> Tested analytics and smoke tested APIM on db2, mssql, mysql, mysql5.7,
> oracle, postgre and h2.
>
> No issues found.
>
> [+] - Stable - go ahead and release
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 10:48 AM, Thilini Cooray <thili...@wso2.com>
> wrote:
>
>> Tested
>>
>>- API import-export
>>- Store Self Sign-up
>>- Store search
>>- Tested main functionalities with MySQL, PostgreSQL and on Windows
>>
>> No issues found.
>>
>> [+] - Stable - go ahead and release
>>
>> Thanks.
>>
>>
>> On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan <abima...@wso2.com>
>> wrote:
>>
>>> *WSO2 API Manager 2.0.0-RC4 Released*
>>>
>>> This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC4 :
>>>
>>>  Runtime :
>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
>>>  Analytics :
>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> <http://stackoverflow.com/users/515034>
>>> <http://lk.linkedin.com/in/abimaran>
>>> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
>>> <https://twitter.com/abimaran>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

2016-07-20 Thread Chamalee De Silva
+ Tested Reverse Proxy as well while having Single Sign On using IS 5.2.0
beta2 for tenant and super tenant.


Thanks,
Chamalee

On Thu, Jul 21, 2016 at 11:05 AM, Chamalee De Silva <chama...@wso2.com>
wrote:

> Tested
>  - basic API Flow
> - Single Sign On using IS 5.2.0 beta2 for tenant and super tenant.
>
>
> No issues found.
>
> [x] - Stable -go ahead and release.
>
>
>
> On Thu, Jul 21, 2016 at 8:45 AM, Nuwan Dias <nuw...@wso2.com> wrote:
>
>> Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
>> basic scenarios for tenant and super tenant users. No issues found.
>>
>> [x] - Stable - go ahead and release
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan <abima...@wso2.com>
>> wrote:
>>
>>> It's there in the github release page of both API Manager Runtime and
>>> Analytics,
>>>
>>> On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
>>>> Hi Abimaran,
>>>>
>>>> Shouldn't we include a list of bugs fixed and features added in the
>>>> release vote? Ideally this should be a JIRA filter link.
>>>>
>>>> Thanks.
>>>>
>>>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan <
>>>> abima...@wso2.com> wrote:
>>>>
>>>>>
>>>>> *WSO2 API Manager 2.0.0-RC3 Released*
>>>>>
>>>>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>>>>
>>>>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>>>>
>>>>>  Runtime :
>>>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>>>>  Analytics :
>>>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>>>
>>>>> Please download, test the product and vote. Vote will be open for 72
>>>>> hours or as needed.
>>>>> Refer to github readme for guides.
>>>>>
>>>>> Please vote as follows.
>>>>> [+] Stable - go ahead and release
>>>>> [-]  Broken - do not release (please explain why)
>>>>>
>>>>> --
>>>>> Thanks
>>>>> Abimaran Kugathasan
>>>>> Senior Software Engineer
>>>>>
>>>>> Email : abima...@wso2.com
>>>>> Mobile : +94 773922820
>>>>>
>>>>> <http://stackoverflow.com/users/515034>
>>>>> <http://lk.linkedin.com/in/abimaran>
>>>>> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
>>>>> <https://twitter.com/abimaran>
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Akila Ravihansa Perera
>>>> WSO2 Inc.;  http://wso2.com/
>>>>
>>>> Blog: http://ravihansa3000.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> <http://stackoverflow.com/users/515034>
>>> <http://lk.linkedin.com/in/abimaran>
>>> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
>>> <https://twitter.com/abimaran>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC3

2016-07-20 Thread Chamalee De Silva
Tested
 - basic API Flow
- Single Sign On using IS 5.2.0 beta2 for tenant and super tenant.


No issues found.

[x] - Stable -go ahead and release.



On Thu, Jul 21, 2016 at 8:45 AM, Nuwan Dias <nuw...@wso2.com> wrote:

> Tested Identity Server as Key Manager using IS 5.2.0 Beta2. Tested the
> basic scenarios for tenant and super tenant users. No issues found.
>
> [x] - Stable - go ahead and release
>
> Thanks,
> NuwanD.
>
>
> On Thu, Jul 21, 2016 at 7:15 AM, Abimaran Kugathasan <abima...@wso2.com>
> wrote:
>
>> It's there in the github release page of both API Manager Runtime and
>> Analytics,
>>
>> On Thu, Jul 21, 2016 at 7:12 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Abimaran,
>>>
>>> Shouldn't we include a list of bugs fixed and features added in the
>>> release vote? Ideally this should be a JIRA filter link.
>>>
>>> Thanks.
>>>
>>> On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan <abima...@wso2.com
>>> > wrote:
>>>
>>>>
>>>> *WSO2 API Manager 2.0.0-RC3 Released*
>>>>
>>>> This is the 3rd Release Candidate of the WSO2 API Manager 2.0.0
>>>>
>>>> Source & binary distribution files of API Manager 2.0.0-RC3 :
>>>>
>>>>  Runtime :
>>>> https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc3
>>>>  Analytics :
>>>> https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>>>>
>>>> Please download, test the product and vote. Vote will be open for 72
>>>> hours or as needed.
>>>> Refer to github readme for guides.
>>>>
>>>> Please vote as follows.
>>>> [+] Stable - go ahead and release
>>>> [-]  Broken - do not release (please explain why)
>>>>
>>>> --
>>>> Thanks
>>>> Abimaran Kugathasan
>>>> Senior Software Engineer
>>>>
>>>> Email : abima...@wso2.com
>>>> Mobile : +94 773922820
>>>>
>>>> <http://stackoverflow.com/users/515034>
>>>> <http://lk.linkedin.com/in/abimaran>
>>>> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
>>>> <https://twitter.com/abimaran>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> <http://stackoverflow.com/users/515034>
>> <http://lk.linkedin.com/in/abimaran>
>> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
>> <https://twitter.com/abimaran>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

2016-07-04 Thread Chamalee De Silva
P.S. Test done base done API Manager 2.0.0 beta-2

On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva <chama...@wso2.com> wrote:

> Hi,
> I tested the kernel 4.4.7 RC1 with
>
> MySQL 5.6 and  5.7,
> Oracle 11g,
> PostgreSQL 9.3
>
> and they worked without an issue.
>
> [x] Stable - go ahead and release.
>
>
>
> Thanks,
> Chamalee
>
> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage <anup...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
>> issue related to this RC.
>>
>> *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6
>> is observed. Hope this will be fixed in a future release.
>>
>> [1] https://wso2.org/jira/browse/CARBON-15973
>>
>> Regards,
>> Anupama
>>
>> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <shash...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I tested the kernal with following databases and no issues observed.
>>>
>>> Test Area:
>>> Add/ Delete resource (inline text) and collection
>>> Add/Remove user and role
>>>
>>> Databases:
>>> mysql 5.5.
>>> mysql 5.7
>>> postgres 9.3
>>> oracle 12c
>>>
>>> Regards,
>>> Shashika
>>>
>>> Shashika Ubhayaratne
>>> Associate Technical Lead - QA
>>> WSO2 Inc: http://www.wso2.com/
>>> Mobile: *+94773383831*
>>>
>>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna <ar...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've tested the kernel with following databases and found no issues.
>>>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>>>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>>>
>>>> [x] Stable - go ahead and release.
>>>>
>>>> Regards,
>>>> Aruna
>>>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <jaya...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>>>>
>>>>> This release fixes the following issues:
>>>>> https://wso2.org/jira/issues/?filter=13113
>>>>>
>>>>> Please download and test your products with kernel 4.4.7 RC1 and vote.
>>>>> Vote will be open for 72 hours or as longer as needed.
>>>>>
>>>>> Source and binary distribution files:
>>>>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>>>>
>>>>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>>>>
>>>>> Maven staging repository
>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>>>>
>>>>> The tag to be voted upon :
>>>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>>>>
>>>>> [ ] Broken - do not release (explain why)
>>>>> [ ] Stable - go ahead and release
>>>>>
>>>>> Thank you
>>>>> Carbon Team​
>>>>>
>>>>>
>>>>> *Jayanga Dissanayake*
>>>>> Associate Technical Lead
>>>>> WSO2 Inc. - http://wso2.com/
>>>>> lean . enterprise . middleware
>>>>> email: jaya...@wso2.com
>>>>> mobile: +94772207259
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Aruna Sujith Karunarathna *
>>>> WSO2, Inc | lean. enterprise. middleware.
>>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>>> Email: ar...@wso2.com | Web: www.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
>>>
>>>
>>
>>
>> --
>> Anupama Pathirage
>> Associate Technical Lead
>> WSO2, Inc.  http://wso2.com/
>> Email: anup...@wso2.com
>> Mobile:+94 71 8273 979
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. .:http://wso2.com
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>
> * <http://wso2.com/>*
>



-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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


Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

2016-07-04 Thread Chamalee De Silva
Hi,
I tested the kernel 4.4.7 RC1 with

MySQL 5.6 and  5.7,
Oracle 11g,
PostgreSQL 9.3

and they worked without an issue.

[x] Stable - go ahead and release.



Thanks,
Chamalee

On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage <anup...@wso2.com> wrote:

> Hi,
>
> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
> issue related to this RC.
>
> *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6
> is observed. Hope this will be fixed in a future release.
>
> [1] https://wso2.org/jira/browse/CARBON-15973
>
> Regards,
> Anupama
>
> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne <shash...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I tested the kernal with following databases and no issues observed.
>>
>> Test Area:
>> Add/ Delete resource (inline text) and collection
>> Add/Remove user and role
>>
>> Databases:
>> mysql 5.5.
>> mysql 5.7
>> postgres 9.3
>> oracle 12c
>>
>> Regards,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna <ar...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the kernel with following databases and found no issues.
>>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Regards,
>>> Aruna
>>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake <jaya...@wso2.com>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>>>
>>>> This release fixes the following issues:
>>>> https://wso2.org/jira/issues/?filter=13113
>>>>
>>>> Please download and test your products with kernel 4.4.7 RC1 and vote.
>>>> Vote will be open for 72 hours or as longer as needed.
>>>>
>>>> Source and binary distribution files:
>>>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>>>
>>>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>>>
>>>> Maven staging repository
>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>>>
>>>> The tag to be voted upon :
>>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>>>
>>>> [ ] Broken - do not release (explain why)
>>>> [ ] Stable - go ahead and release
>>>>
>>>> Thank you
>>>> Carbon Team​
>>>>
>>>>
>>>> *Jayanga Dissanayake*
>>>> Associate Technical Lead
>>>> WSO2 Inc. - http://wso2.com/
>>>> lean . enterprise . middleware
>>>> email: jaya...@wso2.com
>>>> mobile: +94772207259
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.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
>>
>>
>
>
> --
> Anupama Pathirage
> Associate Technical Lead
> WSO2, Inc.  http://wso2.com/
> Email: anup...@wso2.com
> Mobile:+94 71 8273 979
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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


Re: [Dev] WSO2 Committers += Malintha Amarasinghe

2016-01-31 Thread Chamalee De Silva
Congrats Malintha 

On Mon, Feb 1, 2016 at 9:28 AM, Praminda Jayawardana <prami...@wso2.com>
wrote:

> Congratulations Malintha!
>
> On Sun, Jan 31, 2016 at 7:22 PM, Kalyani Yogeswaranathan <kaly...@wso2.com
> > wrote:
>
>> Congrats Malintha!
>>
>> On Sun, Jan 31, 2016 at 8:46 AM, Roshan Wijesena <ros...@wso2.com> wrote:
>>
>>> Congratulations !
>>>
>>> On Sat, Jan 30, 2016 at 8:34 PM, Hasunie Adikari <hasu...@wso2.com>
>>> wrote:
>>>
>>>> Congratz Malintha
>>>>
>>>> On Sat, Jan 30, 2016 at 7:03 PM, Rukshan Premathunga <ruks...@wso2.com>
>>>> wrote:
>>>>
>>>>> congratz malintha...
>>>>>
>>>>> On Sat, Jan 30, 2016 at 6:57 PM, Isuru Wijesinghe <isur...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Congratzz Malintha :)
>>>>>>
>>>>>> On Sat, Jan 30, 2016 at 1:38 PM, Nuwan Dias <nuw...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> It is with great pleasure we welcome Malintha Amarasinghe as a
>>>>>>> WSO2 Committer. @Malintha, congratulations and keep up the good
>>>>>>> work!
>>>>>>>
>>>>>>> Thanks,
>>>>>>> NuwanD.
>>>>>>>
>>>>>>> --
>>>>>>> Nuwan Dias
>>>>>>>
>>>>>>> Technical Lead - WSO2, Inc. http://wso2.com
>>>>>>> email : nuw...@wso2.com
>>>>>>> Phone : +94 777 775 729
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Isuru Wijesinghe
>>>>>> *Software Engineer*
>>>>>> WSO2 inc : http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>> Mobile: 0710933706
>>>>>> isur...@wso2.com
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Rukshan Chathuranga.
>>>>> Software Engineer.
>>>>> WSO2, Inc.
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Hasunie Adikari*
>>>> Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>> blog http://hasuniea.blogspot.com
>>>> Mobile:+94715139495
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: *+94719154640 <%2B94719154640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>> lean.enterprise.middleware.
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Kalyani Yogeswaranathan*
>>
>> *Associate software engineer*
>> *WSO2 Inc.*
>>
>> *Mobile: 0776390284*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590818
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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


Re: [Dev] WSO2 Committers += Sajith Abeywardhana

2016-01-28 Thread Chamalee De Silva
Congrats Sajith !!!

On Thu, Jan 28, 2016 at 12:42 PM, Chathura Dilan <chathu...@wso2.com> wrote:

> Congratz Sajith!
>
> On Thu, Jan 28, 2016 at 12:25 PM, Rasika Perera <rasi...@wso2.com> wrote:
>
>> Congratulations Sajith !!!
>>
>> On Thu, Jan 28, 2016 at 10:05 AM, Yasassri Ratnayake <yasas...@wso2.com>
>> wrote:
>>
>>> Congtrats Sajith!!
>>>
>>> On Thu, Jan 28, 2016 at 9:50 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> It is my pleasure to welcome Sajith Abeywardhana as a WSO2 Committer.
>>>> SajithA, congratulations and keep up the good work.
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> --
>>>> Dinusha Dilrukshi
>>>> Associate Technical Lead
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94725255071
>>>> Blog: http://dinushasblog.blogspot.com/
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Yasassri Ratnayake
>>> Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <%2B94715933168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> <http://yasassriratnayake.blogspot.com/>*
>>> *http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Senior Software Engineer** - WSO2 Inc.*
> www.dilan.me
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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


Re: [Dev] [IS][Greg] Configuring LDAP User Store in IS 5.0.0 and Greg 5.1.0

2015-11-30 Thread Chamalee De Silva
Hi Damith,

Attached here are the user-mgt.xml files of Greg and IS respectively.


Thanks,
Chamalee


On Mon, Nov 30, 2015 at 3:16 PM, Damith Senanayake <dami...@wso2.com> wrote:

> Hi Chamalee,
>
> It could be that the password digest method is different when creating the
> user and later when configuring the user store manager. Could you please
> attach the user-mgt.xml?
>
> On Mon, Nov 30, 2015 at 1:40 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> + Darshana, Damith
>>
>> On Mon, Nov 30, 2015 at 1:37 PM, Chamalee De Silva <chama...@wso2.com>
>> wrote:
>>
>>> Hi devs,
>>>
>>> I have created a *read-write LDAP user store* as per [1] and there I
>>> have used *admin, admin* as credentials. I could successfully create it
>>> and start the server.
>>>
>>> Then I created a user with the following credentials.
>>>
>>> username : adminSOA
>>> password : 123456
>>> role : admin (default admin role)
>>>
>>> Then I followed [2] and configured a read-only (not read-write) external
>>> user store in Greg 5.1.0
>>>
>>> Given the user credentials as per the created user as above.
>>>
>>>
>>> The configuration is as follows in user-mgt.xml in Greg.
>>>
>>> **
>>> * true*
>>> *admin*
>>> **
>>> * adminSOA*
>>> * 123456*
>>> **
>>> *everyone *
>>> *jdbc/WSO2USER_DB*
>>> **
>>>
>>> *-*
>>>
>>> * uid=adminSOA,ou=system
>>>   123456   *
>>>
>>> But when I start Greg it gives the following error.
>>>
>>> [2015-11-30 13:13:36,823] ERROR
>>> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
>>> connection. [LDAP: error code 49 - cannot bind the principalDn.]
>>> javax.naming.AuthenticationException: [LDAP: error code 49 - cannot bind
>>> the principalDn.]
>>> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
>>> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
>>> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
>>> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
>>> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
>>> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
>>> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
>>> at
>>> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
>>> at
>>> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
>>> at
>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
>>> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>>> at javax.naming.InitialContext.init(InitialContext.java:242)
>>> at javax.naming.InitialContext.(InitialContext.java:216)
>>> at
>>> javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
>>> at
>>> org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:167)
>>> at
>>> org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:156)
>>> at
>>> org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:100)
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealm.createObjectWithOptions(DefaultRealm.java:336)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealm.initializeObjects(DefaultRealm.java:203)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:108)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:230)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:96)
>>> at
>>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:109)
>&g

Re: [Dev] [IS][Greg] Configuring LDAP User Store in IS 5.0.0 and Greg 5.1.0

2015-11-30 Thread Chamalee De Silva
Hi Damith,

Changing the connection name form *uid=adminSOA, ou=system* to *uid=adminSOA,
ou=Users, dc=wso2,dc=org* solved the issue.

Thanks for the help.




Thanks,
Chamalee.









On Tue, Dec 1, 2015 at 9:07 AM, Damith Senanayake <dami...@wso2.com> wrote:

> Is it the same stacktrace or something different, if you don't mind, could
> you please attach the new stacktrace.
>
> If it is the same error it could be that the user you are trying to bind
> does not exist. For this, you have to take a look at the following
> property.
>
> If you are trying to connect to the ldap user store of the IS instance you
> are running, you will have to change the port according to the offset you
> have set for it instead of using the standard property value.
>
>  name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
> uid=admin,ou=system
> admin
>
> The value in red indicates that what you are binding is the instance of the 
> GREG (since this was taken from the greg-user-mgt.xml). Instead, if you are 
> using the IS with an offset (say 1 ) you should set the ConnectionURL as :
>
> ldap://localhost:1390
>
> Since we use 10389 as the standard ldap server port for the embedded ldap.
>
>
> Also, if you are trying to set the user you created in IS as your super admin 
> in GREG, you should make sure the following is satisfied.
>
>
> 1. The GREG user store is pointed to the LDAP of the IS (not the embedded one 
> of the GREG but the embedded one of the IS)
>
> 2. The password digest you use in GREG user-mgt.xml is the same when you 
> created the user in IS. In this particular case, I suggest that it will be 
> SHA and not PLAIN_TEXT.
>
> 3. The connection name and password are correct. i.e. the Distinguished Name 
> of the connection should be a valid existing one and the password should be 
> correct. In your case, uid=admin, ou=system is correct. However, if you want 
> to bind to the user you created yourself, it should change to uid=adminSOA, 
> ou=Users, dc=wso2,dc=org.
>
>
>
> On Mon, Nov 30, 2015 at 7:47 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi Damith,
>> Still I get the same error.
>>  [LDAP: error code 49 - cannot bind the principalDn.]
>> Is there any other cause for this exception ?
>>
>>
>>
>> Thanks
>>
>> On Mon, Nov 30, 2015 at 3:27 PM, Damith Senanayake <dami...@wso2.com>
>> wrote:
>>
>>> Yes that is the issue. In the user-mgt-xml-of GREG, the password digest
>>> is configured as PLAIN_TEXT while in the other it is configured as SHA.
>>> They need to be the same.
>>>
>>> Hope this helps.
>>>
>>> Thanks
>>>
>>> On Mon, Nov 30, 2015 at 3:24 PM, Chamalee De Silva <chama...@wso2.com>
>>> wrote:
>>>
>>>> Hi Damith,
>>>>
>>>> Attached here are the user-mgt.xml files of Greg and IS respectively.
>>>>
>>>>
>>>> Thanks,
>>>> Chamalee
>>>>
>>>>
>>>> On Mon, Nov 30, 2015 at 3:16 PM, Damith Senanayake <dami...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Chamalee,
>>>>>
>>>>> It could be that the password digest method is different when creating
>>>>> the user and later when configuring the user store manager. Could you
>>>>> please attach the user-mgt.xml?
>>>>>
>>>>> On Mon, Nov 30, 2015 at 1:40 PM, Chamalee De Silva <chama...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> + Darshana, Damith
>>>>>>
>>>>>> On Mon, Nov 30, 2015 at 1:37 PM, Chamalee De Silva <chama...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi devs,
>>>>>>>
>>>>>>> I have created a *read-write LDAP user store* as per [1] and there
>>>>>>> I have used *admin, admin* as credentials. I could successfully
>>>>>>> create it and start the server.
>>>>>>>
>>>>>>> Then I created a user with the following credentials.
>>>>>>>
>>>>>>> username : adminSOA
>>>>>>> password : 123456
>>>>>>> role : admin (default admin role)
>>>>>>>
>>>>>>> Then I followed [2] and configured a read-only (not read-write)
>>>>>>> external user store in Greg 5.1.0
>>&

[Dev] [IS][Greg] Configuring LDAP User Store in IS 5.0.0 and Greg 5.1.0

2015-11-30 Thread Chamalee De Silva
)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: org.wso2.carbon.user.core.UserStoreException: nullType class
java.lang.reflect.InvocationTargetException
at
org.wso2.carbon.user.core.common.DefaultRealm.initializeObjects(DefaultRealm.java:303)
at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:108)
at
org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:230)
... 19 more
Caused by: org.wso2.carbon.user.core.UserStoreException: nullType class
java.lang.reflect.InvocationTargetException
at
org.wso2.carbon.user.core.common.DefaultRealm.createObjectWithOptions(DefaultRealm.java:382)
at
org.wso2.carbon.user.core.common.DefaultRealm.initializeObjects(DefaultRealm.java:203)
... 21 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at
org.wso2.carbon.user.core.common.DefaultRealm.createObjectWithOptions(DefaultRealm.java:336)
... 22 more
Caused by: org.wso2.carbon.user.core.UserStoreException: Cannot create
connection to LDAP server. Error message Error obtaining connection. [LDAP:
error code 49 - cannot bind the principalDn.]
at
org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:166)
at
org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:100)
... 27 more
Caused by: org.wso2.carbon.user.core.UserStoreException: Error obtaining
connection. [LDAP: error code 49 - cannot bind the principalDn.]
at
org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:177)
at
org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:156)
... 28 more
Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 -
cannot bind the principalDn.]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
at
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
at
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.(InitialContext.java:216)
at
javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
at
org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:167)
... 29 more

When I configure the read-only LDAP with *admin, admin* credentials I can
start the server without errors.

Note : In this setup I have configured a MySQL user db for Greg in
user-mgt.xml as *WSO2USER_DB* and in IS it is default *WSO2CarbonDB*.

Can anyone explain this situation and point me out what is the correct step
to be taken for this ?


[1]
https://docs.wso2.com/display/IS500/Configuring+a+Read-write+LDAP+User+Store
[2]
https://docs.wso2.com/display/Governance450/Configuring+an+External+LDAP+User+Store

-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [IS][Greg] Configuring LDAP User Store in IS 5.0.0 and Greg 5.1.0

2015-11-30 Thread Chamalee De Silva
+ Darshana, Damith

On Mon, Nov 30, 2015 at 1:37 PM, Chamalee De Silva <chama...@wso2.com>
wrote:

> Hi devs,
>
> I have created a *read-write LDAP user store* as per [1] and there I have
> used *admin, admin* as credentials. I could successfully create it and
> start the server.
>
> Then I created a user with the following credentials.
>
> username : adminSOA
> password : 123456
> role : admin (default admin role)
>
> Then I followed [2] and configured a read-only (not read-write) external
> user store in Greg 5.1.0
>
> Given the user credentials as per the created user as above.
>
>
> The configuration is as follows in user-mgt.xml in Greg.
>
> **
> * true*
> *admin*
> **
> * adminSOA*
> * 123456*
> **
> *everyone *
> *jdbc/WSO2USER_DB*
> **
>
> *-*
>
> * uid=adminSOA,ou=system
> 123456   *
>
> But when I start Greg it gives the following error.
>
> [2015-11-30 13:13:36,823] ERROR
> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
> connection. [LDAP: error code 49 - cannot bind the principalDn.]
> javax.naming.AuthenticationException: [LDAP: error code 49 - cannot bind
> the principalDn.]
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
> at
> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> at javax.naming.InitialContext.init(InitialContext.java:242)
> at javax.naming.InitialContext.(InitialContext.java:216)
> at
> javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
> at
> org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnectionContext.java:167)
> at
> org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:156)
> at
> org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager.(ReadOnlyLDAPUserStoreManager.java:100)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.createObjectWithOptions(DefaultRealm.java:336)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.initializeObjects(DefaultRealm.java:203)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:108)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:230)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:96)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:109)
> at
> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:68)
> at
> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:

Re: [Dev] [IS][Greg] Configuring LDAP User Store in IS 5.0.0 and Greg 5.1.0

2015-11-30 Thread Chamalee De Silva
Hi Damith,
Still I get the same error.
 [LDAP: error code 49 - cannot bind the principalDn.]
Is there any other cause for this exception ?



Thanks

On Mon, Nov 30, 2015 at 3:27 PM, Damith Senanayake <dami...@wso2.com> wrote:

> Yes that is the issue. In the user-mgt-xml-of GREG, the password digest is
> configured as PLAIN_TEXT while in the other it is configured as SHA. They
> need to be the same.
>
> Hope this helps.
>
> Thanks
>
> On Mon, Nov 30, 2015 at 3:24 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> Hi Damith,
>>
>> Attached here are the user-mgt.xml files of Greg and IS respectively.
>>
>>
>> Thanks,
>> Chamalee
>>
>>
>> On Mon, Nov 30, 2015 at 3:16 PM, Damith Senanayake <dami...@wso2.com>
>> wrote:
>>
>>> Hi Chamalee,
>>>
>>> It could be that the password digest method is different when creating
>>> the user and later when configuring the user store manager. Could you
>>> please attach the user-mgt.xml?
>>>
>>> On Mon, Nov 30, 2015 at 1:40 PM, Chamalee De Silva <chama...@wso2.com>
>>> wrote:
>>>
>>>> + Darshana, Damith
>>>>
>>>> On Mon, Nov 30, 2015 at 1:37 PM, Chamalee De Silva <chama...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi devs,
>>>>>
>>>>> I have created a *read-write LDAP user store* as per [1] and there I
>>>>> have used *admin, admin* as credentials. I could successfully create
>>>>> it and start the server.
>>>>>
>>>>> Then I created a user with the following credentials.
>>>>>
>>>>> username : adminSOA
>>>>> password : 123456
>>>>> role : admin (default admin role)
>>>>>
>>>>> Then I followed [2] and configured a read-only (not read-write)
>>>>> external user store in Greg 5.1.0
>>>>>
>>>>> Given the user credentials as per the created user as above.
>>>>>
>>>>>
>>>>> The configuration is as follows in user-mgt.xml in Greg.
>>>>>
>>>>> **
>>>>> * true*
>>>>> *admin*
>>>>> **
>>>>> * adminSOA*
>>>>> * 123456*
>>>>> **
>>>>> *everyone *
>>>>> *jdbc/WSO2USER_DB*
>>>>> **
>>>>>
>>>>> *-*
>>>>>
>>>>> * uid=adminSOA,ou=system
>>>>> 123456   *
>>>>>
>>>>> But when I start Greg it gives the following error.
>>>>>
>>>>> [2015-11-30 13:13:36,823] ERROR
>>>>> {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} -  Error obtaining
>>>>> connection. [LDAP: error code 49 - cannot bind the principalDn.]
>>>>> javax.naming.AuthenticationException: [LDAP: error code 49 - cannot
>>>>> bind the principalDn.]
>>>>> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
>>>>> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
>>>>> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
>>>>> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
>>>>> at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:316)
>>>>> at
>>>>> com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
>>>>> at
>>>>> com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
>>>>> at
>>>>> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
>>>>> at
>>>>> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
>>>>> at
>>>>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
>>>>> at
>>>>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
>>>>> at javax.naming.InitialContext.init(InitialContext.java:242)
>>>>> at javax.naming.InitialContext.(InitialContext.java:216)
>>>>> at
>>>>> javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
>>>>> at
>>>>> org.wso2.carbon.user.core.ldap.LDAPConnectionContext.getContext(LDAPConnect

[Dev] [IS][APIM] Error when Updating User Profile for APIM 1.8.0 with identity-mgt feature installed

2015-10-09 Thread Chamalee De Silva
hi all,

I wanted to install the IS identity-mgt features in APIM 1.8.0 to configure
the IS feature Recovery with Notification [1] in APIM.

I have added the repository *http://dist.wso2.org/p2/carbon/releases/4.2.0/
<http://dist.wso2.org/p2/carbon/releases/4.2.0/>  *and installed Account
Recovery and Credential Management 4.2.0 feature in APIM. But I haven't
installed the Self Registration feature.

And then I have configured APIM to have Recover with Notification Feature
as mentioned in [1].

Then  I created a user. But when I update the user profile of the user I
get the following error.

Can anyone explain why this error occurs?

I could do this successfully in IS. But for APIM I get this error.


[2015-10-09 11:59:49,874] ERROR - RPCInOnlyMessageReceiver Exception
occurred while trying to invoke service method setUserProfile
java.lang.StackOverflowError
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:529)
at
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:259)
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:571)
at
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:259)
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:571)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:533)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
[2015-10-09 11:59:50,033] ERROR - UserProfileCient
org.apache.axis2.AxisFault: unknown

[1] https://docs.wso2.com/display/IS500/Recover+with+Notification





-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [IS][APIM] Error when Updating User Profile for APIM 1.8.0 with identity-mgt feature installed

2015-10-09 Thread Chamalee De Silva
so that we can look at the claims given as supported by default.
>
> Regards,
> Tharindu
>
> On Fri, Oct 9, 2015 at 12:16 PM, Chamalee De Silva <chama...@wso2.com>
> wrote:
>
>> hi all,
>>
>> I wanted to install the IS identity-mgt features in APIM 1.8.0 to
>> configure the IS feature Recovery with Notification [1] in APIM.
>>
>> I have added the repository *http://dist.wso2.org/p2/carbon/releases/4.2.0/
>> <http://dist.wso2.org/p2/carbon/releases/4.2.0/>  *and installed Account
>> Recovery and Credential Management 4.2.0 feature in APIM. But I haven't
>> installed the Self Registration feature.
>>
>> And then I have configured APIM to have Recover with Notification Feature
>> as mentioned in [1].
>>
>> Then  I created a user. But when I update the user profile of the user I
>> get the following error.
>>
>> Can anyone explain why this error occurs?
>>
>> I could do this successfully in IS. But for APIM I get this error.
>>
>>
>> [2015-10-09 11:59:49,874] ERROR - RPCInOnlyMessageReceiver Exception
>> occurred while trying to invoke service method setUserProfile
>> java.lang.StackOverflowError
>> at
>> org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:529)
>> at
>> javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:259)
>> at
>> org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:571)
>> at
>> javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:259)
>> at
>> org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRequest.java:571)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:533)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getClone(CarbonContextDataHolder.java:417)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:546)
>> at
>> org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder(CarbonContextDataHolder.java:568)
>> [2015-10-09 11:59:50,033] ERROR - UserProfileCient
>> org.apache.axis2.AxisFault: unknown
>>
>> [1] https://docs.wso2.com/display/IS500/Recover+with+Notification
>>
>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. .:http://wso2.com
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Tharindu Edirisinghe
> Software Engineer | WSO2 Inc
> Identity Server Team
> Blog : tharindue.blogspot.com
> mobile : +94 775 181586
>
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the Fix and the Test Case

2015-08-11 Thread Chamalee De Silva
The fix for the public JIRA [1] and the Test Case related to the Fix is in
[2] and [3] respectively.

$Subject.

[1] https://wso2.org/jira/browse/APIMANAGER-4023
[2] https://github.com/wso2/carbon-apimgt/pull/884
[3] https://github.com/wso2/product-apim/pull/321

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-07-27 Thread Chamalee De Silva
$Subject the Fix [1] for Public JIRA [2].

[1] https://github.com/wso2/carbon-apimgt/pull/852
[2] https://wso2.org/jira/browse/APIMANAGER-3973

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Fetch Email Id from Wso2 Store buser signup section/b

2015-07-20 Thread Chamalee De Silva
Hi Rohit,

At the current implementation of WSO2 API Manager we are not using the
email address of the user for sending approval email notifications.

However if you want to add that functionality, you can add the *email ID of
the user *who is signing up, as a class member in *WorkFlowExecutor.java *

Inside *jsFunction_addUser() *method in *APIStoreHostObject.java *it calls
the UserSignUp workflow.

So there we get the object array (args) from the front end which contain
the email ID of the user in the third element. (line number 3696 in [1])
and then it is further split into a String array and then added into an
array of UserDTO.

P.S. This third element contains a set of field values including the email
address.

According to the front end implementations, the sixth element of the String
array contains the value of email ID.

So that you can take it from the UserDTO array as follows.

*userDTO.getUserFields()[5].toString()*


You can set this value to the variable you defined in *WorkFlowExecutor.java *

When in execution if you have enabled the workflows for the UserSignUp
it will select the UserSignUpWSWorkflowExecutor class for the
execution. In the complete method of that class you can implement your
email sending code after calling *updateRolesOfUser *the following
method in UserSignUpWSWorkflowExecutor if the request is approved by
the admin.

Hope this will solve your problem.


[1]
https://github.com/wso2/carbon-apimgt/blob/release-1.9.0/components/apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/wso2/carbon/apimgt/hostobjects/APIStoreHostObject.java



On Mon, Jul 20, 2015 at 3:47 AM, rohit rohitab...@gmail.com wrote:

 Hello All,
 Can anyone please guide me on how to fetch the email id from the Wso2 Store
 user sign up section. A generic way so that every time user signs up that
 id
 can be captured and can be provided in the workflow-extensions.xml in wso2
 API Manager.
 Thanks in advance!



 --
 View this message in context:
 http://wso2-oxygen-tank.10903.n7.nabble.com/Fetch-Email-Id-from-Wso2-Store-b-user-signup-section-b-tp121955.html
 Sent from the WSO2 Development mailing list archive at Nabble.com.
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Customizing Workflows in wso2 API Manager

2015-07-17 Thread Chamalee De Silva
Hi Rohith,

When Considering API Manager with workflows,
If you want to send an email to the approved user where the admin approves
the event you can implement a custom executor extending the workflow
executor class of the particular event
e.g. If you want to send an email to the user when the admin approves the
Application registraion you can create a custom executor calss extending
ApplicationRegistrationWSWorkflowExecutor.

There you can override execute(WorkflowDTO workflowDTO)  method and achieve
that as follows.


 @Override
public void execute(WorkflowDTO workflowDTO) throws WorkflowException {

ApplicationRegistrationWorkflowDTO appDTO =
(ApplicationRegistrationWorkflowDTO) workflowDTO;

 String emailSubject = appDTO.getKeyType() + Application Registration;

 String emailText = Appplication  + appDTO.getApplication().getName() + 
is registered for  +
   appDTO.getKeyType() +  key by user  + appDTO.getUserName();

 try {
   //Implementation of email sending here e.g. EmailSender.SendEmail Method

 } catch (MessagingException e) {
  // TODO Auto-generated catch block
  e.printStackTrace();
 }

 //SEND EMAIL
 super.execute(workflowDTO);
}
We can use this way to send emails to the admin user as well.



On Fri, Jul 17, 2015 at 12:35 PM, rohit rohitab...@gmail.com wrote:

 Hello All,

 I have been working on wso2 API Manager for some time now. I have added a
 user sign up workflow to it. Now the problem that I am facing is this :
 I have a scenario wherein, once the admin approves the request from the
 admin-dashboard, that is admin can either Approve/Reject the sign up
 request. Once he does so, an email must be sent to the appropriate user.
 This is what I need to achieve.
 (I have also tried the customized subscription workflow provided by wso2,
 and recieved an email whenever I subscribe to an API, But here the email
 was
 sent without any human intervention. There is a SubscriptionWorkflowDTO
 class that contains information about suscriptions created)
 Now I have created a service in esb that is capable of sending an email to
 a
 user. But where I am still facing an issue is, how to *capture the
 admin-dashboard events* that is* once the admin approves/rejects and
 clicks
 on the complete button*, i need to invoke email sending service in esb with
 the appropriate admin response. How do I achieve this? Any help will be
 greatly appreciated
 P.s : I am looking into the source code and trying to modify it to suit my
 situation, but things are not going in my way.



 --
 View this message in context:
 http://wso2-oxygen-tank.10903.n7.nabble.com/Customizing-Workflows-in-wso2-API-Manager-tp121859.html
 Sent from the WSO2 Development mailing list archive at Nabble.com.
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Customizing Workflows in wso2 API Manager

2015-07-17 Thread Chamalee De Silva
Adding more,

Please refer public void complete(WorkflowDTO workFlowDTO) method starting
from line 63 in [1]

[1]
https://github.com/wso2/carbon-apimgt/blob/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/workflow/AbstractApplicationRegistrationWorkflowExecutor.java

On Fri, Jul 17, 2015 at 3:31 PM, Chamalee De Silva chama...@wso2.com
wrote:

 Hi Rohit,

 Well. In our API Manager source code 
 *AbstractApplicationRegistrationWorkflowExecutor.java
 *checks the status of the workFlowDTO status.
 Whether it is created, rejected or approved.
 According to that we perform the operations like updating the database and
 updating the UI with messages.

 So I think  you can use the class [1] to achieve your purpose.

 [1]
 https://github.com/wso2/carbon-apimgt/blob/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/workflow/AbstractApplicationRegistrationWorkflowExecutor.java

 On Fri, Jul 17, 2015 at 2:38 PM, rohit rohitab...@gmail.com wrote:

 Respected Sir thank you so much for your prompt reply. However in your
 sample
 code you are using, *ApplicationRegistrationWorkflowDTO *class which
 contains the necessary details about application registration as well as
 in
 the worflow sample in wso2 documentation, they are using the
 *SubscriptionWorkflowDTO* class which contains information about the
 subscription which is being created. Similarly what I am looking for is
 *one such class which contains the details of admin approval/reject
 events*,
 so that I can extend that class and write my logic that needs to be
 implemented.
 I have created a user sign up workflow and the sign up request goes to
 Admin
 Dashboard Web application (https://Server Host:9443/admin-dashboard)
 provided by wso2.
 What I wanted to know is that If I could capture the admin approval/reject
 events from a href=quot;https://lt;Server
 Host:9443/admin-dashboardhttps://Server Host:9443/admin-dashboard
 and its response so that I can send an email notification to a user
 telling
 him whether his request has been approved/rejected. Please tell me if it
 is
 possible or what is the workaround to achieve to achieve this?
 Thanks in advance.



 --
 View this message in context:
 http://wso2-oxygen-tank.10903.n7.nabble.com/Customizing-Workflows-in-wso2-API-Manager-tp121859p121865.html
 Sent from the WSO2 Development mailing list archive at Nabble.com.
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*





-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Customizing Workflows in wso2 API Manager

2015-07-17 Thread Chamalee De Silva
Hi Rohit,

Well. In our API Manager source code
*AbstractApplicationRegistrationWorkflowExecutor.java
*checks the status of the workFlowDTO status.
Whether it is created, rejected or approved.
According to that we perform the operations like updating the database and
updating the UI with messages.

So I think  you can use the class [1] to achieve your purpose.

[1]
https://github.com/wso2/carbon-apimgt/blob/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/workflow/AbstractApplicationRegistrationWorkflowExecutor.java

On Fri, Jul 17, 2015 at 2:38 PM, rohit rohitab...@gmail.com wrote:

 Respected Sir thank you so much for your prompt reply. However in your
 sample
 code you are using, *ApplicationRegistrationWorkflowDTO *class which
 contains the necessary details about application registration as well as in
 the worflow sample in wso2 documentation, they are using the
 *SubscriptionWorkflowDTO* class which contains information about the
 subscription which is being created. Similarly what I am looking for is
 *one such class which contains the details of admin approval/reject
 events*,
 so that I can extend that class and write my logic that needs to be
 implemented.
 I have created a user sign up workflow and the sign up request goes to
 Admin
 Dashboard Web application (https://Server Host:9443/admin-dashboard)
 provided by wso2.
 What I wanted to know is that If I could capture the admin approval/reject
 events from a href=quot;https://lt;Server
 Host:9443/admin-dashboardhttps://Server Host:9443/admin-dashboard
 and its response so that I can send an email notification to a user telling
 him whether his request has been approved/rejected. Please tell me if it is
 possible or what is the workaround to achieve to achieve this?
 Thanks in advance.



 --
 View this message in context:
 http://wso2-oxygen-tank.10903.n7.nabble.com/Customizing-Workflows-in-wso2-API-Manager-tp121859p121865.html
 Sent from the WSO2 Development mailing list archive at Nabble.com.
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Customizing Workflows in wso2 API Manager

2015-07-17 Thread Chamalee De Silva
Hi Rohith,

I think the best way is to refer the source code well.
There are workflow executor classes for each of the workflows that we are
supporting.
If you browse through the workflow directory under carbon-apimgt
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713
/components
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components
/apimgt
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt
/org.wso2.carbon.apimgt.impl
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl
/src
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src
/main
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main
/java
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java
/org
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org
/wso2
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2
/carbon
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon
/apimgt
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt
/impl
https://github.com/wso2/carbon-apimgt/tree/f517aed904f44b093ce87a392f2fe65a5ff01713/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl
you
can find the implementations for *user signup workflow*  where you can get
the *status of the workflow. *

As an example in *UserSignUpSimpleWorkflowExecutor.java *you can see the
same* complete() method *for user sign up which I mentioned earlier.

So go through them and do your implementations using them.

On Fri, Jul 17, 2015 at 3:37 PM, rohit rohitab...@gmail.com wrote:

 Well Thank you sir, the *AbstractApplicationRegistrationWorkflowExecutor*
 class contains the workFlowDTO status for Application Registration events,
 but what I'm keen on capturing is *UserSignUp *events. Is there a way to do
 that? If that is the case, then may be  according to you suggestion I can
 get the status. Do i need to implement such class definition for my kind of
 scenario?



 --
 View this message in context:
 http://wso2-oxygen-tank.10903.n7.nabble.com/Customizing-Workflows-in-wso2-API-Manager-tp121859p121870.html
 Sent from the WSO2 Development mailing list archive at Nabble.com.
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Get values from javascript or html into jaggery

2015-07-10 Thread Chamalee De Silva
Hi Nashry,

You can use the variables you create in JavaScript same in Jaggery code.
Becuase Jaggery is all about Javascript.

*As a pure Javascript server-side scripting engine, Jaggery combines all
the strengths of Javascript with flexibility and freedom at both the
development and deployment stages. Most JavaScript webapp development
mechanisms restrict developers to a framework-specific structure or
patterns, which demand an additional learning curve. By contrast, with
Jaggery, any developers who are versed in Javascript have everything they
need to get going.*


On Fri, Jul 10, 2015 at 1:16 PM, Lakshani Gamage laksh...@wso2.com wrote:

 Hi Aaquibah,

 Please follow the link[1]. It'll help to solve your problem.

 [1]
 http://blog.lasindu.com/2014/05/how-to-write-wso2-jaggery-application.html

 Thanks,
 Lakshani

 On Fri, Jul 10, 2015 at 1:09 PM, Aaquibah Nashry nas...@wso2.com wrote:

 Hi,

 I need to get the values of javascript variables or values of html
 elements into jaggery code.

 What i am doing is, i am getting values from html elements and i need to
 send them inside the query in jaggery.
 That is,
 in html i have a dropdown as *Year*, i want to pass the value selected.
 Below is the javascript code with the jaggery code:

 function DrawGraph(){
 var year=document.getElementById(Year).value;

 %
 var query =  select sum(Best_Case__c) as 'Best' FROM Opp WHERE
 YEAR(Date__c)=*year*
 %

 }

 How can i do this?
 Any example? Tutorials?

 Thanks in advance.
 Regards,

 M.R.Aaquibah Nashry
 *Intern, Engineering**| **WSO2, Inc.*
 Mobile : +94 773946123
 Tel  : +94 112662541
 Email : nas...@wso2.com nas...@wso2.com

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




 --
 Lakshani Gamage

 *Software Engineer*
 Mobile : +94 (0) 71 5478184 %2B94%20%280%29%20773%20451194

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [AM][TEST] java.lang.ClassNotFoundException: org.h2.Driver

2015-07-09 Thread Chamalee De Silva
The builder pointing the above object creation line as where the error
exists.

On Thu, Jul 9, 2015 at 2:57 PM, Chamalee De Silva chama...@wso2.com wrote:

 hi all,

 I am writing a test case for WSO2 API Manager to test Read Only External
 Stores in java.
 I pointed the WSO2CARBON_DB to add Roles and Users.

 But when I build it fails with a ClassNotFoundException for the following.
 ( java.lang.ClassNotFoundException: org.h2.Driver)

 H2DataBaseManager dbmanager = new H2DataBaseManager(jdbc:h2: +
 ServerConfigurationManager.getCarbonHome() +
 /repository/database/WSO2CARBON_DB, wso2carbon', wso2carbon);
dbmanager.executeUpdate(new
 File(ServerConfigurationManager.getCarbonHome() + /dbscripts/h2.sql));
dbmanager.disconnect();

 *Error Log : *

 java.lang.ClassNotFoundException: org.h2.Driver
 at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:171)
 at
 org.wso2.carbon.automation.test.utils.dbutils.H2DataBaseManager.init(H2DataBaseManager.java:39)
 at
 org.wso2.am.integration.tests.other.ReadOnlyExternalStoreAPITokenGenerationTestCase.setEnvironment(ReadOnlyExternalStoreAPITokenGenerationTestCase.java:94)


 PS : I am creating the external store in the environment setup before the
 test start to run.

 Any ideas to resolve this issue?

 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com
 lean *.* enterprise *.* middleware

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [AM][TEST] java.lang.ClassNotFoundException: org.h2.Driver

2015-07-09 Thread Chamalee De Silva
Hi,

No. Only in the parent pom.xml of product-apim it has the following
dependency.

dependency
groupIdcom.h2database.wso2/groupId
artifactIdh2-database-engine/artifactId
version${orbit.version.h2.engine}/version
/dependency




On Thu, Jul 9, 2015 at 3:07 PM, Irham Iqbal iq...@wso2.com wrote:

 Hi Chamalee,

 Can you please make sure whether you have dependency related to org.h2.Driver
 in your tests-integration module pom.xml

 Thanks,
 Iqbal

 On Thu, Jul 9, 2015 at 2:57 PM, Chamalee De Silva chama...@wso2.com
 wrote:

 hi all,

 I am writing a test case for WSO2 API Manager to test Read Only External
 Stores in java.
 I pointed the WSO2CARBON_DB to add Roles and Users.

 But when I build it fails with a ClassNotFoundException for the
 following. ( java.lang.ClassNotFoundException: org.h2.Driver)

 H2DataBaseManager dbmanager = new H2DataBaseManager(jdbc:h2: +
 ServerConfigurationManager.getCarbonHome() +
 /repository/database/WSO2CARBON_DB, wso2carbon', wso2carbon);
dbmanager.executeUpdate(new
 File(ServerConfigurationManager.getCarbonHome() + /dbscripts/h2.sql));
dbmanager.disconnect();

 *Error Log : *

 java.lang.ClassNotFoundException: org.h2.Driver
 at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:171)
 at
 org.wso2.carbon.automation.test.utils.dbutils.H2DataBaseManager.init(H2DataBaseManager.java:39)
 at
 org.wso2.am.integration.tests.other.ReadOnlyExternalStoreAPITokenGenerationTestCase.setEnvironment(ReadOnlyExternalStoreAPITokenGenerationTestCase.java:94)


 PS : I am creating the external store in the environment setup before the
 test start to run.

 Any ideas to resolve this issue?

 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com
 lean *.* enterprise *.* middleware

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*

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




 --
 Irham Iqbal
 Software Engineer - Test Automation
  WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [AM][TEST] java.lang.ClassNotFoundException: org.h2.Driver

2015-07-09 Thread Chamalee De Silva
hi all,

I am writing a test case for WSO2 API Manager to test Read Only External
Stores in java.
I pointed the WSO2CARBON_DB to add Roles and Users.

But when I build it fails with a ClassNotFoundException for the following.
( java.lang.ClassNotFoundException: org.h2.Driver)

H2DataBaseManager dbmanager = new H2DataBaseManager(jdbc:h2: +
ServerConfigurationManager.getCarbonHome() +
/repository/database/WSO2CARBON_DB, wso2carbon', wso2carbon);
   dbmanager.executeUpdate(new
File(ServerConfigurationManager.getCarbonHome() + /dbscripts/h2.sql));
   dbmanager.disconnect();

*Error Log : *

java.lang.ClassNotFoundException: org.h2.Driver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:171)
at
org.wso2.carbon.automation.test.utils.dbutils.H2DataBaseManager.init(H2DataBaseManager.java:39)
at
org.wso2.am.integration.tests.other.ReadOnlyExternalStoreAPITokenGenerationTestCase.setEnvironment(ReadOnlyExternalStoreAPITokenGenerationTestCase.java:94)


PS : I am creating the external store in the environment setup before the
test start to run.

Any ideas to resolve this issue?

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [AM][TEST] java.lang.ClassNotFoundException: org.h2.Driver

2015-07-09 Thread Chamalee De Silva
Hi,

Could Solve the issue.
Thanks all.

On Thu, Jul 9, 2015 at 3:16 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:

 Hi Chamalee

 Then add below to the test module pom.

 dependency
 groupIdcom.h2database.wso2/groupId
 artifactIdh2-database-engine/artifactId
 /dependency

 Thanks,
 Nuwanw

 On Thu, Jul 9, 2015 at 3:13 PM, Chamalee De Silva chama...@wso2.com
 wrote:

 Hi,

 No. Only in the parent pom.xml of product-apim it has the following
 dependency.

 dependency
 groupIdcom.h2database.wso2/groupId
 artifactIdh2-database-engine/artifactId
 version${orbit.version.h2.engine}/version
 /dependency




 On Thu, Jul 9, 2015 at 3:07 PM, Irham Iqbal iq...@wso2.com wrote:

 Hi Chamalee,

 Can you please make sure whether you have dependency related to 
 org.h2.Driver
 in your tests-integration module pom.xml

 Thanks,
 Iqbal

 On Thu, Jul 9, 2015 at 2:57 PM, Chamalee De Silva chama...@wso2.com
 wrote:

 hi all,

 I am writing a test case for WSO2 API Manager to test Read Only
 External Stores in java.
 I pointed the WSO2CARBON_DB to add Roles and Users.

 But when I build it fails with a ClassNotFoundException for the
 following. ( java.lang.ClassNotFoundException: org.h2.Driver)

 H2DataBaseManager dbmanager = new H2DataBaseManager(jdbc:h2: +
 ServerConfigurationManager.getCarbonHome() +
 /repository/database/WSO2CARBON_DB, wso2carbon', wso2carbon);
dbmanager.executeUpdate(new
 File(ServerConfigurationManager.getCarbonHome() + /dbscripts/h2.sql));
dbmanager.disconnect();

 *Error Log : *

 java.lang.ClassNotFoundException: org.h2.Driver
 at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:171)
 at
 org.wso2.carbon.automation.test.utils.dbutils.H2DataBaseManager.init(H2DataBaseManager.java:39)
 at
 org.wso2.am.integration.tests.other.ReadOnlyExternalStoreAPITokenGenerationTestCase.setEnvironment(ReadOnlyExternalStoreAPITokenGenerationTestCase.java:94)


 PS : I am creating the external store in the environment setup before
 the test start to run.

 Any ideas to resolve this issue?

 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com
 lean *.* enterprise *.* middleware

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*

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




 --
 Irham Iqbal
 Software Engineer - Test Automation
  WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware
 phone: +94 777888452




 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com
 lean *.* enterprise *.* middleware

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*

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




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

 phone: +94 71 668 4620






-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Review and Merge PR

2015-07-02 Thread Chamalee De Silva
Please $Subject the fix [1] for Public Jira [2].

Tested and verified with shared subscriptions as well.
Created Doc JIRA at [3] to update the documentation.


[1] https://github.com/wso2/carbon-apimgt/pull/803
[2] https://wso2.org/jira/browse/APIMANAGER-3945
[3] https://wso2.org/jira/browse/DOCUMENTATION-1934

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge

2015-06-30 Thread Chamalee De Silva
Hi,

Please $Subject the PR [1] as the Fix for the Public JIRA [2].

[1] https://github.com/wso2/carbon-apimgt/pull/798

[2] https://wso2.org/jira/browse/APIMANAGER-3934

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM] Changing the default timeout of published APIs

2015-06-25 Thread Chamalee De Silva
Hi,

Yes. It will change the timeout of the particular API.

On Fri, Jun 26, 2015 at 10:34 AM, Hasanthi Purnima Dissanayake 
hasan...@wso2.com wrote:

 Hi Chamali,
 Thanks for the response. What I'm currently doing is adding different
 timeouts for different APIs in the source view of the UI as below.

   api name=admin--Emailverification
 context=/phoneverify
 version=1.0.0
 version-type=url
   
   send
  endpoint
 name=admin--Emailverification_APIproductionEndpoint_0
 http uri-template=
 http://ws.cdyne.com/emailverify/emailverify.asmx/
 timeout
  duration3/duration
  responseActionfault/responseAction
/timeout
  /endpoint
   /send
 .
 Expecting this will change the timeouts of different APIs from the default.
 Thanks,

 Hasanthi Dissanayake

 Software Engineer | WSO2

 E: hasan...@wso2.com nirosh...@wso2.com
 M :0718407133| http://wso2.com http://wso2.com/

 On Fri, Jun 26, 2015 at 10:25 AM, Chamalee De Silva chama...@wso2.com
 wrote:

 Hi Hasanthi,

 You can change the synapse configuration of all APIs that are created as
 you want according to [1].
 Then it affects to the default values of the APIs created in the future
 too.

 If you want to change the endpoint timeouts of already published APIs you
 can change  the synapse config of each API in
 API-HOME/repository/deployment/server/synapse-configs/default/api
 directory and you can define an response action according to the changed
 timeout.

 Please refer [2] for more information.

 [1]https://docs.wso2.com/display/AM160/Editing+API+Templates
 [2]
 https://docs.wso2.com/display/AM190/Tuning+Performance#TuningPerformance-APIM-levelsettings


 On Fri, Jun 26, 2015 at 8:56 AM, Hasanthi Purnima Dissanayake 
 hasan...@wso2.com wrote:

 Hi All,
 By editing the templates according to [1] we can change the timeout of
 default APIs. I think this will change the default time out of all APIs
 that will publish in future too. Please correct me if I'm wrong. Is there a
 way to change the timeout of already published APIs only without affecting
 to the future publishing APIs.

 [1]https://docs.wso2.com/display/AM160/Editing+API+Templates

 Thanks and Regards,

 Hasanthi Dissanayake

 Software Engineer | WSO2

 E: hasan...@wso2.com nirosh...@wso2.com
 M :0718407133| http://wso2.com http://wso2.com/

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




 --
 Thanks  Regards,

 *Chamalee De Silva*
 Software Engineer
 *WS**O2* Inc. .:http://wso2.com
 lean *.* enterprise *.* middleware

 Office   :- *+94 11 2145345 %2B94%2011%202145345*
 mobile  :- *+94 7 %2B94%2077%2027820391 4315942*





-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [APIM] Changing the default timeout of published APIs

2015-06-25 Thread Chamalee De Silva
Hi Hasanthi,

You can change the synapse configuration of all APIs that are created as
you want according to [1].
Then it affects to the default values of the APIs created in the future too.

If you want to change the endpoint timeouts of already published APIs you
can change  the synapse config of each API in
API-HOME/repository/deployment/server/synapse-configs/default/api
directory and you can define an response action according to the changed
timeout.

Please refer [2] for more information.

[1]https://docs.wso2.com/display/AM160/Editing+API+Templates
[2]
https://docs.wso2.com/display/AM190/Tuning+Performance#TuningPerformance-APIM-levelsettings


On Fri, Jun 26, 2015 at 8:56 AM, Hasanthi Purnima Dissanayake 
hasan...@wso2.com wrote:

 Hi All,
 By editing the templates according to [1] we can change the timeout of
 default APIs. I think this will change the default time out of all APIs
 that will publish in future too. Please correct me if I'm wrong. Is there a
 way to change the timeout of already published APIs only without affecting
 to the future publishing APIs.

 [1]https://docs.wso2.com/display/AM160/Editing+API+Templates

 Thanks and Regards,

 Hasanthi Dissanayake

 Software Engineer | WSO2

 E: hasan...@wso2.com nirosh...@wso2.com
 M :0718407133| http://wso2.com http://wso2.com/

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Maheeka Jayasuriya

2015-06-24 Thread Chamalee De Silva
Congrats Maheeka!

On Wed, Jun 24, 2015 at 1:44 PM, Tharik Kanaka tha...@wso2.com wrote:

 Congradulations

 On Wed, Jun 24, 2015 at 1:20 PM, Isuru Ranawaka isu...@wso2.com wrote:

 Congrats !!!

 On Wed, Jun 24, 2015 at 10:40 AM, Viraj Senevirathne vir...@wso2.com
 wrote:

 Congratulations Maheeka .

 On Wed, Jun 24, 2015 at 10:36 AM, Dinithi De Silva dinit...@wso2.com
 wrote:

 Congratzzz maheeka... :)

 On Wed, Jun 24, 2015 at 10:29 AM, Kasun Indrasiri ka...@wso2.com
 wrote:

 Hi devs,

 Its my pleasure to welcome Maheeka Jayasuriya as a WSO2 Committer.
 Maheeka, welcome aboard and keep up the good work!

 Thanks.
 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

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




 --
 *Dinithi De Silva*
 Associate Software Engineer, WSO2 Inc.
 m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com
 | a: #20, Palm Grove, Colombo 03

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




 --
 Viraj Senevirathne
 Software Engineer; WSO2, Inc.

 Mobile : +94 71 818 4742 %2B94%20%280%29%20773%20451194
 Email : vir...@wso2.com thili...@wso2.com

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




 --
 Best Regards
 Isuru Ranawaka
 M: +94714629880
 Blog : http://isurur.blogspot.com/

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




 --

 *Tharik Kanaka*

 WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

 Email: tha...@wso2.com | Web: www.wso2.com

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Pumudu Ruhunage

2015-06-24 Thread Chamalee De Silva
Congrats Pumudu!

On Wed, Jun 24, 2015 at 11:20 AM, Madhawa Gunasekara madha...@wso2.com
wrote:

 Congratulations Pumudu :)

 On Wed, Jun 24, 2015 at 11:01 AM, Asitha Nanayakkara asi...@wso2.com
 wrote:

 Congratulations Pumudu!

 On Wed, Jun 24, 2015 at 10:59 AM, Ramith Jayasinghe ram...@wso2.com
 wrote:

 Hi Pumudu,
 Congratulations!
 It is with great pleasure that we welcome you as a WSO2 committer. Keep
 up the good work!
 regards,

 --
 Ramith Jayasinghe
 Technical Lead
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware

 E: ram...@wso2.com



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




 --
 *Asitha Nanayakkara*
 Software Engineer
 WSO2, Inc. http://wso2.com/
 Mob: + 94 77 85 30 682


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




 --
 *Madhawa Gunasekara*
 Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 719411002 +94+719411002
 blog: *http://madhawa-gunasekara.blogspot.com
 http://madhawa-gunasekara.blogspot.com*
 linkedin: *http://lk.linkedin.com/in/mgunasekara
 http://lk.linkedin.com/in/mgunasekara*

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Shiva Balachandran

2015-06-16 Thread Chamalee De Silva
Congrats Shiva!

On Tue, Jun 16, 2015 at 6:39 PM, Prasanna Dangalla prasa...@wso2.com
wrote:

 Congratulations Shiva

 On Tue, Jun 16, 2015 at 6:34 PM, Senduran Balasubramaniyam 
 sendu...@wso2.com wrote:

 Congratulations !!!

 On Tue, Jun 16, 2015 at 7:58 AM, Damith Wickramasinghe dami...@wso2.com
 wrote:

 Congratz machn !! :)

 On Tue, Jun 16, 2015 at 1:29 PM, Vijitha Ekanayake vijit...@wso2.com
 wrote:

 Congratulations Shiva !!

 On Tue, Jun 16, 2015 at 1:26 PM, Amal Gunatilake am...@wso2.com
 wrote:

 Congratulations Shiva !!

 On Tue, Jun 16, 2015 at 9:52 AM, Nandika Jayawardana nand...@wso2.com
  wrote:

 Hi All,

 It's my pleasure to announce Shiva Balachandran as a WSO2 committer.
 He has been a contributor to Business Process Server product and Process
 Center Product and in recognition of his contributions, he has been voted
 as a WSO2 Committer.

 Shiva, congratulations and keep up the good work.

 Regards
 Nandika

 --
 Nandika Jayawardana
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware

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




 --
 *Amal Gunatilake*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

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




 --
 Vijitha Ekanayake
 Software Engineer*, *WSO2, Inc.; http://wso2.com/
 Mobile : +94 777 24 73 39 | +94 718 74 44 08
 lean.enterprise.middleware

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




 --
 Software Engineer
 WSO2 Inc.; http://wso2.com
 http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg
 lean.enterprise.middleware

 mobile: *+94728671315 %2B94728671315*


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




 --
 *Senduran *
 Software Engineer,
 WSO2, Inc.;  http://wso2.com/ http://wso2.com/
 Mobile: +94 77 952 6548

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




 --
 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 777 55 80 30 | +94 718 11 27 51
 twitter: @prasa77

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-06-15 Thread Chamalee De Silva
Hi,
This is the fix [1] for public JIRA [2].
$Subject

[1] https://github.com/wso2/carbon-apimgt/pull/732
[2] https://wso2.org/jira/browse/APIMANAGER-3794

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Sam Sivayogam

2015-06-14 Thread Chamalee De Silva
Congrats Sam!

On Mon, Jun 15, 2015 at 9:26 AM, Elilmatha Sivanesan elilma...@wso2.com
wrote:

 Congratulations Sam...

 On Mon, Jun 15, 2015 at 9:19 AM, Kesavan Yogarajah kesav...@wso2.com
 wrote:

 Congratulations Sam !

 Kesavan Yogarajah
 Associate Software Engineer
 Mobile :+94 (0) 779 758021
 kesav...@wso2.com
 WSO2, Inc.
 lean . enterprise . middleware

 On Mon, Jun 15, 2015 at 9:14 AM, Senduran Balasubramaniyam 
 sendu...@wso2.com wrote:

 Congratulations Sam !!!

 On Sun, Jun 14, 2015 at 10:34 PM, Thilini Cooray thili...@wso2.com
 wrote:

 Congratulations, Sam !

 On Mon, Jun 15, 2015 at 8:58 AM, Rajeevan Vimalanathan 
 rajeev...@wso2.com wrote:

 Congrats Sam...!!!

 On Mon, Jun 15, 2015 at 8:44 AM, Vinuri Perera vinu...@wso2.com
 wrote:

 Congrats Sam !

 On Mon, Jun 15, 2015 at 8:37 AM, Saneth Dharmakeerthi 
 sane...@wso2.com wrote:

 Congratulations Sam...

 Thanks and Best Regards,

 Saneth Dharmakeerthi
 Senior Software Engineer
 WSO2, Inc.
 Mobile: +94772325511

 On Mon, Jun 15, 2015 at 8:31 AM, Nuwan Dias nuw...@wso2.com wrote:

 Hi,

 It is with great pleasure we welcome Sam Sivayogam as a WSO2
 Committer. @Sam, congratulations and keep up the good work!

 Thanks,
 NuwanD.

 --
 Nuwan Dias

 Technical Lead - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

 ___
 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




 --
 Vinuri Perera
 Software Engineer | WSO2 Inc

 M : 0711518805


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




 --

 Vimalanathan Rajeevan
 Software Engineer
 WSO2 Inc.:http://wso2.com
 lean.enterprise.middleware


 Mobile : +94 773090875

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




 --
 Best Regards,

 *Thilini Cooray*
 Software Engineer
 Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194
 E-mail : thili...@wso2.com

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

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




 --
 *Senduran *
 Software Engineer,
 WSO2, Inc.;  http://wso2.com/ http://wso2.com/
 Mobile: +94 77 952 6548

 ___
 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




 --
 *S.Elilmatha*
 Associate  Software Engineer,

 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 Mobile 0779842221.


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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-06-10 Thread Chamalee De Silva
Hi,

 This is the fix [1] for Public JIRA [2].

$Subject.

[1] https://github.com/wso2/carbon-apimgt/pull/665
[2] https://wso2.org/jira/browse/APIMANAGER-3779

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Saneth Dharmakeerthi

2015-06-09 Thread Chamalee De Silva
Congrats Saneth!

On Tue, Jun 9, 2015 at 5:32 PM, Nuwan Silva nuw...@wso2.com wrote:

 Congrats Saneth :)

 On Tue, Jun 9, 2015 at 5:22 PM, Dimuthu De Lanerolle dimut...@wso2.com
 wrote:

 Congrats Saneth !!!



 On Tue, Jun 9, 2015 at 2:07 PM, Inshaf Mahath ins...@wso2.com wrote:

 Congrats Saneth!!

 On Tue, Jun 9, 2015 at 2:00 PM, Elilmatha Sivanesan elilma...@wso2.com
 wrote:

 Congratulations Saneth

 On Tue, Jun 9, 2015 at 1:57 PM, Jerad Rutnam je...@wso2.com wrote:

 Congratulations Saneth! :)

 --
 *Jerad Rutnam*
 *Software Engineer*

 WSO2 Inc.
 lean | enterprise | middleware
 M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com

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




 --
 *S.Elilmatha*
 Associate  Software Engineer,

 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 Mobile 0779842221.


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




 --
 Inshaf Mahath
 Associate Software Engineer
 Mobile: +94775907181
 WSO2 Inc.
 Lean . Enterprise . Middleware


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




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




 --


 *Nuwan Silva*
 *Senior Software Engineer - QA*
 Mobile: +9477 980 4543

 WSO2 Inc.
 lean . enterprise . middlewear.
 http://www.wso2.com

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] How to run 2 servers at once using different port numbers?

2015-06-05 Thread Chamalee De Silva
Hi,

Adding more,

To change the port offset in Jaggery server you have to go the following
location, which is bit different from the other WSO2 products.

*PRODUCT_HOME/carbon/repository/conf/carbon.xml*

On Fri, Jun 5, 2015 at 5:32 PM, Shabir Mohamed sha...@wso2.com wrote:

 Hi Aaquibah,

 If you will be working with such scenarios more often, then a more
 persistent way is to change the *port offset *in the *carbon.xml*
  file.
 This way you'll not need to do put in the *-DportOffset *flag all the
 time.

 The *carbon.xml *file is the main configurations file found inside
 every WSO2 carbon based product.

 It's at: *PRODUCT_HOME/repository/conf/carbon.xml*


 *Ports*
 *!-- Ports offset. This entry will set the value of the ports
 defined below to*
 * the define value + Offset.*
 * e.g. Offset=2 and HTTPS port=9443 will set the effective HTTPS
 port to 9445*
 * --*
 *Offset0/Offset*
 * *


 Regards

 -
 *Shabir Mohamed*
 *Software Engineer*
 WSO2 Inc.; http://wso2.com
 Email: sha...@wso2.com ayy...@wso2.com
 Mobile: +94 77 3516019 | +94 71 6583393

 On Fri, Jun 5, 2015 at 5:19 PM, Aaquibah Nashry nas...@wso2.com wrote:

 Hi Kalpa,

 It works.

 Thanks

 M.R.Aaquibah Nashry
 *Intern, Engineering*
 Mobile : +94 773946123
 Tel  : +94 112662541
 nas...@wso2.com

 On Fri, Jun 5, 2015 at 5:16 PM, Kalpa Welivitigoda kal...@wso2.com
 wrote:

 Hi Nashry,

 Try, sh wso2server.sh -DportOffset=1

 On Fri, Jun 5, 2015 at 5:12 PM, Aaquibah Nashry nas...@wso2.com wrote:

 Hi,
 I am trying to run the esb and jaggery servers at once.
 I tried it as follows:
 i first ran the jaggery server. Then used: sh wso2server.sh -D offset
 key=1
 But it doesn't work.
 Can anyone help me on this?

 I am using Ubuntu.
 Thanks,

 M.R.Aaquibah Nashry
 *Intern, Engineering*
 Mobile : +94 773946123
 Tel  : +94 112662541
 nas...@wso2.com

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




 --
 Best Regards,

 Kalpa Welivitigoda
 Software Engineer, WSO2 Inc. http://wso2.com
 Email: kal...@wso2.com
 Mobile: +94776509215



 ___
 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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-06-05 Thread Chamalee De Silva
This is the fix [1] for Public JIRA  issue [2].
$Subject.

[1] https://github.com/wso2/carbon-apimgt/pull/617
[2] https://wso2.org/jira/browse/APIMANAGER-3699


-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Dinithi De Silva

2015-05-28 Thread Chamalee De Silva
Congrats Dinithi !!! :D

On Thu, May 28, 2015 at 11:40 AM, Imesh Gunaratne im...@wso2.com wrote:

 Hi Devs,

 It's my pleasure to welcome Dinithi De Silva as a WSO2 Committer. She has
 contributed to WSO2 Private PaaS and other WSO2 products in many different
 ways. In recognition of her contributions she was voted as a WSO2 Committer.

 Dinithi, Congratulations! Keep up the good work!

 Thanks

 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge.

2015-05-27 Thread Chamalee De Silva
Hi,

This is the fix [1] for Public JIRA [2].

$Subject.

[1] https://github.com/wso2/carbon-apimgt/pull/511
[2] https://wso2.org/jira/browse/APIMANAGER-2750

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge

2015-05-26 Thread Chamalee De Silva
This is the Fix [1] for public JIRA [2].

$Subject.

[1] https://github.com/wso2/carbon-apimgt/pull/492
[2] https://wso2.org/jira/browse/APIMANAGER-3649

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge

2015-05-22 Thread Chamalee De Silva
Hi,

This is the Fix [1] for publich JIRA [2].

Please review and merge.

[1] https://github.com/wso2/carbon-apimgt/pull/459
[2] https://wso2.org/jira/browse/APIMANAGER-1821

-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Review and Merge the PRs

2015-05-20 Thread Chamalee De Silva
Hi,

The JIRA issue [1] is fixed. The PRs for carbon-apimgt and product-apim are
in [2] and [3] respectively.

Please $Subject.

[1]https://wso2.org/jira/browse/APIMANAGER-2854

[2] https://github.com/wso2/carbon-apimgt/pull/445
[3] https://github.com/wso2/product-apim/pull/175


-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please review and merge the PR

2015-05-19 Thread Chamalee De Silva
Hi,

This is the fix PR [1] for Public JIRA [2].
Please $subject.

[1] https://github.com/wso2/carbon-apimgt/pull/416
[2] https://wso2.org/jira/browse/APIMANAGER-3569



-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Vishanth Balasubramaniam

2015-05-16 Thread Chamalee De Silva
Congrats Vishanth..!! :)

On Sat, May 16, 2015 at 8:07 AM, Viraj Senevirathne vir...@wso2.com wrote:

 Congratulations  Vishanth ...!

 On Sat, May 16, 2015 at 5:31 AM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Congratualtions Vishanth...!!

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Sat, May 16, 2015 at 12:13 AM, Prasanna Dangalla prasa...@wso2.com
 wrote:

 Congratulations

 On Fri, May 15, 2015 at 11:12 PM, Damith Wickramasinghe 
 dami...@wso2.com wrote:

 Congrats Vishanth !!!

 On Fri, May 15, 2015 at 10:58 PM, Harsha Kumara hars...@wso2.com
 wrote:

 Congratulation Vishanth!

 On Fri, May 15, 2015 at 10:37 PM, Thusitha Thilina Dayaratne 
 thusit...@wso2.com wrote:

 Congratulations...!

 On Fri, May 15, 2015 at 7:10 PM, Madhuranga Bandara 
 madhura...@wso2.com wrote:

 Congratulations Vishanth !!!
 Madhuranga Sampath Bandara
 Software Engineer

 WSO2, Inc.;http://wso2.com/
 lean.enterprise.middleware
 Mobile: +94722241065


 On Fri, May 15, 2015 at 6:58 PM, Imesh Gunaratne im...@wso2.com
 wrote:
  Hi Devs,
 
  It's my pleasure to welcome Vishanth Balasubramaniam as a WSO2
 Committer.
  Vishanth, welcome aboard and keep up the good work!
 
  Thanks
 
  --
  Imesh Gunaratne
  Senior Technical Lead
  WSO2 Inc: http://wso2.com
  T: +94 11 214 5345 M: +94 77 374 2057
  W: http://imesh.gunaratne.org
  Lean . Enterprise . Middleware
 
 
  ___
  Dev mailing list
  Dev@wso2.org
  http://wso2.org/cgi-bin/mailman/listinfo/dev
 
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina


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




 --
 Harsha Kumara
 Software Engineer, WSO2 Inc.
 Mobile: +94775505618
 Blog:harshcreationz.blogspot.com

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




 --
 Software Engineer
 WSO2 Inc.; http://wso2.com
 http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg
 lean.enterprise.middleware

 mobile: *+94728671315 %2B94728671315*


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




 --
 Prasanna Dangalla
 Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware

 cell: +94 777 55 80 30 | +94 718 11 27 51
 twitter: @prasa77

 ___
 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




 --
 Viraj Senevirathne
 Software Engineer; WSO2, Inc.

 Mobile : +94 71 818 4742 %2B94%20%280%29%20773%20451194
 Email : vir...@wso2.com thili...@wso2.com

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




-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge PR

2015-05-11 Thread Chamalee De Silva
Hi,

Please $subject [1] for issue [2].

[1] https://github.com/wso2/carbon-apimgt/pull/368
[2] https://wso2.org/jira/browse/APIMANAGER-3547


-- 
Thanks  Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware

Office   :- *+94 11 2145345 %2B94%2011%202145345*
mobile  :- *+94 7 %2B94%2077%2027820391 1540738*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please review and Merge the PR

2015-04-28 Thread Chamalee De Silva
Hi,

This is the Fix [1] for the Public JIRA [2].

[1] https://github.com/wso2/carbon-apimgt/pull/257
[2] https://wso2.org/jira/browse/APIMANAGER-3270

 $subject.

-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Mahesh Chinthaka

2015-04-27 Thread Chamalee De Silva
Congratulations Mahesh !

On Tue, Apr 28, 2015 at 11:13 AM, Dilan Udara Ariyaratne dil...@wso2.com
wrote:

 Congratz, Mahesh!!!


 *Dilan U. Ariyaratne*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 Mobile: +94775149066
 lean . enterprise . middleware

 On Tue, Apr 28, 2015 at 10:40 AM, Samith Dassanayake sam...@wso2.com
 wrote:

 Congratz Mahesh!

 On Tue, Apr 28, 2015 at 10:28 AM, Kalpa Welivitigoda kal...@wso2.com
 wrote:

 Congratulations Mahesh !

 On Tue, Apr 28, 2015 at 10:28 AM, Tharik Kanaka tha...@wso2.com wrote:

 Congratulations Mahesh.

 On Tue, Apr 28, 2015 at 9:27 AM, Dimuthu Leelarathne dimut...@wso2.com
  wrote:

 Hi all,

 It is with great pleasure that WSO2 welcomes Mahesh Chinthaka as WSO2
 committer!

 Thank you for your hard work. Congratulation!

 thanks,
 dimuthu

 --
 Dimuthu Leelarathne
 Architect  Product Lead of App Factory

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com
 Mobile : 0773661935

 Lean . Enterprise . Middleware

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




 --

 *Tharik Kanaka* | Associate Software Engineer

 WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

 Email: tha...@wso2.com | Web: www.wso2.com

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




 --
 Best Regards,

 Kalpa Welivitigoda
 Software Engineer, WSO2 Inc. http://wso2.com
 Email: kal...@wso2.com
 Mobile: +94776509215

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




 --
 Best Regards

 Samith Dassanayake
 Software Engineer | Cloud TG
 WSO2, Inc. | http://wso2.com
 lean. enterprise. middleware

 Mobile : +947 76207351

 ___
 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




-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-04-24 Thread Chamalee De Silva
This is the Fix PR [1] for the JIRA [2].

Please review and merge.

[1] https://github.com/wso2/carbon-apimgt/pull/229
[2] https://wso2.org/jira/browse/APIMANAGER-3129

-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please Review and Merge the PR

2015-04-22 Thread Chamalee De Silva
Hi,

This is the fix PR [1] for the public JIRA [2].

Consumer-key:authz_user combination is used to validate the subscription
throttling tier instead of using access token.

Through that the ability of the user to send more than permitted number of
requests per minute by regenerating the access token is avoided.


Please review and merge.

[1] *https://github.com/wso2/carbon-apimgt/pull/208
https://github.com/wso2/carbon-apimgt/pull/208*
[2] https://wso2.org/jira/browse/APIMANAGER-3406

Thanks and Regards,

-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Please merge the pull request

2015-04-16 Thread Chamalee De Silva
Please merge the pull request [1] for fixing the JIRA [2].

[1] https://github.com/wso2/carbon-apimgt/pull/187
[2] https://wso2.org/jira/browse/APIMANAGER-2703

Thank you.

-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [MB] Unauthorized call! when calling a method in AndesAdminService in Message Broker

2015-04-01 Thread Chamalee De Silva
.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Apr 1, 2015 2:38:16 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [bridgeservlet] in context with path
[/] threw exception [An exception occurred processing JSP page
/queues/update_queue_role_permissions_ajaxprocessor.jsp at line 43

40:
41: QueueRolePermission[] queueRolePermissions = new
QueueRolePermission[queueRolePermissionArrayList.size()];
42: try{
43: stub.updatePermissionWithExclusiveConsumer(queue,
queueRolePermissionArrayList.toArray(queueRolePermissions),
exclusiveConsumer);
44: message = Queue updated successfully;
45: } catch (AndesAdminServiceBrokerManagerAdminException e) {
46: message = Error in adding/updating permissions :  +
e.getMessage();



-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [MB] Unauthorized call! when calling a method in AndesAdminService in Message Broker

2015-04-01 Thread Chamalee De Silva
Thanks Hemika and Akalanka,




On Wed, Apr 1, 2015 at 2:56 PM, Hemika Kodikara hem...@wso2.com wrote:

 Hi Chamalee,

 I think you have to add your new stub to the following file.


 carbon-business-messaging/components/andes/org.wso2.carbon.andes.admin/src/main/resources/META-INF/services.xml

 as follows..

 operation name=updatePermissionWithExclusiveConsumer
 parameter name=AuthorizationAction
 locked=false/permission/admin/manage/queue/parameter
 /operation

 Regards,
 Hemika

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

 On Wed, Apr 1, 2015 at 2:50 PM, Chamalee De Silva chama...@wso2.com
 wrote:

 Hi all,

 I am doing fast track training project in WSO2 Message Broker.
 To dynamically update a queue, I wrote a method  called
 updatePermissionWithExclusiveConsumer in AndesAdminService and
 generated stubs for that.


 When calling the stub method through the relevant JSP file it gives this
 error.

 Can I know are there any other configurations to be done when adding a
 method to the AndesAdminService or how to solve this issue?



 

 *StackTrace: *

 [2015-04-01 14:38:16,524] ERROR {org.apache.axis2.engine.AxisEngine} -
  Unauthorized call!. AuthorizationAction has not been specified for
 service:AndesAdminService, operation:updatePermissionWithExclusiveConsumer
 org.apache.axis2.AxisFault: Unauthorized call!. AuthorizationAction has
 not been specified for service:AndesAdminService,
 operation:updatePermissionWithExclusiveConsumer
 at
 org.wso2.carbon.server.admin.module.handler.AuthorizationHandler.invoke(AuthorizationHandler.java:72)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
 at
 org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
 at
 org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
 at
 org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
 at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
 at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
 at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
 at
 org.wso2.carbon.andes.stub.AndesAdminServiceStub.updatePermissionWithExclusiveConsumer(AndesAdminServiceStub.java:1881)
 at
 org.apache.jsp.queues.update_005fqueue_005frole_005fpermissions_005fajaxprocessor_jsp._jspService(update_005fqueue_005frole_005fpermissions_005fajaxprocessor_jsp.java:109)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
 at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
 at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
 at
 org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
 at
 org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
 at
 org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at
 org.apache.catalina.core.StandardContextValve.invoke

Re: [Dev] WSO2 Committers += Hemika Kodikara

2015-03-18 Thread Chamalee De Silva
Congratz Hemika !!

On Tue, Mar 17, 2015 at 1:41 PM, Ramith Jayasinghe ram...@wso2.com wrote:

 Hi Hemika,
 Congratulations!
 It is with great pleasure that we welcome you as a WSO2 committer. Keep
 up the good work!
 regards,

 --
 Ramith Jayasinghe
 Technical Lead
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware

 E: ram...@wso2.com


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




-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Committers += Dinesh J Weerakkody

2015-03-11 Thread Chamalee De Silva
congrats!

On Thu, Mar 12, 2015 at 8:24 AM, Abimaran Kugathasan abima...@wso2.com
wrote:

 Congrats!

 On Thu, Mar 12, 2015 at 8:17 AM, Nuwan Dias nuw...@wso2.com wrote:

 Hi,

 It is with great pleasure we welcome DineshW as a WSO2 Committer.
 @Dinesh, congratulations and keep up the good work!

 Thanks,
 NuwanD.

 --
 Nuwan Dias

 Associate Tech Lead - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

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




 --
 Thanks
 Abimaran Kugathasan

 Software Engineer | WSO2 Inc
 Data  APIs Technologies Team
 Mobile : +94 773922820

 http://stackoverflow.com/users/515034
 http://lk.linkedin.com/in/abimaran
 http://www.lkabimaran.blogspot.com/  https://github.com/abimaran
 https://twitter.com/abimaran


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




-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Management Console UI changes to WSO2 MB

2015-03-10 Thread Chamalee De Silva
Hi all,

I am currently doing my fast track training project in WSO2 Message Broker.

I want  to do a UI change in the Message broker Management Console by
adding another row with a check-box to an existing HTML table.

[image: Inline image 1]



I went through the documentation links and found the following jars to
change the layout and theme etc.

   1. org.wso2.carbon.ui-3.2.2.jar
   2. org.wso2.mb.styles-3.2.0.jar

But my requirement is to add HTML elements. Not changing css  styles.
Can anyone help me in getting this solved.

Thank you.


-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Management Console UI changes to WSO2 MB

2015-03-10 Thread Chamalee De Silva
Hi Indika,

Thanks for the quick response.
This really helps.


On Tue, Mar 10, 2015 at 4:12 PM, Indika Sampath indi...@wso2.com wrote:

 Hi Chamalee,

 Hope you have fork carbon-business-messaging and clone it to your local
 machine. You can find JSP of above page in following location.


 carbon-business-messaging/components/andes/org.wso2.carbon.andes.ui/src/main/resources/web/queues/queue_add.jsp

 Cheers!



 On Tue, Mar 10, 2015 at 3:59 PM, Malintha Adikari malin...@wso2.com
 wrote:



 On Tue, Mar 10, 2015 at 10:16 AM, Chamalee De Silva chama...@wso2.com
 wrote:

 Hi all,

 I am currently doing my fast track training project in WSO2 Message
 Broker.

 I want  to do a UI change in the Message broker Management Console by
 adding another row with a check-box to an existing HTML table.

 [image: Inline image 1]



 I went through the documentation links and found the following jars to
 change the layout and theme etc.

1. org.wso2.carbon.ui-3.2.2.jar
2. org.wso2.mb.styles-3.2.0.jar

 But my requirement is to add HTML elements. Not changing css  styles.
 Can anyone help me in getting this solved.

 Thank you.


 --

 Chamalee De Silva

 Software Engineer | WSO2

 E:chama...@wso2.com nirosh...@wso2.com
 M :0711540738| http://wso2.com http://wso2.com/




 --
 *Malintha Adikari*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 Mobile: +94 71 2312958
 Blog:http://malinthas.blogspot.com
 Page:   http://about.me/malintha

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




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

 Phone: +94 716 424 744
 Blog: http://indikasampath.blogspot.com/




-- 

Chamalee De Silva

Software Engineer | WSO2

E:chama...@wso2.com nirosh...@wso2.com
M :0711540738| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev