date:20160906

Re: [Dev] Introducing patterns for WSO2 Puppet Modules

2016-09-06 Thread Samuel Gnaniah

Noted. Let's have a small chat on this if possible Imesh.

Thanks,

*Samuel Gnaniah*
Lead Technical Writer

WSO2 (pvt.) Ltd.
Colombo, Sri Lanka
(+94) 773131798

On Wed, Sep 7, 2016 at 12:36 AM, Imesh Gunaratne  wrote:

> On Tue, Sep 6, 2016 at 10:09 PM, Pubudu Gunatilaka 
> wrote:
>
>>
>> Patterns will be able to use with hieradata and the following is the
>> hiera hierarchy.
>>
>> ---
>> :hierarchy:
>> - "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
>> - "wso2/%{::product_name}/%{::pattern}/common"
>> - "wso2/common"
>>
>> +1 for the new hierachy.
>
>>
>>
> Initially, we will ship two basic patterns which are single JVM and fully
>> distributed deployment. Product teams will be able to add more patterns by
>> adding relevant hieradata in later stages. You can refer sample patterns
>> done for WSO2 Application Server [2].
>>
>> Hierarchy is created based on the following facts.
>>
>> 1. Pattern_01 will be always the vanilla pack.
>>
>
> It might be better to make this the single JVM deployment pattern. Calling
> it vanilla configuration might mislead users.
>
> BTW do we need to add a zero before the pattern number? I would prefer to
> avoid that.
> 
>
>
>> 2. There will be common.yaml file in every pattern except pattern_01 to
>> share common data among the pattern. For an example, common.yaml in
>> pattern_02 will have the values common to worker and manager profiles [3].
>>
>
>
>> 3. Hieradata which is common to all the products will be kept in
>> puppet-base repo [4] and product specific hieradata will be kept in
>> relevant product repo. To run any product with hieradata, you need to merge
>> hieradata in puppet-base and product repo.
>>
>
> I
> f we use the term merge, it might mean that we need to merge contents of
> files. Might be better to say that we need to copy hieradata files from
> both puppet-base and product repositories.
>
> @Sam: We are trying to standardize deployment patterns of all products via
> Puppet. It would be great if we can document them in WSO2 Docs.
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

2016-09-06 Thread Chamila Adhikarinayake

You have to create a certificate for the keymanager node with CN as
keymanager and then import that certificate to AM client-trustore.jks. This
should fix the issue. See this blog[1] for similar issue

[1]
https://medium.com/@dunithd/wso2-das-how-to-fix-javax-net-ssl-sslexception-160c13bc8fe7#.wnbvm5mvv

On Tue, Sep 6, 2016 at 11:57 AM, Supun Malinga  wrote:

> Hi,
>
> When gateway is validating token with keymanager, getting the following
> error at gateway worker log,
>
> [2016-09-06 06:09:22,013]  INFO - HTTPSender Unable to sendViaPost to url[
> https://keymanager:9443/services/APIKeyValidationService]
> javax.net.ssl.SSLException: hostname in certificate didn't match:
>  != 
> 
>
> Looks like keymanager is rejecting the requests.
> How do I allow all hostnames here?.
>
> In keymanager wso2server.sh I see following enabled already,
>
> -Dorg.opensaml.httpclient.https.disableHostnameVerification=true \
> -Dorg.wso2.ignoreHostnameVerification=true \
>
> thanks,
> --
> Supun Malinga
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Validations applied to 'AndesSetRoutingKey' property

2016-09-06 Thread Hemika Kodikara

Hi Sashika,

The feature will be enabled only when a value is set to the property.

No validation occurs here and also it removes the chance for user error on
setting the property to an invalid value. By default the feature is not
enabled. To enable we have to set a value to the property.

This behavior can be found for "amqj.protocol.logging.level" property[1] as
well in qpid.

[1] -
https://cwiki.apache.org/confluence/display/qpid/System+Properties#SystemProperties-amqj.protocol.logging.level

Regards,
Hemika

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

Mobile : +9477762

On Tue, Sep 6, 2016 at 2:13 AM, Sashika Wijesinghe  wrote:

> Hi Hemika,
>
> When setting a routing key to a message I have used 
> "System.setProperty("AndesSetRoutingKey",
> "1");" as described in the documentation [1]. As I observed any value set
> for the "AndesSetRoutingKey" is considered as valid and the routing key
> property is set to the message.
>
> May I know whether there is any validation applied to this property? I
> have set an empty value as "System.setProperty("AndesSetRoutingKey",
> "");" , this is also considered as valid and the "JMS_ANDES_ROUTING_KEY"
> property set to the correct queue destination. When I passed a null value
> to the property it fails with NullPointerException. According to [2] 'null'
> value can not be set to a property.
>
> [1] https://docs.wso2.com/display/MB320/Setting+the+
> Routing+Key+for+Messages
> [2] http://stackoverflow.com/questions/4323995/set-system-
> propery-to-null-in-java
>
> Thank You
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [puppet] Setting up puppet home from script

2016-09-06 Thread Imesh Gunaratne

Great work Anuruddha! The bash script works well!

Shall we add the ability to install multiple product modules in one go?
Maybe we can use a comma separated product list with -p.

Thanks

On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi  wrote:

> Hi,
>
> We have  created separate GitHub repos for Puppet modules so that the
> Puppet module can be shipped as part of a product release.
>
> Since modules are distributed we have introduced a script to generate
> PUPPET_HOME. The script will work as following.
>
>  1. Check puppet_home folder exists.
>
>  2. Create folder structure required for puppet_home.
> ├── hiera.yaml
> ├── hieradata
> ├── manifests
> └── modules
>
> 3.  Create a symlink to manifest/site.pp file.
>
> 4. Clone wso2base puppet module into  /modules directory.
>
> 5. Create a symlink to wso2base common.yaml hiera-file.
>
>> /modules/wso2base/hieradata/wso2/common.yaml ->
>> /hieradata/dev/wso2/
>
>
> 6. Clone wso2 puppet module into  /modules directory.
>
> 7. Create a symlink to wso2 hiera-files.
>
>>   /wso2/hieradata/dev/wso2/wso2 ->
>> ../hieradata/dev/wso2/
>
>
> Once the setup.sh completes, users can copy product pack and jdk
> distribution for relevant folders and run vagrant setup against
> above-created puppet home.
>
> We are planning to automate the copying of product pack, jdk distribution
> and starting vagrant setup as well.
>
> Setup.sh can be found at [1]. Please share your suggestions towards this
> approach.
>
> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing patterns for WSO2 Puppet Modules

2016-09-06 Thread Imesh Gunaratne

On Tue, Sep 6, 2016 at 10:09 PM, Pubudu Gunatilaka  wrote:

>
> Patterns will be able to use with hieradata and the following is the hiera
> hierarchy.
>
> ---
> :hierarchy:
> - "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
> - "wso2/%{::product_name}/%{::pattern}/common"
> - "wso2/common"
>
> +1 for the new hierachy.

>
>
Initially, we will ship two basic patterns which are single JVM and fully
> distributed deployment. Product teams will be able to add more patterns by
> adding relevant hieradata in later stages. You can refer sample patterns
> done for WSO2 Application Server [2].
>
> Hierarchy is created based on the following facts.
>
> 1. Pattern_01 will be always the vanilla pack.
>

It might be better to make this the single JVM deployment pattern. Calling
it vanilla configuration might mislead users.

BTW do we need to add a zero before the pattern number? I would prefer to
avoid that.



> 2. There will be common.yaml file in every pattern except pattern_01 to
> share common data among the pattern. For an example, common.yaml in
> pattern_02 will have the values common to worker and manager profiles [3].
>


> 3. Hieradata which is common to all the products will be kept in
> puppet-base repo [4] and product specific hieradata will be kept in
> relevant product repo. To run any product with hieradata, you need to merge
> hieradata in puppet-base and product repo.
>

I
f we use the term merge, it might mean that we need to merge contents of
files. Might be better to say that we need to copy hieradata files from
both puppet-base and product repositories.

@Sam: We are trying to standardize deployment patterns of all products via
Puppet. It would be great if we can document them in WSO2 Docs.

Thanks

-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Puppet] Way forward with WSO2 Puppet modules

2016-09-06 Thread Imesh Gunaratne

Thanks for sharing the implementation details Akila! I did some refinements
to the README.md files.

I tried out WSO2AS module and it is working as expected. Great work! It
seems like we still need to copy the product distribution to the
/files folder. Copying it to
/files/packs did not work.

@DevOps Team: It would be great if you guys can review the improvements we
have done.

Thanks


On Tue, Sep 6, 2016 at 5:21 PM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> We have already created separate GitHub repos for Puppet modules so that
> the Puppet module can be shipped as part of a product release. All common
> resources and classes are still in wso2base Puppet module. We have
> refactored the module structure which I'll highlight below;
>
> Please refer to wso2base module [1] and  wso2as module [2] which we have
> implemented as a reference. We will discuss any improvements needed and
> replicate the same structure for other modules.
>
>  - No more Hiera lookups in init.pp
>All Hiera lookups have been moved to params classes in wso2base and
> product module. All common parameters across products are defined in
> wso2base/params.pp and product specific ones are defined in corresponding
> product Puppet module
>
>  - Do Hiera lookups only when enabled via a facter
>wso2base/params.pp lookup a facter named "use_hieradata" and decide
> whether to take default values defined directly in params.pp or to perform
> Hiera lookups. It would have been ideal if Hiera lookups are all done in a
> separate layer (for eg: using roles and profiles pattern), but one problem
> is users will have to write their own profiles module to use Hiera.
> Maintaining profiles in our side would be an overhead. This is still open
> to suggestions.
>
>  - Class parameters to override defaults in params.pp
>Earlier Puppet modules were tightly coupled with Hiera so that users
> were unable to simply include the module from site.pp and run it. Now all
> the variables are defined as class parameters which takes common values
> from wso2base/params.pp [4]. Default values for any product specific
> parameters are kept in /params.pp. For eg: [5]
>
> Any user can now simply do the following in site.pp
>
> class java -> class wso2as
>
> Above manifest will configure wso2as using default configuration (vanilla
> pack). Default values can be overridden by passing values. For eg: to set a
> port offset of 10
>
> $ports = {
> offset => 10
> }
> class java ->
> class  { 'wso2as':
>ports => $ports
> }
>
>  - Class dependencies and containment
>   All base classes are contained in product module main class to enforce
> the class dependency order [6].
>
>  - Data type validation
>To enforce that parameters passed are in expected format and to help
> with troubleshooting we have added validations in wso2base module which
> checks whether data types passed for each parameter is correct [7].
>
>  - Vagrant setup
>We have moved out the Vagrantfile, site.pp and hiera.yaml files to a
> separate repo named "puppet-commons" [3]. This repo will contain any Puppet
> related artifact which does not belong to a Puppet module. It has a
> setup.sh shell script to create the PUPPET_HOME directly by cloning Puppet
> module GitHub repos and merging Hieradata. Details about this setup.sh
> script will be discussed in a separate thread.
>
> Any developer who wants to try out a Puppet module can do so by performing
> following steps;
> 1. Git clone puppet-commons
> 2. Run setup.sh
> 3. Provide PUPPET_HOME when prompted by setup.sh
> 4. Provide JDK file location product pack location when prompted
> 5. Goto puppet-commons/vagrant
> 6. Run vagrant up
>
> Note that we have not fully implemented the end-to-end flow yet.
>
> [1] https://github.com/wso2/puppet-base
> [2] https://github.com/wso2/puppet-as
> [3] https://github.com/wso2/puppet-commons
> [4] https://github.com/wso2/puppet-base/blob/master/manifests/params.pp
> [5] https://github.com/wso2/puppet-as/blob/master/manifests/params.pp#L29
> [6] https://github.com/wso2/puppet-as/blob/master/manifests/init.pp#L115
> [7] https://github.com/wso2/puppet-base/blob/master/
> manifests/init.pp#L55-L86
>
> Thanks.
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Vote] Release WSO2 Complex Event Processor (CEP) 4.2.0-RC2

2016-09-06 Thread Dilini Muthumala

Hi Devs,

This is the second release candidate (RC2) of WSO2 Complex Event Processor
version 4.2.0.

*New Features / Improvements in This Release*

[CEP-322 ] - Unique time window
support for Siddhi
[CEP-1442 ] - Create a role for
analytics dashboard with necessary permissions (CEP & DAS)
[CEP-1476 ] - Siddhi Map Extension :
map:CreateFromXML() only support XML with root element
[CEP-1488 ] - Allow '-' in
@Import/@Export section in execution plan
[CEP-1497 ] - Custom XML input
mapping should be able to populate stream attributes from XML attributes
[CEP-1507 ] - Siddhi Extension for
calculate percentile values
[CEP-1510 ] - External Time Batch
Window Implementation
[CEP-1511 ] - Template Manager
support for other deployable artifacts
[CEP-1512 ] - MaxForever and
MinForever Attribute Aggregators for Siddhi
[CEP-1514 ] - Make Distruptor as
configurable in Siddhi
[CEP-1515 ] - RDBMS event table does
not work with new RDBMS database types
[CEP-1516 ] - Distinct Attribute
Aggretaor for Siddhi
[CEP-1517 ] - Split Function for
String Siddhi Extension
[CEP-1520 ] - Necessary improvement
to ExternalTimeBatch window
[CEP-1526 ] - Improve event
receiver/publisher JMS configuration to support Tibco EMS
[CEP-1528 ] - Provide support for
string values to be used in line charts x axis in real time gadets
[CEP-1532 ] - Add basicAuth enable
property for http event receiver
[CEP-1540 ] - [Template Manager UI]
JSP pages which are not invoked through Ajax are named as
*_ajaxprocessor.jsp
[CEP-1574 ] - JNDI Connector to
Sonic MQ.


*Fixed Issues in This Release*

   - Bug Fixes 

*Known Issues*

   - Known Issues 

*Source and distribution packages:*

   - 
*https://github.com/wso2/product-cep/releases/download/v4.2.0-rc2/wso2cep-4.2.0-RC2.zip
   
*


Please download, test, and vote. The README file under the distribution
contains guide and instructions on how to try it out locally. [+] Stable -
Go ahead and release [-] Broken - Do not release (explain why) This vote
will be open for 72 hours or as needed. Regards,
WSO2 CEP Team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Vote] Release WSO2 Complex Event Processor (CEP) 4.2.0-RC2

2016-09-06 Thread Dilini Muthumala

Hi Devs,

This is the second release candidate (RC2) of WSO2 Complex Event Processor
version 4.2.0.

*New Features / Improvements in This Release*

[CEP-322 ] - Unique time window
support for Siddhi
[CEP-1442 ] - Create a role for
analytics dashboard with necessary permissions (CEP & DAS)
[CEP-1476 ] - Siddhi Map Extension :
map:CreateFromXML() only support XML with root element
[CEP-1488 ] - Allow '-' in
@Import/@Export section in execution plan
[CEP-1497 ] - Custom XML input
mapping should be able to populate stream attributes from XML attributes
[CEP-1507 ] - Siddhi Extension for
calculate percentile values
[CEP-1510 ] - External Time Batch
Window Implementation
[CEP-1511 ] - Template Manager
support for other deployable artifacts
[CEP-1512 ] - MaxForever and
MinForever Attribute Aggregators for Siddhi
[CEP-1514 ] - Make Distruptor as
configurable in Siddhi
[CEP-1515 ] - RDBMS event table does
not work with new RDBMS database types
[CEP-1516 ] - Distinct Attribute
Aggretaor for Siddhi
[CEP-1517 ] - Split Function for
String Siddhi Extension
[CEP-1520 ] - Necessary improvement
to ExternalTimeBatch window
[CEP-1526 ] - Improve event
receiver/publisher JMS configuration to support Tibco EMS
[CEP-1528 ] - Provide support for
string values to be used in line charts x axis in real time gadets
[CEP-1532 ] - Add basicAuth enable
property for http event receiver
[CEP-1540 ] - [Template Manager UI]
JSP pages which are not invoked through Ajax are named as
*_ajaxprocessor.jsp
[CEP-1574 ] - JNDI Connector to
Sonic MQ.


*Fixed Issues in This Release*

   - Bug Fixes 

*Known Issues*

   - Known Issues 

*Source and distribution packages:*

   - 
*https://github.com/wso2/product-cep/releases/download/v4.2.0-rc2/wso2cep-4.2.0-RC2.zip
   
*


Please download, test, and vote. The README file under the distribution
contains guide and instructions on how to try it out locally. [+] Stable -
Go ahead and release [-] Broken - Do not release (explain why) This vote
will be open for 72 hours or as needed. Regards,
WSO2 CEP Team



-- 
*Dilini Muthumala*
Senior Software Engineer,
WSO2 Inc.

*E-mail :* dil...@wso2.com
*Mobile: *+94 713-400-029
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Test Mail

2016-09-06 Thread Mohanadarshan Vivekanandalingam

This a test mail

-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Introducing patterns for WSO2 Puppet Modules

2016-09-06 Thread Pubudu Gunatilaka

Hi,

As we are introducing multiple deployment patterns in PaaS artifacts based
on the discussion in [1], we need to introduce patterns for puppet modules
as well. This is mainly because we use puppet provisioning to build docker
images.

Patterns will be able to use with hieradata and the following is the hiera
hierarchy.

---
:hierarchy:
- "wso2/%{::product_name}/%{::pattern}/%{::product_profile}"
- "wso2/%{::product_name}/%{::pattern}/common"
- "wso2/common"

Initially, we will ship two basic patterns which are single JVM and fully
distributed deployment. Product teams will be able to add more patterns by
adding relevant hieradata in later stages. You can refer sample patterns
done for WSO2 Application Server [2].

Hierarchy is created based on the following facts.

1. Pattern_01 will be always the vanilla pack.
2. There will be common.yaml file in every pattern except pattern_01 to
share common data among the pattern. For an example, common.yaml in
pattern_02 will have the values common to worker and manager profiles [3].
3. Hieradata which is common to all the products will be kept in
puppet-base repo [4] and product specific hieradata will be kept in
relevant product repo. To run any product with hieradata, you need to merge
hieradata in puppet-base and product repo.

Please share your thoughts.

[1] -
http://wso2-oxygen-tank.10903.n7.nabble.com/Managing-Multiple-Deployment-Patterns-in-PaaS-Artifacts-td142359.html
[2] -
https://github.com/wso2/puppet-as/tree/master/hieradata/dev/wso2/wso2as
[3] -
https://github.com/wso2/puppet-as/tree/master/hieradata/dev/wso2/wso2as/pattern_02
[4] -
https://github.com/wso2/puppet-base/blob/master/hieradata/dev/wso2/common.yaml

Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

2016-09-06 Thread Rajith Vitharana

Hi Jagath,

Can't you do something like

1) deploy the service
2) get wsdl
3) modify wsdl to use your custom endpoints
4) use that modified wsdl as publish wsdl(inline or as file)

drawback would be, you will need to do this process every time you do some
changes to the proxy

Thanks,

On 6 September 2016 at 18:39, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> HI Jayanga,
>
> I think "publishWSDL" can be used to modify operations exposed to the
> client from ESB based on back-end service. In our case, it is required to
> change the service address returned from the wsdl, generated from ESB proxy
> service.
>
> Thanks.
>
> On Tue, Sep 6, 2016 at 4:48 PM, Jayanga Dissanayake 
> wrote:
>
>> Hi Maheeka/Jagath,
>>
>> Did you try using the "publishWSDL" option and publishing a custom WSDL
>> with modified endpoints.
>>
>> Thanks,
>> Jayanga.
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259
>> 
>>
>> On Sun, Sep 4, 2016 at 9:19 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> HI Chanaka,
>>>
>>> Yes, we are looking for any configuration or extension we can implement
>>> to achieve this which does not affect usual functionality of tenant mode.
>>>
>>> Thanks.
>>>
>>> On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando 
>>> wrote:
>>>
 If that is the case, then it makes sense to remove the "/t/abc.com"
 from the generated WSDL (as Jagath mentioned). Thanks everyone for the
 clarification. We should do this in a way that it does not affect the
 standalone mode tenant story.



 On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya 
 wrote:

> Hi Chanaka,
>
> The app hostname contains the tenant domain and thus it is possible to
> identify the the app uniquely and rewriting the URL without tenant domain
> works.
>
> For example, SampleApp I created in maheeka.com domain would resolve
> to hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might have
> a custom URL as Amalka mentions above. Apps can be differentiated because
> hostname is composed with tenant domain, app name and version.
>
> Thanks,
> Maheeka
>
>
> Maheeka Jayasuriya
> Senior Software Engineer
> Mobile : +9450661
>
> On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe 
> wrote:
>
>> It is through HAProxy URL rewriting.
>>
>> User can invoke same proxy as following ways.
>> http://tenantDomain-appName-version-wso2apps.com/HellpProxy
>> http://tenantDomain-appName-wso2apps.com/HellpProxy
>> http://custom-url/HellpProxy
>>
>> Then at the HAProxy level we have added a logic to rewrite above urls
>> to
>> http://tenantDomain-appName-version-wso2apps.com/services/t/
>> tenantDomain/HellpProxy
>>
>>
>>
>> On Sun, Sep 4, 2016 at 8:04 AM, Chanaka Fernando 
>> wrote:
>>
>>> I'm bit confused about how we differentiate the endpoints for
>>> different tenants. I thought it was through this "/t/aa.com"
>>> section. If I have a proxy called "HelloProxy" and you have the same 
>>> proxy
>>> (in your tenant), how are we going to differentiate? Is it from "host 
>>> name"
>>> section?
>>>
>>> http://cloud.integration.wso2.com/services/*t/chanaka.com/HelloProxy
>>> *
>>> http://cloud.integration.wso2.com/services/*t/maheeka.com/HelloProxy
>>> *
>>>
>>> or
>>>
>>> http://*xxx.cloud.integration.wso2.com
>>> */services/HelloProxy
>>> http://*yyy.cloud.integration.wso2.com
>>> */services/HelloProxy
>>>
>>>
>>> On Sun, Sep 4, 2016 at 7:28 AM, Maheeka Jayasuriya >> > wrote:
>>>
 Hi Chanaka,

 When we deploy a car file containing a proxy service, we need to
 show the WSDL for the proxy in integration cloud. The endpoints in the 
 WSDL
 are composed with the host name of the app and the tenant suffix -
 t/tenantDomain, since we are doing the deployment in the tenant space.

 When we get a request as http://esb.wso2.com:8280/servi
 ces/HelloProxy.HelloProxyHttpSoap11Endpoint
 ,
 it is actually rewritten to http://esb.wso2.com:8280/servi
 ces/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint
 
 by the HAProxy. Hence, requests are redirected to real tenant

Re: [Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC2

2016-09-06 Thread Gokul Balakrishnan

I have tested the following through the EC2 performance test round:

- Clustered DAS deployment
- Analyzer, Indexer and Receiver profiles
- Data persistence with HBase
- Spark script execution in clustered mode (CarbonAnalytics)
- Clustered indexing operation
- Data explorer
- Basic data publishing
- Smart Home and Wikipedia samples

[+] Stable - Go ahead and release.


On Tuesday, 6 September 2016, Niranda Perera  wrote:

> Hi Devs,
>
> This is the first release candidate 2 (RC2) of WSO2 Data Analytics Server
> 3.1.0 release.
>
> New / Improvements In This Release after RC1
>
>- Upgrading Spark to 1.6.2
>- Improvements for indexing
>
> Issues Fixed in This Release
>
>- WSO2 DAS 3.1.0 Fixed Issues
>
>
> Known Issues
>
>- WSO2 DAS 3.1.0 Known Issues
>
>
> Source and distribution packages:
>
>- https://github.com/wso2/product-das/releases/tag/v3.1.0-RC2
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
> [-] Broken - Do not release (explain why)
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> WSO2 DAS Team
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>


-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

2016-09-06 Thread Jagath Sisirakumara Ariyarathne

HI Jayanga,

I think "publishWSDL" can be used to modify operations exposed to the
client from ESB based on back-end service. In our case, it is required to
change the service address returned from the wsdl, generated from ESB proxy
service.

Thanks.

On Tue, Sep 6, 2016 at 4:48 PM, Jayanga Dissanayake 
wrote:

> Hi Maheeka/Jagath,
>
> Did you try using the "publishWSDL" option and publishing a custom WSDL
> with modified endpoints.
>
> Thanks,
> Jayanga.
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
> 
>
> On Sun, Sep 4, 2016 at 9:19 AM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> HI Chanaka,
>>
>> Yes, we are looking for any configuration or extension we can implement
>> to achieve this which does not affect usual functionality of tenant mode.
>>
>> Thanks.
>>
>> On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando 
>> wrote:
>>
>>> If that is the case, then it makes sense to remove the "/t/abc.com"
>>> from the generated WSDL (as Jagath mentioned). Thanks everyone for the
>>> clarification. We should do this in a way that it does not affect the
>>> standalone mode tenant story.
>>>
>>>
>>>
>>> On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya 
>>> wrote:
>>>
 Hi Chanaka,

 The app hostname contains the tenant domain and thus it is possible to
 identify the the app uniquely and rewriting the URL without tenant domain
 works.

 For example, SampleApp I created in maheeka.com domain would resolve
 to hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might have
 a custom URL as Amalka mentions above. Apps can be differentiated because
 hostname is composed with tenant domain, app name and version.

 Thanks,
 Maheeka


 Maheeka Jayasuriya
 Senior Software Engineer
 Mobile : +9450661

 On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe 
 wrote:

> It is through HAProxy URL rewriting.
>
> User can invoke same proxy as following ways.
> http://tenantDomain-appName-version-wso2apps.com/HellpProxy
> http://tenantDomain-appName-wso2apps.com/HellpProxy
> http://custom-url/HellpProxy
>
> Then at the HAProxy level we have added a logic to rewrite above urls
> to
> http://tenantDomain-appName-version-wso2apps.com/services/t/
> tenantDomain/HellpProxy
>
>
>
> On Sun, Sep 4, 2016 at 8:04 AM, Chanaka Fernando 
> wrote:
>
>> I'm bit confused about how we differentiate the endpoints for
>> different tenants. I thought it was through this "/t/aa.com"
>> section. If I have a proxy called "HelloProxy" and you have the same 
>> proxy
>> (in your tenant), how are we going to differentiate? Is it from "host 
>> name"
>> section?
>>
>> http://cloud.integration.wso2.com/services/*t/chanaka.com/HelloProxy
>> *
>> http://cloud.integration.wso2.com/services/*t/maheeka.com/HelloProxy
>> *
>>
>> or
>>
>> http://*xxx.cloud.integration.wso2.com
>> */services/HelloProxy
>> http://*yyy.cloud.integration.wso2.com
>> */services/HelloProxy
>>
>>
>> On Sun, Sep 4, 2016 at 7:28 AM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Hi Chanaka,
>>>
>>> When we deploy a car file containing a proxy service, we need to
>>> show the WSDL for the proxy in integration cloud. The endpoints in the 
>>> WSDL
>>> are composed with the host name of the app and the tenant suffix -
>>> t/tenantDomain, since we are doing the deployment in the tenant space.
>>>
>>> When we get a request as http://esb.wso2.com:8280/servi
>>> ces/HelloProxy.HelloProxyHttpSoap11Endpoint
>>> ,
>>> it is actually rewritten to http://esb.wso2.com:8280/servi
>>> ces/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint
>>> 
>>> by the HAProxy. Hence, requests are redirected to real tenant endpoint.
>>> However, this tenant information is not necessary to be known to the 
>>> users
>>> when they use the WSDL to send a request. Hence the question whether it 
>>> is
>>> possible to do $subject.
>>>
>>> Thanks,
>>> Maheeka
>>>
>>> Maheeka Jayasuriya
>>> Senior Software Engineer
>>> Mobile : +9450661
>>>
>>> On Sun, Sep 4, 2016 at 7:18 AM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Jagath,

 What is

[Dev] [puppet] Setting up puppet home from script

2016-09-06 Thread Anuruddha Liyanarachchi

Hi,

We have  created separate GitHub repos for Puppet modules so that the
Puppet module can be shipped as part of a product release.

Since modules are distributed we have introduced a script to generate
PUPPET_HOME. The script will work as following.

 1. Check puppet_home folder exists.

 2. Create folder structure required for puppet_home.
├── hiera.yaml
├── hieradata
├── manifests
└── modules

3.  Create a symlink to manifest/site.pp file.

4. Clone wso2base puppet module into  /modules directory.

5. Create a symlink to wso2base common.yaml hiera-file.

> /modules/wso2base/hieradata/wso2/common.yaml ->
> /hieradata/dev/wso2/


6. Clone wso2 puppet module into  /modules directory.

7. Create a symlink to wso2 hiera-files.

>   /wso2/hieradata/dev/wso2/wso2 ->
> ../hieradata/dev/wso2/


Once the setup.sh completes, users can copy product pack and jdk
distribution for relevant folders and run vagrant setup against
above-created puppet home.

We are planning to automate the copying of product pack, jdk distribution
and starting vagrant setup as well.

Setup.sh can be found at [1]. Please share your suggestions towards this
approach.

[1] https://github.com/wso2/puppet-common/blob/master/setup.sh

-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC2

2016-09-06 Thread Niranda Perera

Hi Devs,

This is the first release candidate 2 (RC2) of WSO2 Data Analytics Server
3.1.0 release.

New / Improvements In This Release after RC1

   - Upgrading Spark to 1.6.2
   - Improvements for indexing

Issues Fixed in This Release

   - WSO2 DAS 3.1.0 Fixed Issues
   

Known Issues

   - WSO2 DAS 3.1.0 Known Issues
   

Source and distribution packages:

   - https://github.com/wso2/product-das/releases/tag/v3.1.0-RC2

Please download, test, and vote. The README file under the distribution
contains guide and instructions on how to try it out locally.

[+] Stable - Go ahead and release
[-] Broken - Do not release (explain why)

This vote will be open for 72 hours or as needed.

Regards,
WSO2 DAS Team

-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Machine Learner 1.2.0 RC1

2016-09-06 Thread Supun Sethunga

Hi Devs,

This is the 1st Release Candidate of the WSO2 Machine Learner 1.2.0. This
release includes the  following improvements and fixes:

   - ML-DAS integration
   - Spark upgrade to v1.6.2
   - Security fixes associated with the WSO2 Carbon 4.4.9 platform release


Please download, test the product and vote. Vote will be open for 72 hours
or as needed.
Refer to github readme for guides.

The distribution is available to download at [1].

Fixed Issue in [2]. Tag to be vote upon [3].

[1]
https://github.com/wso2/product-ml/releases/download/v1.2.0-rc1/wso2ml-1.2.0-rc1.zip
[2] https://wso2.org/jira/issues/?filter=13325
[3] https://github.com/wso2/product-ml/releases/tag/v1.2.0-rc1

Please vote as follows.
[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)

Thanks,
WSO2 ML Team

-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Puppet] Way forward with WSO2 Puppet modules

2016-09-06 Thread Akila Ravihansa Perera

Hi,

We have already created separate GitHub repos for Puppet modules so that
the Puppet module can be shipped as part of a product release. All common
resources and classes are still in wso2base Puppet module. We have
refactored the module structure which I'll highlight below;

Please refer to wso2base module [1] and  wso2as module [2] which we have
implemented as a reference. We will discuss any improvements needed and
replicate the same structure for other modules.

 - No more Hiera lookups in init.pp
   All Hiera lookups have been moved to params classes in wso2base and
product module. All common parameters across products are defined in
wso2base/params.pp and product specific ones are defined in corresponding
product Puppet module

 - Do Hiera lookups only when enabled via a facter
   wso2base/params.pp lookup a facter named "use_hieradata" and decide
whether to take default values defined directly in params.pp or to perform
Hiera lookups. It would have been ideal if Hiera lookups are all done in a
separate layer (for eg: using roles and profiles pattern), but one problem
is users will have to write their own profiles module to use Hiera.
Maintaining profiles in our side would be an overhead. This is still open
to suggestions.

 - Class parameters to override defaults in params.pp
   Earlier Puppet modules were tightly coupled with Hiera so that users
were unable to simply include the module from site.pp and run it. Now all
the variables are defined as class parameters which takes common values
from wso2base/params.pp [4]. Default values for any product specific
parameters are kept in /params.pp. For eg: [5]

Any user can now simply do the following in site.pp

class java -> class wso2as

Above manifest will configure wso2as using default configuration (vanilla
pack). Default values can be overridden by passing values. For eg: to set a
port offset of 10

$ports = {
offset => 10
}
class java ->
class  { 'wso2as':
   ports => $ports
}

 - Class dependencies and containment
  All base classes are contained in product module main class to enforce
the class dependency order [6].

 - Data type validation
   To enforce that parameters passed are in expected format and to help
with troubleshooting we have added validations in wso2base module which
checks whether data types passed for each parameter is correct [7].

 - Vagrant setup
   We have moved out the Vagrantfile, site.pp and hiera.yaml files to a
separate repo named "puppet-commons" [3]. This repo will contain any Puppet
related artifact which does not belong to a Puppet module. It has a
setup.sh shell script to create the PUPPET_HOME directly by cloning Puppet
module GitHub repos and merging Hieradata. Details about this setup.sh
script will be discussed in a separate thread.

Any developer who wants to try out a Puppet module can do so by performing
following steps;
1. Git clone puppet-commons
2. Run setup.sh
3. Provide PUPPET_HOME when prompted by setup.sh
4. Provide JDK file location product pack location when prompted
5. Goto puppet-commons/vagrant
6. Run vagrant up

Note that we have not fully implemented the end-to-end flow yet.

[1] https://github.com/wso2/puppet-base
[2] https://github.com/wso2/puppet-as
[3] https://github.com/wso2/puppet-commons
[4] https://github.com/wso2/puppet-base/blob/master/manifests/params.pp
[5] https://github.com/wso2/puppet-as/blob/master/manifests/params.pp#L29
[6] https://github.com/wso2/puppet-as/blob/master/manifests/init.pp#L115
[7]
https://github.com/wso2/puppet-base/blob/master/manifests/init.pp#L55-L86

Thanks.

-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

2016-09-06 Thread Jayanga Dissanayake

Hi Maheeka/Jagath,

Did you try using the "publishWSDL" option and publishing a custom WSDL
with modified endpoints.

Thanks,
Jayanga.

*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259


On Sun, Sep 4, 2016 at 9:19 AM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> HI Chanaka,
>
> Yes, we are looking for any configuration or extension we can implement to
> achieve this which does not affect usual functionality of tenant mode.
>
> Thanks.
>
> On Sun, Sep 4, 2016 at 8:54 AM, Chanaka Fernando 
> wrote:
>
>> If that is the case, then it makes sense to remove the "/t/abc.com" from
>> the generated WSDL (as Jagath mentioned). Thanks everyone for the
>> clarification. We should do this in a way that it does not affect the
>> standalone mode tenant story.
>>
>>
>>
>> On Sun, Sep 4, 2016 at 8:26 AM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Hi Chanaka,
>>>
>>> The app hostname contains the tenant domain and thus it is possible to
>>> identify the the app uniquely and rewriting the URL without tenant domain
>>> works.
>>>
>>> For example, SampleApp I created in maheeka.com domain would resolve to
>>> hostname : maheeka-com-sampleapp.apps.cloud.wso2.com or might have a
>>> custom URL as Amalka mentions above. Apps can be differentiated because
>>> hostname is composed with tenant domain, app name and version.
>>>
>>> Thanks,
>>> Maheeka
>>>
>>>
>>> Maheeka Jayasuriya
>>> Senior Software Engineer
>>> Mobile : +9450661
>>>
>>> On Sun, Sep 4, 2016 at 8:09 AM, Amalka Subasinghe 
>>> wrote:
>>>
 It is through HAProxy URL rewriting.

 User can invoke same proxy as following ways.
 http://tenantDomain-appName-version-wso2apps.com/HellpProxy
 http://tenantDomain-appName-wso2apps.com/HellpProxy
 http://custom-url/HellpProxy

 Then at the HAProxy level we have added a logic to rewrite above urls to
 http://tenantDomain-appName-version-wso2apps.com/services/t/
 tenantDomain/HellpProxy



 On Sun, Sep 4, 2016 at 8:04 AM, Chanaka Fernando 
 wrote:

> I'm bit confused about how we differentiate the endpoints for
> different tenants. I thought it was through this "/t/aa.com" section.
> If I have a proxy called "HelloProxy" and you have the same proxy (in your
> tenant), how are we going to differentiate? Is it from "host name" 
> section?
>
> http://cloud.integration.wso2.com/services/*t/chanaka.com/HelloProxy
> *
> http://cloud.integration.wso2.com/services/*t/maheeka.com/HelloProxy
> *
>
> or
>
> http://*xxx.cloud.integration.wso2.com
> */services/HelloProxy
> http://*yyy.cloud.integration.wso2.com
> */services/HelloProxy
>
>
> On Sun, Sep 4, 2016 at 7:28 AM, Maheeka Jayasuriya 
> wrote:
>
>> Hi Chanaka,
>>
>> When we deploy a car file containing a proxy service, we need to show
>> the WSDL for the proxy in integration cloud. The endpoints in the WSDL 
>> are
>> composed with the host name of the app and the tenant suffix -
>> t/tenantDomain, since we are doing the deployment in the tenant space.
>>
>> When we get a request as http://esb.wso2.com:8280/servi
>> ces/HelloProxy.HelloProxyHttpSoap11Endpoint
>> ,
>> it is actually rewritten to http://esb.wso2.com:8280/servi
>> ces/t/aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint
>> 
>> by the HAProxy. Hence, requests are redirected to real tenant endpoint.
>> However, this tenant information is not necessary to be known to the 
>> users
>> when they use the WSDL to send a request. Hence the question whether it 
>> is
>> possible to do $subject.
>>
>> Thanks,
>> Maheeka
>>
>> Maheeka Jayasuriya
>> Senior Software Engineer
>> Mobile : +9450661
>>
>> On Sun, Sep 4, 2016 at 7:18 AM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Jagath,
>>>
>>> What is the requirement here?
>>>
>>> On Sat, Sep 3, 2016 at 11:57 PM, Jagath Sisirakumara Ariyarathne <
>>> jaga...@wso2.com> wrote:
>>>
 Hi All,

 When a Proxy (e.g. HelloProxy) is deployed in a tenant space (e.g
 abc.com) in ESB, related wsdl will contain service definition as
 follows;

 
 http://esb.wso2.com:8280/services/t/
 aa.com/HelloProxy.HelloProxyHttpSoap11Endpoint

Re: [Dev] Clarification on content aware logic in log mediator

2016-09-06 Thread Bhathiya Jayasekara

Hi Udara,

The default log level is Simple, which logs some headers (plus any
properties you give). So it has to be content aware. If you don't want
those headers to be logged, you should set "custom" explicitly.

Thanks,
Bhathiya

On Tue, Sep 6, 2016 at 4:01 PM, Udara Liyanage  wrote:

> Hi ESB team,
>
>
> Below is isContentAware() method for LogMediator. According to that any
> log which does not have log level custom becomes content aware.
>
>   public boolean isContentAware() {
>   if (logLevel == CUSTOM) {
>   for (MediatorProperty property : properties) {
>   if (property.getExpression() != null &&
> property.getExpression().isContentAware()) {
>   return true;
>   }
>   }
>   return false;
>   }
>   return true;
>   }
>
> If so below log will also become content aware. IMO this is not a content
> aware log, is it?
>
>  
> 
>  
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> Blog: http://udaraliyanage.wordpress.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Clarification on content aware logic in log mediator

2016-09-06 Thread Udara Liyanage

Hi ESB team,


Below is isContentAware() method for LogMediator. According to that any log
which does not have log level custom becomes content aware.

  public boolean isContentAware() {
  if (logLevel == CUSTOM) {
  for (MediatorProperty property : properties) {
  if (property.getExpression() != null &&
property.getExpression().isContentAware()) {
  return true;
  }
  }
  return false;
  }
  return true;
  }

If so below log will also become content aware. IMO this is not a content
aware log, is it?

 

 

-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

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

Re: [Dev] NextGen Tooling - Drag and Drop from Tool-Palette

2016-09-06 Thread Praminda Jayawardana

Hi Susinda,

Check [1] for html5 DnD browser compatibility chart. This seems to be based
on latest stats.
Can we implement a simple app and check if features we require is
implemented now? It'll be much better if we can use native html5 features
without additional libraries.

[1]: http://caniuse.com/#search=drag%20and%20drop

Thanks,
Praminda


On Tue, Sep 6, 2016 at 12:10 PM, Susinda Perera  wrote:

> Some findings on HTML 5 DnD supports - Is seems this is not a good choice
>
> HTML 5 DnD
> This seems not fully implemented in all the browsers [1, 2. 3]
> And its apis behaviour is not that good enough (HTML5 drag and drop module
>  is not just a disaster,
> it’s a *fucking* disaster.[4])
> Some SO comments[5]
> I think the biggest advantage to HTML5 drag and drop over jQuery is the
> elimination of the sizable jQuery UI library and css files. That being
> said, there is the current issue of browser compatibility that makes jQuery
> very much needed.[5]
> down vote
>
> [1] - http://mereskin.github.io/dnd/
> [2] - http://caniuse.com/#feat=dragndrop
> [3] - http://www.useragentman.com/blog/2010/01/10/cross-browser-
> html5-drag-and-drop/
> [4] - http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html
> [5] - http://stackoverflow.com/questions/9524543/advantages-
> of-html-5-drag-and-drop-over-jquery-ui-drag-and-drop
>
>
>
>
> On Tue, Sep 6, 2016 at 11:01 AM, Susinda Perera  wrote:
>
>>
>>
>> On Tue, Sep 6, 2016 at 10:03 AM, Dakshika Jayathilaka 
>> wrote:
>>
>>> +1 for option 2.
>>>
>>
>>> Option 1 will generate problematic situation because most of the
>>> components within Jquery-UI is outdated and IMHO this won't be a good
>>> option for next gen tooling.
>>>
>>
>> With option 2 it's hard to implement moving svg component over HTML (as
>> we discussed today morning). I believe the issue of option1 is using
>> jquery-UI. Our argument was to implement DnD based on d3(svg) vs HTML. As
>> we all agreed we will move this implementation based on HTML. We need to
>> research on which library to use, is it HTML-5 native support or some
>> other. I'll try on this and update the findings.
>>
>>>
>>> Regards,
>>>
>>> *Dakshika Jayathilaka*
>>> PMC Member & Committer of Apache Stratos
>>> Associate Technical Lead
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Mon, Sep 5, 2016 at 8:21 PM, Imesh Gunaratne  wrote:
>>>

 On Mon, Sep 5, 2016 at 6:21 PM, Susinda Perera 
 wrote:

> Hi All
>
> I tried $subject with 2 different approaches, and having following
> +and -s
> 1. Using Jquery-UI DnD support
> + Can drag over other HTML elements
> + Can restrict droppable areas
> + Can implement tool-palette separately even without having D3/Svg
> interaction or knowledge
> - Have to use different technology compared to d3 and svg, which is
> used in all over other places in diagram editor
>
> 2. Using d3 drag drop support
> + Can use the same technology stack as what we used in diagram editor.
> - Can not drag over other HTML elements. (Maybe we can with some RnD,
> but could not found anything yet)
> - Tool Palette need to be implemented as svg element
>
> Any ideas? My preference is 1. As it gives us more flexibility on
> styling and coding.
>
 
 Yes I think it's fine to proceed with option 1 by considering the
 capabilities needed by the tool palette.

 Thanks

>
> Thanks
> Susinda
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


 --
 *Imesh Gunaratne*
 Software Architect
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: https://medium.com/@imesh TW: @imesh
 lean. enterprise. middleware


>>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Praminda Jayawardana*
Software Engineer
WSO2 Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

2016-09-06 Thread Abimaran Kugathasan

Hi Supun,

You need to create the certificate for that particular hostname. Hostname
is strictly verified in products which are based on carbon 4.4.x.  There
aren't any way to disable this hostname verification.

On Tue, Sep 6, 2016 at 12:01 PM, Supun Malinga  wrote:

> Also, in gateway axis2.xml transport Sender, hostname verifier is
> configured..
>
> AllowAll
>
>
> On Tue, Sep 6, 2016 at 11:57 AM, Supun Malinga  wrote:
>
>> Hi,
>>
>> When gateway is validating token with keymanager, getting the following
>> error at gateway worker log,
>>
>> [2016-09-06 06:09:22,013]  INFO - HTTPSender Unable to sendViaPost to url[
>> https://keymanager:9443/services/APIKeyValidationService]
>> javax.net.ssl.SSLException: hostname in certificate didn't match:
>>  != 
>> 
>>
>> Looks like keymanager is rejecting the requests.
>> How do I allow all hostnames here?.
>>
>> In keymanager wso2server.sh I see following enabled already,
>>
>> -Dorg.opensaml.httpclient.https.disableHostnameVerification=true \
>> -Dorg.wso2.ignoreHostnameVerification=true \
>>
>> thanks,
>> --
>> Supun Malinga
>>
>
>
>
> --
> Supun Malinga
>
> ___
> 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


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

[Dev] [DEV] Validations applied to 'AndesSetRoutingKey' property

2016-09-06 Thread Sashika Wijesinghe

Hi Hemika,

When setting a routing key to a message I have used
"System.setProperty("AndesSetRoutingKey", "1");" as described in the
documentation [1]. As I observed any value set for the "AndesSetRoutingKey"
is considered as valid and the routing key property is set to the message.

May I know whether there is any validation applied to this property? I have
set an empty value as "System.setProperty("AndesSetRoutingKey", "");" ,
this is also considered as valid and the "JMS_ANDES_ROUTING_KEY" property
set to the correct queue destination. When I passed a null value to the
property it fails with NullPointerException. According to [2] 'null' value
can not be set to a property.

[1] https://docs.wso2.com/display/MB320/Setting+the+Routing+Key+for+Messages
[2]
http://stackoverflow.com/questions/4323995/set-system-propery-to-null-in-java

Thank You
-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

2016-09-06 Thread Lahiru J Ekanayake

Thank you everyone :)



On Tue, Sep 6, 2016 at 12:13 PM, Rajith Roshan  wrote:

> Congratz Lahiru
>
> On Tue, Sep 6, 2016 at 12:09 PM, Malintha Fernando 
> wrote:
>
>> Congrats Lahiru! :)
>>
>> On Tue, Sep 6, 2016 at 12:04 PM, Sameera Medagammaddegedara <
>> samee...@wso2.com> wrote:
>>
>>> Congratulations Lahiru!
>>>
>>> On Tue, Sep 6, 2016 at 11:13 AM, Madawa Soysa  wrote:
>>>
 Congratulations Lahiru...!!!

 On Tue, Sep 6, 2016 at 11:03 AM, Mushthaq Rumy 
 wrote:

> Congratulation Lahiru...!!! :)
>
> Thanks & Regards,
> Mushthaq
>
> On Tue, Sep 6, 2016 at 11:00 AM, Chandana Napagoda 
> wrote:
>
>> Hi All,
>>
>> It is my pleasure to welcome Lahiru J Ekanayake as a WSO2 Committer.
>> Lahiru has made some great contributions to WSO2 Governance Registry and
>> WSO2 Enterprise Store products during the last few months, specially to
>> implement the taxonomy feature. In recognition of his commitment and
>> contributions, Lahiru has been voted as a Committer for WSO2.
>>
>> Lahiru, welcome aboard and keep up the good work.
>>
>> Best Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile :
>> +94718169299 <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com
>>  | http://chandana.napagoda.com
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Mushthaq Rumy
> *Software Engineer*
> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 Madawa Soysa / Software Engineer
 mada...@wso2.com / +94714616050

 *WSO2 Inc.*
 lean.enterprise.middleware

   




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


>>>
>>>
>>> --
>>> Sameera Medagammaddegedara
>>> Software Engineer
>>>
>>> Contact:
>>> Email: samee...@wso2.com
>>> Mobile: + 94 077 255 3005
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Fernando
>> Software Engineer
>> WSO2 Inc. | http://wso2.com
>> Mobile : +94 718874922
>> Blog : http://blog.malintha.org
>>
>> Lean . Enterprise . Middleware
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>



-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +9471 8812629 / +94778509547
Email : lahi...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

2016-09-06 Thread Rajith Roshan

Congratz Lahiru

On Tue, Sep 6, 2016 at 12:09 PM, Malintha Fernando 
wrote:

> Congrats Lahiru! :)
>
> On Tue, Sep 6, 2016 at 12:04 PM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Congratulations Lahiru!
>>
>> On Tue, Sep 6, 2016 at 11:13 AM, Madawa Soysa  wrote:
>>
>>> Congratulations Lahiru...!!!
>>>
>>> On Tue, Sep 6, 2016 at 11:03 AM, Mushthaq Rumy 
>>> wrote:
>>>
 Congratulation Lahiru...!!! :)

 Thanks & Regards,
 Mushthaq

 On Tue, Sep 6, 2016 at 11:00 AM, Chandana Napagoda 
 wrote:

> Hi All,
>
> It is my pleasure to welcome Lahiru J Ekanayake as a WSO2 Committer.
> Lahiru has made some great contributions to WSO2 Governance Registry and
> WSO2 Enterprise Store products during the last few months, specially to
> implement the taxonomy feature. In recognition of his commitment and
> contributions, Lahiru has been voted as a Committer for WSO2.
>
> Lahiru, welcome aboard and keep up the good work.
>
> Best Regards,
> Chandana
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile :
> +94718169299 <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com
>  | http://chandana.napagoda.com
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Mushthaq Rumy
 *Software Engineer*
 Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
 Email : musht...@wso2.com
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middleware.

 

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


>>>
>>>
>>> --
>>>
>>> Madawa Soysa / Software Engineer
>>> mada...@wso2.com / +94714616050
>>>
>>> *WSO2 Inc.*
>>> lean.enterprise.middleware
>>>
>>>   
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Medagammaddegedara
>> Software Engineer
>>
>> Contact:
>> Email: samee...@wso2.com
>> Mobile: + 94 077 255 3005
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Fernando
> Software Engineer
> WSO2 Inc. | http://wso2.com
> Mobile : +94 718874922
> Blog : http://blog.malintha.org
>
> Lean . Enterprise . Middleware
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] NextGen Tooling - Drag and Drop from Tool-Palette

2016-09-06 Thread Susinda Perera

Some findings on HTML 5 DnD supports - Is seems this is not a good choice

HTML 5 DnD
This seems not fully implemented in all the browsers [1, 2. 3]
And its apis behaviour is not that good enough (HTML5 drag and drop module
 is not just a disaster,
it’s a *fucking* disaster.[4])
Some SO comments[5]
I think the biggest advantage to HTML5 drag and drop over jQuery is the
elimination of the sizable jQuery UI library and css files. That being
said, there is the current issue of browser compatibility that makes jQuery
very much needed.[5]
down vote

[1] - http://mereskin.github.io/dnd/
[2] - http://caniuse.com/#feat=dragndrop
[3] -
http://www.useragentman.com/blog/2010/01/10/cross-browser-html5-drag-and-drop/
[4] - http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html
[5] -
http://stackoverflow.com/questions/9524543/advantages-of-html-5-drag-and-drop-over-jquery-ui-drag-and-drop




On Tue, Sep 6, 2016 at 11:01 AM, Susinda Perera  wrote:

>
>
> On Tue, Sep 6, 2016 at 10:03 AM, Dakshika Jayathilaka 
> wrote:
>
>> +1 for option 2.
>>
>
>> Option 1 will generate problematic situation because most of the
>> components within Jquery-UI is outdated and IMHO this won't be a good
>> option for next gen tooling.
>>
>
> With option 2 it's hard to implement moving svg component over HTML (as we
> discussed today morning). I believe the issue of option1 is using
> jquery-UI. Our argument was to implement DnD based on d3(svg) vs HTML. As
> we all agreed we will move this implementation based on HTML. We need to
> research on which library to use, is it HTML-5 native support or some
> other. I'll try on this and update the findings.
>
>>
>> Regards,
>>
>> *Dakshika Jayathilaka*
>> PMC Member & Committer of Apache Stratos
>> Associate Technical Lead
>> WSO2, Inc.
>> lean.enterprise.middleware
>> 0771100911
>>
>> On Mon, Sep 5, 2016 at 8:21 PM, Imesh Gunaratne  wrote:
>>
>>>
>>> On Mon, Sep 5, 2016 at 6:21 PM, Susinda Perera  wrote:
>>>
 Hi All

 I tried $subject with 2 different approaches, and having following +and
 -s
 1. Using Jquery-UI DnD support
 + Can drag over other HTML elements
 + Can restrict droppable areas
 + Can implement tool-palette separately even without having D3/Svg
 interaction or knowledge
 - Have to use different technology compared to d3 and svg, which is
 used in all over other places in diagram editor

 2. Using d3 drag drop support
 + Can use the same technology stack as what we used in diagram editor.
 - Can not drag over other HTML elements. (Maybe we can with some RnD,
 but could not found anything yet)
 - Tool Palette need to be implemented as svg element

 Any ideas? My preference is 1. As it gives us more flexibility on
 styling and coding.

>>> 
>>> Yes I think it's fine to proceed with option 1 by considering the
>>> capabilities needed by the tool palette.
>>>
>>> Thanks
>>>

 Thanks
 Susinda

 --
 *Susinda Perera*
 Software Engineer
 B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
 Mobile:(+94)716049075
 Blog: susinda.blogspot.com
 WSO2 Inc. http://wso2.com/
 Tel : 94 11 214 5345 Fax :94 11 2145300


>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

2016-09-06 Thread Malintha Fernando

Congrats Lahiru! :)

On Tue, Sep 6, 2016 at 12:04 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Congratulations Lahiru!
>
> On Tue, Sep 6, 2016 at 11:13 AM, Madawa Soysa  wrote:
>
>> Congratulations Lahiru...!!!
>>
>> On Tue, Sep 6, 2016 at 11:03 AM, Mushthaq Rumy  wrote:
>>
>>> Congratulation Lahiru...!!! :)
>>>
>>> Thanks & Regards,
>>> Mushthaq
>>>
>>> On Tue, Sep 6, 2016 at 11:00 AM, Chandana Napagoda 
>>> wrote:
>>>
 Hi All,

 It is my pleasure to welcome Lahiru J Ekanayake as a WSO2 Committer.
 Lahiru has made some great contributions to WSO2 Governance Registry and
 WSO2 Enterprise Store products during the last few months, specially to
 implement the taxonomy feature. In recognition of his commitment and
 contributions, Lahiru has been voted as a Committer for WSO2.

 Lahiru, welcome aboard and keep up the good work.

 Best Regards,
 Chandana

 --
 *Chandana Napagoda*
 Associate Technical Lead
 WSO2 Inc. - http://wso2.org

 *Email  :  chand...@wso2.com **Mobile :
 +94718169299 <%2B94718169299>*

 *Blog  :http://cnapagoda.blogspot.com
  | http://chandana.napagoda.com
 *


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


>>>
>>>
>>> --
>>> Mushthaq Rumy
>>> *Software Engineer*
>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>> Email : musht...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Madawa Soysa / Software Engineer
>> mada...@wso2.com / +94714616050
>>
>> *WSO2 Inc.*
>> lean.enterprise.middleware
>>
>>   
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: samee...@wso2.com
> Mobile: + 94 077 255 3005
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Malintha Fernando
Software Engineer
WSO2 Inc. | http://wso2.com
Mobile : +94 718874922
Blog : http://blog.malintha.org

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

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

2016-09-06 Thread Sameera Medagammaddegedara

Congratulations Lahiru!

On Tue, Sep 6, 2016 at 11:13 AM, Madawa Soysa  wrote:

> Congratulations Lahiru...!!!
>
> On Tue, Sep 6, 2016 at 11:03 AM, Mushthaq Rumy  wrote:
>
>> Congratulation Lahiru...!!! :)
>>
>> Thanks & Regards,
>> Mushthaq
>>
>> On Tue, Sep 6, 2016 at 11:00 AM, Chandana Napagoda 
>> wrote:
>>
>>> Hi All,
>>>
>>> It is my pleasure to welcome Lahiru J Ekanayake as a WSO2 Committer.
>>> Lahiru has made some great contributions to WSO2 Governance Registry and
>>> WSO2 Enterprise Store products during the last few months, specially to
>>> implement the taxonomy feature. In recognition of his commitment and
>>> contributions, Lahiru has been voted as a Committer for WSO2.
>>>
>>> Lahiru, welcome aboard and keep up the good work.
>>>
>>> Best Regards,
>>> Chandana
>>>
>>> --
>>> *Chandana Napagoda*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.org
>>>
>>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>>> <%2B94718169299>*
>>>
>>> *Blog  :http://cnapagoda.blogspot.com
>>>  | http://chandana.napagoda.com
>>> *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Madawa Soysa / Software Engineer
> mada...@wso2.com / +94714616050
>
> *WSO2 Inc.*
> lean.enterprise.middleware
>
>   
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Medagammaddegedara
Software Engineer

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

Re: [Dev] WSO2 Committers += Mushthaq Rumy

2016-09-06 Thread Sameera Medagammaddegedara

Congratulations Rumy!

On Tue, Sep 6, 2016 at 10:29 AM, Praminda Jayawardana 
wrote:

> Congratulations Rumy!!!
>
> On Mon, Sep 5, 2016 at 10:43 AM, Madawa Soysa  wrote:
>
>> Congrats Rumy!!!
>>
>> On Mon, Sep 5, 2016 at 10:23 AM, Sameera Gunarathne 
>> wrote:
>>
>>> Congrats Rumy!!!
>>>
>>> On Mon, Sep 5, 2016 at 10:16 AM, Malintha Fernando 
>>> wrote:
>>>
 Congrats Rumy! :)

 On Mon, Sep 5, 2016 at 9:20 AM, Grainier Perera 
 wrote:

> Congratulations Rumy!!!
>
> On Fri, Sep 2, 2016 at 11:50 AM, Chandana Napagoda 
> wrote:
>
>> Hi all,
>>
>> It is my pleasure to welcome Mushthaq Rumy as a WSO2 Committer. Rumy
>> has made some great contributions to WSO2 Governance Registry and WSO2
>> Enterprise Store products during the last few months and in recognition 
>> of
>> his commitment and contributions, he has been voted as a Committer for 
>> WSO2.
>>
>> Rumy, welcome aboard and keep up the good work.
>>
>> Best Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile :
>> +94718169299 <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com
>>  | http://chandana.napagoda.com
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Grainier Perera
> Software Engineer
> Mobile : +94716122384
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Malintha Fernando
 Software Engineer
 WSO2 Inc. | http://wso2.com
 Mobile : +94 718874922
 Blog : http://blog.malintha.org

 Lean . Enterprise . Middleware







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


>>>
>>>
>>> --
>>> Sameera Gunarathne
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> 
>>> Email: samee...@wso2.com
>>> Mobile: +94714155561
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Madawa Soysa / Software Engineer
>> mada...@wso2.com / +94714616050
>>
>> *WSO2 Inc.*
>> lean.enterprise.middleware
>>
>>   
>>
>>
>>
>>
>> ___
>> 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
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Medagammaddegedara
Software Engineer

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

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

2016-09-06 Thread Supun Malinga

Also, in gateway axis2.xml transport Sender, hostname verifier is
configured..

AllowAll


On Tue, Sep 6, 2016 at 11:57 AM, Supun Malinga  wrote:

> Hi,
>
> When gateway is validating token with keymanager, getting the following
> error at gateway worker log,
>
> [2016-09-06 06:09:22,013]  INFO - HTTPSender Unable to sendViaPost to url[
> https://keymanager:9443/services/APIKeyValidationService]
> javax.net.ssl.SSLException: hostname in certificate didn't match:
>  != 
> 
>
> Looks like keymanager is rejecting the requests.
> How do I allow all hostnames here?.
>
> In keymanager wso2server.sh I see following enabled already,
>
> -Dorg.opensaml.httpclient.https.disableHostnameVerification=true \
> -Dorg.wso2.ignoreHostnameVerification=true \
>
> thanks,
> --
> Supun Malinga
>



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

[Dev] [AM 2.0] Hostname verification issue when calling key validation service

2016-09-06 Thread Supun Malinga

Hi,

When gateway is validating token with keymanager, getting the following
error at gateway worker log,

[2016-09-06 06:09:22,013]  INFO - HTTPSender Unable to sendViaPost to url[
https://keymanager:9443/services/APIKeyValidationService]
javax.net.ssl.SSLException: hostname in certificate didn't match:
 != 


Looks like keymanager is rejecting the requests.
How do I allow all hostnames here?.

In keymanager wso2server.sh I see following enabled already,

-Dorg.opensaml.httpclient.https.disableHostnameVerification=true \
-Dorg.wso2.ignoreHostnameVerification=true \

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

Re: [Dev] Introducing patterns for WSO2 Puppet Modules

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

Re: [Dev] [DEV] Validations applied to 'AndesSetRoutingKey' property

Re: [Dev] [puppet] Setting up puppet home from script

Re: [Dev] Introducing patterns for WSO2 Puppet Modules

Re: [Dev] [Puppet] Way forward with WSO2 Puppet modules

[Dev] [Vote] Release WSO2 Complex Event Processor (CEP) 4.2.0-RC2

[Dev] [Vote] Release WSO2 Complex Event Processor (CEP) 4.2.0-RC2

[Dev] Test Mail

[Dev] Introducing patterns for WSO2 Puppet Modules

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

Re: [Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC2

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

[Dev] [puppet] Setting up puppet home from script

[Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC2

[Dev] [VOTE] Release WSO2 Machine Learner 1.2.0 RC1

[Dev] [Puppet] Way forward with WSO2 Puppet modules

Re: [Dev] Change the service endpoint URL in wsdl generated for proxy service in ESB

Re: [Dev] Clarification on content aware logic in log mediator

[Dev] Clarification on content aware logic in log mediator

Re: [Dev] NextGen Tooling - Drag and Drop from Tool-Palette

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

[Dev] [DEV] Validations applied to 'AndesSetRoutingKey' property

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

Re: [Dev] NextGen Tooling - Drag and Drop from Tool-Palette

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

Re: [Dev] WSO2 Committers += Lahiru J Ekanayake

Re: [Dev] WSO2 Committers += Mushthaq Rumy

Re: [Dev] [AM 2.0] Hostname verification issue when calling key validation service

[Dev] [AM 2.0] Hostname verification issue when calling key validation service

31 matches

Site Navigation

Mail list logo

Footer information