[Dev] send attachment withservice chaining

[Krishantha Dinesh]

Use case:

   1. I need to call back end API with file as a attachment
   2. Its involve service chaining ( I need to call auth service first and
   get session from that and pass session along with file)
   3. when i call first service from proxy attachment get removed from
   messageContext when i looking it for process. [ because i am sending
   payload for first service call and request data getting deleted]
   4. then i used "callTemplate" from my template. but when i do so i am
   getting response for first call and i can see request body on tcpmon. but
   for second call i cant see anything on tcpmon and also backend not
   recognize the request

template code:

http://ws.apache.org/ns/synapse";>








http://localhost:/soap.php"; />



http://localhost:/soap.php";
/>









http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:sug="http://www.sugarcrm.com/sugarcrm";>


http://schemas.xmlsoap.org/soap/encoding/";>
1671qvfrrqfc62j6kss1kdn30

$1
$2



























WORKING SCENARIO (without call template)
+
note: this result not acceptable as session is hard coded
this is the generated SOAP (got from tcp trace)


http://schemas.xmlsoap.org/soap/envelope/";
 xmlns:xsd="http://www.w3.org/2001/XMLSchema";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xmlns:sug="http://www.sugarcrm.com/sugarcrm";>
 
 http://schemas.xmlsoap.org/soap/encoding/";>
 http://ws.apache.org/ns/synapse";
xsi:type="xsd:string">1671qvfrrqfc62j6kss1kdn30
 http://ws.apache.org/ns/synapse";
xsi:type="sug:note_attachment">
 
 
 
 
 
 


NOT WORKING (with call
template)==
this is the generated SOAP (got from tcp trace)
still sessionID hard coded. pls ignore it


http://schemas.xmlsoap.org/soap/envelope/";
 xmlns:xsd="http://www.w3.org/2001/XMLSchema";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xmlns:sug="http://www.sugarcrm.com/sugarcrm";>
 
 http://schemas.xmlsoap.org/soap/encoding/";>
 http://ws.apache.org/ns/synapse";
xsi:type="xsd:string">1671qvfrrqfc62j6kss1kdn30
 http://ws.apache.org/ns/synapse";
xsi:type="sug:note_attachment">
 
 
 
 
 
 


Problem:

*how i can achieve my requirement?*

*how to skeep attachment without deleting when call for service 1 *

*OR*
*how i can fix this code to work with call template*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Moving entitlement and oauth mediators to ESB in Git

[Vanjikumaran Sivajothy]

Hi Eranda,
Currently I am working on that,
Thank you
BR
vanji


On Tue, Feb 18, 2014 at 10:46 AM, Eranda Sooriyabandara wrote:

> Hi Vanji,
> Please add the related features to the project too.
>
> thanks
> Eranda
>
>
> On Tue, Feb 18, 2014 at 10:36 AM, Vanjikumaran Sivajothy 
> wrote:
>
>> +1 Will do the needful
>>
>>
>> On Tue, Feb 18, 2014 at 10:34 AM, Kasun Indrasiri  wrote:
>>
>>> Vanji can you incorporate these changes in to carbon-mediation.
>>>
>>>
>>> On Mon, Feb 17, 2014 at 2:27 PM, Sagara Gunathunga wrote:
>>>



 On Mon, Feb 17, 2014 at 2:12 PM, Chamath Gunawardana >>> > wrote:

> Hi,
>
> Shall we move below components into ESB in Git since these are
> required for ESB release only?
>
> org.wso2.carbon.identity.entitlement.mediator
> org.wso2.carbon.identity.oauth.mediator
>
> WDYT?
>

 I guess this should be fine but ESB team will confirm.



>
> Also is there any dependency on 
> org.wso2.carbon.identity.entitlement.filter.
> AFAIK its a dependency in AS only. Please confirm.
>

 +1

 Thanks !

>
>
> --
> Thanks,
> Best Regards,
> Chamath Gunawardana
> Technical Lead; WSO2 Inc.
> Mobile : +94776322240
>



 --
 Sagara Gunathunga

 Senior Technical Lead; WSO2, Inc.;  http://wso2.com
 V.P Apache Web Services;http://ws.apache.org/
 Linkedin; http://www.linkedin.com/in/ssagara
 Blog ;  http://ssagara.blogspot.com


>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com *
>> *Mobile:(+94)777219209*
>> *Mobile USA:**(+1)918 813 2403*
>> [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
>>
>
>
>
> --
>
> *Eranda Sooriyabandara*Senior Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> E-mail: eranda AT wso2.com
> Mobile: +94 716 472 816
> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
> Blog: http://emsooriyabandara.blogspot.com/
>
>
>
>
>


-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[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] Moving entitlement and oauth mediators to ESB in Git

[Eranda Sooriyabandara]

Hi Vanji,
Please add the related features to the project too.

thanks
Eranda


On Tue, Feb 18, 2014 at 10:36 AM, Vanjikumaran Sivajothy wrote:

> +1 Will do the needful
>
>
> On Tue, Feb 18, 2014 at 10:34 AM, Kasun Indrasiri  wrote:
>
>> Vanji can you incorporate these changes in to carbon-mediation.
>>
>>
>> On Mon, Feb 17, 2014 at 2:27 PM, Sagara Gunathunga wrote:
>>
>>>
>>>
>>>
>>> On Mon, Feb 17, 2014 at 2:12 PM, Chamath Gunawardana 
>>> wrote:
>>>
 Hi,

 Shall we move below components into ESB in Git since these are required
 for ESB release only?

 org.wso2.carbon.identity.entitlement.mediator
 org.wso2.carbon.identity.oauth.mediator

 WDYT?

>>>
>>> I guess this should be fine but ESB team will confirm.
>>>
>>>
>>>

 Also is there any dependency on 
 org.wso2.carbon.identity.entitlement.filter.
 AFAIK its a dependency in AS only. Please confirm.

>>>
>>> +1
>>>
>>> Thanks !
>>>


 --
 Thanks,
 Best Regards,
 Chamath Gunawardana
 Technical Lead; WSO2 Inc.
 Mobile : +94776322240

>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>> V.P Apache Web Services;http://ws.apache.org/
>>> Linkedin; http://www.linkedin.com/in/ssagara
>>> Blog ;  http://ssagara.blogspot.com
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> *Mobile USA:**(+1)918 813 2403*
> [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
>



-- 

*Eranda Sooriyabandara*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Merge kernel patch fixes with Git repo

[Manoj Kumara]

Hi,

Since we are now maintaining Carbon 4.x kernel on Git what will be the best
way to do the $Subject for . Should we merge the changes at the time of the
patch get released as a step of the release process. Otherwise there can be
more pull requests if we merge with Git for every kernel fix.

WDYT ?


[1] https://github.com/wso2/carbon4-kernel


*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Moving entitlement and oauth mediators to ESB in Git

[Vanjikumaran Sivajothy]

+1 Will do the needful


On Tue, Feb 18, 2014 at 10:34 AM, Kasun Indrasiri  wrote:

> Vanji can you incorporate these changes in to carbon-mediation.
>
>
> On Mon, Feb 17, 2014 at 2:27 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>> On Mon, Feb 17, 2014 at 2:12 PM, Chamath Gunawardana 
>> wrote:
>>
>>> Hi,
>>>
>>> Shall we move below components into ESB in Git since these are required
>>> for ESB release only?
>>>
>>> org.wso2.carbon.identity.entitlement.mediator
>>> org.wso2.carbon.identity.oauth.mediator
>>>
>>> WDYT?
>>>
>>
>> I guess this should be fine but ESB team will confirm.
>>
>>
>>
>>>
>>> Also is there any dependency on org.wso2.carbon.identity.entitlement.filter.
>>> AFAIK its a dependency in AS only. Please confirm.
>>>
>>
>> +1
>>
>> Thanks !
>>
>>>
>>>
>>> --
>>> Thanks,
>>> Best Regards,
>>> Chamath Gunawardana
>>> Technical Lead; WSO2 Inc.
>>> Mobile : +94776322240
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[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] Moving entitlement and oauth mediators to ESB in Git

[Kasun Indrasiri]

Vanji can you incorporate these changes in to carbon-mediation.


On Mon, Feb 17, 2014 at 2:27 PM, Sagara Gunathunga  wrote:

>
>
>
> On Mon, Feb 17, 2014 at 2:12 PM, Chamath Gunawardana wrote:
>
>> Hi,
>>
>> Shall we move below components into ESB in Git since these are required
>> for ESB release only?
>>
>> org.wso2.carbon.identity.entitlement.mediator
>> org.wso2.carbon.identity.oauth.mediator
>>
>> WDYT?
>>
>
> I guess this should be fine but ESB team will confirm.
>
>
>
>>
>> Also is there any dependency on org.wso2.carbon.identity.entitlement.filter.
>> AFAIK its a dependency in AS only. Please confirm.
>>
>
> +1
>
> Thanks !
>
>>
>>
>> --
>> Thanks,
>> Best Regards,
>> Chamath Gunawardana
>> Technical Lead; WSO2 Inc.
>> Mobile : +94776322240
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


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

Re: [Dev] Please apply the changes to kernel patch0006

[Eranda Sooriyabandara]

Hi Manoj,
Please add it to the git [1] too.

thanks
Eranda

[1]. https://github.com/wso2/carbon4-kernel


On Tue, Feb 18, 2014 at 9:58 AM, Manoj Kumara  wrote:

> Hi,
>
> Applied to patch0006 with 196934.
>
> Thanks,
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
>
> On Tue, Feb 18, 2014 at 9:16 AM, Chanika Geeganage wrote:
>
>> Hi,
>>
>> axis2.xml is patched to enable httpContentNegotiation parameter by
>> default as per the discussion went on thread "Do we have a JSON sample that
>> ships with DSS?" and the JIRAs raised at [1] and [2]
>>
>> [1] https://wso2.org/jira/browse/CARBON-14567
>> [2] https://wso2.org/jira/browse/DS-851
>>
>> Please review the attached patch and commit it to the patch0006
>>
>> Thanks
>>
>> --
>> Best Regards..
>>
>> Chanika Geeganage
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Eranda Sooriyabandara*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to get Tenant domain within handleResponse - synapse handler

[Venura Kahawala]

Hi Miyuru,

As mentioned by you, it is needed to add below property to the
synapse.properties file in order to get this fixed.

synapse.carbon.ext.tenant.info
=org.wso2.carbon.mediation.initializer.handler.CarbonTenantInfoConfigurator

Regards,
Venura


On Mon, Feb 17, 2014 at 5:24 PM, Venura Kahawala  wrote:

> Hi,
>
> I'm trying to get the tenant domain within a handleResponse method of a
> synapse handler. But it returns null. But if I get the tenant domain within
> handleRequest method, it returns the proper value.
> I'm using synapse 2.1.2.wso2v3.
>
> What might be the issue here?
>
> Regards,
> Venura
>
> --
> Senior Software Engineer
>
> Mobile: +94 71 82 300 20
>
>


-- 
Senior Software Engineer

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

Re: [Dev] Please apply the changes to kernel patch0006

[Chanika Geeganage]

Thanks Manoj


On Tue, Feb 18, 2014 at 9:58 AM, Manoj Kumara  wrote:

> Hi,
>
> Applied to patch0006 with 196934.
>
> Thanks,
>
>
> *Manoj Kumara*
> Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94713448188
>
>
> On Tue, Feb 18, 2014 at 9:16 AM, Chanika Geeganage wrote:
>
>> Hi,
>>
>> axis2.xml is patched to enable httpContentNegotiation parameter by
>> default as per the discussion went on thread "Do we have a JSON sample that
>> ships with DSS?" and the JIRAs raised at [1] and [2]
>>
>> [1] https://wso2.org/jira/browse/CARBON-14567
>> [2] https://wso2.org/jira/browse/DS-851
>>
>> Please review the attached patch and commit it to the patch0006
>>
>> Thanks
>>
>> --
>> Best Regards..
>>
>> Chanika Geeganage
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>>
>


-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please apply the changes to kernel patch0006

[Manoj Kumara]

Hi,

Applied to patch0006 with 196934.

Thanks,


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


On Tue, Feb 18, 2014 at 9:16 AM, Chanika Geeganage  wrote:

> Hi,
>
> axis2.xml is patched to enable httpContentNegotiation parameter by default
> as per the discussion went on thread "Do we have a JSON sample that ships
> with DSS?" and the JIRAs raised at [1] and [2]
>
> [1] https://wso2.org/jira/browse/CARBON-14567
> [2] https://wso2.org/jira/browse/DS-851
>
> Please review the attached patch and commit it to the patch0006
>
> Thanks
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Jaggery2 status update

[Buddhi Mihara]

Core functionalities of jaggery2 were written in using Java.but we change
that approach and now onwards everything is in JavaScript.(Accessing Java
through JavaScript code).Jaggery2 will expose all the core functionalities
via JavaScript.

Jaggery.js is the startup js file which corresponding to load all core
functionalities in jaggery2.At the nashorn engine startup we load the
script file Jaggery.js and bind all jaggery2 core functions to global
ScriptObject using "Object.bindProperties(this,property)".

you can find source @
https://github.com/sidias/jaggery2/tree/jagger2.1

*Edit*
compileScript and runScript methods were redeveloped to bypass issues
mentioned in previous post.

in compiled script function you can execute as follow

globalVar = 0;

var script = vm.compileScript('myfile.js','globalVar += 1');
for (var i = 0; i < 1000 ; i += 1) {
 vm.runScripts(script);
}
 print(globalVar)

output -1000

-- 
Thanks & Best Regards,

*Buddhi Nipun Mihara*
Software Engineer(intern)
WSO2, Inc.:http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] New way of taking JAVA_HOME in mavericks

[Chan]

Hi guys,
In mavericks we don't have to hardcode the $JAVA_HOME in .profile file. We
can get it using */usr/libexec/java_home. *In our wso2server.sh file we are
using the older method which is -

JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/${JAVA_VERSION}/Home

We can get this by using

JAVA_HOME= */usr/libexec/java_home*


in mavericks. I think we should support this new feature in our
wso2server.sh file cause people are facing difficulties when picking up the
proper java path in Mavericks.

Resources
http://java.dzone.com/articles/java-findingsetting
https://developer.apple.com/library/mac/qa/qa1170/_index.html
https://lists.forgerock.org/pipermail/openam/2013-November/014425.html

-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*

*  ~Website   dulithawijewantha.com *

*  ~Blog blog.dulithawijewantha.com
*
*  ~Twitter @dulitharw *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please apply the changes to kernel patch0006

[Chanika Geeganage]

Hi,

axis2.xml is patched to enable httpContentNegotiation parameter by default
as per the discussion went on thread "Do we have a JSON sample that ships
with DSS?" and the JIRAs raised at [1] and [2]

[1] https://wso2.org/jira/browse/CARBON-14567
[2] https://wso2.org/jira/browse/DS-851

Please review the attached patch and commit it to the patch0006

Thanks

-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com


DS-851
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry as a common stream store

[Anjana Fernando]

@Gokul, please note, for the required changes in BAM.

Cheers,
Anjana.


On Mon, Feb 17, 2014 at 11:32 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Hi All,
>
> BAM & CEP are the main products which are always deals with streams. But
> we had a long-time mismatch where BAM stores streams in Cassandra but CEP
> stores streams in registry.. This confuses the user when using CEP features
> in BAM where user needs to define the streams in two places which is not
> good.. Then we have decided to use registry as the single and only stream
> store which contains  all stream definition information and make necessary
> changes to accommodate above functionality. I have done necessary changes
> and committed those in revision 196888. Based on the changes
> cassandra-streamdefn-store will be removed from BAM and registry stream
> store component going to replace that space. Furthermore i have done some
> other important changes and improvements that you might need to know.
>
> 1) Registry-Streamdefn-Store will be exposed as an OSGI service to easily
> dealt with streams.
> 2) Parameter "Credential" is removed from the API methods which is not
> necessary on defining and removing streams.
> 3) Added streamAddRemove listeners in two levels (databridge-core and
> registry-streamdefn-store) which will notify when a new stream added or
> removed
> 4) Added tenantId and tenantdomain in threadLocalContext when an external
> client application calls the api methods.
>
> @BAM Team - Hope these information might helpful to get an idea about the
> changes.. Please raise your concerns if there are any issues on this..
>
> Thanks & Regards,
> Mohan
>
>
> --
> *V. Mohanadarshan*
> *Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
*Anjana Fernando*
Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Refactoring Carbon-data in Github

[Chanika Geeganage]

It is in progress. I will update the thread

Thanks


On Mon, Feb 17, 2014 at 11:31 PM, Sagara Gunathunga  wrote:

>
>
>
> On Mon, Feb 17, 2014 at 9:49 PM, Geeth Munasinghe  wrote:
>
>> Hi
>> As the proposed project architecture, carbon-data will be a separate
>> project. So we need to properly re-factor the project created on github.
>> Can some one in DSS team attend to this?
>> Github url is available in [1]. Please refer the mail thread [2] for the
>> instructions regarding refactoring.
>>
>> [1] https://github.com/wso2/carbon-data
>>
>> [2] Guidelines to move project into GitHub
>>
>
> I believe  Chanika already on this, Chanika please update the progress
> here.
>
> Thanks !
>
>>
>> Thanks
>> Geeth
>>
>>
>> *G. K. S. Munasinghe*
>> *Software Engineer,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
Best Regards..

Chanika Geeganage
Software Engineer
WSO2, Inc.; http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Applying changes for Kernel

[Pushpalanka Jayawardhana]

On Mon, Feb 17, 2014 at 2:43 PM, Asela Pathberiya  wrote:

>
>
>
> On Mon, Feb 17, 2014 at 1:52 PM, Pushpalanka Jayawardhana 
> wrote:
>
>> Hi Sameera,
>>
>> I am not sure why they are declared final. Just looking it the code it
>> seems for 'updateUserListOfRole' method, it has been avoiding overriding
>> the method such that, admin user can be removed from admin role.
>>
>> Use case is related with Appfactory, OT user store, where we needs to
>> keep some virtual roles for user.
>>
>
> AFAIK,  Most of the methods in the "UserStoreManager"  have been declared
> as  "final" inside the Abstract user store manager.  Because common set of
> functions for  most of the user store implementation, have been done there
> (also multiple user store functions , listeners and so on).   And Abstract
> user store manager introduces new methods (such as "doUpdateUserListOfRole"
> method)  to implement.   But, if you want to modify the functions of
> Abstract user store manager, I guess you can implement the your user store
> implementation directly from "UserStoreManager" interface.
> However if there is an issue or improvement on removing admin user from
> admin role. We may need to fix it.
>

Thanks Asela for the explanation. Will try to look on the possibility of
using the interface.

>
> Thanks,
> Asela.
>
>
>>
>> Thanks,
>>
>> On Tue, Feb 11, 2014 at 2:42 PM, Sameera Jayasoma wrote:
>>
>>> Hi Pushpalanka,
>>>
>>> Do you know why these method declared as final? Can we give it a try to
>>> implement your solution without changing the existing API?
>>>
>>> What is your user-case?
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>> On Tue, Feb 11, 2014 at 11:04 AM, Pushpalanka Jayawardhana <
>>> la...@wso2.com> wrote:
>>>
 Hi,

 We have patched the Kernel as attached(removing final) to have the
 freedom at implementing the OTUserStoreManager to override the two methods,

  updateUserListOfRole
 getUserListOfRole

 This is not yet committed to Kernel, but used as a custom patch. Are we
 ok to go ahead and commit this?

 Thanks,
 --

 Pushpalanka Jayawardhana

 Software Engineer

 WSO2 Lanka (pvt) Ltd
 [image: 
 Facebook]
  [image:
 Twitter]
  [image:
 LinkedIn]
  [image:
 Blogger]
  [image:
 SlideShare]
 Mobile: +94779716248

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


>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://sameera.adahas.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>>
>> Pushpalanka Jayawardhana
>>
>> Software Engineer
>>
>> WSO2 Lanka (pvt) Ltd
>> [image: 
>> Facebook]
>>  [image:
>> Twitter]
>>  [image:
>> LinkedIn]
>>  [image:
>> Blogger]
>>  [image:
>> SlideShare]
>> Mobile: +94779716248
>>
>
>
>
> --
> Thanks & Regards,
> Asela
>
> ATL
> Mobile : +94 777 625 933
>


Thanks,
-- 

Pushpalanka Jayawardhana

Software Engineer

WSO2 Lanka (pvt) Ltd
[image: 
Facebook]
[image:
Twitter]
[image:
LinkedIn]
[image:
Blogger]
[image:
SlideShare]
Mobile: +94779716248
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Refactoring Carbon-data in Github

[Sagara Gunathunga]

On Mon, Feb 17, 2014 at 9:49 PM, Geeth Munasinghe  wrote:

> Hi
> As the proposed project architecture, carbon-data will be a separate
> project. So we need to properly re-factor the project created on github.
> Can some one in DSS team attend to this?
> Github url is available in [1]. Please refer the mail thread [2] for the
> instructions regarding refactoring.
>
> [1] https://github.com/wso2/carbon-data
>
> [2] Guidelines to move project into GitHub
>

I believe  Chanika already on this, Chanika please update the progress
here.

Thanks !

>
> Thanks
> Geeth
>
>
> *G. K. S. Munasinghe*
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Registry as a common stream store

[Mohanadarshan Vivekanandalingam]

Hi All,

BAM & CEP are the main products which are always deals with streams. But we
had a long-time mismatch where BAM stores streams in Cassandra but CEP
stores streams in registry.. This confuses the user when using CEP features
in BAM where user needs to define the streams in two places which is not
good.. Then we have decided to use registry as the single and only stream
store which contains  all stream definition information and make necessary
changes to accommodate above functionality. I have done necessary changes
and committed those in revision 196888. Based on the changes
cassandra-streamdefn-store will be removed from BAM and registry stream
store component going to replace that space. Furthermore i have done some
other important changes and improvements that you might need to know.

1) Registry-Streamdefn-Store will be exposed as an OSGI service to easily
dealt with streams.
2) Parameter "Credential" is removed from the API methods which is not
necessary on defining and removing streams.
3) Added streamAddRemove listeners in two levels (databridge-core and
registry-streamdefn-store) which will notify when a new stream added or
removed
4) Added tenantId and tenantdomain in threadLocalContext when an external
client application calls the api methods.

@BAM Team - Hope these information might helpful to get an idea about the
changes.. Please raise your concerns if there are any issues on this..

Thanks & Regards,
Mohan


-- 
*V. Mohanadarshan*
*Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

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

Re: [Dev] Combining WSO2 ESB with WSO2 AS

[Jorge Infante Osorio]

Hi all.

 

I also see that the service publisher to BAM is missing:

 



 

Jorge.

 

De: dev-boun...@wso2.org [mailto:dev-boun...@wso2.org] En nombre de Dimuthu
Upeksha
Enviado el: domingo, 16 de febrero de 2014 13:45
Para: Udara Liyanage
CC: WSO2 Developers' List
Asunto: Re: [Dev] Combining WSO2 ESB with WSO2 AS

 

Hi,

As Mohan mentioned there is a problem with installing SSO in AS 5.2.1 with
ESB 4.8.1 here is the message

 

Your original install request has been modified.
org.wso2.carbon.logging.mgt.feature.group-4.2.1 is already installed, so an
update will be performed instead.
org.wso2.carbon.registry.resource.properties.feature.group-4.2.0 is already
installed, so an update will be performed instead.
org.wso2.carbon.ndatasource.ui.feature.group-4.2.0 is already installed, so
an update will be performed instead.
org.wso2.carbon.ndatasource.feature.group-4.2.0 is already installed, so an
update will be performed instead. Cannot complete the install because of a
conflicting dependency. Software being installed: SAML2 based Single Sign-On
authenticator Feature 4.2.2
(org.wso2.carbon.identity.authenticator.saml2.sso.feature.group 4.2.2)
Software currently installed: SAML2 based authenticator UI Feature 4.2.1
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.1)
Only one of the following can be installed at once: SAML2 based
authenticator UI Feature 4.2.2
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.2)
SAML2 based authenticator UI Feature 4.2.1
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.1)
SAML2 based authenticator UI Feature 4.2.0
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar 4.2.0)
Cannot satisfy dependency: From: SAML2 based Single Sign-On authenticator
Feature 4.2.2
(org.wso2.carbon.identity.authenticator.saml2.sso.feature.group 4.2.2) To:
org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group [4.2.2]
Cannot satisfy dependency: From: SAML2 based authenticator UI Feature 4.2.1
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.1)
To: org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar [4.2.1]
Cannot satisfy dependency: From: SAML2 based authenticator UI Feature 4.2.2
(org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.2.2)
To: org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.jar [4.2.2]

 

Other than that. It works fine.

 

Thanks

Dimuthu

 

On Sun, Feb 16, 2014 at 3:45 PM, Udara Liyanage  wrote:

Hi,

[1] is a article that describe how to install features. However since you
try to install I think you already know it.You can find the appropriate p2
repo from the release matrix [1]. 
However as Mohan mentioned sometimes I have faced issues after installing
features. Try and report the issues you face.

[1] http://wso2.com/products/carbon/release-matrix/
[2] http://docs.wso2.org/display/Carbon401/Installing+Features

Touched, not typed. Erroneous words are a feature, not a typo.





 

-- 

Dimuthu Upeksha

Engineering Intern

WSO2 inc.



III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 
2014. Ver www.uci.cu<>___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Status update on improving automated tests for API manager

[Madhuka Udantha]

Hi,

In AM we have considerable js and jaggery coding and all above test can
cover HostObject (java) and jaggery REST api only. So I think having js or
jaggery code test (unit level test and integration level) will improve
$subject.



On Mon, Feb 17, 2014 at 5:42 PM, Sanjeewa Malalgoda wrote:

> Hi All,
> Here is the latest update on test automation of API manager integration
> tests. Last week i was mainly focused on  API store and publisher
> operations(operations exposed to out side by hostobject classes). For that
> we need to add sample jaggery application and invoke all possible
> operations for API store and publisher host objects. Then we can get single
> response for all operations available and fetch the results according to
> method order. After that we need to validate response against method. With
> these tests line coverage reached* 55%* and method and class coverage
> reached to *70%* and *73%*. I will add some more tests to cover other
> remaining edge cases.  Still there are some issues and we need to address
> them as well.
>
> 01. Integrating with BAM and BPS to cover stats and workflow scenarios(we
> have considerable amount of code to cover usage metering related stuff).
> 02. Need to add some more negative test cases to cover exception classes
> and exception code blocks.
> 03. Need to add test case to cover external API store scenario.
>
> WDYT?
>
> Thanks,
> sanjeewa.
>
>
> On Mon, Jan 27, 2014 at 8:48 PM, Sanjeewa Malalgoda wrote:
>
>> Hi All,
>> After adding tests to cover comment, rating, token generation and host
>> object functionalities i was able to reach 37% line coverage and 52% method
>> coverage. At this point we have covered most of the common API management
>> related use cases. Now we need to pay attention to workflow integration,
>> usage publishing,  token partition and some other edge cases. Also we might
>> need to add test cases to cover negative test cases to cover exception
>> classes as well. I found that auto generated thrift code is having large
>> number of lines and some of them never get executed. Shall we filter out
>> them? Any suggestions or ideas?
>>
>> OVERALL COVERAGE SUMMARY name line, %block, % method, % class, %
>> all classes 37%  (5976.3/16191) 35%  (24800/70841)52%  (969/1847)
>> 67%  (130/194)OVERALL STATS SUMMARY total packages: 33
>> total executable files: 154 total classes:194 total methods:1847total 
>> executable lines:
>> 16191
>>
>>
>> Thanks,
>> Sanjeewa.
>>
>>
>> On Tue, Jan 21, 2014 at 4:53 PM, Sanjeewa Malalgoda wrote:
>>
>>> Hi All,
>>> Here is a brief update about API Manager integration test improvement.
>>> Before adding test cases code coverage was about 2% (default test set).
>>> Once we added nuwanW implemented you tube sample it was about 12%. After
>>> that we added  4 existing JMeter scripts it was about 24% (and i need to
>>> fix some remaining issues in other 2 scripts). So at this moment code
>>> coverage is about 24%. As we do not have usage related tests i removed
>>> usage packages from instrumentation file. We might need to add tests to
>>> cover API Manager and BAM integration to cover usage related code. Here are
>>> some of the areas we might need to focus on (based on emma report).
>>>
>>>
>>>- Tests to cover Key management web service API as we use thrift by
>>>default.
>>>- Also found that exception classes are playing major role as we do
>>>not test exceptions in our tests. For this we can skip exception classes 
>>> of
>>>add tests to cover exceptions.
>>>- We need to implement throttling scenario tests  to cover
>>>throttling code base.
>>>- For the moment we can safely ignore uri-template scenarios as we
>>>have comprehensive unit tests for that. But we might need tests for url
>>>mapping.
>>>- We need to cover JWT generation and signing scenario (include
>>>claims retrieving) as we have significant amount of code written for 
>>> that.
>>>- We need to add tests to cover tenant scenarios.
>>>- We might need to add token parser test cases.
>>>- Also we should add some test cases to cover all operations exposed
>>>by host object classes(we can achieve this through more scenarios).
>>>- Some tests to cover workflow scenarios(user creation, application
>>>creation and subscription).
>>>- Application level throttling tests and we found that significant
>>>amount of throttling code will not execute.
>>>- Add some test to cover comments, rating related operations.
>>>
>>>
>>> Please let know your ideas and feedback. We have planned to add test
>>> cases to cover missed areas.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>  blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> 

[Dev] Regrouping the CEP components

[Mohanadarshan Vivekanandalingam]

Hi All,

Hope you all already know that we have done a major CEP release (version
3.0.0) which is a complete rewrite of WSO2 CEP. It was built based on a
completely new architecture.. After the CEP 3.0.0 release, we have done
major UI improvements as well as many functionality improvements in various
features.. You can see the architecture mail subjected with "CEP UI
re-factoring and adding much more functionality" for more information about
the UI re-factoring. Initially all the CEP specific  components
(event-processing components) grouped under the high level event-processing
component in the code base, but we have decided to move these components in
to three major groups since no of high level components increased and to
give better understanding about the functionality of the components.

Below is the information on how CEP components are grouped,

Event-Processor : Moved as an high level component.
(platform/components/event-processor)
Event-Stream : Contains event-stream-manager, event-formatter,
event-builder, event-input-adaptor, event-output-adaptor & event-dashboard
(platform/components/event-stream)
Event-Monitor : Contains event-tracer & event-statistics.
(platform/components/event-monitor)

Furthermore, all the active development will be happen on these components
targeting next CEP release 3.1.0..

@BAM Team : Please refer above locations for CEP related components.


Thanks & Regards,
Mohan

-- 
*V. Mohanadarshan*
*Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

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

[Dev] Refactoring Carbon-data in Github

[Geeth Munasinghe]

Hi
As the proposed project architecture, carbon-data will be a separate
project. So we need to properly re-factor the project created on github.
Can some one in DSS team attend to this?
Github url is available in [1]. Please refer the mail thread [2] for the
instructions regarding refactoring.

[1] https://github.com/wso2/carbon-data

[2] Guidelines to move project into GitHub

Thanks
Geeth


*G. K. S. Munasinghe*
*Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

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

Re: [Dev] WSO2 BAM 2.4.1-M1

[Dunith Dhanushka]

Hi Thayalan,

This happens since the default admin user has not been granted all
privileges for Cassandra datastore. We are currently looking into this
issue.

This can be temporary fixed by granting all privilleges to admin user in
the management console. Navigate to Home > Manage > Cassandra Keyspaces >
List > Keyspaces. Tick all checkboxes for admin role under "Permissions for
All Keyspaces" section.

Regards,
Dunith


On Mon, Feb 17, 2014 at 12:13 PM, Thayalan  wrote:

> Hi,
>
> I have downloaded the pack and started in Windows 7 environment in
> standalone mode and getting the below exception on server startup
>
> *[2014-02-17 17:28:51,252]  INFO
> {org.wso2.carbon.databridge.core.DataBridge} -  admin connected*
> *[2014-02-17 17:28:51,345] ERROR
> {org.wso2.carbon.bam.notification.task.NotificationDispatchTask} -  Error
> executing notification dispatch task: InvalidRequestException(why:User
> admin has no SELECT permission on  BAM_UTIL_KS.bam_notification_messages> or any of its parents)*
> *me.prettyprint.hector.api.exceptions.HInvalidRequestException:
> InvalidRequestException(why:User admin has no SELECT permission on  BAM_UTIL_KS.bam_notification_messages> or any of its parents)*
> *at
> me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:52)*
> *at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl$3.execute(KeyspaceServiceImpl.java:164)*
> *at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl$3.execute(KeyspaceServiceImpl.java:146)*
> *at
> me.prettyprint.cassandra.service.Operation.executeAndSetResult(Operation.java:104)*
> *at
> me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:253)*
> *at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl.operateWithFailover(KeyspaceServiceImpl.java:132)*
> *at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl.getRangeSlices(KeyspaceServiceImpl.java:168)*
> *at
> me.prettyprint.cassandra.model.thrift.ThriftRangeSlicesQuery$1.doInKeyspace(ThriftRangeSlicesQuery.java:80)*
> *at
> me.prettyprint.cassandra.model.thrift.ThriftRangeSlicesQuery$1.doInKeyspace(ThriftRangeSlicesQuery.java:76)*
> *at
> me.prettyprint.cassandra.model.KeyspaceOperationCallback.doInKeyspaceAndMeasure(KeyspaceOperationCallback.java:20)*
> *at
> me.prettyprint.cassandra.model.ExecutingKeyspace.doExecute(ExecutingKeyspace.java:101)*
> *at
> me.prettyprint.cassandra.model.thrift.ThriftRangeSlicesQuery.execute(ThriftRangeSlicesQuery.java:75)*
> *at
> org.wso2.carbon.bam.notification.task.NotificationDispatchTask.processNotificationRecords(NotificationDispatchTask.java:226)*
> *at
> org.wso2.carbon.bam.notification.task.NotificationDispatchTask.execute(NotificationDispatchTask.java:214)*
> *at
> org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)*
> *at org.quartz.core.JobRunShell.run(JobRunShell.java:213)*
> *at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)*
> *at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)*
> *at java.util.concurrent.FutureTask.run(FutureTask.java:138)*
> *at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)*
> *at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)*
> *at java.lang.Thread.run(Thread.java:662)*
> *Caused by: InvalidRequestException(why:User admin has no SELECT
> permission on  or any of its
> parents)*
> *at
> org.apache.cassandra.thrift.Cassandra$get_range_slices_result.read(Cassandra.java:12916)*
> *at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)*
> *at
> org.apache.cassandra.thrift.Cassandra$Client.recv_get_range_slices(Cassandra.java:734)*
> *at
> org.apache.cassandra.thrift.Cassandra$Client.get_range_slices(Cassandra.java:718)*
> *at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl$3.execute(KeyspaceServiceImpl.java:152)*
>
>
>  Environment Details:
> OS:
> Windows 7 SP1
>
> JAVA
> java version "1.6.0_43"
> Java(TM) SE Runtime Environment (build 1.6.0_43-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
>
> Cygwin
> CYGWIN_NT-6.1 LT-THAYA 1.7.25(0.270/5/3) 2013-08-31 20:37 x86_64 Cygwin
>
> Please advice.
>
>
> On Thu, Feb 13, 2014 at 7:06 PM, Evanthika Amarasiri 
> wrote:
>
>> Hi Dunith,
>>
>> Thaya, Pandula & ChamaraA will start a QA cycle from Monday.
>>
>> Evanthika
>>
>>
>> On Thu, Feb 13, 2014 at 5:39 PM, Dunith Dhanushka wrote:
>>
>>> Hi all,
>>>
>>> BAM 2.4.1-Milestone1 distribution is available at
>>> https://svn.wso2.org/repos/wso2/people/dunith/2.4.1-m1/wso2bam-2.4.1.zip
>>>
>>> Following are the bug fixes, improvements and the new features available
>>> with this release.
>>>
>>> *Bug*
>>>
>>>- [BAM-1408 

Re: [Dev] [APIM] Status update on improving automated tests for API manager

[Sanjeewa Malalgoda]

Hi All,
Here is the latest update on test automation of API manager integration
tests. Last week i was mainly focused on  API store and publisher
operations(operations exposed to out side by hostobject classes). For that
we need to add sample jaggery application and invoke all possible
operations for API store and publisher host objects. Then we can get single
response for all operations available and fetch the results according to
method order. After that we need to validate response against method. With
these tests line coverage reached* 55%* and method and class coverage
reached to *70%* and *73%*. I will add some more tests to cover other
remaining edge cases.  Still there are some issues and we need to address
them as well.

01. Integrating with BAM and BPS to cover stats and workflow scenarios(we
have considerable amount of code to cover usage metering related stuff).
02. Need to add some more negative test cases to cover exception classes
and exception code blocks.
03. Need to add test case to cover external API store scenario.

WDYT?

Thanks,
sanjeewa.


On Mon, Jan 27, 2014 at 8:48 PM, Sanjeewa Malalgoda wrote:

> Hi All,
> After adding tests to cover comment, rating, token generation and host
> object functionalities i was able to reach 37% line coverage and 52% method
> coverage. At this point we have covered most of the common API management
> related use cases. Now we need to pay attention to workflow integration,
> usage publishing,  token partition and some other edge cases. Also we might
> need to add test cases to cover negative test cases to cover exception
> classes as well. I found that auto generated thrift code is having large
> number of lines and some of them never get executed. Shall we filter out
> them? Any suggestions or ideas?
>
> OVERALL COVERAGE SUMMARY name line, %block, % method, % class, %
> all classes 37%  (5976.3/16191) 35%  (24800/70841)52%  (969/1847)
> 67%  (130/194)OVERALL STATS SUMMARY total packages: 33
> total executable files: 154 total classes:194 total methods:1847total 
> executable lines:
> 16191
>
>
> Thanks,
> Sanjeewa.
>
>
> On Tue, Jan 21, 2014 at 4:53 PM, Sanjeewa Malalgoda wrote:
>
>> Hi All,
>> Here is a brief update about API Manager integration test improvement.
>> Before adding test cases code coverage was about 2% (default test set).
>> Once we added nuwanW implemented you tube sample it was about 12%. After
>> that we added  4 existing JMeter scripts it was about 24% (and i need to
>> fix some remaining issues in other 2 scripts). So at this moment code
>> coverage is about 24%. As we do not have usage related tests i removed
>> usage packages from instrumentation file. We might need to add tests to
>> cover API Manager and BAM integration to cover usage related code. Here are
>> some of the areas we might need to focus on (based on emma report).
>>
>>
>>- Tests to cover Key management web service API as we use thrift by
>>default.
>>- Also found that exception classes are playing major role as we do
>>not test exceptions in our tests. For this we can skip exception classes 
>> of
>>add tests to cover exceptions.
>>- We need to implement throttling scenario tests  to cover throttling
>>code base.
>>- For the moment we can safely ignore uri-template scenarios as we
>>have comprehensive unit tests for that. But we might need tests for url
>>mapping.
>>- We need to cover JWT generation and signing scenario (include
>>claims retrieving) as we have significant amount of code written for that.
>>- We need to add tests to cover tenant scenarios.
>>- We might need to add token parser test cases.
>>- Also we should add some test cases to cover all operations exposed
>>by host object classes(we can achieve this through more scenarios).
>>- Some tests to cover workflow scenarios(user creation, application
>>creation and subscription).
>>- Application level throttling tests and we found that significant
>>amount of throttling code will not execute.
>>- Add some test to cover comments, rating related operations.
>>
>>
>> Please let know your ideas and feedback. We have planned to add test
>> cases to cover missed areas.
>>
>> Thanks,
>> sanjeewa.
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>


-- 

*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

 blog
:http://sanjeewamalalgoda.blogspot.com/
___
Dev

[Dev] [DEV] How to get Tenant domain within handleResponse - synapse handler

[Venura Kahawala]

Hi,

I'm trying to get the tenant domain within a handleResponse method of a
synapse handler. But it returns null. But if I get the tenant domain within
handleRequest method, it returns the proper value.
I'm using synapse 2.1.2.wso2v3.

What might be the issue here?

Regards,
Venura

-- 
Senior Software Engineer

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

[Dev] [C5] Test coverage for clustering module

[Kishanthan Thangarajah]

I'm starting to work on $subject. We will focus on these areas.

1. Basic clustering tests (start and shutdown a node, cluster configuration
initializing/populating related tests).
2. Membership schemes (multicast, wka) related tests.
3. Member leaving and joining the cluster related tests.
4. Membership listeners (event notification) related tests.
5. Cluster message sending and receiving related tests.

Thanks,
Kishanthan.
-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

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

Re: [Dev] WSO2 UES - How to forward request parameters to micro-sites (gadgets)

[Ruchira Wageesha]

Try registering an onload event for gadget iframes using jQuery.

/Ruchira


On Mon, Feb 17, 2014 at 3:43 PM, Kavith Lokuhewage  wrote:

> Hi,
>
> I was able to pass request parameters to gadgets with the help of pub/sub
> method. But, as Ruchira has mentioned, the model itself doesn't wait till
> all the i-frames are loaded.
>
> I tried publishing messages after the window load event of dashboard page.
> but I could notice that few gadgets sometimes even fails to receive those
> messages. Right now, I am executing the publisher 100 milliseconds after
> window load event and all the gadgets are now able to fetch the messages.
>
> But, this will largely depend on the client and will badly affect the
> usability. Is there a better way to overcome this issue?
>
> Thanks.
>
>
> On Mon, Feb 17, 2014 at 10:52 AM, Kavith Lokuhewage wrote:
>
>> Hi Tanya and Ruchira,
>>
>> Thanks a lot for your guidance. I am looking into this.
>>
>> Thanks.
>>
>>
>> On Mon, Feb 17, 2014 at 10:47 AM, Tanya Madurapperuma wrote:
>>
>>> Hi Kavith,
>>>
>>> You can refer this post 
>>> [1]regarding
>>>  pub-sub model in UES. But in this post both the publisher and
>>> subscriber are gadgets. AFAIU in your case publisher will not be a gadget
>>> and you will have to publish productID, productVersionId and
>>> productBuildId etc to the channel that the subscriber is listening to.
>>>
>>> [1]
>>> http://tanyamadurapperuma.blogspot.com/2013/12/inter-gadget-communication-with-wso2-ues.html
>>>
>>> Thanks,
>>> Tanya.
>>>
>>>
>>> On Mon, Feb 17, 2014 at 8:26 AM, Ruchira Wageesha wrote:
>>>

 On Mon, Feb 17, 2014 at 12:49 AM, Senaka Fernando wrote:

> Hi Ruchira,
>
> So, you pass the parameters into this page. And then, the javascript
> will use those (perhaps JS written in the header block I suppose) and
> communicate with gadgets?
>
 or should the gadgets delay the loading, wait for the data to be
> available and display the updates after the page is loaded. Which is the
> model that works?
>
 This is how I meant,

- All gadgets in the dashboard will be loaded into their relevant
iframes when the page is being loaded.
- The JavaScript code we write will publish the data to those
gadgets(we might have to wait till iframes are loaded, not sure whether
pubsub librabry itself handle it properly)
- Gadgets will load the data from backends using the data passed
and draw the graphs


> Thanks,
> Senaka.
>
>
> On Sun, Feb 16, 2014 at 8:54 PM, Ruchira Wageesha wrote:
>
>> Hi Kavith,
>>
>> I think, best option would be to use gadget pub-sub model. i.e. You
>> would have include a JavaScript code in your dashboard page, which gets 
>> the
>> project id etc. by parsing the url and publish to gadgets. Then, each
>> gadget will can receive the parameters by listening to the relevant 
>> channel
>> and load the data.
>>
>> /Ruchira
>>
>>
>> On Sun, Feb 16, 2014 at 11:10 AM, Senaka Fernando wrote:
>>
>>> Hi Kavith,
>>>
>>> Particularly, the model should be such where you create a dashboard
>>> that could display stats for any project and you get a specific URL for
>>> each project instructing the dashboard what to load.
>>>
>>> As discussed with Ruchira et al, this should be possible to do. But,
>>> how this has to be done is not something well known AFAIU.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sun, Feb 16, 2014 at 6:20 AM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi,

 I am working on a QA Dashboard on UES [Please refer to the attached
 screen-shot]. A similar dashboard is being built to view reports for 
 git
 commits status, test coverage status and other build status reports.

 These dash boards are linked to a Project Asset Management user
 interface on Enterprise Store. When a user want to see above mentioned
 dashboards for a particular build of a product, he should be able to 
 see it
 by clicking a link on Project Asset management window on ES.

 We need to pass productID, productVersionId and productBuildId as
 request parameters via the link. Is there way to forward these 
 parameters
 to micro sites. Or is there a better approach than this, to overcome 
 this
 problem?


 Thanks.

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

>>>

Re: [Dev] WSO2 UES - How to forward request parameters to micro-sites (gadgets)

[Kavith Lokuhewage]

Hi,

I was able to pass request parameters to gadgets with the help of pub/sub
method. But, as Ruchira has mentioned, the model itself doesn't wait till
all the i-frames are loaded.

I tried publishing messages after the window load event of dashboard page.
but I could notice that few gadgets sometimes even fails to receive those
messages. Right now, I am executing the publisher 100 milliseconds after
window load event and all the gadgets are now able to fetch the messages.

But, this will largely depend on the client and will badly affect the
usability. Is there a better way to overcome this issue?

Thanks.


On Mon, Feb 17, 2014 at 10:52 AM, Kavith Lokuhewage  wrote:

> Hi Tanya and Ruchira,
>
> Thanks a lot for your guidance. I am looking into this.
>
> Thanks.
>
>
> On Mon, Feb 17, 2014 at 10:47 AM, Tanya Madurapperuma wrote:
>
>> Hi Kavith,
>>
>> You can refer this post 
>> [1]regarding
>>  pub-sub model in UES. But in this post both the publisher and
>> subscriber are gadgets. AFAIU in your case publisher will not be a gadget
>> and you will have to publish productID, productVersionId and
>> productBuildId etc to the channel that the subscriber is listening to.
>>
>> [1]
>> http://tanyamadurapperuma.blogspot.com/2013/12/inter-gadget-communication-with-wso2-ues.html
>>
>> Thanks,
>> Tanya.
>>
>>
>> On Mon, Feb 17, 2014 at 8:26 AM, Ruchira Wageesha wrote:
>>
>>>
>>> On Mon, Feb 17, 2014 at 12:49 AM, Senaka Fernando wrote:
>>>
 Hi Ruchira,

 So, you pass the parameters into this page. And then, the javascript
 will use those (perhaps JS written in the header block I suppose) and
 communicate with gadgets?

>>> or should the gadgets delay the loading, wait for the data to be
 available and display the updates after the page is loaded. Which is the
 model that works?

>>> This is how I meant,
>>>
>>>- All gadgets in the dashboard will be loaded into their relevant
>>>iframes when the page is being loaded.
>>>- The JavaScript code we write will publish the data to those
>>>gadgets(we might have to wait till iframes are loaded, not sure whether
>>>pubsub librabry itself handle it properly)
>>>- Gadgets will load the data from backends using the data passed and
>>>draw the graphs
>>>
>>>
 Thanks,
 Senaka.


 On Sun, Feb 16, 2014 at 8:54 PM, Ruchira Wageesha wrote:

> Hi Kavith,
>
> I think, best option would be to use gadget pub-sub model. i.e. You
> would have include a JavaScript code in your dashboard page, which gets 
> the
> project id etc. by parsing the url and publish to gadgets. Then, each
> gadget will can receive the parameters by listening to the relevant 
> channel
> and load the data.
>
> /Ruchira
>
>
> On Sun, Feb 16, 2014 at 11:10 AM, Senaka Fernando wrote:
>
>> Hi Kavith,
>>
>> Particularly, the model should be such where you create a dashboard
>> that could display stats for any project and you get a specific URL for
>> each project instructing the dashboard what to load.
>>
>> As discussed with Ruchira et al, this should be possible to do. But,
>> how this has to be done is not something well known AFAIU.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Sun, Feb 16, 2014 at 6:20 AM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi,
>>>
>>> I am working on a QA Dashboard on UES [Please refer to the attached
>>> screen-shot]. A similar dashboard is being built to view reports for git
>>> commits status, test coverage status and other build status reports.
>>>
>>> These dash boards are linked to a Project Asset Management user
>>> interface on Enterprise Store. When a user want to see above mentioned
>>> dashboards for a particular build of a product, he should be able to 
>>> see it
>>> by clicking a link on Project Asset management window on ES.
>>>
>>> We need to pass productID, productVersionId and productBuildId as
>>> request parameters via the link. Is there way to forward these 
>>> parameters
>>> to micro sites. Or is there a better approach than this, to overcome 
>>> this
>>> problem?
>>>
>>>
>>> Thanks.
>>>
>>> *Kavith Lokuhewage*
>>> Software Engineer
>>> WSO2 Inc. - http://wso2.com
>>> lean . enterprise . middleware
>>> Mobile - +9477-9-145-123 | +9471-455-6-401
>>> Linkedin 
>>> Twitter 
>>>
>>
>>
>>
>> --
>>
>>
>> *[image: http://wso2.com]  Senaka Fernando*
>> Senior Technical Lead; WSO2 Inc.; http://wso2.com
>>
>>
>>
>> * Member; Apache Software Foundation; http://apache.org
>> E-mail: senaka AT wso2.

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.2.x > Products 4.2.0 chunk-07 > #186 has FAILED (26 times).

[Maheshika Goonetilleke]

Hi Kasun

The build will run once the Bamboo local agent is free.


On Mon, Feb 17, 2014 at 11:14 AM, Kasun Gajasinghe  wrote:

> Thanks Thilini.
>
> @Maheshika, can we trigger a new build with this fix? Bamboo build #187
> that is running now will fail anyway since this fix is not included there.
>
>
>
> On Mon, Feb 17, 2014 at 11:11 AM, Thilini Ishaka  wrote:
>
>> This is fixed- 196862r.
>>
>> Thanks
>> Thilini
>>
>>
>> On Mon, Feb 17, 2014 at 11:02 AM, Kasun Gajasinghe wrote:
>>
>>> Hi,
>>>
>>> Could fix this issue in Bamboo please? This seems to have happened
>>> during a svn update of humantask server feature as per the Bamboo logs. I'm
>>> also seeing the same issue [1] but mine is a warning probably because I'm
>>> using Subversion 1.7. All recent 25 builds have been failing for the same
>>> reason!
>>>
>>> svn: E155007:
>>> '/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB005-PRO0015-JOB1/features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/derby.sql'
>>> is not a working copy directory
>>>
>>> [1]
>>> $ svn up
>>> features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/
>>> Updating
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3':
>>> svn: warning: W20: Error handling externals definition for
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/derby.sql':
>>> svn: warning: W17: URL '
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/features/bpel/org.wso2.carbon.bpel.server.feature/4.2,2/resources/dbscripts/derby.sql'
>>> at revision 196861 doesn't exist
>>>
>>> Fetching external item into
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/h2.sql':
>>> External at revision 196861.
>>>
>>>
>>>  Fetching external item into
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/mysql.sql':
>>> External at revision 196861.
>>>
>>>
>>> Fetching external item into
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/oracle.sql':
>>> External at revision 196861.
>>>
>>>
>>> Fetching external item into
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/postgresql.sql':
>>> External at revision 196861.
>>>
>>>
>>> Fetching external item into
>>> 'features/humantask/org.wso2.carbon.humantask.server.feature/4.2.3/resources/dbscripts/mssql.sql':
>>> External at revision 196861.
>>>
>>> At revision 196861.
>>> svn: E205011: Failure occurred processing one or more externals
>>> definitions
>>>
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>> On Mon, Feb 17, 2014 at 8:43 AM, Bamboo  wrote:
>>>
  [image: Failed]  WSO2 Carbon 
 4.2.x› Products
 4.2.0 chunk-07  › 
 #186 has
 failed *26* times

 Changes by Kasun 
 Gajasinghe

 No failed tests found, a possible compilation error.

 This plan has been failing since 
 #161(Changes by Thilini
 Ishaka , 5 days
 before).
   Responsible  lalaji 
 sureshika Automatically
 assigned Sanjeewa 
 Malalgoda 
 Automatically
 assigned Thilini 
 Ishaka Automatically
 assigned
   Failing Jobs Job
 Duration Tests[image: Failed]  Default 
 Job (Default
 Stage)  Unknown  No tests found  
 Logs|
 Artifacts  
Code
 Changes   View
 full change 
 details  
 Kasun
 Gajasinghe 
 Introduced ConfigurationContextObserver to publish the services
 deployed during tenant load  196857 View 
 Online
 | Add 
 Comments

 This message was sent by Atlassian Bamboo .

 If you wish to stop receiving these emails edit your user 
 profileor notify
 your administrator .

>>>
>>>
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>

Re: [Dev] Request to apply patch CARBON-14677 to kernel patch0006

[Manoj Kumara]

Hi Kasun,

Applied to patch0006 with 196889.

Thanks,
Manoj


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


On Thu, Feb 13, 2014 at 6:05 PM, Kasun Gajasinghe  wrote:

> Hi,
>
> Please do $subject for the patch attached at
> https://wso2.org/jira/browse/CARBON-14677
>
> Thanks,
> KasunG
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Moving entitlement and oauth mediators to ESB in Git

[Sagara Gunathunga]

On Mon, Feb 17, 2014 at 2:12 PM, Chamath Gunawardana wrote:

> Hi,
>
> Shall we move below components into ESB in Git since these are required
> for ESB release only?
>
> org.wso2.carbon.identity.entitlement.mediator
> org.wso2.carbon.identity.oauth.mediator
>
> WDYT?
>

I guess this should be fine but ESB team will confirm.



>
> Also is there any dependency on org.wso2.carbon.identity.entitlement.filter.
> AFAIK its a dependency in AS only. Please confirm.
>

+1

Thanks !

>
>
> --
> Thanks,
> Best Regards,
> Chamath Gunawardana
> Technical Lead; WSO2 Inc.
> Mobile : +94776322240
>



-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Applying changes for Kernel

[Asela Pathberiya]

On Mon, Feb 17, 2014 at 1:52 PM, Pushpalanka Jayawardhana wrote:

> Hi Sameera,
>
> I am not sure why they are declared final. Just looking it the code it
> seems for 'updateUserListOfRole' method, it has been avoiding overriding
> the method such that, admin user can be removed from admin role.
>
> Use case is related with Appfactory, OT user store, where we needs to keep
> some virtual roles for user.
>

AFAIK,  Most of the methods in the "UserStoreManager"  have been declared
as  "final" inside the Abstract user store manager.  Because common set of
functions for  most of the user store implementation, have been done there
(also multiple user store functions , listeners and so on).   And Abstract
user store manager introduces new methods (such as "doUpdateUserListOfRole"
method)  to implement.   But, if you want to modify the functions of
Abstract user store manager, I guess you can implement the your user store
implementation directly from "UserStoreManager" interface.
However if there is an issue or improvement on removing admin user from
admin role. We may need to fix it.

Thanks,
Asela.


>
> Thanks,
>
> On Tue, Feb 11, 2014 at 2:42 PM, Sameera Jayasoma wrote:
>
>> Hi Pushpalanka,
>>
>> Do you know why these method declared as final? Can we give it a try to
>> implement your solution without changing the existing API?
>>
>> What is your user-case?
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Tue, Feb 11, 2014 at 11:04 AM, Pushpalanka Jayawardhana <
>> la...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We have patched the Kernel as attached(removing final) to have the
>>> freedom at implementing the OTUserStoreManager to override the two methods,
>>>
>>>  updateUserListOfRole
>>> getUserListOfRole
>>>
>>> This is not yet committed to Kernel, but used as a custom patch. Are we
>>> ok to go ahead and commit this?
>>>
>>> Thanks,
>>> --
>>>
>>> Pushpalanka Jayawardhana
>>>
>>> Software Engineer
>>>
>>> WSO2 Lanka (pvt) Ltd
>>> [image: 
>>> Facebook]
>>>  [image:
>>> Twitter]
>>>  [image:
>>> LinkedIn]
>>>  [image:
>>> Blogger]
>>>  [image:
>>> SlideShare]
>>> Mobile: +94779716248
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
>
> Pushpalanka Jayawardhana
>
> Software Engineer
>
> WSO2 Lanka (pvt) Ltd
> [image: 
> Facebook]
>  [image:
> Twitter]
>  [image:
> LinkedIn]
>  [image:
> Blogger]
>  [image:
> SlideShare]
> Mobile: +94779716248
>



-- 
Thanks & Regards,
Asela

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

[Dev] [Bamboo-Build] Developer Studio > Eclipse-Tools > #1445 was SUCCESSFUL. Change made by harshan...@gmail.com .

[Bamboo]

---
Developer Studio > Eclipse-Tools > #1445 was successful.
---
Code has been updated by harshan...@gmail.com .

http://wso2.org/bamboo/browse/DS0001-DSET01-1445/




--
Code Changes
--
harshan...@gmail.com  
(1f79e633097be8ae02fdb3eed7ec5c4158f7458e):

>Fixed the Bamboo error.



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Encode Url in ESB

[Jay]

Hi Dushan,

My Endpoint is REST. If we define EP in header it will send as a SOAP
request and LinkedIn didn't accept the request.

I tried with following code also,



  



   

In above case "jsonObject" is appending to endpoint. Then API is reject the
request.

[2014-02-17 12:37:59,094] DEBUG - wire << "GET
/v1/people/jsonObject?accessToken=AQW_v8EhR0VLEkXeIgHYtK2t6bPevlIZJUwli7v
L8tz1SVerzEH5l2i3eXHPPXkPv9ebr5cb_rQvxp36t7xaPQKunY7kwA_NOXRW0z1OXqz63apjElBe3w45XKBsvkzZLnUbQ0M4NZY2gNxuguPhx7Pe7bWz3xY
SssVEm7EfKpg8b6ilmL4&apiUrl=https://api.linkedin.com&publicUrl=http://www.linkedin.com/pub/-XXX/87/998/9


My endpoint URL should be as follows;

/v1/people/url=http%3a%2f%2fwww.linkedin.com%2fpub%2f
X-XXX%2f87%2f998%2f935?oauth2_access_token=AQVEsZcqb4H57C2qOxErr6YiAnHBLXCtsmgszGpW8_hqMNcnuBYjbitzQEP41r
Mc60hPu4ESjbmmd4KacrDzZOMUPEx90_9lkHwXZysUL2jkNqkVkekDgwby9KIXNx8EACwYzj7dzjjLQ-sZxe8sp_0t0n7ZAe2vw2HxuO43QpGhCAaSawA&fo
rmat=json

Thanks,
Janaka
 



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

[Dev] Moving entitlement and oauth mediators to ESB in Git

[Chamath Gunawardana]

Hi,

Shall we move below components into ESB in Git since these are required for
ESB release only?

org.wso2.carbon.identity.entitlement.mediator
org.wso2.carbon.identity.oauth.mediator

WDYT?

Also is there any dependency on org.wso2.carbon.identity.entitlement.filter.
AFAIK its a dependency in AS only. Please confirm.

-- 
Thanks,
Best Regards,
Chamath Gunawardana
Technical Lead; WSO2 Inc.
Mobile : +94776322240
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Applying changes for Kernel

[Pushpalanka Jayawardhana]

Hi Sameera,

I am not sure why they are declared final. Just looking it the code it
seems for 'updateUserListOfRole' method, it has been avoiding overriding
the method such that, admin user can be removed from admin role.

Use case is related with Appfactory, OT user store, where we needs to keep
some virtual roles for user.

Thanks,

On Tue, Feb 11, 2014 at 2:42 PM, Sameera Jayasoma  wrote:

> Hi Pushpalanka,
>
> Do you know why these method declared as final? Can we give it a try to
> implement your solution without changing the existing API?
>
> What is your user-case?
>
> Thanks,
> Sameera.
>
>
> On Tue, Feb 11, 2014 at 11:04 AM, Pushpalanka Jayawardhana  > wrote:
>
>> Hi,
>>
>> We have patched the Kernel as attached(removing final) to have the
>> freedom at implementing the OTUserStoreManager to override the two methods,
>>
>>  updateUserListOfRole
>> getUserListOfRole
>>
>> This is not yet committed to Kernel, but used as a custom patch. Are we
>> ok to go ahead and commit this?
>>
>> Thanks,
>> --
>>
>> Pushpalanka Jayawardhana
>>
>> Software Engineer
>>
>> WSO2 Lanka (pvt) Ltd
>> [image: 
>> Facebook]
>>  [image:
>> Twitter]
>>  [image:
>> LinkedIn]
>>  [image:
>> Blogger]
>>  [image:
>> SlideShare]
>> Mobile: +94779716248
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Jayasoma,
> Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>



-- 

Pushpalanka Jayawardhana

Software Engineer

WSO2 Lanka (pvt) Ltd
[image: 
Facebook]
[image:
Twitter]
[image:
LinkedIn]
[image:
Blogger]
[image:
SlideShare]
Mobile: +94779716248
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev