Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC2

[Viraj Senevirathne]

Hi All,

We have changed the kernel version of carbon-mediation and product-esb to
4.4.3 and ran all the integration tests for the product-esb. We didn't
encounter any issues after upgrading the kernel version.

Thank you,

On Mon, Dec 7, 2015 at 6:11 PM, Prabath Abeysekera 
wrote:

> Cool, Thanks for the update Darshana!
>
> Cheers,
> Prabath
>
> On Mon, Dec 7, 2015 at 6:08 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Prabath,
>>
>> We already working on this as we planned to release GA on kernel 4.4.3.
>>
>> Thanks,
>>
>> On Mon, Dec 7, 2015 at 6:06 PM, Prabath Abeysekera 
>> wrote:
>>
>>> Hi IS/API-M folks,
>>>
>>> Would you guys please be able to help test "carbon-identity" and
>>> "carbon-apimgt" functionalities on top of Kernel 4.4.3 and verify soon?
>>>
>>> Cheers,
>>> Prabath
>>>
>>> On Mon, Dec 7, 2015 at 5:18 PM, Nipuni Perera  wrote:
>>>
 Hi Devs,

 This is the RC2 release candidate of WSO2 Carbon Kernel 4.4.3.

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

 Please download and test your products with kernel 4.4.3 RC2
 and vote. Vote will be open for 72 hours or as longer as needed.

 *​Source and binary distribution files:*
 *http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc2/
 *

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

 *The tag to be voted upon:*
 https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC2


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

 Thank you
 Carbon Team

 --
 Nipuni Perera
 Software Engineer; WSO2 Inc.; http://wso2.com
 Email: nip...@wso2.com
 Git hub profile: https://github.com/nipuni
 Blog : http://nipunipererablog.blogspot.com/
 Mobile: +94 (71) 5626680
 


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


>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Technical Lead
>>> WSO2 Inc.
>>> Email: praba...@wso2.com
>>> Mobile: +94774171471
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Viraj Senevirathne
Software Engineer; WSO2, Inc.

Mobile : +94 71 958 0269
Email : vir...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SAML Signature Validation in "Configuring SSO with SAML 2.0" sample

[Pulasthi Harasgama]

Hi, Got it, thanks alot for the help.

Thanks,
Pulasthi

On Wed, Dec 9, 2015 at 12:04 PM, Pushpalanka Jayawardhana 
wrote:

> Hi Pulasthi,
>
> The validation happens in the sso agent jar which is used by the webapp as
> a library.
> Please find the code at [1].
>
> [1] -
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/identity/org.wso2.carbon.identity.sso.agent/
> [2] -
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/identity/org.wso2.carbon.identity.sso.agent/1.4.0/src/main/java/org/wso2/carbon/identity/sso/agent/saml/SAML2SSOManager.java
>
> Thanks,
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
> Mobile: +94779716248
> Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
>
>
> On Wed, Dec 9, 2015 at 12:01 PM, Pulasthi Harasgama 
> wrote:
>
>> Hi,
>>
>> I was following the Single Sign On with SAML 2.0 sample [1] to configure
>> SSO for my web application, and I am having difficulty finding out where
>> the signature in the SAML Token received by travelocity.com is
>> validated. Once the user is authenticated at the identity Server, I think
>> the SAML token issued to the user should be validated by travelocity but I
>> can't seem to locate where this is done in the webapp.
>>
>> If possible, please do let me know if I am missing something here or how
>> this is done by travelocity.
>>
>> [1]
>> https://docs.wso2.com/display/IS500/Configuring+Single+Sign-On+with+SAML+2.0
>>
>> Thanks,
>> --
>> *Pulasthi Harasgama*
>> Software Engineering Intern
>> Mobile: +94774978735
>> WSO2 Inc.: http://wso2.com
>> Blog: https://pulasthiharasgama.wordpress.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Pulasthi Harasgama*
Software Engineering Intern
Mobile: +94774978735
WSO2 Inc.: http://wso2.com
Blog: https://pulasthiharasgama.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Deprecated features in ESB 4.10

[Yumani Ranaweera]

Is it possible to provide sufficient documentation to help the customers
who would be migrating in future.

Thanks,
Yumani


On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando  wrote:

> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> It will make a lot of confusion when we have more than one mediators to do
> the same thing. Therefore, better to deprecate this mediator.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always recommend
> to integrate with databases with the use of DSS (using a separate DSS or
> using DSS features inside ESB)
>
> Even though this mediator has been used by some customers, they are using
> that for very limited functionality and we always suggest them to use DSS
> as Kasun mentioned. If users really want to connect to a database, they can
> easily write a simple class mediator.
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> +1 for deprecating these mediators.
>
> With the new DAS integration, we can deprecate BAM mediator since we have
> the PublishEvent mediator.
>
> On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Yumani Ranaweera* | Technical Lead
Technical Support- Colombo
WSO2 Inc. |  http://wso2.com
Blog: http://yumani.blogspot.com/
Mob: + 94 95242
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Error in invoking APIs after migrating from APIM 1.8.0 to 1.9.0

[Dinithi De Silva]

Hi APIM team,

I have tried migrating from APIM 1.8.0 to 1.9.0 following the document [1].

I have an API in 1.8.0 which has the uri-template as "/api*".  Before the
migration, I was able to invoke the API as usual.

After the migration, the API is no more accessible and I am getting the
following error in the REST client.


900906
No matching resource found in the API for the given
request
Access failure for API: /cm/v1.0, version: v1.0 with key:
a22da6e7f2b6498294391b1e289b6a. Check the API documentation and add a
proper REST resource path to the invocation URL


And the back end error was as follows.

[2015-12-09 13:59:06,198] ERROR - APIKeyValidator Could not find matching
resource for /api
[2015-12-09 13:59:06,199] ERROR - APIKeyValidator Could not find matching
resource for request
[2015-12-09 13:59:06,199]  WARN - APIAuthenticationHandler API
authentication failure due to No matching resource found in the API for the
given request

After analyzing further, we could find out that the APIM UI does not show
the "*" in the url-pattern (See the attached screen shot).
But in the synapse config file I could see the url-mapping="/api*" with the
"*".

I have tried adding the resources with the "*" manually and then I was able
to invoke the API successfully.

Also, I could ensure that nothing went wrong during the migration and the
migration has completed successfully without any issues.

Any help to solve this issue is appreciated.

[1] -
https://docs.wso2.com/display/AM190/Upgrading+from+the+Previous+Release

Thanks.

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

Re: [Dev] PPaaS Artifact Migration Tool

[Akila Ravihansa Perera]

Hi,

Here are some important improvements that you can do to boost your
development productivity and stability of the tool.

1. Develop a set of Unit tests with an embedded web container to mock the
PPaaS API.

 - I've already done this as a demo for you to take as a reference guide at
[1]. I've used Jetty web container as an embedded server in my JUnit test
case to mock the API. I've hosted partition list API in my test server and
assert whether artifact loader reads the partition list correctly.

Advantage of this approach is that when you build your tool, it will
compile the code, test and validate the functionality and package. You
don't need to test the tool manually which is very time consuming. You may
have to refactor/re-organize stuff I've developed to make things clean.

2. Create a class ArtifactConverterRestClient as a wrapper around
HttpClient library and use it to fetch resources from Stratos API. You can
create methods like getPartitionList, getAutoscalePolicyList etc. in this.
Decouple your conversion logic from data transfer layer much as possible.
This will make it easy for you to write tests.


3. Always use HTTPS if you are sending/receiving sensitive information. In
current implementation the tool is passing authentication credentials to
the server, therefore transport should be secure.

4. Make user input parameters configurable via configuration files.
Currently the tool expects username, password, url etc. as user inputs.
Make it read these values from a properties file and prompt only if those
values are missing.

[1] https://github.com/nishadi/product-private-paas/pull/1

Thanks.

On Mon, Dec 7, 2015 at 12:19 PM, Nishadi Kirielle  wrote:

> Hi,
>
> Thank you for the feedback.
>
> @Imesh:
> I have updated the README file[1] in mark down text format and will start
> writing the Wiki page.
>
> @Gayan:
> In the initial version, we have used sample json files as templates and
> used them to be default values. But as it has some conflicts, we have
> removed the use of template files. The current approach is to fetch the
> artifacts from the PPaaS 4.0.0 and convert it to PPaaS 4.1.0 without using
> any default values. I have updated the READ ME file [1]
>
> @Isuru:
> I will take the approach proposed to handle exceptions in
> OldArtifactLoader by wrapping them in a custom exception and update it. I
> will update the log4j properties file to be in the conf directory.
>
> [1]
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README
>
> Thank you,
> Nishadi
>
> On Sun, Dec 6, 2015 at 9:28 AM, Isuru Haththotuwa  wrote:
>
>> Hi Malmee and Nishadi,
>>
>> Good progress in a short time!
>>
>> Had a glance at the code, couple of things I noticed:
>>
>>1. log4j.properties file is available under conf directory as well as
>>the resources directory. Ideally should be in conf directory.
>>2. In the class OldArtifactLoader [1], the methods are throwing
>>IOException in an error scenario. A better approach would be to wrap that
>>with a custom exception (ex.: ArtifactLoadingException, etc.) and throw 
>> it.
>>WDYT? In the class Transformation [2], this approach is followed.
>>
>> [1].
>> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/loader/OldArtifactLoader.java
>>
>> [2].
>> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/Transformation.java
>>
>> On Sat, Dec 5, 2015 at 10:25 PM, Gayan Gunarathne 
>> wrote:
>>
>>> Great stuff. This is a really important tool in the case of Private PaaS
>>> migration.
>>>
>>> As per the README[1] it mention as "Add the default values to the
>>> templates folder, if needed".I am not clear on that? Are we packing the
>>> 4.1.0 artifacts templates with the artifact migration tool? So user need to
>>> put the default values for those artifacts?
>>>
>>> [1]
>>> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Fri, Dec 4, 2015 at 2:51 PM, Nishadi Kirielle 
>>> wrote:
>>>
 Hi All,

 Currently,we are engaged in developing an artifact migration tool to be
 used to fetch the artifact json files from PPaaS 4.0.0 REST API endpoints
 and convert them to be compatible with PPaaS 4.1.0. [1]

 We have implemented the conversions for the following artifacts ;
- auto scale policy artifacts
- network partition list artifacts
- deployment policy artifacts
- cartridge artifacts

 Now we are implementing the conversion of cartridge subscription
 artifacts to application signups and domain mapping subscriptions.

 Please raise if there are any concerns regarding 

[Dev] [FB Connector] Can't Publish a Video Using fileUrl with FB Connector

[Thusitha Thilina Dayaratne]

Hi All,

I tried to publish a video to a facebook page using the fileUrl via
Facebook connector. It returns following error

{
  "error": {
"message": "(#100) Param content_category must be one of
{BEAUTY_FASHION, BUSINESS, CARS_TRUCKS, COMEDY, CUTE_ANIMALS,
ENTERTAINMENT, FAMILY, FOOD_HEALTH, HOME, LIFESTYLE, MUSIC, NEWS,
POLITICS, SCIENCE, SPORTS, TECHNOLOGY, VIDEO_GAMING, OTHER}",
"type": "OAuthException",
"code": 100,
"fbtrace_id": "F7CZIU6jVK2"
  }

}

When I checked the code it seems that the value of contentCategory is
assigned by fileUrl value. AFAIU that is not correct. I manually changed
that and then tried with the edited connector. Then it works fine.
I've created following JIRA[1] and PR[2]

[1] - https://wso2.org/jira/browse/ESBCONNECT-75
[2] - https://github.com/wso2/esb-connectors/pull/440

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

[Dev] [DAS] Error reading from RDBMS

[Rukshan Premathunga]

Hi,

i point to a mysql table using CarbonJDBC. RDBMS table contain the column
name api,day,week time etc.

But when reading values of the `day` column i got following error.

*SparkSQL >* select day from APIThrottleSummaryData;
ERROR :  Job aborted due to stage failure: Task 0 in stage 11.0 failed 1
times, most recent failure: Lost task 0.0 in stage 11.0 (TID 23,
localhost): java.lang.IllegalArgumentException: Unsupported field
StructField(day,ShortType,true)
at
org.apache.spark.sql.jdbc.JDBCRDD$$anonfun$getConversions$1.apply(JDBCRDD.scala:342)
at
org.apache.spark.sql.jdbc.JDBCRDD$$anonfun$getConversions$1.apply(JDBCRDD.scala:329)
at
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
at
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
at
scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33)
at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:108)
at scala.collection.TraversableLike$class.map(TraversableLike.scala:244)
at scala.collection.mutable.ArrayOps$ofRef.map(ArrayOps.scala:108)
at org.apache.spark.sql.jdbc.JDBCRDD.getConversions(JDBCRDD.scala:329)
at org.apache.spark.sql.jdbc.JDBCRDD$$anon$1.(JDBCRDD.scala:374)
at org.apache.spark.sql.jdbc.JDBCRDD.compute(JDBCRDD.scala:350)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:277)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:244)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:35)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:277)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:244)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:63)
at org.apache.spark.scheduler.Task.run(Task.scala:70)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Driver stacktrace:
*SparkSQL >*

any solutions?

Thanks and regards.

-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Deprecated features in ESB 4.10

[Chanaka Fernando]

*- Callout mediator :*
 All the callout functionality is supported with 'call' mediator with
blocking=true. Having two similar mediators will be create a bit of a
confusion.

It will make a lot of confusion when we have more than one mediators to do
the same thing. Therefore, better to deprecate this mediator.

*- DBReport/DBLookup mediator*
These mediators offer very limited functionality and we always recommend to
integrate with databases with the use of DSS (using a separate DSS or using
DSS features inside ESB)

Even though this mediator has been used by some customers, they are using
that for very limited functionality and we always suggest them to use DSS
as Kasun mentioned. If users really want to connect to a database, they can
easily write a simple class mediator.

*- Bean, POJOCommand, Spring* : Rarely used mediators and no active
development happens on these.
*- Router* : Same as filter mediator, so no use of having this.
*- In, Out * : Rarely used and often not required with the new call/respond
mediator approach.

+1 for deprecating these mediators.

With the new DAS integration, we can deprecate BAM mediator since we have
the PublishEvent mediator.

On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  wrote:

> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always recommend
> to integrate with databases with the use of DSS (using a separate DSS or
> using DSS features inside ESB)
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> Any comments  on these or any other features that we should deprecate from
> 4.10 release?
>
> Thanks,
> Kasun.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue while indexing pdf files.

[Kishanthan Thangarajah]

You could easily open the current compass project bundle and checks its pom
to find out whether it's an orbit. If yes, you may have to add to the
current orbit repo to get a new release.

On Tue, Dec 8, 2015 at 3:05 PM, Lakshman Udayakantha 
wrote:

> Hi,
>
> Some pdf files gives below error while indexing.
>
> ERROR - PDFIndexer Failed to write to the index
>
> java.io.IOException: Error: expected hex character and not  :32
>
> at org.fontbox.cmap.CMapParser.parseNextToken(CMapParser.java:283)
>
>
> According to [1], this issue is there in pdfbox which used in registry to
> parse pdf files before indexing. pfdbox 0.7.3 is used in registry 4.4.8
> version. According to [1] this issue is fixed in pdfbox version 1.3.1. I
> checked in carbon-orbit [2] for compass project in which pdfbox is
> embedded. but could not found.
>
> In which repository is compass project?
>
> [1] https://issues.apache.org/jira/browse/PDFBOX-790
> [2] https://github.com/wso2/orbit
>
> Thanks
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0714388124*
>
>


-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Malaka Silva]

+1 except  DBReport/DBLookup mediators

On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera  wrote:

> Is it possible to provide sufficient documentation to help the customers
> who would be migrating in future.
>
> Thanks,
> Yumani
>
>
> On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando 
> wrote:
>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> It will make a lot of confusion when we have more than one mediators to
>> do the same thing. Therefore, better to deprecate this mediator.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> Even though this mediator has been used by some customers, they are using
>> that for very limited functionality and we always suggest them to use DSS
>> as Kasun mentioned. If users really want to connect to a database, they can
>> easily write a simple class mediator.
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> +1 for deprecating these mediators.
>>
>> With the new DAS integration, we can deprecate BAM mediator since we have
>> the PublishEvent mediator.
>>
>> On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  wrote:
>>
>>> Shall we deprecate following mediators in 4.10 release.
>>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> Any comments  on these or any other features that we should deprecate
>>> from 4.10 release?
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Yumani Ranaweera* | Technical Lead
> Technical Support- Colombo
> WSO2 Inc. |  http://wso2.com
> Blog: http://yumani.blogspot.com/
> Mob: + 94 95242
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Best Regards,

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

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

https://store.wso2.com/store/

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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Harshana Eranga Martin]

Hi Kasun,

Please see the comments inline.

Thanks and Regards,
Harshana
--
Harshana Eranga Martin

Committer - Eclipse ECF: http://www.eclipse.org/ecf/
Blog: http://harshana05.blogspot.com
Profile: https://www.google.com/profiles/harshana05

On 9 December 2015 at 17:41, Kasun Indrasiri  wrote:

> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>

Can we use the Call mediator with blocking=true instead of Callout mediator
for the NTLM scenarios?

I have tried a NTLM scenario recently with Call mediator and blocking=true
in ESB 4.9.0 but it didn't work while the Callout mediator works fine for
the same scenario. I also assumed Call mediator would work but it didn't.
Can you please check and verify?



> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always recommend
> to integrate with databases with the use of DSS (using a separate DSS or
> using DSS features inside ESB)
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> Any comments  on these or any other features that we should deprecate from
> 4.10 release?
>
> Thanks,
> Kasun.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][BPMN] New REST API for BPMN statistics

[Natasha Wijesekara]

Hi,

I  documented a user guide which contains details about the new rest API
implemented to generate the statistics for bpmn.
Appreciate any suggestions and comments.

Thanks,
Natasha

On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda  wrote:

> [Adding Architecture group]
>
> On Tue, Dec 8, 2015 at 2:45 PM, Natasha Wijesekara 
> wrote:
>
>> Hi ,
>>
>> Currently the statistics generated for the bpmn-explorer is generated
>> using jaggery. When the work load is high, the  bpmn-explorer takes a
>> longer time to generate these statistics which causes performance issues.
>>
>> As a solution I am working a new stats REST api  to generate these
>> statistics at the back-end. This reduces the work load  and thereby solves
>> the performance issues caused during peak times (when the workload is at
>> its maximum).
>>
>> After taking in data about  the bpmn processes, tasks  and users
>> involved, the api  processes these data into meaningful statistics.These
>> statistics generated is used in the bpmn-explorer reporting dashboard to
>> generate the statistical graphs.
>>
>> The statistics generated includes:
>>
>> 1) Average time duration for all completed processes.
>> The user has the option to either view all completed processes or the top
>> 10 processes which finished within a short time duration or the top 10
>> processes which took a long time duration to finish.
>>
>> 2) Average time duration of tasks of a  completed process.
>> The user can select the completed process from the combo box and view the
>> average time duration.
>>
>> 3) User and the no. of tasks he/she has completed upto now.
>>
>> 4) Average time taken by each user to complete the tasks assigned to
>> him/her.
>>
>> 5) Task demand variation over time i.e. no. of tasks started and no. of
>> tasks completed in each month. This is useful for resource allocation
>> purposes.
>>
>> 6) Process demand variation over time i.e. no. of processes started and
>> no. of processes completed in each month regardless of a specific user.
>> This is useful for resource allocation purposes.
>>
>> 7) User Performance i.e. Task demand variation of users separately over
>> time i.e. no. of tasks started and no. of tasks completed in each month.
>> This is useful for resource allocation purposes.
>>
>> I have attached the class diagram of the REST api. The new stats REST api
>> will be integrated with the existing bpmn REST api.
>> Appreciate any suggestions and comments.
>>
>> Thanks,
>> --
>> *Natasha Wijesekare*
>>
>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>> *
>> *email  : nata...@wso2.com *
>> *mobile: +94 771358651 <%2B94%20771358651>*
>>
>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
>
>


-- 
*Natasha Wijesekare*

*Software Engineering Intern, WSO2  Inc:  http://wso2.com
*
*email  : nata...@wso2.com *
*mobile: +94 771358651*


bpmn-stats rest .odt
Description: application/vnd.oasis.opendocument.text
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [FB Connector] Can't Publish a Video Using fileUrl with FB Connector

[Malaka Silva]

Hi Shakila,

Please check this.

On Wed, Dec 9, 2015 at 4:02 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi All,
>
> I tried to publish a video to a facebook page using the fileUrl via
> Facebook connector. It returns following error
>
> {
>   "error": {
> "message": "(#100) Param content_category must be one of {BEAUTY_FASHION, 
> BUSINESS, CARS_TRUCKS, COMEDY, CUTE_ANIMALS, ENTERTAINMENT, FAMILY, 
> FOOD_HEALTH, HOME, LIFESTYLE, MUSIC, NEWS, POLITICS, SCIENCE, SPORTS, 
> TECHNOLOGY, VIDEO_GAMING, OTHER}",
> "type": "OAuthException",
> "code": 100,
> "fbtrace_id": "F7CZIU6jVK2"
>   }
>
> }
>
> When I checked the code it seems that the value of contentCategory is
> assigned by fileUrl value. AFAIU that is not correct. I manually changed
> that and then tried with the edited connector. Then it works fine.
> I've created following JIRA[1] and PR[2]
>
> [1] - https://wso2.org/jira/browse/ESBCONNECT-75
> [2] - https://github.com/wso2/esb-connectors/pull/440
>
> Thanks
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 

Best Regards,

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

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

https://store.wso2.com/store/

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

[Dev] Machine Learning Help Needed

[NIFRAS ISMAIL]

Hi Machine Learners,

Again I need your favour for Data Anaysis on My final year projects.

My Meta Data Labels are

"city","country","birthdate","education","gender","houseowner","marital_status","member_card","num_cars_owned","num_children_at_home","occupation","postal_code","state_province","total_children","yearly_income","product_name"

You may notice that this is a customer and his transaction mapping data of
a shopping mall.

Class Label is  : product_name

Problem: My issue is I need to find the interest classes from my data which
contains the above headers.

then If a new customer come to the mall I may predict which item he will
looking for using Multi Class Multi Label Classification.


Could Any one there to help to me ? Looking forward your reply ML Team

Thank you


Regards.
*M. Nifras Ismail*
[image: LinkedIn] 





Sent with MailTrack

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

Re: [Dev] [FB Connector] Can't Publish a Video Using fileUrl with FB Connector

[Shakila Sivagnanarajah]

Hi Malaka,

I checked and merged.

Thanks

On Wed, Dec 9, 2015 at 5:44 PM, Malaka Silva  wrote:

> Hi Shakila,
>
> Please check this.
>
> On Wed, Dec 9, 2015 at 4:02 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi All,
>>
>> I tried to publish a video to a facebook page using the fileUrl via
>> Facebook connector. It returns following error
>>
>> {
>>   "error": {
>> "message": "(#100) Param content_category must be one of 
>> {BEAUTY_FASHION, BUSINESS, CARS_TRUCKS, COMEDY, CUTE_ANIMALS, ENTERTAINMENT, 
>> FAMILY, FOOD_HEALTH, HOME, LIFESTYLE, MUSIC, NEWS, POLITICS, SCIENCE, 
>> SPORTS, TECHNOLOGY, VIDEO_GAMING, OTHER}",
>> "type": "OAuthException",
>> "code": 100,
>> "fbtrace_id": "F7CZIU6jVK2"
>>   }
>>
>> }
>>
>> When I checked the code it seems that the value of contentCategory is
>> assigned by fileUrl value. AFAIU that is not correct. I manually changed
>> that and then tried with the edited connector. Then it works fine.
>> I've created following JIRA[1] and PR[2]
>>
>> [1] - https://wso2.org/jira/browse/ESBCONNECT-75
>> [2] - https://github.com/wso2/esb-connectors/pull/440
>>
>> Thanks
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Shakila Sivagnanarajah
Associate Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [FB Connector] Can't Publish a Video Using fileUrl with FB Connector

[Malaka Silva]

Can we re-upload the connector and resolve the issue

On Wed, Dec 9, 2015 at 5:48 PM, Shakila Sivagnanarajah 
wrote:

> Hi Malaka,
>
> I checked and merged.
>
> Thanks
>
> On Wed, Dec 9, 2015 at 5:44 PM, Malaka Silva  wrote:
>
>> Hi Shakila,
>>
>> Please check this.
>>
>> On Wed, Dec 9, 2015 at 4:02 PM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I tried to publish a video to a facebook page using the fileUrl via
>>> Facebook connector. It returns following error
>>>
>>> {
>>>   "error": {
>>> "message": "(#100) Param content_category must be one of 
>>> {BEAUTY_FASHION, BUSINESS, CARS_TRUCKS, COMEDY, CUTE_ANIMALS, 
>>> ENTERTAINMENT, FAMILY, FOOD_HEALTH, HOME, LIFESTYLE, MUSIC, NEWS, POLITICS, 
>>> SCIENCE, SPORTS, TECHNOLOGY, VIDEO_GAMING, OTHER}",
>>> "type": "OAuthException",
>>> "code": 100,
>>> "fbtrace_id": "F7CZIU6jVK2"
>>>   }
>>>
>>> }
>>>
>>> When I checked the code it seems that the value of contentCategory is
>>> assigned by fileUrl value. AFAIU that is not correct. I manually changed
>>> that and then tried with the edited connector. Then it works fine.
>>> I've created following JIRA[1] and PR[2]
>>>
>>> [1] - https://wso2.org/jira/browse/ESBCONNECT-75
>>> [2] - https://github.com/wso2/esb-connectors/pull/440
>>>
>>> Thanks
>>> --
>>> Thusitha Dayaratne
>>> Software Engineer
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> Mobile  +94712756809
>>> Blog  alokayasoya.blogspot.com
>>> Abouthttp://about.me/thusithathilina
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
>



-- 

Best Regards,

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

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

https://store.wso2.com/store/

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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC2

[Darshana Gunawardana]

Hi All,

Please note that we are testing a IS 5.1.0 pack built on top of kernel
4.4.3 rc2.

All IS 5.1.0 integration tests passed successfully with this pack. We have
done manual testing on user-management as well as general IS use cases and
there are no issues found at this point. We are continuing our testing
further and we will the status confirm tomorrow.

Thanks,

On Wed, Dec 9, 2015 at 3:05 PM, Viraj Senevirathne  wrote:

> Hi All,
>
> We have changed the kernel version of carbon-mediation and product-esb to
> 4.4.3 and ran all the integration tests for the product-esb. We didn't
> encounter any issues after upgrading the kernel version.
>
> Thank you,
>
> On Mon, Dec 7, 2015 at 6:11 PM, Prabath Abeysekera 
> wrote:
>
>> Cool, Thanks for the update Darshana!
>>
>> Cheers,
>> Prabath
>>
>> On Mon, Dec 7, 2015 at 6:08 PM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi Prabath,
>>>
>>> We already working on this as we planned to release GA on kernel 4.4.3.
>>>
>>> Thanks,
>>>
>>> On Mon, Dec 7, 2015 at 6:06 PM, Prabath Abeysekera 
>>> wrote:
>>>
 Hi IS/API-M folks,

 Would you guys please be able to help test "carbon-identity" and
 "carbon-apimgt" functionalities on top of Kernel 4.4.3 and verify soon?

 Cheers,
 Prabath

 On Mon, Dec 7, 2015 at 5:18 PM, Nipuni Perera  wrote:

> Hi Devs,
>
> This is the RC2 release candidate of WSO2 Carbon Kernel 4.4.3.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12540
>
> Please download and test your products with kernel 4.4.3 RC2
> and vote. Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> *http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc2/
> *
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-163/
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC2
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Blog : http://nipunipererablog.blogspot.com/
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471

>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>>
>>> *Darshana Gunawardana*Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>>
>>> *E-mail: darsh...@wso2.com *
>>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Viraj Senevirathne
> Software Engineer; WSO2, Inc.
>
> Mobile : +94 71 958 0269
> Email : vir...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,


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

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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Kasun Indrasiri]

On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva  wrote:

> +1 except  DBReport/DBLookup mediators
>
> DBReport and DBLookup only offer a very limited set of capabilities. IMO,
for any real integration scenario, we can't use them.  :).

> On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera  wrote:
>
>> Is it possible to provide sufficient documentation to help the customers
>> who would be migrating in future.
>>
>> Thanks,
>> Yumani
>>
>>
>> On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando 
>> wrote:
>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>> It will make a lot of confusion when we have more than one mediators to
>>> do the same thing. Therefore, better to deprecate this mediator.
>>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> Even though this mediator has been used by some customers, they are
>>> using that for very limited functionality and we always suggest them to use
>>> DSS as Kasun mentioned. If users really want to connect to a database, they
>>> can easily write a simple class mediator.
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> +1 for deprecating these mediators.
>>>
>>> With the new DAS integration, we can deprecate BAM mediator since we
>>> have the PublishEvent mediator.
>>>
>>> On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  wrote:
>>>
 Shall we deprecate following mediators in 4.10 release.

 *- Callout mediator :*
  All the callout functionality is supported with 'call' mediator with
 blocking=true. Having two similar mediators will be create a bit of a
 confusion.

 *- DBReport/DBLookup mediator*
 These mediators offer very limited functionality and we always
 recommend to integrate with databases with the use of DSS (using a separate
 DSS or using DSS features inside ESB)

 *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
 development happens on these.
 *- Router* : Same as filter mediator, so no use of having this.
 *- In, Out * : Rarely used and often not required with the new
 call/respond mediator approach.

 Any comments  on these or any other features that we should deprecate
 from 4.10 release?

 Thanks,
 Kasun.

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

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

>>>
>>>
>>>
>>> --
>>> Thank you and Best Regards,
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>>
>> *Yumani Ranaweera* | Technical Lead
>> Technical Support- Colombo
>> WSO2 Inc. |  http://wso2.com
>> Blog: http://yumani.blogspot.com/
>> Mob: + 94 95242
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



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

[Dev] [APIM] Changing default API endpoint using a custom sequence

[Shenavi de Mel]

Hi APIM Team,

When i was trying to invoke a custom endpoint which dynamically changes
with a header value using a send mediator in my custom sequence, i
experienced a behavior where the request will go first to the endpoint of
my custom sequence after that it will send a request to the endpoint
specified when creating the API (Production endpoint) . I am trying to
understand the reason for two requests being sent in this scenario? I would
be grateful if you could explain to me why this is happening.

When API is invoked which uses the custom in sequence following was seen on
the wire logs. I have also attached the complete wire logs received to the
mail.

 DEBUG - wire << "GET
/t/backstage/webapps/customerservice-1.1.0/services/customers/customerservice/customerservice/customers/123
HTTP/1.1[\r][\n]"

DEBUG - wire << "GET
/t/backstage/webapps/customerservice-default-SNAPSHOT/services/customers/customerservice/customerservice/customers/123
HTTP/1.1[\r][\n]"

I have attached my custom sequences as well. Your help will be much
appreciated on this matter.

Thanks and Regards
Shenavi
[2015-12-09 16:52:29,228] DEBUG - wire >> "GET 
/newApp/1.0/customerservice/customers/123 HTTP/1.1[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "User-Agent: curl/7.35.0[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "Host: 10.100.7.47:8243[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "Accept: application/json[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "Version: 
customerservice-1.1.0[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "Authorization: Bearer 
f2dab8c6f39a1a1239cee8f299ce4[\r][\n]"
[2015-12-09 16:52:29,228] DEBUG - wire >> "[\r][\n]"
[2015-12-09 16:52:29,230]  INFO - LogMediator uri.var.version = 
customerservice-1.1.0
[2015-12-09 16:52:29,914] DEBUG - wire << "GET 
/t/backstage/webapps/customerservice-1.1.0/services/customers/customerservice/customerservice/customers/123
 HTTP/1.1[\r][\n]"
[2015-12-09 16:52:29,914] DEBUG - wire << "Version: 
customerservice-1.1.0[\r][\n]"
[2015-12-09 16:52:29,914] DEBUG - wire << "Accept: application/json[\r][\n]"
[2015-12-09 16:52:29,914] DEBUG - wire << "Host: 
appserver.dev.cloud.wso2.com:80[\r][\n]"
[2015-12-09 16:52:29,915] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2015-12-09 16:52:29,915] DEBUG - wire << "User-Agent: 
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2015-12-09 16:52:29,915] DEBUG - wire << "[\r][\n]"
[2015-12-09 16:52:30,149] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2015-12-09 16:52:30,149] DEBUG - wire >> "Content-Type: 
application/json[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire >> "Date: Wed, 09 Dec 2015 11:22:05 
GMT[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire >> "Server: 
WSO2-PassThrough-HTTP[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "GET 
/t/backstage/webapps/customerservice-default-SNAPSHOT/services/customers/customerservice/customerservice/customers/123
 HTTP/1.1[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "Version: 
customerservice-1.1.0[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "Accept: application/json[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "Host: 
appserver.dev.cloud.wso2.com:80[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire << "User-Agent: 
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2015-12-09 16:52:30,150] DEBUG - wire >> "[\r][\n]"
[2015-12-09 16:52:30,151] DEBUG - wire >> "25[\r][\n]"
[2015-12-09 16:52:30,151] DEBUG - wire >> 
"{"Customer":{"id":123,"name":"John"}}[\r][\n]"
[2015-12-09 16:52:30,151] DEBUG - wire >> "0[\r][\n]"
[2015-12-09 16:52:30,151] DEBUG - wire >> "[\r][\n]"
[2015-12-09 16:52:30,151] DEBUG - wire << "[\r][\n]"
[2015-12-09 16:52:30,152]  INFO - LogMediator To: 
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , 
MessageID: urn:uuid:20e7b918-e0f3-4925-88bb-26e80e2d8014, Direction: response, 
Envelope: http://schemas.xmlsoap.org/soap/envelope/;>123John
[2015-12-09 16:52:30,153] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Access-Control-Allow-Headers: 
authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Access-Control-Allow-Origin: 
*[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Access-Control-Allow-Methods: 
GET[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Content-Type: 
application/json[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Date: Wed, 09 Dec 2015 11:22:30 
GMT[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Server: 
WSO2-PassThrough-HTTP[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << "25[\r][\n]"
[2015-12-09 16:52:30,153] DEBUG - wire << 

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Malaka Silva]

In my experience using ​DB mediator we can cover some of the use cases
using ESB out of the box, which I find very handy.

Also use case of integrating with stored procs can easily covered with
this.

However there are limits like batch update or getting multiple rows.

​I guess we can argue both ways. IMO we should keep these mediators since
it'll become handy for some use cases :)

On Wed, Dec 9, 2015 at 4:58 PM, Kasun Indrasiri  wrote:

>
>
> On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva  wrote:
>
>> +1 except  DBReport/DBLookup mediators
>>
>> DBReport and DBLookup only offer a very limited set of capabilities. IMO,
> for any real integration scenario, we can't use them.  :).
>
>> On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera  wrote:
>>
>>> Is it possible to provide sufficient documentation to help the customers
>>> who would be migrating in future.
>>>
>>> Thanks,
>>> Yumani
>>>
>>>
>>> On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando 
>>> wrote:
>>>
 *- Callout mediator :*
  All the callout functionality is supported with 'call' mediator with
 blocking=true. Having two similar mediators will be create a bit of a
 confusion.

 It will make a lot of confusion when we have more than one mediators to
 do the same thing. Therefore, better to deprecate this mediator.

 *- DBReport/DBLookup mediator*
 These mediators offer very limited functionality and we always
 recommend to integrate with databases with the use of DSS (using a separate
 DSS or using DSS features inside ESB)

 Even though this mediator has been used by some customers, they are
 using that for very limited functionality and we always suggest them to use
 DSS as Kasun mentioned. If users really want to connect to a database, they
 can easily write a simple class mediator.

 *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
 development happens on these.
 *- Router* : Same as filter mediator, so no use of having this.
 *- In, Out * : Rarely used and often not required with the new
 call/respond mediator approach.

 +1 for deprecating these mediators.

 With the new DAS integration, we can deprecate BAM mediator since we
 have the PublishEvent mediator.

 On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  wrote:

> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always
> recommend to integrate with databases with the use of DSS (using a 
> separate
> DSS or using DSS features inside ESB)
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> Any comments  on these or any other features that we should deprecate
> from 4.10 release?
>
> Thanks,
> Kasun.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



 --
 Thank you and Best Regards,
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya





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


>>>
>>>
>>> --
>>>
>>>
>>> *Yumani Ranaweera* | Technical Lead
>>> Technical Support- Colombo
>>> WSO2 Inc. |  http://wso2.com
>>> Blog: http://yumani.blogspot.com/
>>> Mob: + 94 95242
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/

Re: [Dev] [APIM] Changing default API endpoint using a custom sequence

[Nuwan Dias]

Why would you want the send mediator to send the request and not execute
the rest? That design would introduced problems such as response stats not
being available, swagger console issues, etc.

It looks like you're trying to achieve the use case of sending the request
to a dynamic endpoint. If that is the case, you can design your endpoint
url with parameters at the time of API Publishing.

Ex: http://host:port/{resource_path}/{param}

Then using custom mediation policies (sequences) you could execute your
logic and populate the values for these parameters accordingly. Read more
about the "HTTP Endpoint" on the ESB docs to understand how to populate the
values of those parameters dynamically.

Thanks,
NuwanD.

On Wed, Dec 9, 2015 at 4:59 PM, Shenavi de Mel  wrote:

> Hi APIM Team,
>
> When i was trying to invoke a custom endpoint which dynamically changes
> with a header value using a send mediator in my custom sequence, i
> experienced a behavior where the request will go first to the endpoint of
> my custom sequence after that it will send a request to the endpoint
> specified when creating the API (Production endpoint) . I am trying to
> understand the reason for two requests being sent in this scenario? I would
> be grateful if you could explain to me why this is happening.
>
> When API is invoked which uses the custom in sequence following was seen
> on the wire logs. I have also attached the complete wire logs received to
> the mail.
>
>  DEBUG - wire << "GET
> /t/backstage/webapps/customerservice-1.1.0/services/customers/customerservice/customerservice/customers/123
> HTTP/1.1[\r][\n]"
>
> DEBUG - wire << "GET
> /t/backstage/webapps/customerservice-default-SNAPSHOT/services/customers/customerservice/customerservice/customers/123
> HTTP/1.1[\r][\n]"
>
> I have attached my custom sequences as well. Your help will be much
> appreciated on this matter.
>
> Thanks and Regards
> Shenavi
>
>
>
>


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

Re: [Dev] Securing HTTP event receiver

[Udara Rathnayake]

I have changed transport to https and provided Authorization header while
invoking the EP. Thanks Lasantha and Tharik.

On Wed, Dec 9, 2015 at 1:25 AM, Lasantha Fernando  wrote:

> Hi Udara,
>
> To add to Tharik's reply above, the username, password supplied from the
> client side will be authenticated against the user store of the particular
> tenant where the event receiver is configured. i.e. any user in that tenant
> domain can authenticate using basic auth and send events to the HTTP
> receiver.
>
> Thanks,
> Lasantha
>
> On 9 December 2015 at 11:02, Tharik Kanaka  wrote:
>
>> Hi Udara,
>>
>> I was mistaken in previous mail, it is possible to authenticate with HTTP
>> receiver https mode via 9443 port. When you are creating the receiver make
>> sure that you select https instead of all.
>>
>> Please refer following CEP producer sample [1].
>>
>> https://github.com/wso2/product-cep/tree/master/modules/samples/producers/http
>>
>> Regards,
>>
>> On Wed, Dec 9, 2015 at 9:20 AM, Tharik Kanaka  wrote:
>>
>>> Hi Udara,
>>>
>>> There is no authentication take place HTTP receiver as i know. You can
>>> achieve authentication if you could use wso2event receiver with thrift.
>>>
>>> Regards,
>>>
>>> On Wed, Dec 9, 2015 at 8:10 AM, Udara Rathnayake 
>>> wrote:
>>>
 Hi,

 Can we do the $subject?
 After creating a HTTP event receiver[1] within DAS, anyone with the EP
 and the stream definition can publish events. Is there any possibility to
 accept events from a single authorized party?

 [1] https://docs.wso2.com/display/DAS300/HTTP+Event+Receiver


 Regards,
 UdaraR

 ___
 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
>>>
>>
>>
>>
>> --
>>
>> *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
>>
>>
>
>
> --
> *Lasantha Fernando*
> Senior Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 71 5247551
>



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

Re: [Dev] [BPS][BPMN] New REST API for BPMN statistics

[Nuwan Pallewela]

Hi Natasha,

Great work.
What happens if an invalid request or request with an illegal argument sent
to the API ?
It is better to have those response messages or response status code also
in the documentation.

Thanks,
Nuwan

On Wed, Dec 9, 2015 at 5:08 PM, Natasha Wijesekara  wrote:

> Hi,
>
> I  documented a user guide which contains details about the new rest API
> implemented to generate the statistics for bpmn.
> Appreciate any suggestions and comments.
>
> Thanks,
> Natasha
>
> On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda  wrote:
>
>> [Adding Architecture group]
>>
>> On Tue, Dec 8, 2015 at 2:45 PM, Natasha Wijesekara 
>> wrote:
>>
>>> Hi ,
>>>
>>> Currently the statistics generated for the bpmn-explorer is generated
>>> using jaggery. When the work load is high, the  bpmn-explorer takes a
>>> longer time to generate these statistics which causes performance issues.
>>>
>>> As a solution I am working a new stats REST api  to generate these
>>> statistics at the back-end. This reduces the work load  and thereby solves
>>> the performance issues caused during peak times (when the workload is at
>>> its maximum).
>>>
>>> After taking in data about  the bpmn processes, tasks  and users
>>> involved, the api  processes these data into meaningful statistics.These
>>> statistics generated is used in the bpmn-explorer reporting dashboard to
>>> generate the statistical graphs.
>>>
>>> The statistics generated includes:
>>>
>>> 1) Average time duration for all completed processes.
>>> The user has the option to either view all completed processes or the
>>> top 10 processes which finished within a short time duration or the top 10
>>> processes which took a long time duration to finish.
>>>
>>> 2) Average time duration of tasks of a  completed process.
>>> The user can select the completed process from the combo box and view
>>> the average time duration.
>>>
>>> 3) User and the no. of tasks he/she has completed upto now.
>>>
>>> 4) Average time taken by each user to complete the tasks assigned to
>>> him/her.
>>>
>>> 5) Task demand variation over time i.e. no. of tasks started and no. of
>>> tasks completed in each month. This is useful for resource allocation
>>> purposes.
>>>
>>> 6) Process demand variation over time i.e. no. of processes started and
>>> no. of processes completed in each month regardless of a specific user.
>>> This is useful for resource allocation purposes.
>>>
>>> 7) User Performance i.e. Task demand variation of users separately over
>>> time i.e. no. of tasks started and no. of tasks completed in each month.
>>> This is useful for resource allocation purposes.
>>>
>>> I have attached the class diagram of the REST api. The new stats REST
>>> api will be integrated with the existing bpmn REST api.
>>> Appreciate any suggestions and comments.
>>>
>>> Thanks,
>>> --
>>> *Natasha Wijesekare*
>>>
>>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>>> *
>>> *email  : nata...@wso2.com *
>>> *mobile: +94 771358651 <%2B94%20771358651>*
>>>
>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>>
>>
>
>
> --
> *Natasha Wijesekare*
>
> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
> *
> *email  : nata...@wso2.com *
> *mobile: +94 771358651 <%2B94%20771358651>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

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

[Dev] [VOTE] Release WSO2 Developer Studio Kernel 4.0.0 RC2

[Kavith Lokuhewage]

Hi Devs,

Vote for WSO2 Developer Studio Kernel 4.0.0 - Second Release Candidate.

This release contains the new tooling kernel - a set of common tooling
components - separated from the 3.8.0 release of Developer Studio.
In addition to that, this contains following fixes and improvements.
https://wso2.org/jira/issues/?filter=12574

Please install Developer Studio kernel into Eclipse Luna JEE SR2, test and
vote. Vote will be open for 72 hours or longer as needed.

*P2 repository*
http://builder1.us1.wso2.org/~developerstudio/devs-kernel/4.0.0/releases/rc2/p2/

*P2 archives*
http://builder1.us1.wso2.org/~developerstudio/devs-kernel/4.0.0/releases/rc2/

*The tag to be voted upon*
https://github.com/wso2/developer-studio/tree/4.0.0.201512091030-RC2

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

Thanks,
Developer Studio Team

-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

Re: [Dev] [APIM] Changing default API endpoint using a custom sequence

[Shenavi de Mel]

Hi Nuwan,

Thanks for the suggestion. I was able to get the requirement working using
the method suggested by you.

Thanks
Shenavi

*Shenavi de Mel*
Software Engineer
WSO2 Inc: http://wso2.com
email: shen...@wso2.com
mobile:+94771244470


On Wed, Dec 9, 2015 at 10:35 PM, Shenavi de Mel  wrote:

> Hi Nuwan,
>
> I was not aware that we are able to specify the production endpoint in
> this parameterized manner. I will go through the docs to understand how to
> populate them dynamically This is a customer requirement and we have raised
> the concerns mentioned by you to the customer as well in going for this
> approach but then he mentions that they need to have the support for a
> version specific endpoint with designing a single API with endpoints of
> various versions. (User will be specifying the version in the header and
> the request should be made accordingly).
>
> Thanks
> Shenavi
>
> *Shenavi de Mel*
> Software Engineer
> WSO2 Inc: http://wso2.com
> email: shen...@wso2.com
> mobile:+94771244470
>
>
> On Wed, Dec 9, 2015 at 7:37 PM, Nuwan Dias  wrote:
>
>> Why would you want the send mediator to send the request and not execute
>> the rest? That design would introduced problems such as response stats not
>> being available, swagger console issues, etc.
>>
>> It looks like you're trying to achieve the use case of sending the
>> request to a dynamic endpoint. If that is the case, you can design your
>> endpoint url with parameters at the time of API Publishing.
>>
>> Ex: http://host:port/{resource_path}/{param}
>>
>> Then using custom mediation policies (sequences) you could execute your
>> logic and populate the values for these parameters accordingly. Read more
>> about the "HTTP Endpoint" on the ESB docs to understand how to populate the
>> values of those parameters dynamically.
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Dec 9, 2015 at 4:59 PM, Shenavi de Mel  wrote:
>>
>>> Hi APIM Team,
>>>
>>> When i was trying to invoke a custom endpoint which dynamically changes
>>> with a header value using a send mediator in my custom sequence, i
>>> experienced a behavior where the request will go first to the endpoint of
>>> my custom sequence after that it will send a request to the endpoint
>>> specified when creating the API (Production endpoint) . I am trying to
>>> understand the reason for two requests being sent in this scenario? I would
>>> be grateful if you could explain to me why this is happening.
>>>
>>> When API is invoked which uses the custom in sequence following was seen
>>> on the wire logs. I have also attached the complete wire logs received to
>>> the mail.
>>>
>>>  DEBUG - wire << "GET
>>> /t/backstage/webapps/customerservice-1.1.0/services/customers/customerservice/customerservice/customers/123
>>> HTTP/1.1[\r][\n]"
>>>
>>> DEBUG - wire << "GET
>>> /t/backstage/webapps/customerservice-default-SNAPSHOT/services/customers/customerservice/customerservice/customers/123
>>> HTTP/1.1[\r][\n]"
>>>
>>> I have attached my custom sequences as well. Your help will be much
>>> appreciated on this matter.
>>>
>>> Thanks and Regards
>>> Shenavi
>>>
>>>
>>>
>>>
>>
>>
>> --
>> 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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Vanjikumaran Sivajothy]

Is it going to be complete functional Deprecate? If yes, there will be not
forward compatibility during the upgrades.

On Wed, Dec 9, 2015 at 10:23 AM, Isuru Udana  wrote:

> Hi Harshana,
>
> On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin <
> harshan...@gmail.com> wrote:
>
>> Hi Kasun,
>>
>> Please see the comments inline.
>>
>> Thanks and Regards,
>> Harshana
>> --
>> Harshana Eranga Martin
>>
>> Committer - Eclipse ECF: http://www.eclipse.org/ecf/
>> Blog: http://harshana05.blogspot.com
>> Profile: https://www.google.com/profiles/harshana05
>>
>> On 9 December 2015 at 17:41, Kasun Indrasiri  wrote:
>>
>>> Shall we deprecate following mediators in 4.10 release.
>>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>
>> Can we use the Call mediator with blocking=true instead of Callout
>> mediator for the NTLM scenarios?
>>
>> I have tried a NTLM scenario recently with Call mediator and
>> blocking=true in ESB 4.9.0 but it didn't work while the Callout mediator
>> works fine for the same scenario. I also assumed Call mediator would work
>> but it didn't. Can you please check and verify?
>>
>> If that the case, we need to fix that bug.
>
>>
>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> Any comments  on these or any other features that we should deprecate
>>> from 4.10 release?
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vanjikumaran Sivajothy
*Associate Technical Lead*
*WSO2 Inc. http://wso2.com *
*USA Mobile **+1-812-361-1286*
*Srilanka Mobile:+94-777-219-209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]


This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Harshana,

On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin  wrote:

> Hi Kasun,
>
> Please see the comments inline.
>
> Thanks and Regards,
> Harshana
> --
> Harshana Eranga Martin
>
> Committer - Eclipse ECF: http://www.eclipse.org/ecf/
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
> On 9 December 2015 at 17:41, Kasun Indrasiri  wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>
> Can we use the Call mediator with blocking=true instead of Callout
> mediator for the NTLM scenarios?
>
> I have tried a NTLM scenario recently with Call mediator and blocking=true
> in ESB 4.9.0 but it didn't work while the Callout mediator works fine for
> the same scenario. I also assumed Call mediator would work but it didn't.
> Can you please check and verify?
>
> If that the case, we need to fix that bug.

>
>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DAS]WSO2 DAS load balancing ports.

[Roshan Wijesena]

Hi,

When load balancing a minimum HA DAS cluster[1] what are the ports that we
need to expose to the outside? I Could not find proper documentation around
that?

[1]
https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Availability+Deployment

-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [BPS][BPMN] New REST API for BPMN statistics

[Dinithi De Silva]

Hi Natasha,

How are you going to ensure the security of the APIs? Have you thought of
using any security models?

You can use  permission/role based model in order to achieve this. Just
make sure which APIs need the administrative privileges.

Thanks.


On Wed, Dec 9, 2015 at 9:30 PM, Nuwan Pallewela  wrote:

> Hi Natasha,
>
> Great work.
> What happens if an invalid request or request with an illegal argument
> sent to the API ?
> It is better to have those response messages or response status code also
> in the documentation.
>
> Thanks,
> Nuwan
>
> On Wed, Dec 9, 2015 at 5:08 PM, Natasha Wijesekara 
> wrote:
>
>> Hi,
>>
>> I  documented a user guide which contains details about the new rest API
>> implemented to generate the statistics for bpmn.
>> Appreciate any suggestions and comments.
>>
>> Thanks,
>> Natasha
>>
>> On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda  wrote:
>>
>>> [Adding Architecture group]
>>>
>>> On Tue, Dec 8, 2015 at 2:45 PM, Natasha Wijesekara 
>>> wrote:
>>>
 Hi ,

 Currently the statistics generated for the bpmn-explorer is generated
 using jaggery. When the work load is high, the  bpmn-explorer takes a
 longer time to generate these statistics which causes performance issues.

 As a solution I am working a new stats REST api  to generate these
 statistics at the back-end. This reduces the work load  and thereby solves
 the performance issues caused during peak times (when the workload is at
 its maximum).

 After taking in data about  the bpmn processes, tasks  and users
 involved, the api  processes these data into meaningful statistics.These
 statistics generated is used in the bpmn-explorer reporting dashboard to
 generate the statistical graphs.

 The statistics generated includes:

 1) Average time duration for all completed processes.
 The user has the option to either view all completed processes or the
 top 10 processes which finished within a short time duration or the top 10
 processes which took a long time duration to finish.

 2) Average time duration of tasks of a  completed process.
 The user can select the completed process from the combo box and view
 the average time duration.

 3) User and the no. of tasks he/she has completed upto now.

 4) Average time taken by each user to complete the tasks assigned to
 him/her.

 5) Task demand variation over time i.e. no. of tasks started and no. of
 tasks completed in each month. This is useful for resource allocation
 purposes.

 6) Process demand variation over time i.e. no. of processes started and
 no. of processes completed in each month regardless of a specific user.
 This is useful for resource allocation purposes.

 7) User Performance i.e. Task demand variation of users separately over
 time i.e. no. of tasks started and no. of tasks completed in each month.
 This is useful for resource allocation purposes.

 I have attached the class diagram of the REST api. The new stats REST
 api will be integrated with the existing bpmn REST api.
 Appreciate any suggestions and comments.

 Thanks,
 --
 *Natasha Wijesekare*

 *Software Engineering Intern, WSO2  Inc:  http://wso2.com
 *
 *email  : nata...@wso2.com *
 *mobile: +94 771358651 <%2B94%20771358651>*

>>>
>>>
>>>
>>> --
>>> Vinod Kavinda
>>> Software Engineer
>>> *WSO2 Inc. - lean . enterprise . middleware .*
>>> Mobile : +94 (0) 712 415544
>>> Blog : http://soatechflicks.blogspot.com/
>>>
>>>
>>
>>
>> --
>> *Natasha Wijesekare*
>>
>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>> *
>> *email  : nata...@wso2.com *
>> *mobile: +94 771358651 <%2B94%20771358651>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Viraj Senevirathne]

Hi,

I think we will have to test call mediator in blocking mode for some
different use cases. Then we will have to update Documentation about
blocking capability of call mediator. For example the Call Mediator
Documentation for ESB 4.9.0 [1] does not contain any information about
blocking behavior of the call mediator. I think most of the people do not
know about this feature because of that. In any case we will have to test
blocking behavior more as there are some complains about it.

[1] https://docs.wso2.com/display/ESB490/Call+Mediator
Thank you,

On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
wrote:

> +1 to deprecate Callout mediator since we have the Callout mediator
> functionalities in Call mediator.
>
> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
> wrote:
>
>> I've found DBReport / DBLookup to be quite useful for simple DB
>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>> limited in it's ability to only being able to return a single row of data,
>> DB Report mediator is still quite useful in writing to a database,
>> especially when we use a DB as part of the mediation sequences.
>>
>> I also feel it is worth continuing with POJOCommand, as it is the most
>> simplest way of executing some custom code as part of a sequence. Although
>> it is possible to do the same with a Class mediator, one doesn't have to
>> worry about adding the proper jars, working with MessageContext etc. with
>> the POJOCommand. I think we should retain it for the sake of simplicity of
>> use.
>>
>> I'm +1 to deprecate the rest of the mediators.
>>
>> Thanks,
>>
>> Vidura
>>
>>
>>
>> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>>
>>> Shall we deprecate following mediators in 4.10 release.
>>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> Any comments  on these or any other features that we should deprecate
>>> from 4.10 release?
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Vidura Gamini Abhaya, Ph.D.
>> Director of Engineering
>> M:+94 77 034 7754
>> E: vid...@wso2.com
>>
>> WSO2 Inc. (http://wso2.com)
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Viraj Senevirathne
Software Engineer; WSO2, Inc.

Mobile : +94 71 958 0269
Email : vir...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Vidura Gamini Abhaya]

Hi Isuru,

I've used it in a mediation sequence where I use a POJO to generate a
unique customer id given a couple of parameters and there's a checksum
added to the end. I already had written this code and it was quite simple
and straightforward to reuse it with a POJOCommand mediator. I feel the
simplicity of it is a welcome feature, where reading and setting values in
MessageContext is automatically handled for me.

I don't know whether a single usage case is enough to make the case to keep
it. However, if we decide to keep it though, I suggest that we improve the
documentation on it. I had to dig around to find out how the what the
different actions mean. It wasn't clear to me in the docs (I believe most
of the content is carried forward from Syanpse).

Thanks and Regards,

Vidura



On 10 December 2015 at 10:57, Isuru Udana  wrote:

> Hi Kathees,
>
> I think we should do a comparison once more to make sure that we have
> covered everything before removing Callout. NTLM one which Harshana pointed
> out may be due to absence of initClientOptions configuration option.
>
> Hi Vidura,
> Point you raised on the POJOCommand mediator is really interesting. We
> haven't seen any usage of that over years. But now we found at least one
> user who has found it useful. Thanks for pointing that out. So we should
> reconsider how useful it is.
>
> Thanks.
>
>
>
> On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
> wrote:
>
>> +1 to deprecate Callout mediator since we have the Callout mediator
>> functionalities in Call mediator.
>>
>> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
>> wrote:
>>
>>> I've found DBReport / DBLookup to be quite useful for simple DB
>>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>>> limited in it's ability to only being able to return a single row of data,
>>> DB Report mediator is still quite useful in writing to a database,
>>> especially when we use a DB as part of the mediation sequences.
>>>
>>> I also feel it is worth continuing with POJOCommand, as it is the most
>>> simplest way of executing some custom code as part of a sequence. Although
>>> it is possible to do the same with a Class mediator, one doesn't have to
>>> worry about adding the proper jars, working with MessageContext etc. with
>>> the POJOCommand. I think we should retain it for the sake of simplicity of
>>> use.
>>>
>>> I'm +1 to deprecate the rest of the mediators.
>>>
>>> Thanks,
>>>
>>> Vidura
>>>
>>>
>>>
>>> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>>>
 Shall we deprecate following mediators in 4.10 release.

 *- Callout mediator :*
  All the callout functionality is supported with 'call' mediator with
 blocking=true. Having two similar mediators will be create a bit of a
 confusion.

 *- DBReport/DBLookup mediator*
 These mediators offer very limited functionality and we always
 recommend to integrate with databases with the use of DSS (using a separate
 DSS or using DSS features inside ESB)

 *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
 development happens on these.
 *- Router* : Same as filter mediator, so no use of having this.
 *- In, Out * : Rarely used and often not required with the new
 call/respond mediator approach.

 Any comments  on these or any other features that we should deprecate
 from 4.10 release?

 Thanks,
 Kasun.

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

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

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


>>>
>>>
>>> --
>>> Vidura Gamini Abhaya, Ph.D.
>>> Director of Engineering
>>> M:+94 77 034 7754
>>> E: vid...@wso2.com
>>>
>>> WSO2 Inc. (http://wso2.com)
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vidura Gamini Abhaya, Ph.D.
Director of Engineering
M:+94 77 034 7754
E: vid...@wso2.com

WSO2 

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Kathees,

I think we should do a comparison once more to make sure that we have
covered everything before removing Callout. NTLM one which Harshana pointed
out may be due to absence of initClientOptions configuration option.

Hi Vidura,
Point you raised on the POJOCommand mediator is really interesting. We
haven't seen any usage of that over years. But now we found at least one
user who has found it useful. Thanks for pointing that out. So we should
reconsider how useful it is.

Thanks.



On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
wrote:

> +1 to deprecate Callout mediator since we have the Callout mediator
> functionalities in Call mediator.
>
> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
> wrote:
>
>> I've found DBReport / DBLookup to be quite useful for simple DB
>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>> limited in it's ability to only being able to return a single row of data,
>> DB Report mediator is still quite useful in writing to a database,
>> especially when we use a DB as part of the mediation sequences.
>>
>> I also feel it is worth continuing with POJOCommand, as it is the most
>> simplest way of executing some custom code as part of a sequence. Although
>> it is possible to do the same with a Class mediator, one doesn't have to
>> worry about adding the proper jars, working with MessageContext etc. with
>> the POJOCommand. I think we should retain it for the sake of simplicity of
>> use.
>>
>> I'm +1 to deprecate the rest of the mediators.
>>
>> Thanks,
>>
>> Vidura
>>
>>
>>
>> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>>
>>> Shall we deprecate following mediators in 4.10 release.
>>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> Any comments  on these or any other features that we should deprecate
>>> from 4.10 release?
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Vidura Gamini Abhaya, Ph.D.
>> Director of Engineering
>> M:+94 77 034 7754
>> E: vid...@wso2.com
>>
>> WSO2 Inc. (http://wso2.com)
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [FB Connector] Can't Publish a Video Using fileUrl with FB Connector

[Shakila Sivagnanarajah]

Hi Malaka,

Connector is re-uploaded.

Thanks

On Wed, Dec 9, 2015 at 6:16 PM, Malaka Silva  wrote:

> Can we re-upload the connector and resolve the issue
>
> On Wed, Dec 9, 2015 at 5:48 PM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi Malaka,
>>
>> I checked and merged.
>>
>> Thanks
>>
>> On Wed, Dec 9, 2015 at 5:44 PM, Malaka Silva  wrote:
>>
>>> Hi Shakila,
>>>
>>> Please check this.
>>>
>>> On Wed, Dec 9, 2015 at 4:02 PM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
 Hi All,

 I tried to publish a video to a facebook page using the fileUrl via
 Facebook connector. It returns following error

 {
   "error": {
 "message": "(#100) Param content_category must be one of 
 {BEAUTY_FASHION, BUSINESS, CARS_TRUCKS, COMEDY, CUTE_ANIMALS, 
 ENTERTAINMENT, FAMILY, FOOD_HEALTH, HOME, LIFESTYLE, MUSIC, NEWS, 
 POLITICS, SCIENCE, SPORTS, TECHNOLOGY, VIDEO_GAMING, OTHER}",
 "type": "OAuthException",
 "code": 100,
 "fbtrace_id": "F7CZIU6jVK2"
   }

 }

 When I checked the code it seems that the value of contentCategory is
 assigned by fileUrl value. AFAIU that is not correct. I manually changed
 that and then tried with the edited connector. Then it works fine.
 I've created following JIRA[1] and PR[2]

 [1] - https://wso2.org/jira/browse/ESBCONNECT-75
 [2] - https://github.com/wso2/esb-connectors/pull/440

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

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


>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Shakila Sivagnanarajah
>> Associate Software Engineer
>> Mobile :+94 (0) 768 856837
>> shak...@wso2.com
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Shakila Sivagnanarajah
Associate Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Malaka Silva]

IMO best option in that case is have connectors supporting different spring
versions, similar to what we are doing for EJBs. Having a mediator will
only limit for single version.

On Thu, Dec 10, 2015 at 11:35 AM, Maheeka Jayasuriya 
wrote:

> Hi,
>
> I've observed spring mediator being used extensively in situations where
> maintaining the domain model useful (class mediators are the alternative
> with a POJO domain model). This allows maintainability and is easily
> extensible. However, Spring mediator right now does not explore best of
> Spring capabilities, also because we are using spring 1.2.8 where as latest
> is 4.2.X.
>
> It might be worthwhile to retain Spring mediator if we can upgrade the
> framework and explore more options, but depends on the validity of use
> cases.
>
> Thanks,
> Maheeka
>
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Thu, Dec 10, 2015 at 11:03 AM, Viraj Senevirathne 
> wrote:
>
>> Hi,
>>
>> I think we will have to test call mediator in blocking mode for some
>> different use cases. Then we will have to update Documentation about
>> blocking capability of call mediator. For example the Call Mediator
>> Documentation for ESB 4.9.0 [1] does not contain any information about
>> blocking behavior of the call mediator. I think most of the people do not
>> know about this feature because of that. In any case we will have to test
>> blocking behavior more as there are some complains about it.
>>
>> [1] https://docs.wso2.com/display/ESB490/Call+Mediator
>> Thank you,
>>
>> On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
>> wrote:
>>
>>> +1 to deprecate Callout mediator since we have the Callout mediator
>>> functionalities in Call mediator.
>>>
>>> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
>>> wrote:
>>>
 I've found DBReport / DBLookup to be quite useful for simple DB
 operations as they are easy to do OOTB. While DB Lookup mediator maybe
 limited in it's ability to only being able to return a single row of data,
 DB Report mediator is still quite useful in writing to a database,
 especially when we use a DB as part of the mediation sequences.

 I also feel it is worth continuing with POJOCommand, as it is the most
 simplest way of executing some custom code as part of a sequence. Although
 it is possible to do the same with a Class mediator, one doesn't have to
 worry about adding the proper jars, working with MessageContext etc. with
 the POJOCommand. I think we should retain it for the sake of simplicity of
 use.

 I'm +1 to deprecate the rest of the mediators.

 Thanks,

 Vidura



 On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:

> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always
> recommend to integrate with databases with the use of DSS (using a 
> separate
> DSS or using DSS features inside ESB)
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> Any comments  on these or any other features that we should deprecate
> from 4.10 release?
>
> Thanks,
> Kasun.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Vidura Gamini Abhaya, Ph.D.
 Director of Engineering
 M:+94 77 034 7754
 E: vid...@wso2.com

 WSO2 Inc. (http://wso2.com)
 lean.enterprise.middleware

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


>>>
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Viraj Senevirathne
>> Software Engineer; WSO2, Inc.
>>
>> Mobile : +94 71 958 0269
>> Email : vir...@wso2.com
>>
>> 

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Kathees Rajendram]

+1 to deprecate Callout mediator since we have the Callout mediator
functionalities in Call mediator.

On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
wrote:

> I've found DBReport / DBLookup to be quite useful for simple DB operations
> as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
> ability to only being able to return a single row of data, DB Report
> mediator is still quite useful in writing to a database, especially when we
> use a DB as part of the mediation sequences.
>
> I also feel it is worth continuing with POJOCommand, as it is the most
> simplest way of executing some custom code as part of a sequence. Although
> it is possible to do the same with a Class mediator, one doesn't have to
> worry about adding the proper jars, working with MessageContext etc. with
> the POJOCommand. I think we should retain it for the sake of simplicity of
> use.
>
> I'm +1 to deprecate the rest of the mediators.
>
> Thanks,
>
> Vidura
>
>
>
> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Vidura Gamini Abhaya, Ph.D.
> Director of Engineering
> M:+94 77 034 7754
> E: vid...@wso2.com
>
> WSO2 Inc. (http://wso2.com)
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


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

Re: [Dev] [DEV][DAS]WSO2 DAS load balancing ports.

[Maninda Edirisooriya]

Hi Roshen,

Please find the required port in [1] and [2].

[1] https://docs.wso2.com/display/DAS300/WSO2+DAS+Specific+Ports
[2] https://docs.wso2.com/display/DAS300/Default+Ports+of+WSO2+Products

Thanks.


*Maninda Edirisooriya*
Senior Software Engineer

*WSO2, Inc.*lean.enterprise.middleware.

*Blog* : http://maninda.blogspot.com/
*E-mail* : mani...@wso2.com
*Skype* : @manindae
*Twitter* : @maninda

On Thu, Dec 10, 2015 at 5:16 AM, Roshan Wijesena  wrote:

> Hi,
>
> When load balancing a minimum HA DAS cluster[1] what are the ports that we
> need to expose to the outside? I Could not find proper documentation around
> that?
>
> [1]
> https://docs.wso2.com/display/CLUSTER44x/Minimum+High+Availability+Deployment
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Maheeka Jayasuriya]

Hi,

I've observed spring mediator being used extensively in situations where
maintaining the domain model useful (class mediators are the alternative
with a POJO domain model). This allows maintainability and is easily
extensible. However, Spring mediator right now does not explore best of
Spring capabilities, also because we are using spring 1.2.8 where as latest
is 4.2.X.

It might be worthwhile to retain Spring mediator if we can upgrade the
framework and explore more options, but depends on the validity of use
cases.

Thanks,
Maheeka


Maheeka Jayasuriya
Software Engineer
Mobile : +9450661

On Thu, Dec 10, 2015 at 11:03 AM, Viraj Senevirathne 
wrote:

> Hi,
>
> I think we will have to test call mediator in blocking mode for some
> different use cases. Then we will have to update Documentation about
> blocking capability of call mediator. For example the Call Mediator
> Documentation for ESB 4.9.0 [1] does not contain any information about
> blocking behavior of the call mediator. I think most of the people do not
> know about this feature because of that. In any case we will have to test
> blocking behavior more as there are some complains about it.
>
> [1] https://docs.wso2.com/display/ESB490/Call+Mediator
> Thank you,
>
> On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
> wrote:
>
>> +1 to deprecate Callout mediator since we have the Callout mediator
>> functionalities in Call mediator.
>>
>> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
>> wrote:
>>
>>> I've found DBReport / DBLookup to be quite useful for simple DB
>>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>>> limited in it's ability to only being able to return a single row of data,
>>> DB Report mediator is still quite useful in writing to a database,
>>> especially when we use a DB as part of the mediation sequences.
>>>
>>> I also feel it is worth continuing with POJOCommand, as it is the most
>>> simplest way of executing some custom code as part of a sequence. Although
>>> it is possible to do the same with a Class mediator, one doesn't have to
>>> worry about adding the proper jars, working with MessageContext etc. with
>>> the POJOCommand. I think we should retain it for the sake of simplicity of
>>> use.
>>>
>>> I'm +1 to deprecate the rest of the mediators.
>>>
>>> Thanks,
>>>
>>> Vidura
>>>
>>>
>>>
>>> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>>>
 Shall we deprecate following mediators in 4.10 release.

 *- Callout mediator :*
  All the callout functionality is supported with 'call' mediator with
 blocking=true. Having two similar mediators will be create a bit of a
 confusion.

 *- DBReport/DBLookup mediator*
 These mediators offer very limited functionality and we always
 recommend to integrate with databases with the use of DSS (using a separate
 DSS or using DSS features inside ESB)

 *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
 development happens on these.
 *- Router* : Same as filter mediator, so no use of having this.
 *- In, Out * : Rarely used and often not required with the new
 call/respond mediator approach.

 Any comments  on these or any other features that we should deprecate
 from 4.10 release?

 Thanks,
 Kasun.

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

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

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


>>>
>>>
>>> --
>>> Vidura Gamini Abhaya, Ph.D.
>>> Director of Engineering
>>> M:+94 77 034 7754
>>> E: vid...@wso2.com
>>>
>>> WSO2 Inc. (http://wso2.com)
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Viraj Senevirathne
> Software Engineer; WSO2, Inc.
>
> Mobile : +94 71 958 0269
> Email : vir...@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

[Dev] [MDM][AppManager] APP Publisher and store login issue

[Manoj Gunawardena]

Hi All,

APP Manager store and publisher login fails with following error.

ERROR
{org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor}
-  ALERT: Invalid Assertion Consumer URL value '
https://localhost:9443/publisher/acs' in the AuthnRequest message from  the
issuer 'publisher'. Possibly an attempt for a spoofing attack

Attached the sso-idp-config.xml file.

The 5.0.3 is the  identity version we are checking.


-- 
Manoj Gunawardena
Tech Lead
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
Mobile : +94 77 2291643


https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp


cdm
https://localhost:9443/cdm/acs
true
true
false
false

http://wso2.org/claims/role
http://wso2.org/claims/emailaddress

false

true

carbonServer




mdm
https://localhost:9443/mdm/sso/acs
true
true
false
false

http://wso2.org/claims/role
http://wso2.org/claims/emailaddress

false

true

carbonServer




store
https://localhost:9443/store/acs
https://localhost:9443/store/acs
https://localhost:9443/store/acs
true
/store/login.jag


social
https://localhost:9443/social/acs
https://localhost:9443/social/acs
https://localhost:9443/social/acs
true
/social/login


publisher
https://localhost:9443/publisher/acs
https://localhost:9443/publisher/acs
https://localhost:9443/publisher/acs
true
/publisher/controllers/login.jag



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

Re: [Dev] [MDM][AppManager] APP Publisher and store login issue

[Kasun Dananjaya Delgolla]

Hi Manoj,

We got the issue resolved by correcting the SSO IDP config issues.
sso-idp-config.xml configuration "AssertionConsumerServiceURLs" entries
should be as follows,


 https://l

ocalhost:9443/store/acs
 
 https://

l

ocalhost:9443/store/acs

Attached the complete config file for your reference.

Thanks

On Thu, Dec 10, 2015 at 11:36 AM, Manoj Gunawardena  wrote:

> Hi All,
>
> APP Manager store and publisher login fails with following error.
>
> ERROR
> {org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor}
> -  ALERT: Invalid Assertion Consumer URL value '
> https://localhost:9443/publisher/acs' in the AuthnRequest message from
> the issuer 'publisher'. Possibly an attempt for a spoofing attack
>
> Attached the sso-idp-config.xml file.
>
> The 5.0.3 is the  identity version we are checking.
>
>
> --
> Manoj Gunawardena
> Tech Lead
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> Mobile : +94 77 2291643
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kasun Dananjaya Delgolla

Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Tel:  +94 11 214 5345
Fax: +94 11 2145300
Mob: + 94 771 771 015
Blog: http://kddcodingparadise.blogspot.com
Linkedin: *http://lk.linkedin.com/in/kasundananjaya
*


https://stratos-local.wso2.com/carbon/tenant-register/select_domain.jsp


cdm
https://localhost:9443/cdm/acs
true
true
false
false

http://wso2.org/claims/role
http://wso2.org/claims/emailaddress

false

true

carbonServer




mdm
	
 		https://localhost:9443/emm/sso/acs
   	
https://localhost:9443/emm/sso/acs
true
true
false
false

http://wso2.org/claims/role
http://wso2.org/claims/emailaddress

false

true

carbonServer




store
	
 		https://localhost:9443/store/acs
   	
https://localhost:9443/store/acs
true
/store/login.jag


social
	
 		https://localhost:9443/social/acs
   	
https://localhost:9443/social/acs
true
/social/login


publisher
	
 		https://localhost:9443/publisher/acs
   	
https://localhost:9443/publisher/acs
true
/publisher/controllers/login.jag



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

Re: [Dev] [Architecture] [BPS][BPMN] New REST API for BPMN statistics

[Vinod Kavinda]

Hi Natasha,
You can use the format used in Activiti rest api documentations [1] for
this also. It includes response codes and sample success responses.

@Dinithi, we are doing basic authentication using the security handler [2]
AFAIK.

[1] - http://www.activiti.org/userguide/#_get_a_deployment
[2] -
https://github.com/wso2/carbon-business-process/blob/master/components/bpmn/bpmn-rest/src/main/java/org/wso2/carbon/bpmn/rest/security/AuthenticationHandler.java

Regards,
Vinod Kavinda

On Thu, Dec 10, 2015 at 7:30 AM, Dinithi De Silva  wrote:

> Hi Natasha,
>
> How are you going to ensure the security of the APIs? Have you thought of
> using any security models?
>
> You can use  permission/role based model in order to achieve this. Just
> make sure which APIs need the administrative privileges.
>
> Thanks.
>
>
> On Wed, Dec 9, 2015 at 9:30 PM, Nuwan Pallewela  wrote:
>
>> Hi Natasha,
>>
>> Great work.
>> What happens if an invalid request or request with an illegal argument
>> sent to the API ?
>> It is better to have those response messages or response status code also
>> in the documentation.
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, Dec 9, 2015 at 5:08 PM, Natasha Wijesekara 
>> wrote:
>>
>>> Hi,
>>>
>>> I  documented a user guide which contains details about the new rest API
>>> implemented to generate the statistics for bpmn.
>>> Appreciate any suggestions and comments.
>>>
>>> Thanks,
>>> Natasha
>>>
>>> On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda  wrote:
>>>
 [Adding Architecture group]

 On Tue, Dec 8, 2015 at 2:45 PM, Natasha Wijesekara 
 wrote:

> Hi ,
>
> Currently the statistics generated for the bpmn-explorer is generated
> using jaggery. When the work load is high, the  bpmn-explorer takes a
> longer time to generate these statistics which causes performance issues.
>
> As a solution I am working a new stats REST api  to generate these
> statistics at the back-end. This reduces the work load  and thereby solves
> the performance issues caused during peak times (when the workload is at
> its maximum).
>
> After taking in data about  the bpmn processes, tasks  and users
> involved, the api  processes these data into meaningful statistics.These
> statistics generated is used in the bpmn-explorer reporting dashboard to
> generate the statistical graphs.
>
> The statistics generated includes:
>
> 1) Average time duration for all completed processes.
> The user has the option to either view all completed processes or the
> top 10 processes which finished within a short time duration or the top 10
> processes which took a long time duration to finish.
>
> 2) Average time duration of tasks of a  completed process.
> The user can select the completed process from the combo box and view
> the average time duration.
>
> 3) User and the no. of tasks he/she has completed upto now.
>
> 4) Average time taken by each user to complete the tasks assigned to
> him/her.
>
> 5) Task demand variation over time i.e. no. of tasks started and no.
> of tasks completed in each month. This is useful for resource allocation
> purposes.
>
> 6) Process demand variation over time i.e. no. of processes started
> and no. of processes completed in each month regardless of a specific 
> user.
> This is useful for resource allocation purposes.
>
> 7) User Performance i.e. Task demand variation of users separately
> over time i.e. no. of tasks started and no. of tasks completed in each
> month. This is useful for resource allocation purposes.
>
> I have attached the class diagram of the REST api. The new stats REST
> api will be integrated with the existing bpmn REST api.
> Appreciate any suggestions and comments.
>
> Thanks,
> --
> *Natasha Wijesekare*
>
> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
> *
> *email  : nata...@wso2.com *
> *mobile: +94 771358651 <%2B94%20771358651>*
>



 --
 Vinod Kavinda
 Software Engineer
 *WSO2 Inc. - lean . enterprise . middleware .*
 Mobile : +94 (0) 712 415544
 Blog : http://soatechflicks.blogspot.com/


>>>
>>>
>>> --
>>> *Natasha Wijesekare*
>>>
>>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>>> *
>>> *email  : nata...@wso2.com *
>>> *mobile: +94 771358651 <%2B94%20771358651>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> 

Re: [Dev] Machine Learning Help Needed

[Maheshakya Wijewardena]

Hi,

You can use the multi class classification algorithms in WSO2 Machine
Learner for your task. The quick start guide(
https://docs.wso2.com/display/ML100/Quick+Start+Guide) describes the steps
you have to follow from uploading a dataset to predicting from a trained a
model.
If you need to predict from data online (in case a new customer comes), use
WSO2 CEP extension for ML predictions(
https://docs.wso2.com/display/ML100/WSO2+CEP+Extension+for+ML+Predictions).

Best regards.

On Wed, Dec 9, 2015 at 4:41 PM, NIFRAS ISMAIL 
wrote:

> Hi Machine Learners,
>
> Again I need your favour for Data Anaysis on My final year projects.
>
> My Meta Data Labels are
>
>
> "city","country","birthdate","education","gender","houseowner","marital_status","member_card","num_cars_owned","num_children_at_home","occupation","postal_code","state_province","total_children","yearly_income","product_name"
>
> You may notice that this is a customer and his transaction mapping data of
> a shopping mall.
>
> Class Label is  : product_name
>
> Problem: My issue is I need to find the interest classes from my data
> which contains the above headers.
>
> then If a new customer come to the mall I may predict which item he will
> looking for using Multi Class Multi Label Classification.
>
>
> Could Any one there to help to me ? Looking forward your reply ML Team
>
> Thank you
>
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] 
>
>
>
>
>
> Sent with MailTrack
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Pruthuvi Maheshakya Wijewardena
Software Engineer
WSO2 : http://wso2.com/
Email: mahesha...@wso2.com
Mobile: +94711228855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ML]Recommender System

[Nethaji Chandrasiri]

Hi,

I'm currently working on a website to demonstrate a recommender system
using Machine Learner. As per chosen scenario I've displayed movie
recommendations according to user id, using the model which I built using
collaborative filtering algorithm by uploading a dataset , therefore
recommendation list varies according to current user.

As the next step I've managed to build the model using a DAS table as I'm
planning to update the DAS table accordings to rates provided by current
user, in that case I'm building a new model in ML for every 3 hours using a
script and displaying the recommended movies according to latest model.

As I'm still working on this task I'll update the details accordingly.

Appreciate any suggestions and comments.
-- 
*Nethaji Chandrasiri*
*Software Engineering* *Intern; WSO2, Inc.; http://wso2.com
*
Mobile : +94 (0) 779171059 <%2B94%20%280%29%20778%20800570>
Email  : neth...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 09-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/09-12-2015/wso2appm-1.1.0-SNAPSHOT-09-12-2015.zip

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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Vidura Gamini Abhaya]

I've found DBReport / DBLookup to be quite useful for simple DB operations
as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
ability to only being able to return a single row of data, DB Report
mediator is still quite useful in writing to a database, especially when we
use a DB as part of the mediation sequences.

I also feel it is worth continuing with POJOCommand, as it is the most
simplest way of executing some custom code as part of a sequence. Although
it is possible to do the same with a Class mediator, one doesn't have to
worry about adding the proper jars, working with MessageContext etc. with
the POJOCommand. I think we should retain it for the sake of simplicity of
use.

I'm +1 to deprecate the rest of the mediators.

Thanks,

Vidura



On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:

> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always recommend
> to integrate with databases with the use of DSS (using a separate DSS or
> using DSS features inside ESB)
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> Any comments  on these or any other features that we should deprecate from
> 4.10 release?
>
> Thanks,
> Kasun.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vidura Gamini Abhaya, Ph.D.
Director of Engineering
M:+94 77 034 7754
E: vid...@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] [APIM] Changing default API endpoint using a custom sequence

[Shenavi de Mel]

Hi Nuwan,

I was not aware that we are able to specify the production endpoint in this
parameterized manner. I will go through the docs to understand how to
populate them dynamically This is a customer requirement and we have raised
the concerns mentioned by you to the customer as well in going for this
approach but then he mentions that they need to have the support for a
version specific endpoint with designing a single API with endpoints of
various versions. (User will be specifying the version in the header and
the request should be made accordingly).

Thanks
Shenavi

*Shenavi de Mel*
Software Engineer
WSO2 Inc: http://wso2.com
email: shen...@wso2.com
mobile:+94771244470


On Wed, Dec 9, 2015 at 7:37 PM, Nuwan Dias  wrote:

> Why would you want the send mediator to send the request and not execute
> the rest? That design would introduced problems such as response stats not
> being available, swagger console issues, etc.
>
> It looks like you're trying to achieve the use case of sending the request
> to a dynamic endpoint. If that is the case, you can design your endpoint
> url with parameters at the time of API Publishing.
>
> Ex: http://host:port/{resource_path}/{param}
>
> Then using custom mediation policies (sequences) you could execute your
> logic and populate the values for these parameters accordingly. Read more
> about the "HTTP Endpoint" on the ESB docs to understand how to populate the
> values of those parameters dynamically.
>
> Thanks,
> NuwanD.
>
> On Wed, Dec 9, 2015 at 4:59 PM, Shenavi de Mel  wrote:
>
>> Hi APIM Team,
>>
>> When i was trying to invoke a custom endpoint which dynamically changes
>> with a header value using a send mediator in my custom sequence, i
>> experienced a behavior where the request will go first to the endpoint of
>> my custom sequence after that it will send a request to the endpoint
>> specified when creating the API (Production endpoint) . I am trying to
>> understand the reason for two requests being sent in this scenario? I would
>> be grateful if you could explain to me why this is happening.
>>
>> When API is invoked which uses the custom in sequence following was seen
>> on the wire logs. I have also attached the complete wire logs received to
>> the mail.
>>
>>  DEBUG - wire << "GET
>> /t/backstage/webapps/customerservice-1.1.0/services/customers/customerservice/customerservice/customers/123
>> HTTP/1.1[\r][\n]"
>>
>> DEBUG - wire << "GET
>> /t/backstage/webapps/customerservice-default-SNAPSHOT/services/customers/customerservice/customerservice/customers/123
>> HTTP/1.1[\r][\n]"
>>
>> I have attached my custom sequences as well. Your help will be much
>> appreciated on this matter.
>>
>> Thanks and Regards
>> Shenavi
>>
>>
>>
>>
>
>
> --
> 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