Re: [Dev] WSO2 Committers += Heshitha Hettihewa

2016-09-11 Thread Dilshani Subasinghe 
Congratulations Heshitha !!!

On Mon, Sep 12, 2016 at 11:55 AM, Nandika Jayawardana 
wrote:

> Hi all,
>
> It is my pleasure to welcome Heshitha Hettihewa as a WSO2 Committer.
> Heshitha has been the leading contributor to Business Process Server
> tooling effort and in recognition of his contributions, he has been voted
> as a Committer.
>
> Heshitha, welcome aboard and keep up the good work.
>
> Regards,
> Nandika
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware

Mobile : +94773375185
Blog: dilshanilive.blogspot.com


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

Re: [Dev] WSO2 Committers += Heshitha Hettihewa

2016-09-11 Thread Yashothara Shanmugarajah 
Congrats Hetti :)

Best Regards,
Yashothara.S
Software Engineer
WSO2
http://wso2.com
https://wso2.com/signature


On Mon, Sep 12, 2016 at 11:55 AM, Nandika Jayawardana 
wrote:

> Hi all,
>
> It is my pleasure to welcome Heshitha Hettihewa as a WSO2 Committer.
> Heshitha has been the leading contributor to Business Process Server
> tooling effort and in recognition of his contributions, he has been voted
> as a Committer.
>
> Heshitha, welcome aboard and keep up the good work.
>
> Regards,
> Nandika
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Heshitha Hettihewa

2016-09-11 Thread Nandika Jayawardana 
Hi all,

It is my pleasure to welcome Heshitha Hettihewa as a WSO2 Committer.
Heshitha has been the leading contributor to Business Process Server
tooling effort and in recognition of his contributions, he has been voted
as a Committer.

Heshitha, welcome aboard and keep up the good work.

Regards,
Nandika

-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dependancy issue identity-inbound-auth-saml-cloud 5.2.0-M1 Branch

2016-09-11 Thread Jenananthan Yogendran 
Hi

Build is success.

On Mon, Sep 12, 2016 at 11:45 AM, Godwin Shrimal  wrote:

> Hi Jenananthan,
>
> Changed the framework version dependency issue. Can you check now ?
>
>
> Thanks
> Godwin
>
>
> On Mon, Sep 12, 2016 at 10:59 AM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Hi
>>
>> Getting build issue on 5.2.0-M1 Branch.
>> Seems Idenity frame work version[1] still refer to snapshot
>>
>> INFO] WSO2 Carbon SAML SSO Cloud  SUCCESS [1.597s]
>> [INFO] WSO2 Carbon - SAML Web Browser SSO Cloud .. FAILURE
>> [13.492s]
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 15.823s
>> [INFO] Finished at: Mon Sep 12 10:36:38 IST 2016
>> [INFO] Final Memory: 16M/491M
>> [INFO] 
>> 
>> [ERROR] Failed to execute goal on project 
>> org.wso2.carbon.identity.sso.saml.cloud:
>> Could not resolve dependencies for project org.wso2.carbon.identity:org.w
>> so2.carbon.identity.sso.saml.cloud:bundle:5.1.2-SNAPSHOT: Could not find
>> artifact org.wso2.carbon.identity:org.wso2.carbon.identity.applicatio
>> n.authentication.framework:jar:5.2.1-SNAPSHOT in wso2-nexus (
>> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/conflu
>> ence/display/MAVEN/DependencyResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :org.wso2.carbon.identity.sso.saml.cloud
>>
>> 1.https://github.com/wso2-extensions/identity-inbound-auth-
>> saml-cloud/blob/5.2.0-M1/pom.xml#L253
>> --
>> Jenananthan Yogendran
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
Jenananthan Yogendran
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Opening the JSON interface instead of SOAP to the clients(applications)

2016-09-11 Thread 郑文兴 
Dear gurus,

 

We are ongoing the customizing our application based on the WSO2 Application
Server, appreciated for your advices on how to provide the JSON interface to
the external users(applications) instead of SOAP? Is it easy to make it?

 

Thanks, Wenxing

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

Re: [Dev] Dependancy issue identity-inbound-auth-saml-cloud 5.2.0-M1 Branch

2016-09-11 Thread Godwin Shrimal 
Hi Jenananthan,

Changed the framework version dependency issue. Can you check now ?


Thanks
Godwin


On Mon, Sep 12, 2016 at 10:59 AM, Jenananthan Yogendran <
jenanant...@wso2.com> wrote:

> Hi
>
> Getting build issue on 5.2.0-M1 Branch.
> Seems Idenity frame work version[1] still refer to snapshot
>
> INFO] WSO2 Carbon SAML SSO Cloud  SUCCESS [1.597s]
> [INFO] WSO2 Carbon - SAML Web Browser SSO Cloud .. FAILURE
> [13.492s]
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 15.823s
> [INFO] Finished at: Mon Sep 12 10:36:38 IST 2016
> [INFO] Final Memory: 16M/491M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project 
> org.wso2.carbon.identity.sso.saml.cloud:
> Could not resolve dependencies for project org.wso2.carbon.identity:org.
> wso2.carbon.identity.sso.saml.cloud:bundle:5.1.2-SNAPSHOT: Could not find
> artifact org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.authentication.framework:jar:5.2.1-SNAPSHOT in wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :org.wso2.carbon.identity.sso.saml.cloud
>
> 1.https://github.com/wso2-extensions/identity-inbound-
> auth-saml-cloud/blob/5.2.0-M1/pom.xml#L253
> --
> Jenananthan Yogendran
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
>


-- 
*Godwin Amila Shrimal*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

[Dev] Dependancy issue identity-inbound-auth-saml-cloud 5.2.0-M1 Branch

2016-09-11 Thread Jenananthan Yogendran 
Hi

Getting build issue on 5.2.0-M1 Branch.
Seems Idenity frame work version[1] still refer to snapshot

INFO] WSO2 Carbon SAML SSO Cloud  SUCCESS [1.597s]
[INFO] WSO2 Carbon - SAML Web Browser SSO Cloud .. FAILURE [13.492s]
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 15.823s
[INFO] Finished at: Mon Sep 12 10:36:38 IST 2016
[INFO] Final Memory: 16M/491M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.identity.sso.saml.cloud: Could not resolve dependencies for
project
org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.cloud:bundle:5.1.2-SNAPSHOT:
Could not find artifact
org.wso2.carbon.identity:org.wso2.carbon.identity.application.authentication.framework:jar:5.2.1-SNAPSHOT
in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.carbon.identity.sso.saml.cloud

1.
https://github.com/wso2-extensions/identity-inbound-auth-saml-cloud/blob/5.2.0-M1/pom.xml#L253
-- 
Jenananthan Yogendran
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] Unmatched messages when using message selectors

2016-09-11 Thread Hasitha Hiranya 
Hi Shazni,

This is the expected behavior of MB.
Messages will go to DLC if not matched. Things to note here is

1. MB does not support selectors cluster-wide (if there is a subscriber
with a matching selector on some other node, sorry)
2. We cannot keep the message in the queue because of "slot based message
distribution logic" we have. It complicates the slot story. Thus messages
are moved to DLC.

Is there a possibility for you to use Admin Services to route messages back
to original queue? Even then, if not matched to any subscriber, messages
will get back to DLC.

Thanks

On Sun, Sep 11, 2016 at 9:31 PM, Shazni Nazeer  wrote:

> Hi all,
>
> I created a queue in WSO2 MB and placed a couple of messages with given
> correlation id's using the management console. And I wrote a sample message
> receiver to receive messages from the queue with a selector matching the
> correlation id. I could successfully retrieve the message.
>
> However, I could also see that the messages which didn't match are moved
> to the dead letter channel (DLC) queue. This is o.k in certain
> circumstances.
>
> I also could find the [1] where the new feature requirement is to delete
> the messages. Therefore moving to DLC seems to be the default behavior.
>
> But what if I want to keep the unmatched messages untouched in the queue
> it self for further processing. Is there a configuration to achieve this?
> Or do we have other means to bring back to the original queue. (Of course
> not by using the management console)
>
> [1] https://wso2.org/jira/browse/MB-1597
>
> Shazni Nazeer
> Associate Technical Lead | WSO2
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> 
>



-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] integration with wso2

2016-09-11 Thread Roger Giuffre 
can you provide an economic offer related to the implementation of an
integration solution with killbill including rendering of invoices?

Regards

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

[Dev] [MB] Unmatched messages when using message selectors

2016-09-11 Thread Shazni Nazeer 
Hi all,

I created a queue in WSO2 MB and placed a couple of messages with given
correlation id's using the management console. And I wrote a sample message
receiver to receive messages from the queue with a selector matching the
correlation id. I could successfully retrieve the message.

However, I could also see that the messages which didn't match are moved to
the dead letter channel (DLC) queue. This is o.k in certain circumstances.

I also could find the [1] where the new feature requirement is to delete
the messages. Therefore moving to DLC seems to be the default behavior.

But what if I want to keep the unmatched messages untouched in the queue it
self for further processing. Is there a configuration to achieve this? Or
do we have other means to bring back to the original queue. (Of course not
by using the management console)

[1] https://wso2.org/jira/browse/MB-1597

Shazni Nazeer
Associate Technical Lead | WSO2

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com


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