Re: [Dev] [APIM] REST API - adding a custom sequence and associating with an api

[Chathurika De Silva]

Got it working with the following payload

{
   "name": "TaskDetails",
   "description": "This document describe a RESTFul API for TestAPIfromREST
API.\r\n",
   "context": "tasks",
   "version": "1.0.0",
   "provider":"Administrator",

"apiDefinition":"{\"swagger\":\"2.0\",\"paths\":{\"/task/{id}\":{\"get\":{\"responses\":{\"200\":{\"description\":\"this
is
test\"}},\"parameters\":[{\"name\":\"id\",\"in\":\"path\",\"allowMultiple\":false,\"required\":true,\"type\":\"string\"}],\"x-auth-type\":\"Application
& Application
User\",\"x-throttling-tier\":\"Unlimited\"}}},\"info\":{\"title\":\"TaskDetails\",\"version\":\"1.0.0\"}}",

   "isDefaultVersion": false,
   "type": "HTTP",
   "transport":[
  "http",
  "https"
   ],
   "tiers": ["Unlimited"],
   "visibility": "PUBLIC",
   "endpointConfig": "{\"production_endpoints\":{\"url\":\"
http://localhost:8080//sample-data-backend/rservice/taskservice/\",\"config\":null},\"sandbox_endpoints\":{\"url\":\"/sample-data-backend/rservice/taskservice/\",\"config\":null},\"endpoint_type\":\"http\"};,

   "sequences":[{"name":"custom-in","type": "in","id":
"/_system/governance/apimgt/customsequences/in/custom-in.xml"},{"name":"custom-out","type":
"out","id":
"/_system/governance/apimgt/customsequences/out/custom-out.xml"}],
   "subscriptionAvailability": "current_tenant",
   "subscriptionAvailableTenants": null
}

Thanks for your help!!!

On Mon, Jan 22, 2018 at 3:05 PM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Thank you both for the information. Will try it.
>
>
>
> On Mon, Jan 22, 2018 at 2:59 PM, Abimaran Kugathasan <abima...@wso2.com>
> wrote:
>
>> Hi Chathurika,
>>
>> If you have already added the sequence to registry through the registry
>> APIs, then you can use sequence parameter to populate it in the API
>> creation time, otherwise, you will have to create the API first and upload
>> the sequence through the API mentioned by Praminda.
>>
>> On Mon, Jan 22, 2018 at 2:47 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi Praminda
>>>
>>> Thank you. I will try this. Since the payload in [1] consists of a
>>> parameter called "sequence" it was bit confusing.
>>>
>>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/models#API
>>>
>>> On Mon, Jan 22, 2018 at 2:43 PM, Praminda Jayawardana <prami...@wso2.com
>>> > wrote:
>>>
>>>> Hi Erandi,
>>>>
>>>> I don't think you can attach a sequence at API creation. However did
>>>> you try [1] which is the API for adding a mediation sequence to existing
>>>> API?
>>>>
>>>> [1]: https://docs.wso2.com/display/AM210/apidocs/publisher/#!/ope
>>>> rations#MediationPolicyCollection#apisApiIdPoliciesMediationPost
>>>>
>>>> Thanks,
>>>> Praminda
>>>>
>>>> On Mon, Jan 22, 2018 at 2:31 PM, Chathurika De Silva <
>>>> chathuri...@wso2.com> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> There is a need to create/update an api with a custom sequence
>>>>> associated through the REST APIs. In [1] the sample payload has a field
>>>>> called sequences which is taking an array as the argument. But from the
>>>>> document it's not clear how to proceed with it (whether we need to first
>>>>> upload the sequence to the registry, etc...) It would be highly 
>>>>> appreciated
>>>>> if a sample can be pointed out that addresses the $subject need.
>>>>>
>>>>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/ope
>>>>> rations#APIIndividual#apisApiIdPut
>>>>>
>>>>> Thanks
>>>>> Erandi
>>>>>
>>>>> --
>>>>> *Chathurika Erandi*
>>>>> Senior Software Engineer,
>>>>> WSO2 Inc.

Re: [Dev] [APIM] REST API - adding a custom sequence and associating with an api

[Chathurika De Silva]

Thank you both for the information. Will try it.



On Mon, Jan 22, 2018 at 2:59 PM, Abimaran Kugathasan <abima...@wso2.com>
wrote:

> Hi Chathurika,
>
> If you have already added the sequence to registry through the registry
> APIs, then you can use sequence parameter to populate it in the API
> creation time, otherwise, you will have to create the API first and upload
> the sequence through the API mentioned by Praminda.
>
> On Mon, Jan 22, 2018 at 2:47 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi Praminda
>>
>> Thank you. I will try this. Since the payload in [1] consists of a
>> parameter called "sequence" it was bit confusing.
>>
>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/models#API
>>
>> On Mon, Jan 22, 2018 at 2:43 PM, Praminda Jayawardana <prami...@wso2.com>
>> wrote:
>>
>>> Hi Erandi,
>>>
>>> I don't think you can attach a sequence at API creation. However did you
>>> try [1] which is the API for adding a mediation sequence to existing API?
>>>
>>> [1]: https://docs.wso2.com/display/AM210/apidocs/publisher/#!/ope
>>> rations#MediationPolicyCollection#apisApiIdPoliciesMediationPost
>>>
>>> Thanks,
>>> Praminda
>>>
>>> On Mon, Jan 22, 2018 at 2:31 PM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
>>>> Hi
>>>>
>>>> There is a need to create/update an api with a custom sequence
>>>> associated through the REST APIs. In [1] the sample payload has a field
>>>> called sequences which is taking an array as the argument. But from the
>>>> document it's not clear how to proceed with it (whether we need to first
>>>> upload the sequence to the registry, etc...) It would be highly appreciated
>>>> if a sample can be pointed out that addresses the $subject need.
>>>>
>>>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/ope
>>>> rations#APIIndividual#apisApiIdPut
>>>>
>>>> Thanks
>>>> Erandi
>>>>
>>>> --
>>>> *Chathurika Erandi*
>>>> Senior Software Engineer,
>>>> WSO2 Inc.
>>>>
>>>> *E-mail:* chathuri...@wso2.com
>>>> *Mobile: *+94714 328 612
>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Praminda Jayawardana*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>>>
>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <+94%2077%20392%202820>
>
> <http://stackoverflow.com/users/515034>
> <http://lk.linkedin.com/in/abimaran>
> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
> <https://twitter.com/abimaran>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] REST API - adding a custom sequence and associating with an api

[Chathurika De Silva]

Hi Praminda

Thank you. I will try this. Since the payload in [1] consists of a
parameter called "sequence" it was bit confusing.

[1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/models#API

On Mon, Jan 22, 2018 at 2:43 PM, Praminda Jayawardana <prami...@wso2.com>
wrote:

> Hi Erandi,
>
> I don't think you can attach a sequence at API creation. However did you
> try [1] which is the API for adding a mediation sequence to existing API?
>
> [1]: https://docs.wso2.com/display/AM210/apidocs/publisher/#!/operations#
> MediationPolicyCollection#apisApiIdPoliciesMediationPost
>
> Thanks,
> Praminda
>
> On Mon, Jan 22, 2018 at 2:31 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi
>>
>> There is a need to create/update an api with a custom sequence associated
>> through the REST APIs. In [1] the sample payload has a field called
>> sequences which is taking an array as the argument. But from the document
>> it's not clear how to proceed with it (whether we need to first upload the
>> sequence to the registry, etc...) It would be highly appreciated if a
>> sample can be pointed out that addresses the $subject need.
>>
>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/ope
>> rations#APIIndividual#apisApiIdPut
>>
>> Thanks
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918 <+94%2071%20659%200918>
>



-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] REST API - adding a custom sequence and associating with an api

[Chathurika De Silva]

Hi

There is a need to create/update an api with a custom sequence associated
through the REST APIs. In [1] the sample payload has a field called
sequences which is taking an array as the argument. But from the document
it's not clear how to proceed with it (whether we need to first upload the
sequence to the registry, etc...) It would be highly appreciated if a
sample can be pointed out that addresses the $subject need.

[1]
https://docs.wso2.com/display/AM210/apidocs/publisher/#!/operations#APIIndividual#apisApiIdPut

Thanks
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM-220][Rest API] Creating an API with Access Control restricted to roles

[Chathurika De Silva]

Hi Kavitha

Thank you. It worked. I have reported a doc issue as this information
should be included to documentation

[1] https://github.com/wso2/product-apim/issues/2431

Best Regards
Erandi

On Tue, Jan 16, 2018 at 3:05 PM, Kavitha Subramaniyam <kavi...@wso2.com>
wrote:

> Hi Chathurika,
>
> I hope you were trying to add access control with restricted by roles and
> not the visibility. Can you please try the below parameters and see?
>
> "accessControl": "RESTRICTED",
> "accessControlRoles": [
> "rolename"
> ],
>
> Thanks,
> Kavitha
>
> On Tue, Jan 16, 2018 at 2:59 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
> wrote:
>
>> In this document[1] we have added sample request to create API. There we
>> have visibility and visible roles attributes.
>>
>> "visibility": "PUBLIC", "visibleRoles": [], "visibleTenants": [],
>>
>> [1]https://docs.wso2.com/display/AM210/apidocs/publisher/#!/
>> operations#APICollection#apisPost
>>
>> Thanks,
>> sanjeewa.
>>
>> On Tue, Jan 16, 2018 at 2:55 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> I am trying to creating an api using the rest interfaces to have access
>>> control for selected roles. In Publisher UI i can set "Restricted to Roles"
>>> as Access Control mechanism. Referred [1] to find the relevant parameter to
>>> set the above through the REST APIs but couldn't find the reference. Any
>>> help regarding this is much appreciated.
>>>
>>> [1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/models#API
>>>
>>>
>>> Thanks
>>> Erandi
>>>
>>> *Chathurika Erandi*
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779 <+94%2071%20306%208779>
>>
>> <http://sanjeewamalalgoda.blogspot.com/>blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> <http://sanjeewamalalgoda.blogspot.com/>
>>
>>
>>
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> email : kavi...@wso2.com
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM-220][Rest API] Creating an API with Access Control restricted to roles

[Chathurika De Silva]

Hi

I am trying to creating an api using the rest interfaces to have access
control for selected roles. In Publisher UI i can set "Restricted to Roles"
as Access Control mechanism. Referred [1] to find the relevant parameter to
set the above through the REST APIs but couldn't find the reference. Any
help regarding this is much appreciated.

[1] https://docs.wso2.com/display/AM210/apidocs/publisher/#!/models#API


Thanks
Erandi

*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Federation proxy]Configuring WSO2 IS as external IDP of WSO2 APPM

[Chathurika De Silva]

Hi Kavitha

Yes, I got the parts you have mentioned working and I am now stuck with a
separate issue which I have raised in [1] . Please do provide any answer on
that if you have tried this earlier and please be kind enough to record
that in the query itself. Your help is much appreciated.

[1] https://github.com/wso2/product-is/issues/1540

Thank You

On Fri, Dec 15, 2017 at 10:10 AM, Kavitha Subramaniyam <kavi...@wso2.com>
wrote:

> Hi Chathurika,
>
> As I understood the solution, if you can do all steps mentioned in the doc
> [2] you should be able to SSO login to pub/store using IS1 as IDP and this
> setup together (IS1 + APPM) will be able to funtion as federation proxy in
> this scenario(solution15). After you should configure external IDP (IS2 as
> IDP) into federation proxy (inside IS1).
>
> I'm not clear about your question here.
> Are you struggled to implement the first part of configuration? or is it
> not working kind of situation?
>
> Thanks,
> Kavitha
>
> On Sat, Dec 9, 2017 at 2:49 AM, Chathurika De Silva <chathuri...@wso2.com>
> wrote:
>
>> Hi
>>
>> In order to achieve the $subject to implement solution 15 in [1] I have
>> done the below steps
>> 1. Add WSO2 IS as an Identity provider in WSO2 APPM (added as a
>> federation hub identity provider)
>> 2. Followed from step 1 to 3 in [2]
>>
>> It would be much appreciated if the above mentioned steps can be verified
>> and mention if I am missing any specific configurations.
>>
>> [1] https://medium.facilelogin.com/thirty-solution-patterns-with
>> -the-wso2-identity-server-16f9fd0c0389
>> [2] https://docs.wso2.com/display/APPM120/Configuring+with+an+Ex
>> ternal+Identity+Server
>>
>> Thanks
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> email : kavi...@wso2.com
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Federation proxy]Configuring WSO2 IS as external IDP of WSO2 APPM

[Chathurika De Silva]

Hi

In order to achieve the $subject to implement solution 15 in [1] I have
done the below steps
1. Add WSO2 IS as an Identity provider in WSO2 APPM (added as a federation
hub identity provider)
2. Followed from step 1 to 3 in [2]

It would be much appreciated if the above mentioned steps can be verified
and mention if I am missing any specific configurations.

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
[2]
https://docs.wso2.com/display/APPM120/Configuring+with+an+External+Identity+Server

Thanks
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Enabling Role-Based Access Control Using XACML

[Chathurika De Silva]

Hi

While trying to get a fine grained access control implemented for apis
using WSO2 Identity server, I came across [1] which provides a high level
guide to get it done, then going forward I referred [2] which discusses
$subject.

In [1] it mentions using WSO2 IS set up as the key manager for WSO2 API
Manager, whereas in [2] the first step describes only on setting up a
common user store between the two products.

As [3] indicates, setting up WSO2 IS as the key manager contains some
additional configurations. So in order to get fine grain access control
implemented, will just setting up a common user store be sufficient or does
the IS as the key manager setup as mentioned in [1] is required?

[1]
https://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
- Fine-grained access control for APIs
[2]
https://docs.wso2.com/display/AM210/Enabling+Role-Based+Access+Control+Using+XACML
[3]
https://docs.wso2.com/display/AM210/Configuring+WSO2+Identity+Server+as+a+Key+Manager

Thanks
Erandi



-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

[Chathurika De Silva]

Hi Nuwan

Awesome. Thank You

Best Regards
Erandi

On Mon, Jul 25, 2016 at 5:05 PM, Nuwan Pallewela <nuw...@wso2.com> wrote:

> Hi Chathurika,
>
> Yes. We have discussed it and going to do it[1]. We will provide a
> editable drop down with the configuration need to provide to select the
> input and operator description in the configure dialog about it.
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-655
>
> Thanks,
> Nuwan
>
> On Mon, Jul 25, 2016 at 4:36 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi
>>
>> It was observed that the operators which manipulates values using both
>> the configuration and the inputs always takes the configured value as the
>> preceded one when both ways are present. According to the discussion in [1]
>> the user has to keep the default values in the configuration as it is to
>> make the values from the input to take precedence for the manipulation.
>>
>> In data mapper there are multiple operators that behave similarly and
>> currently the user should be either knowledgable or find out by reading
>> documentation which is an extra effort.
>>
>> In order to solve this, can we have an instruction wording in the
>> operator it self, so that the user will know how to use it directly. Since
>> this is a common improvement for most of the operators, it would be ideal
>> if this is done for this release itself.
>>
>> WDYT?
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-643
>>
>> Thank you
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com <nuw...@wso2.com>*
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

[Chathurika De Silva]

Hi

It was observed that the operators which manipulates values using both the
configuration and the inputs always takes the configured value as the
preceded one when both ways are present. According to the discussion in [1]
the user has to keep the default values in the configuration as it is to
make the values from the input to take precedence for the manipulation.

In data mapper there are multiple operators that behave similarly and
currently the user should be either knowledgable or find out by reading
documentation which is an extra effort.

In order to solve this, can we have an instruction wording in the operator
it self, so that the user will know how to use it directly. Since this is a
common improvement for most of the operators, it would be ideal if this is
done for this release itself.

WDYT?

[1] https://wso2.org/jira/browse/DEVTOOLESB-643

Thank you
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Chathurika De Silva]

Hi Jagath

Thank you, will verify once the fix is given

Best Regards
Erandi

On Fri, Jul 22, 2016 at 7:23 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Chathurika,
>
> This will be solved with the fix which we are going to apply for [1].
> Issue is that Dev Studio calls admin services with additional '/' and it
> will be removed with the fix.
>
> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
>
> Thanks.
>
> On Fri, Jul 22, 2016 at 6:54 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi
>>
>> A similar issue exists for un-deploying a CAPP and the issue is reported
>> as [1]. Would it be possible for us to get this fixed?
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-642
>>
>> Thank You
>> Erandi
>>
>> On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan <pubu...@wso2.com>
>> wrote:
>>
>>> Awesome. Thanks!
>>>
>>> Cheers,
>>> Pubudu.
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando <chana...@wso2.com>
>>> wrote:
>>>
>>>> Hi Pubudu,
>>>>
>>>> We have already fixed this in the latest source and will share a pack
>>>> soon.
>>>>
>>>> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan <pubu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hello Viraj and DevStudio team,
>>>>>
>>>>> We have observed the issue logged at [1] while testing ESB tooling
>>>>> shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists
>>>>> for both p2 repo as well as the pre-packaged Eclipse.
>>>>>
>>>>> Would it be possible for us to get this fix in with the next ESB pack
>>>>> released for testing? Thanks!
>>>>>
>>>>>
>>>>> [1] https://wso2.org/jira/browse/DEVTOOLESB-574
>>>>>
>>>>> Cheers,
>>>>> Pubudu D.P
>>>>> Senior Software Engineer - QA Team | WSO2 inc.
>>>>> Mobile : +94775464547
>>>>>
>>>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>>>> Medium: https://medium.com/@pubududp
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] [Tooling] Issue when deploying a CAPP to a remote ESB server

[Chathurika De Silva]

Hi

A similar issue exists for un-deploying a CAPP and the issue is reported as
[1]. Would it be possible for us to get this fixed?

[1] https://wso2.org/jira/browse/DEVTOOLESB-642

Thank You
Erandi

On Wed, Jul 13, 2016 at 11:34 AM, Pubudu Priyashan  wrote:

> Awesome. Thanks!
>
> Cheers,
> Pubudu.
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> Linkedin: https://uk.linkedin.com/in/pubududp
> Medium: https://medium.com/@pubududp
>
>
> On Wed, Jul 13, 2016 at 11:31 AM, Chanaka Fernando 
> wrote:
>
>> Hi Pubudu,
>>
>> We have already fixed this in the latest source and will share a pack
>> soon.
>>
>> On Wed, Jul 13, 2016 at 11:13 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hello Viraj and DevStudio team,
>>>
>>> We have observed the issue logged at [1] while testing ESB tooling
>>> shipped with wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. Issue persists for
>>> both p2 repo as well as the pre-packaged Eclipse.
>>>
>>> Would it be possible for us to get this fix in with the next ESB pack
>>> released for testing? Thanks!
>>>
>>>
>>> [1] https://wso2.org/jira/browse/DEVTOOLESB-574
>>>
>>> Cheers,
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> Linkedin: https://uk.linkedin.com/in/pubududp
>>> Medium: https://medium.com/@pubududp
>>>
>>>
>>
>>
>> --
>> 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
>>
>>
>>
>>
>>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Improvement on constant operator

[Chathurika De Silva]

Hi Viraj

Thank you for your reply.

Agree with you on a proper graphical representation for a global constant
as it will increase usability.

Best Regards
Erandi

On Fri, Jul 22, 2016 at 5:47 PM, Viraj Rajaguru <vi...@wso2.com> wrote:

> Hi Chaturika,
>
> We got your point and we will consider this improvement for a next release
> with a proper graphical representation.
>
> BTW, we are encouraging users to write self contained custom functions as
> much as possible to reduce the complexity. So that its better to define
> constants within the custom function scope. Without having a proper
> graphical representation of the connectivity between a custom function and
> a global constant, facilitating such a feature might lead to a confusion.
>
> We had to introduce global variables concept, since there was no other
> option to achieve some use cases.
>
> Thanks,
> Viraj.
>
> On Fri, Jul 22, 2016 at 5:03 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi ESB Team
>>
>> Currently the constant operator provides just a setting of value and
>> mapping to an output. In the present mapping configuration the constant is
>> not defined as a constant, rather the defined value is assigned directly to
>> the relevant output.
>>
>> If there is a mechanism to define a global constant, this can be reused
>> (e.g. in custom functions) and hence will upgrade the usage of the data
>> mapper as well. I have created [1] for this and hope this will be
>> considered as this will add a greater value.
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-640
>>
>> Thank You
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB Tooling] Improvement on constant operator

[Chathurika De Silva]

Hi ESB Team

Currently the constant operator provides just a setting of value and
mapping to an output. In the present mapping configuration the constant is
not defined as a constant, rather the defined value is assigned directly to
the relevant output.

If there is a mechanism to define a global constant, this can be reused
(e.g. in custom functions) and hence will upgrade the usage of the data
mapper as well. I have created [1] for this and hope this will be
considered as this will add a greater value.

[1] https://wso2.org/jira/browse/DEVTOOLESB-640

Thank You
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB Tooling] Data mapper interprets multiplication of negative integers by zero results in signed zero

[Chathurika De Silva]

Hi

Currently in data mapper, the multiplication of -2 * 0 results in -0.
Ideally in basic mathematics the value zero should not have any - or +
marking on it. I have reported [1] regarding this and according to jira's
comments if this is to be fixed the -0 should be converted to string and
then again to a number and it is shown as a concern there that this will
have a performance impact due to unnecessary operations.

Signed zero itself is used for some mathematical operations[2]  but
seemingly there is no such operation that uses signed zero available in
data mapper currently. So rather than shipping signed zero, can we ship it
to adhere the basic mathematics (if there's no hidden usage of signed -0
that is) because first impression matters and first impression depends on
minor things like these as well.

[1] https://wso2.org/jira/browse/DEVTOOLESB-627
[2] https://en.wikipedia.org/wiki/Signed_zero

Best Regards
Erandi
-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

[Chathurika De Silva]

Hi Chanaka

Thank you for your reply and I am sorry if my earlier mail was confusing.

Currently the compare operator consists of greater than and less than
functions. Usually these operators are used for numeric comparisons. But
when two Strings are given for greater than or less than function, it is
also compared. In native javascript this kind of comparison is doable which
is the underlining language used for the Data Mapper.

My concern is that even-though such a comparison is doable in javascript,
should we ship the data mapper in the exact same manner?

 Since we are providing an enhanced mechanism for data conversion and
mapping and not a graphical UI for javascript through Data Mapper,
shouldn't we add validations where appropriate in scenarios similar to
above to maintain our own standard for the WSO2 Data Mapper?

Thank You
Erandi



On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando <chana...@wso2.com> wrote:

> Hi Erandi,
>
> Appreciate your feedback on improving the DM. The existing compare
> operator checks for the equality (==) of the values passed into the
> operator. If you passed in 2 String values, it will check the equality of
> strings. If it is integer values, it will check for the equality of integer
> values.
>
> Are you talking about adding ">" (greater than) and "<" (less than) as new
> operators?
>
> Basically, you can do this kind of operations with a custom function.
>
> Please correct me If I understood your suggestion in a different manner.
>
> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi
>>
>> Currently the data mapper compares (compare operator) String values for >
>> (greater than), < (less than). The native javascript too does the same
>> which is the underlining engine of data mapper.
>>
>> Since we are providing data mapper to the user to enhance conversion and
>> mapping, rather than a graphical UI for javascript itself, it would be
>> better if we should add UI (ESB tooling) validations for similar scenarios
>> as $subject.
>>
>> WDYT???
>>
>>
>> Best Regards
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com <https://wso2.com/signature>
>
>
>
>
>
>
>


-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

[Chathurika De Silva]

Hi

Currently the data mapper compares (compare operator) String values for >
(greater than), < (less than). The native javascript too does the same
which is the underlining engine of data mapper.

Since we are providing data mapper to the user to enhance conversion and
mapping, rather than a graphical UI for javascript itself, it would be
better if we should add UI (ESB tooling) validations for similar scenarios
as $subject.

WDYT???


Best Regards
Erandi

-- 
*Chathurika Erandi*
Senior Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

[Chathurika De Silva]

Hi Chanaka

When testing the debugger, following observation was made

Currently if a Transport property such as SOAPAction is removed, it's
removed from the variable view but when the request is sent to the backend
it's added again by the ESB. Since we are explicitly removing it, shouldn't
the request fail? Currently it seems that clearing that property really
does not have an affect on the execution.

Can you please explain if this observation is credible?

Thank You
Erandi

On Mon, May 9, 2016 at 1:37 PM, Praneesha Chandrasiri <pranee...@wso2.com>
wrote:

> Updated the information given on the "Resend ESB Debug Points" option in
> [1], to match the current implementation.
>
> Thanks everyone!
>
> [1] https://docs.wso2.com/display/ESB500/Debugging+Mediation
>
> On Mon, May 9, 2016 at 1:24 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Chanaka,
>>
>> Added a jira [1] and +1 for fixing it with this release.
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-208
>>
>> Regards,
>> Dilshani
>>
>>
>> On Mon, May 9, 2016 at 1:00 PM, Nuwan Pallewela <nuw...@wso2.com> wrote:
>>
>>> Hi Chanaka,
>>>
>>> This is not reported as a public JIRA yet.
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Mon, May 9, 2016 at 12:51 PM, Chanaka Fernando <chana...@wso2.com>
>>> wrote:
>>>
>>>> Is there any public JIRA already created?
>>>>
>>>> On Mon, May 9, 2016 at 12:46 PM, Isabelle Mauny <isabe...@wso2.com>
>>>> wrote:
>>>>
>>>>> +1 - Can we fix this in 5.0.0 …
>>>>> __
>>>>>
>>>>> Isabelle Mauny
>>>>> VP, Product Management; WSO2, Inc.;  http://wso2.com/
>>>>>
>>>>> On May 9, 2016, at 9:05 AM, Chathurika De Silva <chathuri...@wso2.com>
>>>>> wrote:
>>>>>
>>>>> Hi ESB Team
>>>>>
>>>>> Addition to dilshani' and nuwan's feedback, from user's perspective,
>>>>> when debug points are set and if the artifact is not changed, the need for
>>>>> him to resend debug point information is an additional task. Ideally it's
>>>>> better to give the same feel to a developer who is using this tool after
>>>>> using the general eclipse debugging (since we are based on eclipse). It's
>>>>> understandable that resend is needed when the artifact has changed, but if
>>>>> doesn't the developer should be able to start debugging without any extra
>>>>> effort from the tooling side. So is there any possibility in getting this
>>>>> fixed with this release rather than marking it as an improvement?
>>>>>
>>>>> Thank You
>>>>> Erandi
>>>>>
>>>>> On Mon, May 9, 2016 at 12:09 PM, Dilshani Subasinghe <
>>>>> dilsh...@wso2.com> wrote:
>>>>>
>>>>>> Hi ESB Team,
>>>>>>
>>>>>> After restarting debug process, it may not identify previously added
>>>>>> debug points. But newly added ESB points will be added to debug process
>>>>>> successfully.
>>>>>>
>>>>>> When we using the option "*Resend ESB Debug Points*", it may send
>>>>>> previous debug points too.
>>>>>>
>>>>>> As Far As I Feel, this is bit of misleading and I also took much time
>>>>>> to identify relevant option.
>>>>>>
>>>>>> What is the improvement you can do about that ?
>>>>>>
>>>>>> @Nisrin/Praneesha - As I seen in the blog post (
>>>>>> https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
>>>>>> "*Resend ESB Debug Points*" will be useful when we changing the
>>>>>> artifact. But in documentation it may just give explanation like "Sends
>>>>>> all registered debugging points to the ESB Server".
>>>>>>
>>>>>> Hope it will be better to be more descriptive with relevant
>>>>>> functionalities (Ex: When to use). Because user may confuse with exact
>>>>>> options as they are having similar functionalities.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> --
>>>>>> Best Rega

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

[Chathurika De Silva]

Hi ESB Team

Addition to dilshani' and nuwan's feedback, from user's perspective, when
debug points are set and if the artifact is not changed, the need for him
to resend debug point information is an additional task. Ideally it's
better to give the same feel to a developer who is using this tool after
using the general eclipse debugging (since we are based on eclipse). It's
understandable that resend is needed when the artifact has changed, but if
doesn't the developer should be able to start debugging without any extra
effort from the tooling side. So is there any possibility in getting this
fixed with this release rather than marking it as an improvement?

Thank You
Erandi

On Mon, May 9, 2016 at 12:09 PM, Dilshani Subasinghe 
wrote:

> Hi ESB Team,
>
> After restarting debug process, it may not identify previously added debug
> points. But newly added ESB points will be added to debug process
> successfully.
>
> When we using the option "*Resend ESB Debug Points*", it may send
> previous debug points too.
>
> As Far As I Feel, this is bit of misleading and I also took much time to
> identify relevant option.
>
> What is the improvement you can do about that ?
>
> @Nisrin/Praneesha - As I seen in the blog post (
> https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
> "*Resend ESB Debug Points*" will be useful when we changing the artifact.
> But in documentation it may just give explanation like "Sends all
> registered debugging points to the ESB Server".
>
> Hope it will be better to be more descriptive with relevant
> functionalities (Ex: When to use). Because user may confuse with exact
> options as they are having similar functionalities.
>
> Thank you
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] - XSLT mediator: Features

[Chathurika De Silva]

Hi ESB team

The $subject, the documentation gives
http://ws.apache.org/ns/synapse/transform/feature/dom as the example. Is
there any predefined feature list that can be used here?

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Oauth Mediator Documentation

[Chathurika De Silva]

Hi

As per the offline chat with Asela the documentation that is pointed by [1]
is Oauth 1.0 [2] . There seems to be no sample for Oauth 2.0 related
scenario. Can we get it included in the documentation?

[1] https://docs.wso2.com/display/ESB500/OAuth+Mediator
[2]
https://docs.wso2.com/display/IS510/2-legged+OAuth+for+Securing+a+RESTful+Service

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] - Throttling Mediator

[Chathurika De Silva]

Raised [1] with the concern as well

[1] https://wso2.org/jira/browse/ESBJAVA-4455

On Tue, Mar 1, 2016 at 11:04 AM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Hi
>
> With regarding to the $subject what is the default action on a incoming
> request?
>
> If i further explain, say i configure ip address 1 as allowed. Then the
> incoming requests from this particular ip address will be allowed.
> Currently, if i invoke from another ip address (ip addres 2) then those
> requests are also allowed.
>
> But allowing one ip address by the rule is generally understood as denying
> the other requests coming from other ip addresses. In the above mentioned
> scenario this general understanding is violated and the allow rule has no
> significant meaning.
>
> Could you kindly explain the functionality of throttling mediator with
> regarding to the rules?
>
> Thank You
> Erandi
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] - Throttling Mediator

[Chathurika De Silva]

Hi

With regarding to the $subject what is the default action on a incoming
request?

If i further explain, say i configure ip address 1 as allowed. Then the
incoming requests from this particular ip address will be allowed.
Currently, if i invoke from another ip address (ip addres 2) then those
requests are also allowed.

But allowing one ip address by the rule is generally understood as denying
the other requests coming from other ip addresses. In the above mentioned
scenario this general understanding is violated and the allow rule has no
significant meaning.

Could you kindly explain the functionality of throttling mediator with
regarding to the rules?

Thank You
Erandi
-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Version 500 in JIRA affected version and fixed version

[Chathurika De Silva]

Hi

Currently the version 500 is not there in the jira. Could you please update
it?

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon-Kernel 4.2.0] Compilation Error while building

[Chathurika De Silva]

Hi Madhawa

This blog might be a help as well [1]

[1] https://dzone.com/articles/how-build-wso2-carbon-420

Regards
Erandi

On Thu, Feb 11, 2016 at 3:24 PM, Tharindu Edirisinghe 
wrote:

> Hi Madhawa,
>
> Can you try to build with some maven 3.0.x version ? According to [1]
> that's the recommendation. I've been able to build the kernel with 3.0.4
> version.
>
> [1] https://docs.wso2.com/display/Carbon420/Installation+Prerequisites
>
> Regards,
> TharinduE
>
> On Thu, Feb 11, 2016 at 3:18 PM, Madhawa Perera  wrote:
>
>> Hi,
>>
>> I'm getting following compilation error when building the Carbon Kernel
>> 4.2.0 from source. I'm using apache maven 3.3.9 and jdk 1.7.0_80
>>
>> The error that I'm getting is as follows
>>
>> [ERROR] COMPILATION ERROR :
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.1:compile
>> (default-compile) on project wss4j: Compilation failure: Compilation
>> failure:
>> [ERROR]
>> /home/madhawap/wso2carbon-kernel/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbTicketDecoder.java:[10,24]
>> EncryptionKey is internal proprietary API and may be removed in a future
>> release
>>
>> Further it gives following warnings as well .
>>
>> [INFO] --- maven-pmd-plugin:2.5:pmd (pmd) @ wss4j ---
>> [WARNING] File encoding has not been set, using platform encoding UTF-8,
>> i.e. build is platform dependent!
>>
>> [WARNING] Error while parsing
>> /home/madhawap/wso2carbon-kernel/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/KerberosTokenPrincipal.java:
>> Can't use annotations when running in JDK 1.4 mode!
>>
>> [WARNING] Error while parsing
>> /home/madhawap/wso2carbon-kernel/dependencies/wss4j/1.5.11-wso2v6/src/org/apache/ws/security/kerberos/KrbSessionCache.java:
>> Can't use generics unless running in JDK 1.5 mode!
>>
>> Is this a problem with maven and jdk versions? The prerequisites
>> documentation suggests maven 3.0.x and has mentioned that jdk 1.7 is
>> compatible.
>>
>> Thank you
>> Regards,
>>
>> --
>> Madhawa Perera
>> *Software Engineer*
>> Mobile : +94 (0) 773655496
>> <%2B94%20%280%29%20773%20451194>
>> madha...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Tharindu Edirisinghe
> Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : tharindue.blogspot.com
> mobile : +94 775181586
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ANNOUNCEMENT][WSO2 ESB]Changing the version number of the next WSO2 ESB release from 4.10.0 to 5.0.0

[Chathurika De Silva]

Hi Nisrin

According to the above mail ESB  4.10.0 will be ESB 5.0.0 with immediate
effect. Can we change the documentation space to reflect it as well?

Thank You
Erandi

On Wed, Feb 10, 2016 at 3:14 PM, Kasun Indrasiri  wrote:

> Also, to clarify that there won't be any major changes related to
> mediation language or runtime. Therefore that ensures the seamless
> migration from old versions to ESB 5.
>
> On Wed, Feb 10, 2016 at 2:03 PM, Chanaka Fernando 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 team has decided to change the version of the next WSO2 ESB release
>> from 4.10.0 to 5.0.0 with immediate effect. We have been adding several new
>> features with the ongoing development tasks and after considering the
>> importance of the new features, we have decided to do a major version bump
>> and made the next ESB release version as 5.0.0. Here are the main features
>> which we are going to introduce with this release.
>>
>> 1. WebSockets Connectivity - Adding websockets support for WSO2 ESB.
>>
>> 2. Message Flow Tracing - Comprehensive message flow tracing with the
>> Data Analytics Server (DAS) integration.
>>
>> 3. Message Flow Statistics - Advanced application level statistics
>> (Proxy, API, Sequence, Mediator) support with the DAS integration.
>>
>> 4. JMS 2.0 support - Adding JMS 2.0 specification support for existing
>> JMS messaging features.
>>
>> 5. Mediation flow debugger - Adding debugging capability to ESB mediation
>> flows from the WSO2 Developer Studio tool.
>>
>> 6. Updating smooks - To achieve better performance, smooks bundle has
>> been updated to latest stable released version 1.5.1.
>>
>> We will release the first milestone version of the ESB 5.0.0 as the next
>> release.
>>
>> Thanks,
>> Chanaka
>>
>> --
>> 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
>>
>>
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> 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
>
>


-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Load balance endpoint: Session Management

[Chathurika De Silva]

Thank You Shafreen

On Wed, Feb 3, 2016 at 2:16 PM, Shafreen Anfar <shafr...@wso2.com> wrote:

> Hi Chathurika,
>
> Following article should help you to understand the difference between
> those two scopes.
>
> http://wso2.com/library/articles/axis2-session-management-part-2/
>
> On Wed, Feb 3, 2016 at 11:14 AM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Adding the doc link [1]
>>
>> [1] https://docs.wso2.com/display/ESB4100/Load-balance+Group
>>
>> On Wed, Feb 3, 2016 at 11:13 AM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> In [1] there are two session management methods as "Transport" and
>>> "Soap". The document does not provide comprehensive details on their usage.
>>> Can you please explain their usage with a user scenario?
>>>
>>> Thank You
>>> Erandi
>>>
>>> --
>>> *Chathurika Erandi*
>>> Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Load balance endpoint: Session Management

[Chathurika De Silva]

Adding the doc link [1]

[1] https://docs.wso2.com/display/ESB4100/Load-balance+Group

On Wed, Feb 3, 2016 at 11:13 AM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Hi
>
> In [1] there are two session management methods as "Transport" and "Soap".
> The document does not provide comprehensive details on their usage. Can you
> please explain their usage with a user scenario?
>
> Thank You
> Erandi
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Load balance endpoint: Session Management

[Chathurika De Silva]

Hi

In [1] there are two session management methods as "Transport" and "Soap".
The document does not provide comprehensive details on their usage. Can you
please explain their usage with a user scenario?

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] Affect of migration on BPMN from 350 to 351

[Chathurika De Silva]

Hi Hasitha

Do we have any differences in BPMN related functionality that affects
migration from 350 to 351?

Couldn't find a reference in the documentation

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Asanthi Kulasinghe

[Chathurika De Silva]

Congratzz!!!1
Kaushi!



On Wed, Jan 13, 2016 at 1:47 PM, Chalitha Waldeniyage 
wrote:

> Congratulations !!! Kaushi
>
> On Wed, Jan 13, 2016 at 1:43 PM, Chankami Maddumage 
> wrote:
>
>> Congrats Kawshy :)
>>
>> On Wed, Jan 13, 2016 at 1:31 PM, Yasassri Ratnayake 
>> wrote:
>>
>>> Congrats Asanthi!! :)
>>>
>>> On Wed, Jan 13, 2016 at 12:25 PM, Dilini Gunatilake 
>>> wrote:
>>>
 Congrats Kaushi!!!

 On Wed, Jan 13, 2016 at 12:20 PM, Aparna Karunarathna 
 wrote:

> Hi All,
>
> It's my pleasure to announce Asanthi Kulasinghe as a WSO2 Committer.
> Asanthi is an active member of QA team and has given a great
> contribution to API Manager, App Manager,  ESB product releases and API
> Manager, ESB service packs.
>
> Congratulations Asanthi and keep up the good work...!
>
> --
> *Regards,*
>
> *Aparna Karunarathna.*
>
>
> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Dilini GunatilakeSoftware Engineer - QA Team*
 Mobile : +94 (0) 771 162518
 dili...@wso2.com

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


>>>
>>>
>>> --
>>> Yasassri Ratnayake
>>> Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <%2B94715933168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> *
>>> *http://wso2logs.blogspot.com *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Best Regards ,
>>
>>
>> *Chankami Maddumage*
>> Software Engineer - QA Team
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94 (0) 770 030 469 <%2B94%20%280%29%20773%20381%20250>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Chalitha Maheshwari*
> Software Engineer-QA,
> WSO2 Inc.
>
> *E-mail:* chali...@wso2.com
> *Mobile: *+94710 411 112
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM-200] Clustering documentation is not available

[Chathurika De Silva]

Hi

Since the Alpha is released, the QA people MUST setup the cluster now. Is
there any way we can get the deployment details and get them documented?
This is currently BLOCKING our testing cycle on Alpha.

Thank You
Erandi

On Wed, Nov 11, 2015 at 9:29 PM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Hi
>
> We have to start testing with the deployment once the Alpha is out (the
> predicted date of release 13.10.2015). Can we please get the deployment
> guide updated asap?
>
> Thank You
> Erandi
>
> On Fri, Nov 6, 2015 at 8:59 AM, Prabath Abeysekera <praba...@wso2.com>
> wrote:
>
>> Ack! Will share the relevant details ASAP.
>>
>> Cheers,
>> Prabath
>>
>> On Thu, Nov 5, 2015 at 11:37 AM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> Any update on this please, as we need to go for deployment soon.
>>>
>>> Thank You
>>> Erandi
>>>
>>> On Thu, Oct 29, 2015 at 11:06 AM, Samuel Gnaniah <sam...@wso2.com>
>>> wrote:
>>>
>>>> Hi EMM team,
>>>>
>>>> Please provide some content for this.
>>>>
>>>> Thanks,
>>>>
>>>> *Samuel Gnaniah*
>>>> Lead Technical Writer
>>>>
>>>> WSO2 (pvt.) Ltd.
>>>> Colombo, Sri Lanka
>>>> (+94) 773131798
>>>>
>>>> On Thu, Oct 29, 2015 at 10:25 AM, Chathurika De Silva <
>>>> chathuri...@wso2.com> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> The clustering guide in [1] is not currently available. Can you please
>>>>> provide us documentation on this as this is currently blocking our testing
>>>>> process.
>>>>>
>>>>> Please find the jira reported on this [2]
>>>>>
>>>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+WSO2+Products
>>>>> [2] https://wso2.org/jira/browse/DOCUMENTATION-2626
>>>>>
>>>>> Thank You
>>>>> Erandi
>>>>> --
>>>>> *Chathurika Erandi*
>>>>> Software Engineer,
>>>>> WSO2 Inc.
>>>>>
>>>>> *E-mail:* chathuri...@wso2.com
>>>>> *Mobile: *+94714 328 612
>>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "WSO2 Techcontent Group" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to techcontent-group+unsubscr...@wso2.com.
>>>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Chathurika Erandi*
>>> Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>
>>
>>
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>
>
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM-200] Clustering documentation is not available

[Chathurika De Silva]

Hi

We have to start testing with the deployment once the Alpha is out (the
predicted date of release 13.10.2015). Can we please get the deployment
guide updated asap?

Thank You
Erandi

On Fri, Nov 6, 2015 at 8:59 AM, Prabath Abeysekera <praba...@wso2.com>
wrote:

> Ack! Will share the relevant details ASAP.
>
> Cheers,
> Prabath
>
> On Thu, Nov 5, 2015 at 11:37 AM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi
>>
>> Any update on this please, as we need to go for deployment soon.
>>
>> Thank You
>> Erandi
>>
>> On Thu, Oct 29, 2015 at 11:06 AM, Samuel Gnaniah <sam...@wso2.com> wrote:
>>
>>> Hi EMM team,
>>>
>>> Please provide some content for this.
>>>
>>> Thanks,
>>>
>>> *Samuel Gnaniah*
>>> Lead Technical Writer
>>>
>>> WSO2 (pvt.) Ltd.
>>> Colombo, Sri Lanka
>>> (+94) 773131798
>>>
>>> On Thu, Oct 29, 2015 at 10:25 AM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
>>>> Hi
>>>>
>>>> The clustering guide in [1] is not currently available. Can you please
>>>> provide us documentation on this as this is currently blocking our testing
>>>> process.
>>>>
>>>> Please find the jira reported on this [2]
>>>>
>>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+WSO2+Products
>>>> [2] https://wso2.org/jira/browse/DOCUMENTATION-2626
>>>>
>>>> Thank You
>>>> Erandi
>>>> --
>>>> *Chathurika Erandi*
>>>> Software Engineer,
>>>> WSO2 Inc.
>>>>
>>>> *E-mail:* chathuri...@wso2.com
>>>> *Mobile: *+94714 328 612
>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "WSO2 Techcontent Group" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to techcontent-group+unsubscr...@wso2.com.
>>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>>
>>>
>>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 latest build pack - 30/10/2015

[Chathurika De Silva]

Hi All

Currently in the above pack, the following main scenarios cannot be executed

1. Change the default H2 database
2. Applying policies
3. Secondary user store association for Oracle, MSSQL
4. Device not being able to be enrolled for a tenant user
5. Email as a username cannot be used
6. Etc...

Some of the above reported issues are fixed in 2.0.0 Alpha [1]. It would be
great if we can have the Alpha release with the above fixed to continue our
testing.

Furthermore below [2] & [3] depicts the current open/inprogress and blocker
issues respectively.

[1] https://wso2.org/jira/browse/EMM-943?filter=12512
[2] https://wso2.org/jira/browse/EMM-947?filter=12504
[3] https://wso2.org/jira/browse/EMM-946?filter=12478

Thank You
Erandi



On Sat, Oct 31, 2015 at 2:28 PM, Inosh Perera  wrote:

> Hi all,
>
> Please find the $subject here[1]
>
> [1].
> https://svn.wso2.org/repos/wso2/people/prabatha/MDM/builds/30102015/wso2mdm-2.0.0-SNAPSHOT.zip
>
> Regards,
> Inosh
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 0785293686
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM-200] Clustering documentation is not available

[Chathurika De Silva]

Hi

Any update on this please, as we need to go for deployment soon.

Thank You
Erandi

On Thu, Oct 29, 2015 at 11:06 AM, Samuel Gnaniah <sam...@wso2.com> wrote:

> Hi EMM team,
>
> Please provide some content for this.
>
> Thanks,
>
> *Samuel Gnaniah*
> Lead Technical Writer
>
> WSO2 (pvt.) Ltd.
> Colombo, Sri Lanka
> (+94) 773131798
>
> On Thu, Oct 29, 2015 at 10:25 AM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi
>>
>> The clustering guide in [1] is not currently available. Can you please
>> provide us documentation on this as this is currently blocking our testing
>> process.
>>
>> Please find the jira reported on this [2]
>>
>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+WSO2+Products
>> [2] https://wso2.org/jira/browse/DOCUMENTATION-2626
>>
>> Thank You
>> Erandi
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Techcontent Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to techcontent-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>


-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM-200] Clustering documentation is not available

[Chathurika De Silva]

Hi

The clustering guide in [1] is not currently available. Can you please
provide us documentation on this as this is currently blocking our testing
process.

Please find the jira reported on this [2]

[1] https://docs.wso2.com/display/CLUSTER44x/Clustering+WSO2+Products
[2] https://wso2.org/jira/browse/DOCUMENTATION-2626

Thank You
Erandi
-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM] Roles and Permissions

[Chathurika De Silva]

Hi

In EMM for permissions the following structure is there

   -Device Management
  -Device Management Admin

User 1 -> Device Management (parent level permission)
User 2 -> Device Management Admin  (Child level permission only)

What are the contexts that above users can be used? Help regarding this is
highly appreciated.

Thank You
Erandi
-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

[Chathurika De Silva]

Hi

As of today EOD we have total number of 13 blockers [1] raised and these
have affected the following scenarios

1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
2. Unable to change default username and role
3. Unable to self enrol device
4. Unable to apply policies for QR enrolled devices since all requests are
in pending state
5. Unable to unregister the device and re-register.

Considering the above factors effective testing of the EMM cannot be done.
A solution is highly appreciated.

[1] https://wso2.org/jira/browse/EMM-880?filter=12478

Thank You
Erandi




On Mon, Oct 26, 2015 at 2:12 PM, Geeth Munasinghe  wrote:

> Hi all,
>
> We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
>
> This release includes the following features and improvements.
>
>1. Adding users and sending email invitations.  (admin ui)
>2. Adding roles (admin ui)
>3. View device details (Admin ui)
>4. Android device management
>   1. Device Enrollment
>   2. Executing device operations (Admin ui & Android Agent)
>5. Windows
>   1. Device Enrollment
>   2. Executing device operations (Admin ui & Windows native agent)
>6. Operations
>   1. Add operations to device  (Admin ui)
>7. Policy
>   1. Add policy (Admin ui)
>   2. Edit policy (Admin ui)
>   3. Change priorities (Admin ui)
>   4. Change management (When a policy changed, related devices should
>   be notified to apply new changes)
>   5. Monitoring the device to check whether applied policy is
>   violated or not.
>
>
> References
>
> Product  can be downloaded from [1].
> [1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/
>
> Thanks
> Geeth
>
>
>
>
> *G. K. S. Munasinghe*
> *Senior Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

[Chathurika De Silva]

Hi

As of today EOD we have total number of 13 blockers [1] raised and these
have affected the following scenarios

1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
2. Unable to change default username and role
3. Unable to self enrol device
4. Unable to apply policies for QR enrolled devices since all requests are
in pending state
5. Unable to unregister the device and re-register.

Considering the above factors effective testing of the EMM cannot be done.
A solution is highly appreciated.

[1] https://wso2.org/jira/browse/EMM-880?filter=12478

Thank You
Erandi

On Mon, Oct 26, 2015 at 6:36 PM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Hi
>
> As of today EOD we have total number of 13 blockers [1] raised and these
> have affected the following scenarios
>
> 1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
> 2. Unable to change default username and role
> 3. Unable to self enrol device
> 4. Unable to apply policies for QR enrolled devices since all requests are
> in pending state
> 5. Unable to unregister the device and re-register.
>
> Considering the above factors effective testing of the EMM cannot be done.
> A solution is highly appreciated.
>
> [1] https://wso2.org/jira/browse/EMM-880?filter=12478
>
> Thank You
> Erandi
>
>
>
>
> On Mon, Oct 26, 2015 at 2:12 PM, Geeth Munasinghe <ge...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
>>
>> This release includes the following features and improvements.
>>
>>1. Adding users and sending email invitations.  (admin ui)
>>2. Adding roles (admin ui)
>>3. View device details (Admin ui)
>>4. Android device management
>>   1. Device Enrollment
>>   2. Executing device operations (Admin ui & Android Agent)
>>5. Windows
>>   1. Device Enrollment
>>   2. Executing device operations (Admin ui & Windows native agent)
>>6. Operations
>>   1. Add operations to device  (Admin ui)
>>7. Policy
>>   1. Add policy (Admin ui)
>>   2. Edit policy (Admin ui)
>>   3. Change priorities (Admin ui)
>>   4. Change management (When a policy changed, related devices
>>   should be notified to apply new changes)
>>   5. Monitoring the device to check whether applied policy is
>>   violated or not.
>>
>>
>> References
>>
>> Product  can be downloaded from [1].
>> [1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/
>>
>> Thanks
>> Geeth
>>
>>
>>
>>
>> *G. K. S. Munasinghe*
>> *Senior Software Engineer,*
>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>
>
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] - Performance test - Long running

[Chathurika De Silva]

Hi

While running the $subject on a manager, 2 worker cluster, noticed a
dis-ambiguity reported in [1]

Can you please provide an explanation on this? Your help is greatly
appreciated.

[1] https://wso2.org/jira/browse/BPS-912

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] - Performance test - Long running

[Chathurika De Silva]

Furthermore, following WARNING is observed frequently in the cluster at the
4th day of the long running test

TID: [-1] [] [2015-10-16 03:58:45,455]  WARN
{org.apache.ode.scheduler.simple.SimpleScheduler} -  Dispatching jobs with
more than 5 minutes delay. Either the server was down for some time or the
job load is greater than available capacity
{org.apache.ode.scheduler.simple.SimpleScheduler}

Also although i clean up the database once in every day at the 4th day of
the test, the database ran out of space and had to alter by adding another
datafile. What is the recommended frequency for the cleanup?

Please find the test parameters in [1]

[1] https://wso2.org/jira/browse/BPS-912


On Thu, Oct 15, 2015 at 3:14 PM, Chathurika De Silva <chathuri...@wso2.com>
wrote:

> Hi
>
> While running the $subject on a manager, 2 worker cluster, noticed a
> dis-ambiguity reported in [1]
>
> Can you please provide an explanation on this? Your help is greatly
> appreciated.
>
> [1] https://wso2.org/jira/browse/BPS-912
>
> Thank You
> Erandi
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS 350]: SchedulerTask Error

[Chathurika De Silva]

Hi

Done [1]

[1] https://wso2.org/jira/browse/BPS-907

On Mon, Oct 12, 2015 at 11:35 AM, Firzhan Naqash <firz...@wso2.com> wrote:

> Hi,
>
> Then this seems to be the Hazlecast OOM issue. Please report a jira for
> this.
>
>
> Regards,
> Firzhan
>
>
> --
> *Firzhan Naqash*
> Senior Software Engineer - Integration Platform Team
> WSO2 Inc. http://wso2.com
>
> email: firz...@wso2.com <lasan...@wso2.com>
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
> <http://firzhanblogger.blogspot.com/>  <http://suhothayan.blogspot.com/>*
> *twitter: https://twitter.com/firzhan007
> <https://twitter.com/firzhan007> | linked-in: 
> **https://www.linkedin.com/in/firzhan
> <https://www.linkedin.com/in/firzhan>*
>
> On Mon, Oct 12, 2015 at 11:11 AM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi Firzhan
>>
>> The cluster have the following configuration currently. The default value
>> is 256m
>>
>> Xms512m -Xmx2048m -XX:MaxPermSize=512m
>>
>> Please advice with the recommended value and please note that this
>> configuration is not given in the documentation
>>
>> On Mon, Oct 12, 2015 at 10:56 AM, Firzhan Naqash <firz...@wso2.com>
>> wrote:
>>
>>> Hi Chathiruka,
>>>
>>> This seems to be the hazlecast OOM error observed with kernel 4.4.1. Can
>>> you increase heap size and check this scenario again.
>>>
>>>
>>> *TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>>> {org.apache.tomcat.util.net
>>> <http://org.apache.tomcat.util.net>.NioEndpoint$Poller} -
>>> {org.apache.tomcat.util.net
>>> <http://org.apache.tomcat.util.net>.NioEndpoint$Poller}java.lang.OutOfMemoryError:
>>> GC overhead limit exceeded*
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> --
>>> *Firzhan Naqash*
>>> Senior Software Engineer - Integration Platform Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: firz...@wso2.com <lasan...@wso2.com>
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>> <http://firzhanblogger.blogspot.com/>  <http://suhothayan.blogspot.com/>*
>>> *twitter: https://twitter.com/firzhan007
>>> <https://twitter.com/firzhan007> | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> <https://www.linkedin.com/in/firzhan>*
>>>
>>> On Mon, Oct 12, 2015 at 10:51 AM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
>>>> Hi All
>>>>
>>>> We have configured a SchedulerTask for the BPS cluster (2 workers and
>>>> manager fronted by nginx). The task runs every day 5.10 pm and deletes
>>>> FAILED instances. The cluster was up and running in the weekend but was
>>>> idle. Following error was observed.
>>>>
>>>>
>>>> TID: [-1] [] [2015-10-09 18:49:23,157] ERROR
>>>> {org.apache.ode.scheduler.simple.SimpleScheduler} -  Error during
>>>> SchedulerTask execution {org.apache.ode.scheduler.simple.SimpleScheduler}
>>>> com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast
>>>> instance is not active!
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.getService(ProxyRegistry.java:65)
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.(ProxyRegistry.java:53)
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:74)
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:72)
>>>> at
>>>> com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:51)
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getOrCreateRegistry(ProxyServiceImpl.java:110)
>>>> at
>>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getDistributedObject(ProxyServiceImpl.java:118)
>>>> at
>>>> com.hazelcast.instance.HazelcastInstanceImpl.getDistributedObject(HazelcastInstanceImpl.java:390)
>>>> at
>>>> com.hazelcast.instance.HazelcastInstanceImpl.getMap(HazelcastInstanceImpl.java:192)
>>>> at
>>>> com.hazelcast.instance.HazelcastInstanceProxy.getMap(HazelcastInstanceProxy.java:75)
>

[Dev] [BPS 350]: SchedulerTask Error

[Chathurika De Silva]

Hi All

We have configured a SchedulerTask for the BPS cluster (2 workers and
manager fronted by nginx). The task runs every day 5.10 pm and deletes
FAILED instances. The cluster was up and running in the weekend but was
idle. Following error was observed.


TID: [-1] [] [2015-10-09 18:49:23,157] ERROR
{org.apache.ode.scheduler.simple.SimpleScheduler} -  Error during
SchedulerTask execution {org.apache.ode.scheduler.simple.SimpleScheduler}
com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance
is not active!
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.getService(ProxyRegistry.java:65)
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.(ProxyRegistry.java:53)
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:74)
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:72)
at
com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:51)
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getOrCreateRegistry(ProxyServiceImpl.java:110)
at
com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getDistributedObject(ProxyServiceImpl.java:118)
at
com.hazelcast.instance.HazelcastInstanceImpl.getDistributedObject(HazelcastInstanceImpl.java:390)
at
com.hazelcast.instance.HazelcastInstanceImpl.getMap(HazelcastInstanceImpl.java:192)
at
com.hazelcast.instance.HazelcastInstanceProxy.getMap(HazelcastInstanceProxy.java:75)
at
org.wso2.carbon.bpel.core.ode.integration.BPELServerImpl$ODEClusterImpl.getKnownNodes(BPELServerImpl.java:1009)
at
org.apache.ode.scheduler.simple.SimpleScheduler.updateHeartBeatAndGetStaleNodes(SimpleScheduler.java:848)
at
org.apache.ode.scheduler.simple.SimpleScheduler.access$800(SimpleScheduler.java:53)
at
org.apache.ode.scheduler.simple.SimpleScheduler$CheckStaleNodes.run(SimpleScheduler.java:1226)
at
org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:810)
at
org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:807)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
{org.apache.tomcat.util.net.NioEndpoint$Poller} -
{org.apache.tomcat.util.net.NioEndpoint$Poller}
java.lang.OutOfMemoryError: GC overhead limit exceeded
TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
{org.apache.tomcat.util.net.NioEndpoint$Poller} -
{org.apache.tomcat.util.net.NioEndpoint$Poller}
java.lang.OutOfMemoryError: GC overhead limit exceeded
TID: [-1] [] [2015-10-09 18:49:41,310] ERROR
{org.apache.tomcat.util.net.NioEndpoint$Poller} -
{org.apache.tomcat.util.net.NioEndpoint$Poller}
java.lang.OutOfMemoryError: GC overhead limit exceeded
TID: [-1] [] [2015-10-09 18:49:53,704] ERROR
{com.hazelcast.spi.impl.operationservice.impl.Invocation} -
[192.168.48.199]:4000 [wso2.bps.qa.domain] [3.5] Failed asynchronous
execution of execution callback:
com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService$IsOperationStillRunningCallback@6adde0a6for
call Invocation{ serviceName='hz:impl:mapService',
op=com.hazelcast.spi.impl.operationservice.impl.operations.IsStillExecutingOperation{serviceName='hz:impl:mapService',
partitionId=-1, callId=0, invocationTime=-1, waitTimeout=-1,
callTimeout=5000}, partitionId=-1, replicaIndex=0, tryCount=0,
tryPauseMillis=0, invokeCount=0, callTimeout=5000, target=null,
backupsExpected=0, backupsCompleted=0}
{com.hazelcast.spi.impl.operationservice.impl.Invocation}
java.lang.OutOfMemoryError: GC overhead limit exceeded
TID: [-1] [] [2015-10-09 18:50:06,800] ERROR
{com.hazelcast.spi.impl.operationservice.impl.Invocation} -
[192.168.48.199]:4000 [wso2.bps.qa.domain] [3.5] Failed asynchronous
execution of execution callback:
com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService$IsOperationStillRunningCallback@295de461for
call Invocation{ serviceName='hz:impl:mapService',
op=com.hazelcast.spi.impl.operationservice.impl.operations.IsStillExecutingOperation{serviceName='hz:impl:mapService',
partitionId=-1, callId=0, invocationTime=115365856, waitTimeout=-1,
callTimeout=5000}, partitionId=-1, replicaIndex=0, tryCount=0,
tryPauseMillis=0, invokeCount=1, callTimeout=5000,
target=Address[192.168.48.2]:4000, backupsExpected=0, backupsCompleted=0}
{com.hazelcast.spi.impl.operationservice.impl.Invocation}
java.lang.OutOfMemoryError: GC overhead limit exceeded
TID: [-1] [] [2015-10-09 18:50:30,826] ERROR
{org.wso2.carbon.humantask.core.scheduler.SimpleScheduler} -  Error loading
immediate jobs from database.
{org.wso2.carbon.humantask.core.scheduler.SimpleScheduler}

org.apache.openjpa.persistence.PersistenceException: No more data to read
from socket
FailedObject: 

Re: [Dev] [BPS 350]: SchedulerTask Error

[Chathurika De Silva]

Hi Firzhan

The cluster have the following configuration currently. The default value
is 256m

Xms512m -Xmx2048m -XX:MaxPermSize=512m

Please advice with the recommended value and please note that this
configuration is not given in the documentation

On Mon, Oct 12, 2015 at 10:56 AM, Firzhan Naqash <firz...@wso2.com> wrote:

> Hi Chathiruka,
>
> This seems to be the hazlecast OOM error observed with kernel 4.4.1. Can
> you increase heap size and check this scenario again.
>
>
> *TID: [-1] [] [2015-10-09 18:49:36,827] ERROR {org.apache.tomcat.util.net
> <http://org.apache.tomcat.util.net>.NioEndpoint$Poller} -
> {org.apache.tomcat.util.net
> <http://org.apache.tomcat.util.net>.NioEndpoint$Poller}java.lang.OutOfMemoryError:
> GC overhead limit exceeded*
>
> Regards,
> Firzhan
>
>
> --
> *Firzhan Naqash*
> Senior Software Engineer - Integration Platform Team
> WSO2 Inc. http://wso2.com
>
> email: firz...@wso2.com <lasan...@wso2.com>
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
> <http://firzhanblogger.blogspot.com/>  <http://suhothayan.blogspot.com/>*
> *twitter: https://twitter.com/firzhan007
> <https://twitter.com/firzhan007> | linked-in: 
> **https://www.linkedin.com/in/firzhan
> <https://www.linkedin.com/in/firzhan>*
>
> On Mon, Oct 12, 2015 at 10:51 AM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi All
>>
>> We have configured a SchedulerTask for the BPS cluster (2 workers and
>> manager fronted by nginx). The task runs every day 5.10 pm and deletes
>> FAILED instances. The cluster was up and running in the weekend but was
>> idle. Following error was observed.
>>
>>
>> TID: [-1] [] [2015-10-09 18:49:23,157] ERROR
>> {org.apache.ode.scheduler.simple.SimpleScheduler} -  Error during
>> SchedulerTask execution {org.apache.ode.scheduler.simple.SimpleScheduler}
>> com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast
>> instance is not active!
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.getService(ProxyRegistry.java:65)
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.(ProxyRegistry.java:53)
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:74)
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:72)
>> at
>> com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:51)
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getOrCreateRegistry(ProxyServiceImpl.java:110)
>> at
>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getDistributedObject(ProxyServiceImpl.java:118)
>> at
>> com.hazelcast.instance.HazelcastInstanceImpl.getDistributedObject(HazelcastInstanceImpl.java:390)
>> at
>> com.hazelcast.instance.HazelcastInstanceImpl.getMap(HazelcastInstanceImpl.java:192)
>> at
>> com.hazelcast.instance.HazelcastInstanceProxy.getMap(HazelcastInstanceProxy.java:75)
>> at
>> org.wso2.carbon.bpel.core.ode.integration.BPELServerImpl$ODEClusterImpl.getKnownNodes(BPELServerImpl.java:1009)
>> at
>> org.apache.ode.scheduler.simple.SimpleScheduler.updateHeartBeatAndGetStaleNodes(SimpleScheduler.java:848)
>> at
>> org.apache.ode.scheduler.simple.SimpleScheduler.access$800(SimpleScheduler.java:53)
>> at
>> org.apache.ode.scheduler.simple.SimpleScheduler$CheckStaleNodes.run(SimpleScheduler.java:1226)
>> at
>> org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:810)
>> at
>> org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:807)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>> {org.apache.tomcat.util.net.NioEndpoint$Poller} -
>> {org.apache.tomcat.util.net.NioEndpoint$Poller}
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>> TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>> {org.apache.tomcat.util.net.NioEndpoint$Poller} -
>> {org.apache.tomcat.util.net.NioEndpoint$Poller}
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>> TID: [-1] [] [2015-10-09 18:49:41,310] ERROR
>> {org.apache.tomcat.util.ne

[Dev] [BPS][BPMN]: Rest API - Create New Deployment

[Chathurika De Silva]

Hi

I am trying to use the $subject through jmeter. I am getting response code
201 which is the success code for deployment [1].

In the BPS logs i am observing the following

TID: [-1234] [] [2015-10-05 06:21:15,781]  INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
connection created successfully in read-write mode
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
TID: [-1234] [] [2015-10-05 06:21:15,823]  INFO
{org.activiti.engine.impl.bpmn.deployer.BpmnDeployer} -  Processing
resource manualTask.bpmn20.xml
{org.activiti.engine.impl.bpmn.deployer.BpmnDeployer}

The test is done in a Worker/Manager cluster fronted by Nginx with dep sync
enabled. For manual uploads it works fine with manager syncing the deployed
to the workers. But when done with the api there is no proper deployment
being done.

The jira [2] contains the debug logs of activiti and the script i have used.

[1] http://www.activiti.org/userguide/#_create_a_new_deployment
[2] https://wso2.org/jira/browse/BPS-892

Any help regarding this is highly appreciated.

Thank You
Erandi





-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][BPMN]: Rest API - Create New Deployment

[Chathurika De Silva]

@Firzhan

When uploading an artifact through the API where does it actually get
created?

Currently in the  cluster, the manager is the point of upload and the
workers get the artifacts through dep sync.

Can you please give an insight of how the deployment through the API is
working? Or could you direct me to any documentation explaining this
specific deployment model?

Your help on this is highly appreciated.


On Mon, Oct 5, 2015 at 12:36 PM, Vinod Kavinda <vi...@wso2.com> wrote:

> Hi Chathurika,
>
> You can use the BPMNUploaderService admin service instead.
>
> Regards,
> Vinod Kavinda
>
> On Mon, Oct 5, 2015 at 12:25 PM, Firzhan Naqash <firz...@wso2.com> wrote:
>
>> Hi Chaturika,
>>
>> When you are using the activiti rest-api, the process artifacts won't get
>> copied to the deployment/server/bpmn folder.
>> Thus it won't get synchronized with the rest of the nodes.
>>
>> When you upload the archived bar file, it copies to the respective
>> location and then passes the process artifacts to the activiti api.
>>
>>
>> Regards,
>> Firzhan
>>
>>
>> --
>> *Firzhan Naqash*
>> Senior Software Engineer - Integration Platform Team
>> WSO2 Inc. http://wso2.com
>>
>> email: firz...@wso2.com <lasan...@wso2.com>
>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>> blog: http://firzhanblogger.blogspot.com/
>> <http://firzhanblogger.blogspot.com/>  <http://suhothayan.blogspot.com/>*
>> *twitter: https://twitter.com/firzhan007
>> <https://twitter.com/firzhan007> | linked-in: 
>> **https://www.linkedin.com/in/firzhan
>> <https://www.linkedin.com/in/firzhan>*
>>
>> On Mon, Oct 5, 2015 at 12:15 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> I am trying to use the $subject through jmeter. I am getting response
>>> code 201 which is the success code for deployment [1].
>>>
>>> In the BPS logs i am observing the following
>>>
>>> TID: [-1234] [] [2015-10-05 06:21:15,781]  INFO
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
>>> connection created successfully in read-write mode
>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
>>> TID: [-1234] [] [2015-10-05 06:21:15,823]  INFO
>>> {org.activiti.engine.impl.bpmn.deployer.BpmnDeployer} -  Processing
>>> resource manualTask.bpmn20.xml
>>> {org.activiti.engine.impl.bpmn.deployer.BpmnDeployer}
>>>
>>> The test is done in a Worker/Manager cluster fronted by Nginx with dep
>>> sync enabled. For manual uploads it works fine with manager syncing the
>>> deployed to the workers. But when done with the api there is no proper
>>> deployment being done.
>>>
>>> The jira [2] contains the debug logs of activiti and the script i have
>>> used.
>>>
>>> [1] http://www.activiti.org/userguide/#_create_a_new_deployment
>>> [2] https://wso2.org/jira/browse/BPS-892
>>>
>>> Any help regarding this is highly appreciated.
>>>
>>> Thank You
>>> Erandi
>>>
>>>
>>>
>>>
>>>
>>> --
>>> *Chathurika Erandi*
>>> Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.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
>>
>>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
>
>


-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS 3.5.0] QA Cycle

[Chathurika De Silva]

Hi

For BPS 3.5.0 following sections will be tested. Please note that this will
be a non release oriented test.

1. BPEL
2. BPMN
3. BPMN Explorer (new feature in 3.5.0)
4. Human Tasks
5. Human Task Explorer (new feature in 3.5.0)
6. Migration from 3.2.0 to 3.5.0
7. Performance
8. Provided patches

Thank You
Erandi






-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarifications on CEP

[Chathurika De Silva]

Hi Suho

In a multi tenancy environment, with the increment of tenants how does the
supervisor slots behave? As in do they increment with the number of
tenants?

Best Regards
Erandi



On Mon, Sep 14, 2015 at 12:32 PM, Manorama Perera  wrote:

> Yes, this is because ML uses carbon.analytics 1.0.3-SNAPSHOT which
> requires carbon.analytics.common 5.0.2-SNAPSHOT version, but CEP uses
> carbon.analytics.common 5.0.1.
>
> We can change the carbon.analytics.common version to 5.0.1 in ML once DAS
> team do the required version changes in carbon.analytics.
>
> Thanks.
>
> On Mon, Sep 14, 2015 at 11:53 AM, Nirmal Fernando  wrote:
>
>> Thanks Sashika, I think this is due to recent version upgrades.
>>
>> @Mano could you please check?
>>
>> On Mon, Sep 14, 2015 at 11:30 AM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi Nirmal,
>>>
>>> I tried to install 'Machine learner core' feature in a fresh CEP pack
>>> (13th September Jenkins pack) , but couldn't continue installation due to
>>> below issue.
>>>
>>> Cannot complete the install because of a conflicting dependency.
>>> Software being installed: WSO2 Carbon - Machine Learner Core Feature
>>> 1.0.1.SNAPSHOT (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT)
>>> Software currently installed: WSO2 Carbon - Event Publisher Feature 5.0.1
>>> (org.wso2.carbon.event.publisher.feature.group 5.0.1) Only one of the
>>> following can be installed at once: WSO2 Carbon - Event Output Email
>>> Adapter Server Feature 5.0.1
>>> (org.wso2.carbon.event.output.adapter.email.server.feature.jar 5.0.1) WSO2
>>> Carbon - Event Output Email Adapter Server Feature 5.0.2.SNAPSHOT
>>> (org.wso2.carbon.event.output.adapter.email.server.feature.jar
>>> 5.0.2.SNAPSHOT) Cannot satisfy dependency: From: WSO2 Carbon - Event Output
>>> Email Adapter Server Feature 5.0.1
>>> (org.wso2.carbon.event.output.adapter.email.server.feature.group 5.0.1) To:
>>> org.wso2.carbon.event.output.adapter.email.server.feature.jar [5.0.1]
>>> Cannot satisfy dependency: From: WSO2 Carbon - Event Output Email Adapter
>>> Server Feature 5.0.2.SNAPSHOT
>>> (org.wso2.carbon.event.output.adapter.email.server.feature.group
>>> 5.0.2.SNAPSHOT) To:
>>> org.wso2.carbon.event.output.adapter.email.server.feature.jar
>>> [5.0.2.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Carbon - Event
>>> Publisher Output Adapter Feature 5.0.1
>>> (org.wso2.carbon.event.output.adapter.feature.group 5.0.1) To:
>>> org.wso2.carbon.event.output.adapter.email.server.feature.group [5.0.1]
>>> Cannot satisfy dependency: From: WSO2 Carbon - Event Publisher Feature
>>> 5.0.1 (org.wso2.carbon.event.publisher.feature.group 5.0.1) To:
>>> org.wso2.carbon.event.output.adapter.feature.group [5.0.1] Cannot satisfy
>>> dependency: From: WSO2 Carbon - Machine Learner Core Feature 1.0.1.SNAPSHOT
>>> (org.wso2.carbon.ml.core.feature.group 1.0.1.SNAPSHOT) To:
>>> org.wso2.carbon.event.output.adapter.email.server.feature.group
>>> [5.0.2.SNAPSHOT,5.1.0)
>>>
>>> Appreciate your help on this matter.
>>>
>>> Thanks.
>>>
>>> On Mon, Sep 14, 2015 at 10:02 AM, Nirmal Fernando 
>>> wrote:
>>>
 Shared the ML p2-repo with Sashika.

 On Sun, Sep 13, 2015 at 10:40 PM, Shavantha Weerasinghe <
 shavan...@wso2.com> wrote:

> Hi Sashika
>
> I got the p2 from lasantha last week will share tomorrow
> On Sep 12, 2015 10:24 PM, "Sashika Wijesinghe" 
> wrote:
>
>> Hi All,
>>
>> May I know the location to download P2 repository to add ML features
>> for CEP?
>>
>> Thanks
>>
>> On Wed, Sep 9, 2015 at 12:02 PM, Sashika Wijesinghe > > wrote:
>>
>>> Hi Lasantha,
>>>
>>> Thanks for the clarification.
>>>
>>> In the documentation it has mentioned that '-DworkerNode=true"
>>> argument will deactivate the UI bundle, So I thought there should not be
>>> any UI component when a user tried to access to the worker node.
>>> And I felt its good if we are not enabling the login page. because
>>> when I tried to login to the CEP using worker node I got '*login
>>> failed*' error message.
>>>
>>> Thanks & Regards,
>>>
>>> On Wed, Sep 9, 2015 at 11:21 AM, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Hi Sashika,

 Yes that is the usual behaviour for WSO2 servers when started with
 worker node true. The login page will be visible, but you won't be 
 allowed
 to login.

 Thanks,

 On 9 September 2015 at 11:16, Sashika Wijesinghe 
 wrote:

> Hi Suho/Lasantha,
>
> I'm working on CEP distributed mode set up. When a worker node is
> started using "-DworkerNode=true" argument, I expected that UI of the
> worker node should not be visible. However CEP login page is visible 
> when

Re: [Dev] APIM Test case clarification :Once the API is published, update it in GW

[Chathurika De Silva]

Hi

As an addition to what pavithra mentioned, an example for a use case,
Disabling chunked encdoing from gateway can be considered. Here we have to
associate a custom sequence and this can be done by following [1]

We can write a simple sequence as follows

sequence xmlns=http://ws.apache.org/ns/synapse;
name=admin--testapi1:v1.0--Out
   !--
   log level=full
property name  Message# === value=/property
/log
--
   property name=DISABLE_CHUNKING value=true scope=axis2 /
/sequence

[1]https://docs.wso2.com/display/AM180/Adding+Mediation+Extensions

Hope its helpful

Thank You
Erandi


On Mon, Mar 30, 2015 at 2:22 PM, Pavithra Madurangi pavit...@wso2.com
wrote:

 Hi Saneth,

 I guess the the steps should be something like

 - Add API
 - Now edit API definition
 e.g :

- Add a new handler (e.g
https://docs.wso2.com/display/AM180/Writing+Custom+Handlers)

Expected result : Check whether custom authentication handler is
 executed


- Add a new mediation logic (E.g

 http://nuwanzone.blogspot.com/2013/03/how-to-extend-mediaiton-flow-in-wso2.html
)

Expected result : Check whether this new sequence is executed.

 I'm adding Nirodha, Asanthi, Kala, Shamin and Chathurika to the thread for
 more clarification.

 On a related note this particular scenario can be divided into several
 test cases.
 @AsankaV,
 Can you please improve these kind of scenarios when you update the current
 test plan.

 Regards,
 Pavithra

 On Mon, Mar 30, 2015 at 1:44 PM, Saneth Dharmakeerthi sane...@wso2.com
 wrote:

 Hi all,

 I need to clarify the scope, steps and expected output of following test
 case to write a integration test.
 This test case has written in high level and its hard to define a scope
 on it.
 If there is any artefacts that can be used in the test process please
 share it with me.

 Test case : Once the API is published, update it in GW (e.g:- add a new
 handler, add a new mediation logic)
 Test case can be found in [1] under API Life Cycle tab and row 43


 [1]
 https://docs.google.com/a/wso2.com/spreadsheets/d/1SiktQWh463KZzr86ADqBnsyyHa2Tre-fIlGYvYRQfTQ/edit#gid=78


 Thanks and Best Regards,

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




 --
 *Pavithra Madurangi*
 Associate Technical Lead - QA.
 WSO2 Inc.: http://wso2.com/
 Mobile: 0777207357 / 0112747089




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppFactory] Error while creating an application

[Chathurika De Silva]

Hi

There a reported jira [1] which is similar to your exception. Maybe the
related fix will be a help to you

[1] https://wso2.org/jira/browse/APPFAC-2717

Thank You
Erandi

On Thu, Mar 12, 2015 at 3:06 PM, Fathima Dilhasha dilha...@wso2.com wrote:

 Hi,

 I am trying to create an application in the private cloud deployed in the
 remote machine at 192.168.57.4

 It gives the following error.

 *TID: [0] [AF] [2015-03-12 09:24:55,089] ERROR
 {module/lifecycle/lifecycle.jag} -  Error in calling manage generic
 artifact service JavaException:
 org.jaggeryjs.scriptengine.exceptions.ScriptException: Error occured while
 invoking the service {module/lifecycle/lifecycle.jag}*
 *TID: [0] [AF] [2015-03-12 09:24:55,089] ERROR
 {module/application/add/add.jag} -  Error while storing resource *
 *undefined {module/application/add/add.jag}*
 *TID: [0] [AF] [2015-03-12 09:24:55,089] ERROR
 {module/application/add/add.jag} -  Error while creating application *
 *Error while storing registry resource {module/application/add/add.jag}*
 *TID: [0] [AF] [2015-03-12 09:24:55,089] ERROR
 {JAGGERY.site.blocks.application.add.ajax.add:jag} -  Error while creating
 the applicationundefined {JAGGERY.site.blocks.application.add.ajax.add:jag}*
 *TID: [0] [AF] [2015-03-12 09:24:55,089] ERROR
 {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
  org.mozilla.javascript.JavaScriptException: Error while creating the
 applicationundefined (/appmgt/site/blocks/application/add/ajax/add.jag#89)
 {org.jaggeryjs.jaggery.core.manager.WebAppManager}*
 *org.jaggeryjs.scriptengine.exceptions.ScriptException:
 org.mozilla.javascript.JavaScriptException: Error while creating the
 applicationundefined (/appmgt/site/blocks/application/add/ajax/add.jag#89)*
 * at
 org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)*
 * at
 org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)*
 * at
 org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:541)*
 * at
 org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)*
 * at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)*
 * at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)*
 * at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)*
 * at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)*
 * at
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)*
 * at
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)*
 * at
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)*
 * at
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)*
 * at
 org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)*
 * at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)*
 * at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)*
 * at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)*
 * at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)*
 * at
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)*
 * at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)*
 * at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)*
 * at
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)*
 * at
 org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)*
 * at
 org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)*
 * at
 org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)*
 * at
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)*
 * at
 org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)*
 * at
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)*
 * at
 org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)*
 * at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)*
 * at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)*
 * at
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)*
 * at
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)*
 * at
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)*
 * at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)*
 * at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)*
 * at 

Re: [Dev] [AppFactory] Clarification regarding auto build / deploy functionality

[Chathurika De Silva]

Hi Danushka

Thank you for the clarification. Reported a jira [1]

[1] https://wso2.org/jira/browse/APPFAC-3045

Thank You
Erandi

On Wed, Mar 11, 2015 at 11:04 AM, Danushka Fernando danush...@wso2.com
wrote:

 I think this is how it is implemented now. Since we have a different job
 for the fork, We will need to have different configuration for fork. Thanks
 for reporting. Please create a jira. We will decide when to fix this.

 Thanks  Regards
 Danushka Fernando
 Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729

 On Wed, Mar 11, 2015 at 10:30 AM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi

 Currently in App Factory, the fork repository as well as the main
 repository is affected by the auto build/deploy configuration. Is this the
 functional requirement?

 Thank You
 Erandi

 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com

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





-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AppFactory] Clarification regarding auto build / deploy functionality

[Chathurika De Silva]

Hi

Currently in App Factory, the fork repository as well as the main
repository is affected by the auto build/deploy configuration. Is this the
functional requirement?

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] User permission update for Runtime Configs

[Chathurika De Silva]

Hi All

Since the permission model has changed we have to update our test cases
while testing. Since we are giving priority to testing we need additional
two days of testing time to get our test cases updated.

Thank You
Erandi



On Tue, Feb 10, 2015 at 4:43 PM, Amalka Subasinghe ama...@wso2.com wrote:

 the users who have create permissions, can delete resources

 On Tue, Feb 10, 2015 at 4:38 PM, Sewmini Jayaweera sewm...@wso2.com
 wrote:

 Hi Amalka,

  How about delete permission?
 As I understand it should be only admin, application owner, developer can
 delete from development environment is it ?


 Thank You,
 Sewmini

 Sewmini Jayaweera
 *Software Engineer - QA Team*
 Mobile: +94 (0) 773 381 250
 sewm...@wso2.com

 On Tue, Feb 10, 2015 at 12:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi

 One QA resource will be unavailable on 12th and 13th. So there will be a
 deviation around one day to the original estimate of one week because only
 one resource will be working on the above mentioned two days.

 Thank You
 Erandi

 On Tue, Feb 10, 2015 at 11:39 AM, Dimuthu Leelarathne dimut...@wso2.com
  wrote:

 Hi,

 We'll give a new setup tomorrow morning. Meanwhile please cover the
 breath in other areas that have not changed.

 thanks,
 dimuthu

 On Tue, Feb 10, 2015 at 11:20 AM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 Considering the above changes and the bug fixes that will be
 incorporated in the latest pack, there should be a new qa cycle on the
 latest pack. While considering the amount of test cases we have as well as
 the available qa resources (#2) it will take around one week to complete
 the test cycle after the pack release date.

 Thank You
 Erandi

 On Tue, Feb 10, 2015 at 11:18 AM, Manjula Rathnayake 
 manju...@wso2.com wrote:

 Hi all,

 Please note that only change with respect to existing permission
 model is that, appOwner is not allowed to create runtime configs in 
 Testing
 and Production stages. Configs will be copied at the time of
 promotion/deployment of application in Testing and Production stages.

 However, the permissions related to databases will not be changed
 from existing model where each stake holders of runtime environments are
 allowed to create databases in their environments. eg. QA can create
 databases on Testing but not in Production.

 thank you.


 On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe ama...@wso2.com
 wrote:

 Hi All,

 I'm going to do the following changes to the runtime configs
 (datasources, properties, external apis)

 - Create/update/read permissions will be as shown in the table after
 this fix.

 - The tenant admin also have similar permissions as appowner; he can
 only create in development stage and then resources will be propagated 
 to
 the testing and production environments via promoting.
 So, create resources in all environments checkbox, is not valid
 anymore, I'm removing it.




 development testing production
  appowner create x



 update x x x

 read x x x






  dev create x



 update x



 read x x







  qa create




 update
 x


 read x x







  devops create




 update

 x

 read
 x x






  admin create x



 update x x x

 read x x x

 Thanks
 Amalka


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




 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 Dimuthu Leelarathne
 Architect  Product Lead of App Factory

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

 Lean . Enterprise . Middleware




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com





 --

 Amalka Subasinghe

 WSO2 Inc.
 Mobile: +94 77 9401267




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] User permission update for Runtime Configs

[Chathurika De Silva]

Hi

Yes let's go ahead as planned.

Thank You
Erandi

On Wed, Feb 11, 2015 at 6:25 PM, Dimuthu Leelarathne dimut...@wso2.com
wrote:

 Hi,

 Could we still go ahead release beta on the 18th while you do the
 documentation?

 thanks,
 dimuthu


 On Wed, Feb 11, 2015 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 Since the permission model has changed we have to update our test cases
 while testing. Since we are giving priority to testing we need additional
 two days of testing time to get our test cases updated.

 Thank You
 Erandi



 On Tue, Feb 10, 2015 at 4:43 PM, Amalka Subasinghe ama...@wso2.com
 wrote:

 the users who have create permissions, can delete resources

 On Tue, Feb 10, 2015 at 4:38 PM, Sewmini Jayaweera sewm...@wso2.com
 wrote:

 Hi Amalka,

  How about delete permission?
 As I understand it should be only admin, application owner, developer
 can delete from development environment is it ?


 Thank You,
 Sewmini

 Sewmini Jayaweera
 *Software Engineer - QA Team*
 Mobile: +94 (0) 773 381 250
 sewm...@wso2.com

 On Tue, Feb 10, 2015 at 12:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi

 One QA resource will be unavailable on 12th and 13th. So there will be
 a deviation around one day to the original estimate of one week because
 only one resource will be working on the above mentioned two days.

 Thank You
 Erandi

 On Tue, Feb 10, 2015 at 11:39 AM, Dimuthu Leelarathne 
 dimut...@wso2.com wrote:

 Hi,

 We'll give a new setup tomorrow morning. Meanwhile please cover the
 breath in other areas that have not changed.

 thanks,
 dimuthu

 On Tue, Feb 10, 2015 at 11:20 AM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 Considering the above changes and the bug fixes that will be
 incorporated in the latest pack, there should be a new qa cycle on the
 latest pack. While considering the amount of test cases we have as well 
 as
 the available qa resources (#2) it will take around one week to complete
 the test cycle after the pack release date.

 Thank You
 Erandi

 On Tue, Feb 10, 2015 at 11:18 AM, Manjula Rathnayake 
 manju...@wso2.com wrote:

 Hi all,

 Please note that only change with respect to existing permission
 model is that, appOwner is not allowed to create runtime configs in 
 Testing
 and Production stages. Configs will be copied at the time of
 promotion/deployment of application in Testing and Production stages.

 However, the permissions related to databases will not be changed
 from existing model where each stake holders of runtime environments 
 are
 allowed to create databases in their environments. eg. QA can create
 databases on Testing but not in Production.

 thank you.


 On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe 
 ama...@wso2.com wrote:

 Hi All,

 I'm going to do the following changes to the runtime configs
 (datasources, properties, external apis)

 - Create/update/read permissions will be as shown in the table
 after this fix.

 - The tenant admin also have similar permissions as appowner; he
 can only create in development stage and then resources will be 
 propagated
 to the testing and production environments via promoting.
 So, create resources in all environments checkbox, is not valid
 anymore, I'm removing it.




 development testing production
  appowner create x



 update x x x

 read x x x






  dev create x



 update x



 read x x







  qa create




 update
 x


 read x x







  devops create




 update

 x

 read
 x x






  admin create x



 update x x x

 read x x x

 Thanks
 Amalka


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




 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 Dimuthu Leelarathne
 Architect  Product Lead of App Factory

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

 Lean . Enterprise . Middleware




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com





 --

 Amalka Subasinghe

 WSO2 Inc.
 Mobile: +94 77 9401267




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 Dimuthu Leelarathne
 Architect  Product Lead of App Factory

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

 Lean . Enterprise . Middleware




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] User permission update for Runtime Configs

[Chathurika De Silva]

Hi All

Considering the above changes and the bug fixes that will be incorporated
in the latest pack, there should be a new qa cycle on the latest pack.
While considering the amount of test cases we have as well as the available
qa resources (#2) it will take around one week to complete the test cycle
after the pack release date.

Thank You
Erandi

On Tue, Feb 10, 2015 at 11:18 AM, Manjula Rathnayake manju...@wso2.com
wrote:

 Hi all,

 Please note that only change with respect to existing permission model is
 that, appOwner is not allowed to create runtime configs in Testing and
 Production stages. Configs will be copied at the time of
 promotion/deployment of application in Testing and Production stages.

 However, the permissions related to databases will not be changed from
 existing model where each stake holders of runtime environments are allowed
 to create databases in their environments. eg. QA can create databases on
 Testing but not in Production.

 thank you.


 On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe ama...@wso2.com
 wrote:

 Hi All,

 I'm going to do the following changes to the runtime configs
 (datasources, properties, external apis)

 - Create/update/read permissions will be as shown in the table after this
 fix.

 - The tenant admin also have similar permissions as appowner; he can only
 create in development stage and then resources will be propagated to the
 testing and production environments via promoting.
 So, create resources in all environments checkbox, is not valid
 anymore, I'm removing it.




 development testing production
  appowner create x



 update x x x

 read x x x






  dev create x



 update x



 read x x







  qa create




 update
 x


 read x x







  devops create




 update

 x

 read
 x x






  admin create x



 update x x x

 read x x x

 Thanks
 Amalka


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




 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] User permission update for Runtime Configs

[Chathurika De Silva]

Hi

One QA resource will be unavailable on 12th and 13th. So there will be a
deviation around one day to the original estimate of one week because only
one resource will be working on the above mentioned two days.

Thank You
Erandi

On Tue, Feb 10, 2015 at 11:39 AM, Dimuthu Leelarathne dimut...@wso2.com
wrote:

 Hi,

 We'll give a new setup tomorrow morning. Meanwhile please cover the breath
 in other areas that have not changed.

 thanks,
 dimuthu

 On Tue, Feb 10, 2015 at 11:20 AM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 Considering the above changes and the bug fixes that will be incorporated
 in the latest pack, there should be a new qa cycle on the latest pack.
 While considering the amount of test cases we have as well as the available
 qa resources (#2) it will take around one week to complete the test cycle
 after the pack release date.

 Thank You
 Erandi

 On Tue, Feb 10, 2015 at 11:18 AM, Manjula Rathnayake manju...@wso2.com
 wrote:

 Hi all,

 Please note that only change with respect to existing permission model
 is that, appOwner is not allowed to create runtime configs in Testing and
 Production stages. Configs will be copied at the time of
 promotion/deployment of application in Testing and Production stages.

 However, the permissions related to databases will not be changed from
 existing model where each stake holders of runtime environments are allowed
 to create databases in their environments. eg. QA can create databases on
 Testing but not in Production.

 thank you.


 On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe ama...@wso2.com
 wrote:

 Hi All,

 I'm going to do the following changes to the runtime configs
 (datasources, properties, external apis)

 - Create/update/read permissions will be as shown in the table after
 this fix.

 - The tenant admin also have similar permissions as appowner; he can
 only create in development stage and then resources will be propagated to
 the testing and production environments via promoting.
 So, create resources in all environments checkbox, is not valid
 anymore, I'm removing it.




 development testing production
  appowner create x



 update x x x

 read x x x






  dev create x



 update x



 read x x







  qa create




 update
 x


 read x x







  devops create




 update

 x

 read
 x x






  admin create x



 update x x x

 read x x x

 Thanks
 Amalka


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




 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 Dimuthu Leelarathne
 Architect  Product Lead of App Factory

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

 Lean . Enterprise . Middleware




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API Manager 1.8.0: Out of the box work flows does not work for tenant

[Chathurika De Silva]

Hi All

While testing it's observed that work-flow scenarios are not working out of
the box for API Manager 1.8.0 and BPS 3.2.0.

In order to get it working had to apply patch 0009 to BPS [1]

This was an offline advice i have got and there's no indication anywhere in
documentation or wherever that this patch should be applied. [2]

Please provide directives in proceeding because the tenant scenarios won't
work out of the box.


1. https://wso2.org/jira/browse/CARBON-14841
2. https://docs.wso2.com/display/AM180/Configuring+Workflows+for+Tenants

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {chunk 13 packs}-14-09-2014/

[Chathurika De Silva]

Hi All


Is a new pack available?

Thanks
Erandi

On Fri, Oct 17, 2014 at 12:08 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 There is a newer pack,

 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/06-10-2014/

 But we plan to build another pack tonight



 On 17 October 2014 12:04, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi All

 Since we are going to start the release testing is it ok to use the packs
 in the location
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/29-09-2014/
 because it's the most recent for APIM

 Thank You
 Erandi

 On Wed, Sep 17, 2014 at 5:55 PM, Evanthika Amarasiri evanth...@wso2.com
 wrote:

 Hi Ratha,

 The OOM issue we noticed was due to the fact there was not enough memory
 in the cloud instance that these servers were running on. We will move the
 servers to an instance with more memory and see whether we see the same.
 You can ignore this issue for the moment.

 Regards,
 Evanthika

 On Tue, Sep 16, 2014 at 6:51 PM, Evanthika Amarasiri evanth...@wso2.com
  wrote:

 Hi Ratha,

 We are getting an OOM error and key manager/gatway nodes crash when
 regenerating tokens and doing some other operations. See [1]. We are
 blocked by this issue since we cannot continue testing on our clustered
 setup.  Also, we see some other issues with the store as well. See [2]. How
 soon can we get a new pack with fixes for these issues?

 [1] - https://wso2.org/jira/browse/APIMANAGER-2856
 [2] - https://wso2.org/jira/browse/APIMANAGER-2858

 Regards,
 Evanthika Amarasiri
 Senior Technical Lead - Quality Assurance
 Mobile: +94773125935

 wso2.com lean.enterprise.middleware

 On Mon, Sep 15, 2014 at 11:08 AM, Amila De Silva ami...@wso2.com
 wrote:

 Hi,
 Added the config element mentioned in [1] to specify a custom
 JWTGenerator. However, the default implementation will be picked if this
 change is absent.


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

 On Mon, Sep 15, 2014 at 9:18 AM, Pavithra Madurangi pavit...@wso2.com
  wrote:

 Hi Ratha,

 In the latest build, observed that configuration for self sign up to
 the store is missing from api-manager.xml (below config). Any particular
 reason for that?

 !--
 Use this configuration to control the self-sign-up capability
 in API store.
 --
 SelfSignUp
 !--
 Enable or disable the self-sign-up feature.
 --
 Enabledtrue/Enabled

 !--
 Self signed up users should be associated with a suitable
 subscriber
 role for them to be able to access the API store portal.
 This required
 parameter specifies which role should be used for that
 purpose. The role
 specified here must have the
 '/permission/admin/manage/api/subscribe'
 permission.
 --
 SubscriberRoleNamesubscriber/SubscriberRoleName
 /SelfSignUp

 On Mon, Sep 15, 2014 at 7:05 AM, Evanthika Amarasiri 
 evanth...@wso2.com wrote:

 Meaning, have you introduced new configurations since the  last
 release? We are planning to replace the packs and copy the conf folder 
 in
 the setup we have done. But last time we noticed you have introduced two
 new parameters to registry.xml  api manager.xmls.
 Hence the question.


 On Monday, September 15, 2014, Vijayaratha Vijayasingam 
 rat...@wso2.com wrote:

 What type of config change you mean?

 BTW, p2 repo is here[1] (not in the same folder since i got some
 svn conflicts).
 @Pavithra, i will check the p2 issue you reported..

 [1]
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/14_09_2014_p2/

 Thanks

 On 14 September 2014 22:37, Evanthika Amarasiri evanth...@wso2.com
  wrote:

 Hi Ratha,

 Have you guys done any configuration changes since the day you
 released 4th September packs?

 Regards,
 Evanthika

 On Sun, Sep 14, 2014 at 10:21 PM, Vijayaratha Vijayasingam 
 rat...@wso2.com wrote:

 Please find here;

 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/14-09-2014/

 Will commit p2 repo soon..

 Thanks..

 --
 -Ratha





 --
 -Ratha



 --
 Regards,
 Evanthika Amarasiri
 Senior Technical Lead - Quality Assurance
 Mobile: +94773125935

 wso2.com lean.enterprise.middleware


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




 --
 *Pavithra Madurangi*
 Associate Technical Lead - QA.
 WSO2 Inc.: http://wso2.com/
 Mobile: +94777207357 / +94773814110

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




 --
 *Amila De Silva*

 WSO2 Inc.
 mobile :(+94) 775119302


 ___
 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




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com

Re: [Dev] {chunk 13 packs}-14-09-2014/

[Chathurika De Silva]

Hi All

Since we are going to start the release testing is it ok to use the packs
in the location
https://svn.wso2.org/repos/wso2/scratch/chunk13-release/29-09-2014/ because
it's the most recent for APIM

Thank You
Erandi

On Wed, Sep 17, 2014 at 5:55 PM, Evanthika Amarasiri evanth...@wso2.com
wrote:

 Hi Ratha,

 The OOM issue we noticed was due to the fact there was not enough memory
 in the cloud instance that these servers were running on. We will move the
 servers to an instance with more memory and see whether we see the same.
 You can ignore this issue for the moment.

 Regards,
 Evanthika

 On Tue, Sep 16, 2014 at 6:51 PM, Evanthika Amarasiri evanth...@wso2.com
 wrote:

 Hi Ratha,

 We are getting an OOM error and key manager/gatway nodes crash when
 regenerating tokens and doing some other operations. See [1]. We are
 blocked by this issue since we cannot continue testing on our clustered
 setup.  Also, we see some other issues with the store as well. See [2]. How
 soon can we get a new pack with fixes for these issues?

 [1] - https://wso2.org/jira/browse/APIMANAGER-2856
 [2] - https://wso2.org/jira/browse/APIMANAGER-2858

 Regards,
 Evanthika Amarasiri
 Senior Technical Lead - Quality Assurance
 Mobile: +94773125935

 wso2.com lean.enterprise.middleware

 On Mon, Sep 15, 2014 at 11:08 AM, Amila De Silva ami...@wso2.com wrote:

 Hi,
 Added the config element mentioned in [1] to specify a custom
 JWTGenerator. However, the default implementation will be picked if this
 change is absent.


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

 On Mon, Sep 15, 2014 at 9:18 AM, Pavithra Madurangi pavit...@wso2.com
 wrote:

 Hi Ratha,

 In the latest build, observed that configuration for self sign up to
 the store is missing from api-manager.xml (below config). Any particular
 reason for that?

 !--
 Use this configuration to control the self-sign-up capability
 in API store.
 --
 SelfSignUp
 !--
 Enable or disable the self-sign-up feature.
 --
 Enabledtrue/Enabled

 !--
 Self signed up users should be associated with a suitable
 subscriber
 role for them to be able to access the API store portal.
 This required
 parameter specifies which role should be used for that
 purpose. The role
 specified here must have the
 '/permission/admin/manage/api/subscribe'
 permission.
 --
 SubscriberRoleNamesubscriber/SubscriberRoleName
 /SelfSignUp

 On Mon, Sep 15, 2014 at 7:05 AM, Evanthika Amarasiri 
 evanth...@wso2.com wrote:

 Meaning, have you introduced new configurations since the  last
 release? We are planning to replace the packs and copy the conf folder in
 the setup we have done. But last time we noticed you have introduced two
 new parameters to registry.xml  api manager.xmls.
 Hence the question.


 On Monday, September 15, 2014, Vijayaratha Vijayasingam 
 rat...@wso2.com wrote:

 What type of config change you mean?

 BTW, p2 repo is here[1] (not in the same folder since i got some svn
 conflicts).
 @Pavithra, i will check the p2 issue you reported..

 [1]
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/14_09_2014_p2/

 Thanks

 On 14 September 2014 22:37, Evanthika Amarasiri evanth...@wso2.com
 wrote:

 Hi Ratha,

 Have you guys done any configuration changes since the day you
 released 4th September packs?

 Regards,
 Evanthika

 On Sun, Sep 14, 2014 at 10:21 PM, Vijayaratha Vijayasingam 
 rat...@wso2.com wrote:

 Please find here;
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/14-09-2014/

 Will commit p2 repo soon..

 Thanks..

 --
 -Ratha





 --
 -Ratha



 --
 Regards,
 Evanthika Amarasiri
 Senior Technical Lead - Quality Assurance
 Mobile: +94773125935

 wso2.com lean.enterprise.middleware


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




 --
 *Pavithra Madurangi*
 Associate Technical Lead - QA.
 WSO2 Inc.: http://wso2.com/
 Mobile: +94777207357 / +94773814110

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




 --
 *Amila De Silva*

 WSO2 Inc.
 mobile :(+94) 775119302


 ___
 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




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Harshan Liyanage

[Chathurika De Silva]

Congratulations Harshan 

On Thu, Sep 18, 2014 at 9:35 AM, Sewwandi Perera sewwa...@wso2.com wrote:

 Congratulations Harshan...!!! :)

 On Thu, Sep 18, 2014 at 9:34 AM, Inosh Perera ino...@wso2.com wrote:

 Congrats Harshan!!! :)

 On Thu, Sep 18, 2014 at 9:33 AM, Niranjan Karunanandham 
 niran...@wso2.com wrote:

 Congrats Harshan!!


 On Thu, Sep 18, 2014 at 9:27 AM, Shanmugarajah Sinnathamby 
 s...@wso2.com wrote:

 Hi,

 Its my pleasure to welcome Harshan Liyanage  as a WSO2 Committer.
 Harshan has made great contributions to EMM product and other related
 products during the last few months and in recognition of his commitment
 and contributions, he has been voted as a committer.

 Harshan, welcome aboard and keep up the good work.

 Best Regards,
 Shan









 --
 *Shanmugarajah (Shan)*
 Director, Mobile Architecture,
 WSO2, Inc.; http://wso2.com
 Email: s...@wso2.com
 Mobile : +9448260
 Blog: http://shanfour.blogspot.com



 --
 *Shanmugarajah (Shan)*
 Director, Mobile Architecture,
 WSO2, Inc.; http://wso2.com
 Email: s...@wso2.com
 Mobile : +9448260
 Blog: http://shanfour.blogspot.com

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




 --

 *Niranjan Karunanandham*
 Senior Software Engineer - WSO2 Inc.
 WSO2 Inc.: http://www.wso2.com

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




 --
 Inosh Perera
 Software Engineer, WSO2 Inc.
 Tel: 0785293686

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




 --
 Sewwandi Perera
 Software Engineer

 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 mobile: +94-713765098

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




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi Chamila

I cannot find the mentioned resource in the 04/09/2014 pack. I followed the
steps given in the README.txt to migrate the database.

Thank You
Erandi


On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake chami...@wso2.com
wrote:

 Hi Chathurika,
 There is a new resource migration-1.7.0_to_1.7.1 to modify the database.
 it creates the related column SUBS_CREATE_STATE (which is mentioned in
 the error log). Did you use that one? I think this might be the problem.


 On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 The migration cannot be tested in the 04/09/2014 due to the following
 issue, since none of the migrated APIs can be retrieved. Testing is
 currently blocking.

 https://wso2.org/jira/browse/APIMANAGER-2799

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 I have reopened the issue APIMANAGER-2662 because this issue should be
 fixed and shipped in a newer revision or as a patch itself.

 Thank You




 On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 I'll create a small java client to modify the apis in the
 synapse-config/default/api folder.
 Thanks,
 Chamila.


 On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote:

 We should be able to write a simple script or java client to do this
 right?

 Thanks,
 NuwanD.


 On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 As i understand regarding APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two
 workarounds.

 1. As mentioned in the readme.txt., edit *each* api xml in the
 APIM_1.7.0/repository/deployment/server/synapse-config/default/api
 directory.
Replace
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/
with
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
 property name=configKey
 value=gov:/apimgt/statistics/ga-config.xml/
 /handler

 2. Manually go to implement tab in the edit mode of *each* of the
 APIs and click manage

 If a customer wants to migrate hundreds of APIs, is it a feasible
 solution from the customer's perspective? Ideally when a customer 
 migrates
 from an older version, they should be able to work with their data as 
 they
 worked before the migration. Since invoking an API is the core
 functionality of API Manager, is it really feasible in asking the 
 customer
 to follow above 1st or 2nd method?

 From the customer/user perspective above given solution cannot be
 accepted. In my opinion this should be handled by our side without asking
 the customer/user to take extra effort in bringing his migrated data to
 work properly.

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 Hi Chathurika,

 Issues mentioned in the previous mail are fixed in the latest
 17/08/2014 pack[1]. There are some updates done to the migration tool
 readme.txt file as well. You can proceed with the migration testing. For
 the issue APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 please read the
 comments in the jira (these instructions are added to the readme.txt).

 [1]
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
 Thanks,
 Chamila.


 On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662
 - issue status - inprogress. This is the main scenario of the 
 migration.
 Thus the fix for this is crucial to proceed with the proper user 
 scenario
 based testing
 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698
 - issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669
 - issue status - reopened. The resources added before the migration is 
 not
 copied correctly
 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672
 - issue status - reopened (due to APIMANAGER-2669
 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue
 cannot be verified until APIMANAGER-2698
 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.

 Since the above mentioned issues are blocking, the migration
 testing cannot be proceeded for the 05/08/2014 pack

 Thank You


 On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 The ticket has been resolved, please continue with testing


 On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com
 wrote:

 Seems the stack trace is different from what was originally
 reported for this ticket, can we have a closer look at this? Please 
 ping me
 when you get back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

As we are shipping the final pack to the customer, any inclusions should be
in the released pack. So until this is included in the pack itself, the
migration cannot be tested and will remain in the status blocked.


On Fri, Sep 5, 2014 at 12:35 PM, Chamila Adhikarinayake chami...@wso2.com
wrote:

 this can be found in the svn location[1] but is missing in the pack

 [1]
 https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.7.1/modules/distribution/resources/migration-1.7.0_to_1.7.1/


 On Fri, Sep 5, 2014 at 12:05 PM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi Chamila

 I cannot find the mentioned resource in the 04/09/2014 pack. I followed
 the steps given in the README.txt to migrate the database.

 Thank You
 Erandi


 On Fri, Sep 5, 2014 at 11:57 AM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 Hi Chathurika,
 There is a new resource migration-1.7.0_to_1.7.1 to modify the
 database. it creates the related column SUBS_CREATE_STATE (which is
 mentioned in the error log). Did you use that one? I think this might be
 the problem.


 On Fri, Sep 5, 2014 at 11:18 AM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 The migration cannot be tested in the 04/09/2014 due to the following
 issue, since none of the migrated APIs can be retrieved. Testing is
 currently blocking.

 https://wso2.org/jira/browse/APIMANAGER-2799

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 I have reopened the issue APIMANAGER-2662 because this issue should be
 fixed and shipped in a newer revision or as a patch itself.

 Thank You




 On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 I'll create a small java client to modify the apis in the
 synapse-config/default/api folder.
 Thanks,
 Chamila.


 On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote:

 We should be able to write a simple script or java client to do this
 right?

 Thanks,
 NuwanD.


 On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 As i understand regarding APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 following are the
 two workarounds.

 1. As mentioned in the readme.txt., edit *each* api xml in the
 APIM_1.7.0/repository/deployment/server/synapse-config/default/api
 directory.
Replace
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/
with
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
 property name=configKey
 value=gov:/apimgt/statistics/ga-config.xml/
 /handler

 2. Manually go to implement tab in the edit mode of *each* of the
 APIs and click manage

 If a customer wants to migrate hundreds of APIs, is it a feasible
 solution from the customer's perspective? Ideally when a customer 
 migrates
 from an older version, they should be able to work with their data as 
 they
 worked before the migration. Since invoking an API is the core
 functionality of API Manager, is it really feasible in asking the 
 customer
 to follow above 1st or 2nd method?

 From the customer/user perspective above given solution cannot be
 accepted. In my opinion this should be handled by our side without 
 asking
 the customer/user to take extra effort in bringing his migrated data to
 work properly.

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 Hi Chathurika,

 Issues mentioned in the previous mail are fixed in the latest
 17/08/2014 pack[1]. There are some updates done to the migration tool
 readme.txt file as well. You can proceed with the migration testing. 
 For
 the issue APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 please read the
 comments in the jira (these instructions are added to the readme.txt).

 [1]
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
 Thanks,
 Chamila.


 On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662
 - issue status - inprogress. This is the main scenario of the 
 migration.
 Thus the fix for this is crucial to proceed with the proper user 
 scenario
 based testing
 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698
 - issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669
 - issue status - reopened. The resources added before the migration 
 is not
 copied correctly
 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672
 - issue status - reopened (due to APIMANAGER-2669
 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue
 cannot be verified until APIMANAGER-2698
 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed

[Dev] Cannot proceed with testing of API-M 1.7.1 testing with MSSQL

[Chathurika De Silva]

Hi All

I connected the pack released on 04/09 to the MSSQL database i used with a
previous 1.7.1 pack and the following error occurred.

https://wso2.org/jira/browse/APIMANAGER-2802

Please provide directives in proceeding.

Thank You
Erandi

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Akila Ravihansa Perera

[Chathurika De Silva]

Congratulations Akila


On Thu, Sep 4, 2014 at 3:43 PM, Sewwandi Perera sewwa...@wso2.com wrote:

 Congratulations Akila...!!!


 On Thu, Sep 4, 2014 at 3:13 PM, Dumidu Handakumbura dum...@wso2.com
 wrote:

 Congrats Akila.


 On Thu, Sep 4, 2014 at 2:53 PM, Dunith Dhanushka dun...@wso2.com wrote:

 Congrats Akila!


 On Thu, Sep 4, 2014 at 2:36 PM, Nirmal Fernando nir...@wso2.com wrote:

 Congratz Akila!


 On Thu, Sep 4, 2014 at 2:30 PM, Milinda Perera milin...@wso2.com
 wrote:

 Congratulations Akila 


 On Thu, Sep 4, 2014 at 2:15 PM, Vijitha Ekanayake vijit...@wso2.com
 wrote:

 Congratulations Akila ..!!!


 On Thu, Sep 4, 2014 at 1:19 PM, Lakmal Warusawithana lak...@wso2.com
  wrote:

 Hi all,

 It's my pleasure to announce Akila as a WSO2 Committer. Akila has
 done great contributions to Apache Stratos and WSO2 Private PaaS 
 products.
 And in recognition of his contribution he has been voted as a WSO2 
 commiter.

 Akila, welcome aboard and keep up the good work!.

 --
 Lakmal Warusawithana
 Vice President, Apache Stratos
 Director - Cloud Architecture; WSO2 Inc.
 Mobile : +94714289692
 Blog : http://lakmalsview.blogspot.com/


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




 --
 Vijitha Ekanayake
 *Software Engineer*
 Mobile : +94 (0) 777 247339
 vijit...@wso2.com

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




 --
 Milinda Perera
 Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


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




 --

 Thanks  regards,
 Nirmal

 Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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




 --
 Regards,

 Dunith Dhanushka,
 Senior Software Engineer - BAM,
 WSO2 Inc,

 Mobile - +94 71 8615744
 Blog - dunithd.wordpress.com http://blog.dunith.com
 Twitter - @dunithd http://twitter.com/dunithd

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




 --
 *Dumidu Handakumbura*
 Software Engineer - QA
 WSO2 Inc; http://www.wso2.com/.
 Mobile;
 *+9406740 %2B9406740 *

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




 --
 Sewwandi Perera
 Software Engineer

 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 mobile: +94-713765098

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




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

The migration cannot be tested in the 04/09/2014 due to the following
issue, since none of the migrated APIs can be retrieved. Testing is
currently blocking.

https://wso2.org/jira/browse/APIMANAGER-2799

Thank You
Erandi



On Mon, Aug 18, 2014 at 1:45 PM, Chathurika De Silva chathuri...@wso2.com
wrote:

 Hi Chamila

 I have reopened the issue APIMANAGER-2662 because this issue should be
 fixed and shipped in a newer revision or as a patch itself.

 Thank You




 On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com
  wrote:

 I'll create a small java client to modify the apis in the
 synapse-config/default/api folder.
 Thanks,
 Chamila.


 On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote:

 We should be able to write a simple script or java client to do this
 right?

 Thanks,
 NuwanD.


 On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 As i understand regarding APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two
 workarounds.

 1. As mentioned in the readme.txt., edit *each* api xml in the
 APIM_1.7.0/repository/deployment/server/synapse-config/default/api
 directory.
Replace
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/
with
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
 property name=configKey
 value=gov:/apimgt/statistics/ga-config.xml/
 /handler

 2. Manually go to implement tab in the edit mode of *each* of the APIs
 and click manage

 If a customer wants to migrate hundreds of APIs, is it a feasible
 solution from the customer's perspective? Ideally when a customer migrates
 from an older version, they should be able to work with their data as they
 worked before the migration. Since invoking an API is the core
 functionality of API Manager, is it really feasible in asking the customer
 to follow above 1st or 2nd method?

 From the customer/user perspective above given solution cannot be
 accepted. In my opinion this should be handled by our side without asking
 the customer/user to take extra effort in bringing his migrated data to
 work properly.

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 Hi Chathurika,

 Issues mentioned in the previous mail are fixed in the latest
 17/08/2014 pack[1]. There are some updates done to the migration tool
 readme.txt file as well. You can proceed with the migration testing. For
 the issue APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 please read the
 comments in the jira (these instructions are added to the readme.txt).

 [1]
 https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
 Thanks,
 Chamila.


 On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 -
 issue status - inprogress. This is the main scenario of the migration. 
 Thus
 the fix for this is crucial to proceed with the proper user scenario 
 based
 testing
 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 -
 issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 -
 issue status - reopened. The resources added before the migration is not
 copied correctly
 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 -
 issue status - reopened (due to APIMANAGER-2669
 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot
 be verified until APIMANAGER-2698
 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.

 Since the above mentioned issues are blocking, the migration testing
 cannot be proceeded for the 05/08/2014 pack

 Thank You


 On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 The ticket has been resolved, please continue with testing


 On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com
 wrote:

 Seems the stack trace is different from what was originally
 reported for this ticket, can we have a closer look at this? Please 
 ping me
 when you get back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi

 We started to test the migration with the 05/08/2014 pack and
 APIMANAGER-2529 is reopened. This is currently blocking the testing

 Thank You


 On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi,

 We have covered entire cycle of testing with 29th pack.But untill
 we get the above mentioned issues fixed,we cannot proceed with 
 migration
 testing in API Manager 1.7.1 further.

 Thank you


 On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As of today (01.08.2014) the migration test is being done

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi Chamila

As i understand regarding APIMANAGER-2662
https://wso2.org/jira/browse/APIMANAGER-2662 following are the two
workarounds.

1. As mentioned in the readme.txt., edit *each* api xml in the
APIM_1.7.0/repository/deployment/server/synapse-config/default/api
directory.
   Replace
handler
class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/
   with
handler
class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
property name=configKey
value=gov:/apimgt/statistics/ga-config.xml/
/handler

2. Manually go to implement tab in the edit mode of *each* of the APIs and
click manage

If a customer wants to migrate hundreds of APIs, is it a feasible  solution
from the customer's perspective? Ideally when a customer migrates from an
older version, they should be able to work with their data as they worked
before the migration. Since invoking an API is the core functionality of
API Manager, is it really feasible in asking the customer to follow above
1st or 2nd method?

From the customer/user perspective above given solution cannot be accepted.
In my opinion this should be handled by our side without asking the
customer/user to take extra effort in bringing his migrated data to work
properly.

Thank You
Erandi



On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com
wrote:

 Hi Chathurika,

 Issues mentioned in the previous mail are fixed in the latest 17/08/2014
 pack[1]. There are some updates done to the migration tool readme.txt file
 as well. You can proceed with the migration testing. For the issue
 APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please
 read the comments in the jira (these instructions are added to the
 readme.txt).

 [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
 Thanks,
 Chamila.


 On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 -
 issue status - inprogress. This is the main scenario of the migration. Thus
 the fix for this is crucial to proceed with the proper user scenario based
 testing
 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 -
 issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 -
 issue status - reopened. The resources added before the migration is not
 copied correctly
 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 -
 issue status - reopened (due to APIMANAGER-2669
 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be
 verified until APIMANAGER-2698
 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.

 Since the above mentioned issues are blocking, the migration testing
 cannot be proceeded for the 05/08/2014 pack

 Thank You


 On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com
  wrote:

 The ticket has been resolved, please continue with testing


 On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com
 wrote:

 Seems the stack trace is different from what was originally reported
 for this ticket, can we have a closer look at this? Please ping me when you
 get back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi

 We started to test the migration with the 05/08/2014 pack and
 APIMANAGER-2529 is reopened. This is currently blocking the testing

 Thank You


 On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi,

 We have covered entire cycle of testing with 29th pack.But untill we
 get the above mentioned issues fixed,we cannot proceed with migration
 testing in API Manager 1.7.1 further.

 Thank you


 On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As of today (01.08.2014) the migration test is being done with the
 API Manager pack (29/07/2014)

 The issue APIMANAGER-2559 is now fixed and thus closed after
 verifying in the above mentioned pack.

 Furthermore a smoke test was done in the windows environment for the
 migration as well as for basic API Manager scenarios.

 Thank You






 On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I conducted a test on windows environment to verify APIMANAGER-2559

 This is issue is fixed for super tenant but not for other tenants
 due to APIMANAGER-2529. Both of the above issues are reopened since 
 it's
 blocking tenant related data migration.


 Thanks and best regards



 On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I am going to conduct a testing round in Windows to verify
 APIMANAGER-2559. Will circle back to you once i am done.

 Thank You



 On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi Chamila

I have reopened the issue APIMANAGER-2662 because this issue should be
fixed and shipped in a newer revision or as a patch itself.

Thank You




On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com
wrote:

 I'll create a small java client to modify the apis in the
 synapse-config/default/api folder.
 Thanks,
 Chamila.


 On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote:

 We should be able to write a simple script or java client to do this
 right?

 Thanks,
 NuwanD.


 On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi Chamila

 As i understand regarding APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two
 workarounds.

 1. As mentioned in the readme.txt., edit *each* api xml in the
 APIM_1.7.0/repository/deployment/server/synapse-config/default/api
 directory.
Replace
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/
with
 handler
 class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
 property name=configKey
 value=gov:/apimgt/statistics/ga-config.xml/
 /handler

 2. Manually go to implement tab in the edit mode of *each* of the APIs
 and click manage

 If a customer wants to migrate hundreds of APIs, is it a feasible
 solution from the customer's perspective? Ideally when a customer migrates
 from an older version, they should be able to work with their data as they
 worked before the migration. Since invoking an API is the core
 functionality of API Manager, is it really feasible in asking the customer
 to follow above 1st or 2nd method?

 From the customer/user perspective above given solution cannot be
 accepted. In my opinion this should be handled by our side without asking
 the customer/user to take extra effort in bringing his migrated data to
 work properly.

 Thank You
 Erandi



 On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake 
 chami...@wso2.com wrote:

 Hi Chathurika,

 Issues mentioned in the previous mail are fixed in the latest
 17/08/2014 pack[1]. There are some updates done to the migration tool
 readme.txt file as well. You can proceed with the migration testing. For
 the issue APIMANAGER-2662
 https://wso2.org/jira/browse/APIMANAGER-2662 please read the
 comments in the jira (these instructions are added to the readme.txt).

 [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
 Thanks,
 Chamila.


 On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As per the pack released on 05/08/2014 following is the status

 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 -
 issue status - inprogress. This is the main scenario of the migration. 
 Thus
 the fix for this is crucial to proceed with the proper user scenario based
 testing
 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 -
 issue status - reopened. This issue corrupts the entire database.
 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 -
 issue status - reopened. The resources added before the migration is not
 copied correctly
 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 -
 issue status - reopened (due to APIMANAGER-2669
 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot
 be verified until APIMANAGER-2698
 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.

 Since the above mentioned issues are blocking, the migration testing
 cannot be proceeded for the 05/08/2014 pack

 Thank You


 On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 The ticket has been resolved, please continue with testing


 On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com
 wrote:

 Seems the stack trace is different from what was originally reported
 for this ticket, can we have a closer look at this? Please ping me when 
 you
 get back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi

 We started to test the migration with the 05/08/2014 pack and
 APIMANAGER-2529 is reopened. This is currently blocking the testing

 Thank You


 On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi,

 We have covered entire cycle of testing with 29th pack.But untill
 we get the above mentioned issues fixed,we cannot proceed with 
 migration
 testing in API Manager 1.7.1 further.

 Thank you


 On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As of today (01.08.2014) the migration test is being done with
 the API Manager pack (29/07/2014)

 The issue APIMANAGER-2559 is now fixed and thus closed after
 verifying in the above mentioned pack.

 Furthermore a smoke test was done in the windows environment for
 the migration as well as for basic API Manager scenarios.

 Thank You






 On Thu, Jul 31, 2014 at 6:09 PM, Chathurika

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

As per the pack released on 05/08/2014 following is the status

1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue
status - inprogress. This is the main scenario of the migration. Thus the
fix for this is crucial to proceed with the proper user scenario based
testing
2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue
status - reopened. This issue corrupts the entire database.
3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue
status - reopened. The resources added before the migration is not copied
correctly
3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue
status - reopened (due to APIMANAGER-2669
https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be
verified until APIMANAGER-2698
https://wso2.org/jira/browse/APIMANAGER-2698 is fixed.

Since the above mentioned issues are blocking, the migration testing cannot
be proceeded for the 05/08/2014 pack

Thank You


On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 The ticket has been resolved, please continue with testing


 On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote:

 Seems the stack trace is different from what was originally reported for
 this ticket, can we have a closer look at this? Please ping me when you get
 back to your seat. Thanks


 On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi

 We started to test the migration with the 05/08/2014 pack and
 APIMANAGER-2529 is reopened. This is currently blocking the testing

 Thank You


 On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com
  wrote:

 Hi,

 We have covered entire cycle of testing with 29th pack.But untill we
 get the above mentioned issues fixed,we cannot proceed with migration
 testing in API Manager 1.7.1 further.

 Thank you


 On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 As of today (01.08.2014) the migration test is being done with the API
 Manager pack (29/07/2014)

 The issue APIMANAGER-2559 is now fixed and thus closed after verifying
 in the above mentioned pack.

 Furthermore a smoke test was done in the windows environment for the
 migration as well as for basic API Manager scenarios.

 Thank You






 On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I conducted a test on windows environment to verify APIMANAGER-2559

 This is issue is fixed for super tenant but not for other tenants due
 to APIMANAGER-2529. Both of the above issues are reopened since it's
 blocking tenant related data migration.


 Thanks and best regards



 On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I am going to conduct a testing round in Windows to verify
 APIMANAGER-2559. Will circle back to you once i am done.

 Thank You



 On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi All

 We are currently carrying on the $subject and please find the
 update as of 30.07.2014

 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva

 *Environment details*:

 Operating System : Linux
 Java Version/Java VM :jdk1.7.0 (Oracle)
 Packs : APIM 1.7.1
 DBMS: mysql and oracle
 Browser : Firefox 29.0 and Chrome 35.0
 Set up :Stand alone pack

 *Issues reported - Priority (Blocker)*

 APIMANAGER-2529  - This issue is blocking the actual migration
 process but a workaround has been given.The latest documentation 
 should be
 updated accordingly
 APIMANAGER-2534 - This issue is related to missing information
 after the migration
 APIMANAGER-2535 - HTTP verbs are not correctly copied to the
 migrated APIs.
 APIMANAGER-2672 - When versions are created. HTTP verbs are not
 correctly copied for them
 APIMANAGER-2662 - Cannot invoke an API which is in state published
 after migration.

 *Problems encountered: specific to oracle*

 Oracle database script of API Manager 1.6.0 should be updated to
 work with workflows. This is blocking the migration testing related to
 workflows.

 In summary as of today, the migration test scenarios cannot be
 fully covered due to above reported  issues.







 Thank you,

 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




 --
 *Chathurika Erandi

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi

We started to test the migration with the 05/08/2014 pack and
APIMANAGER-2529 is reopened. This is currently blocking the testing

Thank You


On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com
wrote:

 Hi,

 We have covered entire cycle of testing with 29th pack.But untill we get
 the above mentioned issues fixed,we cannot proceed with migration testing
 in API Manager 1.7.1 further.

 Thank you


 On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com
 wrote:

 Hi All

 As of today (01.08.2014) the migration test is being done with the API
 Manager pack (29/07/2014)

 The issue APIMANAGER-2559 is now fixed and thus closed after verifying in
 the above mentioned pack.

 Furthermore a smoke test was done in the windows environment for the
 migration as well as for basic API Manager scenarios.

 Thank You






 On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I conducted a test on windows environment to verify APIMANAGER-2559

 This is issue is fixed for super tenant but not for other tenants due to
 APIMANAGER-2529. Both of the above issues are reopened since it's blocking
 tenant related data migration.


 Thanks and best regards



 On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I am going to conduct a testing round in Windows to verify
 APIMANAGER-2559. Will circle back to you once i am done.

 Thank You



 On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage 
 chali...@wso2.com wrote:

 Hi All

 We are currently carrying on the $subject and please find the update
 as of 30.07.2014

 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva

 *Environment details*:

 Operating System : Linux
 Java Version/Java VM :jdk1.7.0 (Oracle)
 Packs : APIM 1.7.1
 DBMS: mysql and oracle
 Browser : Firefox 29.0 and Chrome 35.0
 Set up :Stand alone pack

 *Issues reported - Priority (Blocker)*

 APIMANAGER-2529  - This issue is blocking the actual migration process
 but a workaround has been given.The latest documentation should be updated
 accordingly
 APIMANAGER-2534 - This issue is related to missing information after
 the migration
 APIMANAGER-2535 - HTTP verbs are not correctly copied to the migrated
 APIs.
 APIMANAGER-2672 - When versions are created. HTTP verbs are not
 correctly copied for them
 APIMANAGER-2662 - Cannot invoke an API which is in state published
 after migration.

 *Problems encountered: specific to oracle*

 Oracle database script of API Manager 1.6.0 should be updated to work
 with workflows. This is blocking the migration testing related to
 workflows.

 In summary as of today, the migration test scenarios cannot be fully
 covered due to above reported  issues.







 Thank you,

 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

As of today (01.08.2014) the migration test is being done with the API
Manager pack (29/07/2014)

The issue APIMANAGER-2559 is now fixed and thus closed after verifying in
the above mentioned pack.

Furthermore a smoke test was done in the windows environment for the
migration as well as for basic API Manager scenarios.

Thank You






On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com
wrote:

 Hi All

 I conducted a test on windows environment to verify APIMANAGER-2559

 This is issue is fixed for super tenant but not for other tenants due to
 APIMANAGER-2529. Both of the above issues are reopened since it's blocking
 tenant related data migration.


 Thanks and best regards



 On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 I am going to conduct a testing round in Windows to verify
 APIMANAGER-2559. Will circle back to you once i am done.

 Thank You



 On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage chali...@wso2.com
 wrote:

 Hi All

 We are currently carrying on the $subject and please find the update as
 of 30.07.2014

 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva

 *Environment details*:

 Operating System : Linux
 Java Version/Java VM :jdk1.7.0 (Oracle)
 Packs : APIM 1.7.1
 DBMS: mysql and oracle
 Browser : Firefox 29.0 and Chrome 35.0
 Set up :Stand alone pack

 *Issues reported - Priority (Blocker)*

 APIMANAGER-2529  - This issue is blocking the actual migration process
 but a workaround has been given.The latest documentation should be updated
 accordingly
 APIMANAGER-2534 - This issue is related to missing information after the
 migration
 APIMANAGER-2535 - HTTP verbs are not correctly copied to the migrated
 APIs.
 APIMANAGER-2672 - When versions are created. HTTP verbs are not
 correctly copied for them
 APIMANAGER-2662 - Cannot invoke an API which is in state published after
 migration.

 *Problems encountered: specific to oracle*

 Oracle database script of API Manager 1.6.0 should be updated to work
 with workflows. This is blocking the migration testing related to
 workflows.

 In summary as of today, the migration test scenarios cannot be fully
 covered due to above reported  issues.







 Thank you,

 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

I conducted a test on windows environment to verify APIMANAGER-2559

This is issue is fixed for super tenant but not for other tenants due to
APIMANAGER-2529. Both of the above issues are reopened since it's blocking
tenant related data migration.


Thanks and best regards



On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva chathuri...@wso2.com
wrote:

 Hi All

 I am going to conduct a testing round in Windows to verify
 APIMANAGER-2559. Will circle back to you once i am done.

 Thank You



 On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage chali...@wso2.com
 wrote:

 Hi All

 We are currently carrying on the $subject and please find the update as
 of 30.07.2014

 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva

 *Environment details*:

 Operating System : Linux
 Java Version/Java VM :jdk1.7.0 (Oracle)
 Packs : APIM 1.7.1
 DBMS: mysql and oracle
 Browser : Firefox 29.0 and Chrome 35.0
 Set up :Stand alone pack

 *Issues reported - Priority (Blocker)*

 APIMANAGER-2529  - This issue is blocking the actual migration process
 but a workaround has been given.The latest documentation should be updated
 accordingly
 APIMANAGER-2534 - This issue is related to missing information after the
 migration
 APIMANAGER-2535 - HTTP verbs are not correctly copied to the migrated
 APIs.
 APIMANAGER-2672 - When versions are created. HTTP verbs are not correctly
 copied for them
 APIMANAGER-2662 - Cannot invoke an API which is in state published after
 migration.

 *Problems encountered: specific to oracle*

 Oracle database script of API Manager 1.6.0 should be updated to work
 with workflows. This is blocking the migration testing related to
 workflows.

 In summary as of today, the migration test scenarios cannot be fully
 covered due to above reported  issues.







 Thank you,

 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.

[Chathurika De Silva]

Hi All

I am going to conduct a testing round in Windows to verify APIMANAGER-2559.
Will circle back to you once i am done.

Thank You



On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage chali...@wso2.com
wrote:

 Hi All

 We are currently carrying on the $subject and please find the update as of
 30.07.2014

 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva

 *Environment details*:

 Operating System : Linux
 Java Version/Java VM :jdk1.7.0 (Oracle)
 Packs : APIM 1.7.1
 DBMS: mysql and oracle
 Browser : Firefox 29.0 and Chrome 35.0
 Set up :Stand alone pack

 *Issues reported - Priority (Blocker)*

 APIMANAGER-2529  - This issue is blocking the actual migration process but
 a workaround has been given.The latest documentation should be updated
 accordingly
 APIMANAGER-2534 - This issue is related to missing information after the
 migration
 APIMANAGER-2535 - HTTP verbs are not correctly copied to the migrated
 APIs.
 APIMANAGER-2672 - When versions are created. HTTP verbs are not correctly
 copied for them
 APIMANAGER-2662 - Cannot invoke an API which is in state published after
 migration.

 *Problems encountered: specific to oracle*

 Oracle database script of API Manager 1.6.0 should be updated to work with
 workflows. This is blocking the migration testing related to workflows.

 In summary as of today, the migration test scenarios cannot be fully
 covered due to above reported  issues.







 Thank you,

 --
 *Chalitha Maheshwari*
 Software Engineer-QA,
 WSO2 Inc.

 *E-mail:* chali...@wso2.com
 *Mobile: *+94710 411 112




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Business Rule Server 2.1.0 (Ch-11) - Testing update

[Chathurika De Silva]

Hi

Test cases added and related samples can be found attached with the
following issue
https://wso2.org/jira/browse/BRS-88

Best Regards
Erandi


On Fri, May 16, 2014 at 2:05 PM, Waruna Jayaweera waru...@wso2.com wrote:

 Hi,
 We need to test Decision table samples too. Please add that to the doc.


 On Mon, May 12, 2014 at 5:57 PM, Sandapa Handakumbura sand...@wso2.comwrote:

 Hi All,

 We have been testing the alpha pack until the latest pack was released on
 the 9th. There was a major issue [1] in alpha pack that was blocking us
 from testing Rule service feature and it has been fixed in the 9th May
 pack. WarunaJ is working on other reported issues.

 Testing is carried out in a Worker/Manager separated cluster (deployment
 pattern1) and test cases executed so far, are marked in [2]. We have tested
 the basic scenarios of Integrating BRS with IS (SSO), BPS and ESB. Planning
 to do further testing around those integration scenarios.

 Load / Performance tests are yet to be done.


 [1] https://wso2.org/jira/browse/BRS-74
 [2]
 https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharing#gid=1


 Thanks,

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 Regards,

 Waruna Lakshitha Jayaweera
 Software Engineer
 WSO2 Inc; http://wso2.com
 phone: +94713255198




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BRS 2.1.0 Alpha testing update

[Chathurika De Silva]

Hi

We are testing BRS Alpha (2.1.0) pack with ELB Alpha release. The
previously mentioned issue is now closed.

Best Regards


On Wed, May 7, 2014 at 5:22 PM, Sandapa Handakumbura sand...@wso2.comwrote:

 Hi All,

 We have set up the BRS W/M separated cluster with ELB 2.1.0 and started
 functional testing in the clustered setup. We will be following [1] as our
 test plan (during testing more scenarios will be added if required).

 [1]
 https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharing#gid=1

 Regards,
 Sandapa


 On Wed, May 7, 2014 at 11:55 AM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 We tried to set up the cluster for above mentioned BRS version using ELB
 2.1.1. We encountered the following blocker which we reported under LB-147

 Due the above issue, we are moving to ELB 2.1.0 for our further testing
 process until the issue is fixed.

 Best Regards

 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com

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




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] BRS 2.1.0 Alpha testing update

[Chathurika De Silva]

Hi All

We tried to set up the cluster for above mentioned BRS version using ELB
2.1.1. We encountered the following blocker which we reported under LB-147

Due the above issue, we are moving to ELB 2.1.0 for our further testing
process until the issue is fixed.

Best Regards

-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when starting BRS with db2 datasource

[Chathurika De Silva]

Following errors occurred when starting the BRS  2.0.0 with the below db2
configuration

datasource
nameWSO2_CARBON_DB/name
descriptionThe datasource used for registry and user
manager/description
jndiConfig
namejdbc/WSO2CarbonDB/name
/jndiConfig
definition type=RDBMS
configuration
urljdbc:db2://192.168.18.13:5/CEP/url
usernamedb2admin/username
passwordpass#word2/password

driverClassNamecom.ibm.db2.jcc.DB2Driver/driverClassName
maxActive80/maxActive
maxWait36/maxWait
minIdle5/minIdle
testOnBorrowtrue/testOnBorrow
validationQueryselect 1 from
sysibm.sysdummy1/validationQuery
validationInterval3/validationInterval
/configuration
/definition
/datasource

*Errors *

[2014-04-21 14:06:19,369] ERROR - DatabaseUtil Error! DB2 SQL Error:
SQLCODE=-407, SQLSTATE=23502, SQLERRMC=TBSPACEID=2, TABLEID=264, COLNO=5,
DRIVER=3.50.152
com.ibm.db2.jcc.b.lm: DB2 SQL Error: SQLCODE=-407, SQLSTATE=23502,
SQLERRMC=TBSPACEID=2, TABLEID=264, COLNO=5, DRIVER=3.50.152
at com.ibm.db2.jcc.b.wc.a(wc.java:575)
at com.ibm.db2.jcc.b.wc.a(wc.java:57)
at com.ibm.db2.jcc.b.wc.a(wc.java:126)
at com.ibm.db2.jcc.b.tk.b(tk.java:1593)
at com.ibm.db2.jcc.b.tk.c(tk.java:1576)
at com.ibm.db2.jcc.t4.db.k(db.java:353)
at com.ibm.db2.jcc.t4.db.a(db.java:59)
at com.ibm.db2.jcc.t4.t.a(t.java:50)
at com.ibm.db2.jcc.t4.tb.b(tb.java:200)
at com.ibm.db2.jcc.b.uk.Gb(uk.java:2355)
at com.ibm.db2.jcc.b.uk.e(uk.java:3129)
at com.ibm.db2.jcc.b.uk.zb(uk.java:568)
at com.ibm.db2.jcc.b.uk.executeUpdate(uk.java:551)
at
org.wso2.carbon.user.core.util.DatabaseUtil.updateDatabase(DatabaseUtil.java:396)
at
org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.addAuthorizationForRole(JDBCAuthorizationManager.java:540)
at
org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.authorizeRole(JDBCAuthorizationManager.java:258)
at
org.wso2.carbon.registry.core.jdbc.realm.RegistryAuthorizationManager.authorizeRole(RegistryAuthorizationManager.java:155)
at
org.wso2.carbon.captcha.mgt.util.CaptchaUtil.setAnonAuthorization(CaptchaUtil.java:281)
at
org.wso2.carbon.captcha.mgt.util.CaptchaUtil.setAnonAccessToCaptchaImages(CaptchaUtil.java:265)
at
org.wso2.carbon.captcha.mgt.internal.CaptchaMgtServiceComponent.activate(CaptchaMgtServiceComponent.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:513)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
at

[Dev] Maven optimization variable error

[Chathurika De Silva]

Hi All

I tried to use the following MAVEN_OPTS value which is in the documentation

*MAVEN_OPTS=-Xms768m -Xmx3072m -XX:MaxPermSize=1200m*

but it resulted in an error saying *Xms768m not found*


When i used the following command worked

*MAVEN_OPTS=-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m*


Is there any reason why the previous one is not working?

Thanks and best regards
-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven optimization variable error

[Chathurika De Silva]

Hi Gayan

You are correct, that is the problem. Shouldn't it be specified in the
documentation? Not to copy paste?

Thanks


On Wed, Apr 2, 2014 at 4:51 PM, Gayan Yalpathwala gay...@wso2.com wrote:

 Hi Chathurika,

 I am afraid there occurs a serious issue if you copy and paste the
 MAVEN_OPTS string in WSO2 docs directly. This is because of character ()
 where it should be () precisely. Please ack if this is what troubled you.

 Thanks,


 On Wed, Apr 2, 2014 at 12:01 PM, Chathurika De Silva chathuri...@wso2.com
  wrote:

 Hi All

 I tried to use the following MAVEN_OPTS value which is in the
 documentation

 *MAVEN_OPTS=-Xms768m -Xmx3072m -XX:MaxPermSize=1200m*

 but it resulted in an error saying *Xms768m not found*


 When i used the following command worked

 *MAVEN_OPTS=-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m*


 Is there any reason why the previous one is not working?

 Thanks and best regards
 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com

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




 --
 *Gayan Kaushalya Yalpathwala*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 71 8682704 http://asia14.wso2con.com/

  http://asia14.wso2con.com/




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven optimization variable error

[Chathurika De Silva]

Thank you Gihan


On Wed, Apr 2, 2014 at 5:11 PM, Gayan Yalpathwala gay...@wso2.com wrote:

 Hi Chathurika,

 Yes this should be fixed in docs. I have raised a documentation jira [1]
 accordingly.

 [1] https://wso2.org/jira/browse/DOCUMENTATION-682

 Thanks,


 On Wed, Apr 2, 2014 at 4:58 PM, Chathurika De Silva 
 chathuri...@wso2.comwrote:

 Hi Gayan

 You are correct, that is the problem. Shouldn't it be specified in the
 documentation? Not to copy paste?

 Thanks


 On Wed, Apr 2, 2014 at 4:51 PM, Gayan Yalpathwala gay...@wso2.comwrote:

 Hi Chathurika,

 I am afraid there occurs a serious issue if you copy and paste the
 MAVEN_OPTS string in WSO2 docs directly. This is because of character ()
 where it should be () precisely. Please ack if this is what troubled
 you.

 Thanks,


 On Wed, Apr 2, 2014 at 12:01 PM, Chathurika De Silva 
 chathuri...@wso2.com wrote:

 Hi All

 I tried to use the following MAVEN_OPTS value which is in the
 documentation

 *MAVEN_OPTS=-Xms768m -Xmx3072m -XX:MaxPermSize=1200m*

 but it resulted in an error saying *Xms768m not found*


 When i used the following command worked

 *MAVEN_OPTS=-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m*


 Is there any reason why the previous one is not working?

 Thanks and best regards
 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com

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




 --
 *Gayan Kaushalya Yalpathwala*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 71 8682704 http://asia14.wso2con.com/

  http://asia14.wso2con.com/




 --
 *Chathurika Erandi*
 Software Engineer,
 WSO2 Inc.

 *E-mail:* chathuri...@wso2.com
 *Mobile: *+94714 328 612
 *Blog*: chathurikaerandi.blogspot.com




 --
 *Gayan Kaushalya Yalpathwala*
  Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 71 8682704 http://asia14.wso2con.com/

  http://asia14.wso2con.com/




-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error in rampart module when running the secure client

[Chathurika De Silva]

Hi All

I have implemented a secure proxy service and a client that talks to that
service. In the client i have referenced rampart module as below

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(/home/erandi/axis2-1.6.2/repository,
null);

When running the client i get the following error. Can someone help me with
this error?

ERROR] The rampart-1.6.2.mar module, which is not valid, caused
org.apache.rampart.Rampart
org.apache.axis2.deployment.DeploymentException: org.apache.rampart.Rampart
at
org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:527)
at
org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:77)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:264)
at
org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:69)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:64)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:158)
at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:133)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at
org.orderprocess.OrderProcessorClient.main(OrderProcessorClient.java:17)
Caused by: org.apache.axis2.deployment.DeploymentException:
org.apache.rampart.Rampart
at
org.apache.axis2.deployment.ModuleBuilder.populateModule(ModuleBuilder.java:233)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:514)
... 11 more
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev