Re: [Dev] WSO2 Committers += Gokul

[Ishara Premadasa]

Congratulations Gokul :)


On Thu, Aug 29, 2013 at 11:58 AM, Susinda Perera  wrote:

> Congratulations Gokul.
>
>
> On Thu, Aug 29, 2013 at 11:36 AM, Asanka Sanjeewa wrote:
>
>> Congratulations Gokul.
>>
>> Regards,
>> AsankaS.
>>
>>
>> On Thu, Aug 29, 2013 at 11:19 AM, Pulasthi Supun wrote:
>>
>>> Congratz Goku(l)!! :)
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:11 AM, Shameera Rathnayaka >> > wrote:
>>>
 Congratulation Gokul !!!


 On Wed, Aug 28, 2013 at 9:01 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

> Congrats Gokul !!!
>
>
> Regards,
> Mohan
>
>
> On Wed, Aug 28, 2013 at 6:11 PM, Manoj Kumara  wrote:
>
>> Congratulations Gokul ...
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Wed, Aug 28, 2013 at 6:07 PM, Manula Chathurika Thantriwatte <
>> manu...@wso2.com> wrote:
>>
>>> Congratulations Gokul !!!
>>>
>>>
>>> On Wed, Aug 28, 2013 at 5:57 PM, Chanaka Fernando >> > wrote:
>>>
 Congrats Gokul 



 On Wed, Aug 28, 2013 at 5:30 PM, Maninda Edirisooriya <
 mani...@wso2.com> wrote:

> Congratulations Gokul. :-)
>
> *
> Maninda Edirisooriya*
> Software Engineer
> *WSO2, Inc.
> *lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *Phone* : +94 777603226
>
>
> On Wed, Aug 28, 2013 at 5:15 PM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> Congratulations Gokul...
>>
>>
>> On Wed, Aug 28, 2013 at 5:07 PM, Darshana Gunawardana <
>> darsh...@wso2.com> wrote:
>>
>>> Congratulations Gokul...!!!
>>>
>>>
>>>  On Wed, Aug 28, 2013 at 4:59 PM, Anjana Fernando <
>>> anj...@wso2.com> wrote:
>>>
 Hi everyone,

 It's my pleasure to announce Gokul as a WSO2 commiter. Gokul
 has done many contributions in improving the BAM product. And I'm 
 sure he
 will continue to be a key member in the team. Gokul, welcome 
 aboard and
 keep it up! ..


 Cheers,
 Anjana.

 --
 *Anjana Fernando*
 Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

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


>>>
>>>
>>> --
>>> Regards,
>>>
>>> *
>>> Darshana Gunawardana
>>> *Software Engineer
>>> WSO2 Inc.; http://wso2.com*
>>> E-mail: darsh...@wso2.com
>>> **Mobile: +94718566859
>>> *Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com*
>> *
>> *
>> *Phone: +94715478185*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
>> *Twitter: https://twitter.com/bhathiyax*
>>
>> ___
>> 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
>
>


 --
 --
 Chanaka Fernando
 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
 Wordpress:http://chanakaudaya.wordpress.com




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


>>>
>>>
>>> --
>>> Regards,
>>> Manula Chathurika Thantriwatte
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> email : manu...@wso2

Re: [Dev] WSO2 Committers += Gokul

[Gayan Dhanushka]

Congratzz Gokul...!!!


On Thu, Aug 29, 2013 at 12:39 PM, Ishara Premadasa  wrote:

> Congratulations Gokul :)
>
>
> On Thu, Aug 29, 2013 at 11:58 AM, Susinda Perera  wrote:
>
>> Congratulations Gokul.
>>
>>
>> On Thu, Aug 29, 2013 at 11:36 AM, Asanka Sanjeewa wrote:
>>
>>> Congratulations Gokul.
>>>
>>> Regards,
>>> AsankaS.
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:19 AM, Pulasthi Supun wrote:
>>>
 Congratz Goku(l)!! :)


 On Thu, Aug 29, 2013 at 11:11 AM, Shameera Rathnayaka <
 shame...@wso2.com> wrote:

> Congratulation Gokul !!!
>
>
> On Wed, Aug 28, 2013 at 9:01 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> Congrats Gokul !!!
>>
>>
>> Regards,
>> Mohan
>>
>>
>> On Wed, Aug 28, 2013 at 6:11 PM, Manoj Kumara  wrote:
>>
>>> Congratulations Gokul ...
>>>
>>> Best Regards..
>>>
>>>
>>> Manoj Kumara
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Twitter:  http://twitter.com/ManKuma
>>> Mobile: +94713448188
>>>
>>>
>>> On Wed, Aug 28, 2013 at 6:07 PM, Manula Chathurika Thantriwatte <
>>> manu...@wso2.com> wrote:
>>>
 Congratulations Gokul !!!


 On Wed, Aug 28, 2013 at 5:57 PM, Chanaka Fernando <
 chana...@wso2.com> wrote:

> Congrats Gokul 
>
>
>
> On Wed, Aug 28, 2013 at 5:30 PM, Maninda Edirisooriya <
> mani...@wso2.com> wrote:
>
>> Congratulations Gokul. :-)
>>
>> *
>> Maninda Edirisooriya*
>> Software Engineer
>> *WSO2, Inc.
>> *lean.enterprise.middleware.
>>
>> *Blog* : http://maninda.blogspot.com/
>> *Phone* : +94 777603226
>>
>>
>> On Wed, Aug 28, 2013 at 5:15 PM, Bhathiya Jayasekara <
>> bhath...@wso2.com> wrote:
>>
>>> Congratulations Gokul...
>>>
>>>
>>> On Wed, Aug 28, 2013 at 5:07 PM, Darshana Gunawardana <
>>> darsh...@wso2.com> wrote:
>>>
 Congratulations Gokul...!!!


  On Wed, Aug 28, 2013 at 4:59 PM, Anjana Fernando <
 anj...@wso2.com> wrote:

> Hi everyone,
>
> It's my pleasure to announce Gokul as a WSO2 commiter. Gokul
> has done many contributions in improving the BAM product. And I'm 
> sure he
> will continue to be a key member in the team. Gokul, welcome 
> aboard and
> keep it up! ..
>
>
> Cheers,
> Anjana.
>
> --
> *Anjana Fernando*
> Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Regards,

 *
 Darshana Gunawardana
 *Software Engineer
 WSO2 Inc.; http://wso2.com*
 E-mail: darsh...@wso2.com
 **Mobile: +94718566859
 *Lean . Enterprise . Middleware

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


>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Software Engineer,*
>>> *WSO2 inc., http://wso2.com*
>>> *
>>> *
>>> *Phone: +94715478185*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
>>> *Twitter: https://twitter.com/bhathiyax*
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> --
> Chanaka Fernando
> 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
> Wordpress:http://chanakaudaya.wordpress.com
>
>
>
>
> ___
> Dev mailing list

Re: [Dev] WSO2 Committers += Gokul

[Dunith Dhanushka]

Congratulations Gokul!


On Thu, Aug 29, 2013 at 12:44 PM, Gayan Dhanushka  wrote:

> Congratzz Gokul...!!!
>
>
> On Thu, Aug 29, 2013 at 12:39 PM, Ishara Premadasa wrote:
>
>> Congratulations Gokul :)
>>
>>
>> On Thu, Aug 29, 2013 at 11:58 AM, Susinda Perera wrote:
>>
>>> Congratulations Gokul.
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:36 AM, Asanka Sanjeewa wrote:
>>>
 Congratulations Gokul.

 Regards,
 AsankaS.


 On Thu, Aug 29, 2013 at 11:19 AM, Pulasthi Supun wrote:

> Congratz Goku(l)!! :)
>
>
> On Thu, Aug 29, 2013 at 11:11 AM, Shameera Rathnayaka <
> shame...@wso2.com> wrote:
>
>> Congratulation Gokul !!!
>>
>>
>> On Wed, Aug 28, 2013 at 9:01 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Congrats Gokul !!!
>>>
>>>
>>> Regards,
>>> Mohan
>>>
>>>
>>> On Wed, Aug 28, 2013 at 6:11 PM, Manoj Kumara wrote:
>>>
 Congratulations Gokul ...

 Best Regards..


 Manoj Kumara
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Twitter:  http://twitter.com/ManKuma
 Mobile: +94713448188


 On Wed, Aug 28, 2013 at 6:07 PM, Manula Chathurika Thantriwatte <
 manu...@wso2.com> wrote:

> Congratulations Gokul !!!
>
>
> On Wed, Aug 28, 2013 at 5:57 PM, Chanaka Fernando <
> chana...@wso2.com> wrote:
>
>> Congrats Gokul 
>>
>>
>>
>> On Wed, Aug 28, 2013 at 5:30 PM, Maninda Edirisooriya <
>> mani...@wso2.com> wrote:
>>
>>> Congratulations Gokul. :-)
>>>
>>> *
>>> Maninda Edirisooriya*
>>> Software Engineer
>>> *WSO2, Inc.
>>> *lean.enterprise.middleware.
>>>
>>> *Blog* : http://maninda.blogspot.com/
>>> *Phone* : +94 777603226
>>>
>>>
>>> On Wed, Aug 28, 2013 at 5:15 PM, Bhathiya Jayasekara <
>>> bhath...@wso2.com> wrote:
>>>
 Congratulations Gokul...


 On Wed, Aug 28, 2013 at 5:07 PM, Darshana Gunawardana <
 darsh...@wso2.com> wrote:

> Congratulations Gokul...!!!
>
>
>  On Wed, Aug 28, 2013 at 4:59 PM, Anjana Fernando <
> anj...@wso2.com> wrote:
>
>> Hi everyone,
>>
>> It's my pleasure to announce Gokul as a WSO2 commiter. Gokul
>> has done many contributions in improving the BAM product. And 
>> I'm sure he
>> will continue to be a key member in the team. Gokul, welcome 
>> aboard and
>> keep it up! ..
>>
>>
>> Cheers,
>> Anjana.
>>
>> --
>> *Anjana Fernando*
>> Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> *
> Darshana Gunawardana
> *Software Engineer
> WSO2 Inc.; http://wso2.com*
> E-mail: darsh...@wso2.com
> **Mobile: +94718566859
> *Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Bhathiya Jayasekara*
 *Software Engineer,*
 *WSO2 inc., http://wso2.com*
 *
 *
 *Phone: +94715478185*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
 *Twitter: https://twitter.com/bhathiyax*

 ___
 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
>>>
>>>
>>
>>
>> --
>> --
>> Chanaka Fernando
>> Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pu

[Dev] [Build Faliure] trunk/components/mediation

[Gihan Anuruddha]

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1:05.423s
[INFO] Finished at: Mon Aug 26 12:17:44 IST 2013
[INFO] Final Memory: 28M/490M
[INFO]

[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-compiler-plugin:2.0:compile (default-compile) on project org.wso2.
carbon.connector.salesforce: Compilation failure: Compilation failure:
[ERROR] /home/gihan
/wso2/carbon/platform/trunk/components/mediation/mediation-library/connectors/org
.wso2.carbon.connector.salesforce/src/main/java/org/wso2/carbon/connector/
salesforce/SetupLoginParams.java:[41,56] package org.wso2.carbon.mediation.
library.connectors.core does not exist
[ERROR]
[ERROR] /home/gihan
/wso2/carbon/platform/trunk/components/mediation/mediation-library/connectors/org
.wso2.carbon.connector.salesforce/src/main/java/org/wso2/carbon/connector/
salesforce/SetupLoginParams.java:[42,61] package org.wso2.carbon.mediation.
library.connectors.core.util does not exist
[ERROR]
[ERROR] /home/gihan
/wso2/carbon/platform/trunk/components/mediation/mediation-library/connectors/org
.wso2.carbon.connector.salesforce/src/main/java/org/wso2/carbon/connector/
salesforce/SetupLoginParams.java:[44,38] cannot find symbol
[ERROR] symbol: class AbstractConnector
[ERROR] public class SetupLoginParams extends AbstractConnector {
[ERROR]
[ERROR] /home/gihan
/wso2/carbon/platform/trunk/components/mediation/mediation-library/connectors/org
.wso2.carbon.connector.salesforce/src/main/java/org/wso2/carbon/connector/
salesforce/SetupLoginParams.java:[49,29] cannot find symbol
[ERROR] symbol  : variable ConnectorUtils
[ERROR] location: class org.wso2.carbon.connector.salesforce.
SetupLoginParams
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException


-- 
---
W.G. Gihan Anuruddha
Senior Software Engineer | WSO2, Inc.
M: +94772272595
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] JSON format issue with paypal connector

[Malaka Silva]

Hi,

I have the following issue when sending a json.

following is the required format

{
  "intent":"sale",
  "payer":{
"payment_method":"credit_card",
"funding_instruments":[
  {
"credit_card":{
  "number":"4417119669820331",
  "type":"visa",
  "expire_month":11,
  "expire_year":2018,
  "cvv2":"874",
  "first_name":"Joe",
  "last_name":"Shopper",
  "billing_address":{
"line1":"52 N Main ST",
"city":"Johnstown",
"country_code":"US",
"postal_code":"43210",
"state":"OH"
  }
}
  }
]
  },
  "transactions":[
{
  "amount":{
"total":"7.47",
"currency":"USD",
"details":{
  "subtotal":"7.41",
  "tax":"0.03",
  "shipping":"0.03"
}
  },
  "description":"This is the payment transaction description."
}
  ]
}

So I set the payload using following configuration

 

{"intent":"sale","payer":{"payment_method":"credit_card","funding_instruments":[{"credit_card":{"number":"4417119669820331","type":"visa","expire_month":11,"expire_year":2018,"cvv2":"874","first_name":"Joe","last_name":"Shopper","billing_address":{"line1":"52
N Main
ST","city":"Johnstown","country_code":"US","postal_code":"43210","state":"OH"}}}]},"transactions":[{"amount":{"total":"0.47","currency":"USD","details":{"subtotal":"0.41","tax":"0.03","shipping":"0.03"}},"description":"This
is the payment transaction description."}]}

 


However following is the actual wire log when sending.

{"intent":"sale","payer":{"payment_method":"credit_card","funding_instruments":{"credit_card":{"number":"4417119669820331","type":"visa","expire_month":"11","expire_year":"2018","cvv2":"874","first_name":"Joe","last_name":"Shopper","billing_address":{"line1":"52
N Main
ST","city":"Johnstown","country_code":"US","postal_code":"43210","state":"OH","transactions":{"amount":{"total":"0.47","currency":"USD","details":{"subtotal":"0.41","tax":"0.03","shipping":"0.03"}},"description":"This
is the payment transaction description."}}[\r][\n]"


I noticed that the '[' and ']'  are missing when sending to paypal. I guess
this is because it transforms the JSON to XML and XML to JSON before
sending. It is causing this.

Any idea to solve this?

thx

-- 
Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
T: +1 408 754 7388
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

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

[Dev] [AF][Update] - Meeting Notes of mid milestone 4 review

[Shiroshica Kulatilake]

Hi,

We had our 4th mid milestone review yesterday. The review was conducted in
2 stages. The first being a demonstration of the AF 1.0 version to James
and the second a quick review of work ongoing in milestone 4. Below are the
discussion points that came up during the meeting.

*AF 1.0 review:*
Features:
1. Currently the 3rd party systems that we connect to have their own look
and feel - a question was raised whether the same Look and feel (of AF) is
required for the 3rd party eco system products
2. Linking of the bug tracker to the SCM system - this is a feature which
makes the life of a developer using AF comfortable. A user should be able
to click on the bug and be directed to the relevant file/module in SCM.
3. When code is checked in to the SCM this should ideally be checked as to
whether the build is not broken and only then should the commit go through.
4. Debugging facilities within AF
5. Social features within AF

Improvements:
1. AF needs to connect through SSO to all other systems i.e. SCM, Build
system, Issue tracker etc.
2. In the governance page currently the the promote/demote buttons do not
indicate that once they are clicked an option list would pop-up - check
list of items that need to be done in order to go through with a promote or
a demote should be visible on the page itself.
3. Branch/Version naming should be anything

*Mid milestone 4 review:*
1. There should be a default tenant created for all OT users - this will
allow people who already have an OT account to simply try out aPaaS without
having to create a new tenant.
2. Though application specific roles have been removed, tenant roles
indicating devs, QA etc should be in place with the necessary permissions.


@AF team, please add any missing details if any.

Thank you,
Shiro

-- 
Shiroshica Kulatilake

Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF][Update] - Meeting Notes of mid milestone 4 review

[Shiroshica Kulatilake]

Hi,

We also had a product review with Paul on the 27th and the points that were
discussed are listed below.
Dimuthu has already added these to the road map.

*Improvements:*
1. Jenkins should not have security holes - i.e when building an
application there should be mechanisms to make sure whether there are no
malicious scripts running
2. Usage of OAuth instead of mutual SSL for accessing the admin services
3. Application roles in AF 1.0 enables good use cases for private
installations - hence a similar role based concept should be available in
aPaaS. (Using tenant roles instead as mentioned in the mail above would be
a solution to this)

*Features:*
1. Each tenant should be able to link to their own preferred issue tracker
2. There needs to be a graphical way to govern life cycles and bpels
3. There should be a way where user who is trying out aPaaS to be able to
sign up easily - possibly without having to create a tenant. (Having a
default tenant in the preview which is for all OT account holders as
mentioned in the email above would be a solution to this)

Thank you,
Shiro


On Thu, Aug 29, 2013 at 10:22 AM, Shiroshica Kulatilake wrote:

> Hi,
>
> We had our 4th mid milestone review yesterday. The review was conducted in
> 2 stages. The first being a demonstration of the AF 1.0 version to James
> and the second a quick review of work ongoing in milestone 4. Below are the
> discussion points that came up during the meeting.
>
> *AF 1.0 review:*
> Features:
> 1. Currently the 3rd party systems that we connect to have their own look
> and feel - a question was raised whether the same Look and feel (of AF) is
> required for the 3rd party eco system products
> 2. Linking of the bug tracker to the SCM system - this is a feature which
> makes the life of a developer using AF comfortable. A user should be able
> to click on the bug and be directed to the relevant file/module in SCM.
> 3. When code is checked in to the SCM this should ideally be checked as to
> whether the build is not broken and only then should the commit go through.
> 4. Debugging facilities within AF
> 5. Social features within AF
>
> Improvements:
> 1. AF needs to connect through SSO to all other systems i.e. SCM, Build
> system, Issue tracker etc.
> 2. In the governance page currently the the promote/demote buttons do not
> indicate that once they are clicked an option list would pop-up - check
> list of items that need to be done in order to go through with a promote or
> a demote should be visible on the page itself.
> 3. Branch/Version naming should be anything
>
> *Mid milestone 4 review:*
> 1. There should be a default tenant created for all OT users - this will
> allow people who already have an OT account to simply try out aPaaS without
> having to create a new tenant.
> 2. Though application specific roles have been removed, tenant roles
> indicating devs, QA etc should be in place with the necessary permissions.
>
>
> @AF team, please add any missing details if any.
>
> Thank you,
> Shiro
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>



-- 
Shiroshica Kulatilake

Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JSON format issue with paypal connector

[Vanjikumaran Sivajothy]

i also have encountered the same issue when single element in the array, in
your case funding_instruments and transactions contain only one element in
array.

Nalin's suggestion would do the needful! Nevertheless other
further operations you do might get failed if you use that!

it can be send as it is if you don't build the message!



On Thu, Aug 29, 2013 at 11:26 AM, Ravi Undupitiya  wrote:

> Maybe you can place another dummy object inside the JSON arrays instead of
> having just one object inside?
> That is not a proper solution, but it may help to find out if this is a
> JSON -> XML -> JSON serialisation issue.
>
>
> On Thu, Aug 29, 2013 at 5:41 AM, Malaka Silva  wrote:
>
>> Hi,
>>
>> I have the following issue when sending a json.
>>
>> following is the required format
>>
>> {
>>   "intent":"sale",
>>   "payer":{
>> "payment_method":"credit_card",
>> "funding_instruments":[
>>   {
>> "credit_card":{
>>   "number":"4417119669820331",
>>   "type":"visa",
>>   "expire_month":11,
>>   "expire_year":2018,
>>   "cvv2":"874",
>>   "first_name":"Joe",
>>   "last_name":"Shopper",
>>   "billing_address":{
>> "line1":"52 N Main ST",
>> "city":"Johnstown",
>> "country_code":"US",
>> "postal_code":"43210",
>> "state":"OH"
>>   }
>> }
>>   }
>> ]
>>   },
>>   "transactions":[
>> {
>>   "amount":{
>> "total":"7.47",
>> "currency":"USD",
>> "details":{
>>   "subtotal":"7.41",
>>   "tax":"0.03",
>>   "shipping":"0.03"
>> }
>>   },
>>   "description":"This is the payment transaction description."
>> }
>>   ]
>> }
>>
>> So I set the payload using following configuration
>>
>>  
>>
>> {"intent":"sale","payer":{"payment_method":"credit_card","funding_instruments":[{"credit_card":{"number":"4417119669820331","type":"visa","expire_month":11,"expire_year":2018,"cvv2":"874","first_name":"Joe","last_name":"Shopper","billing_address":{"line1":"52
>> N Main
>> ST","city":"Johnstown","country_code":"US","postal_code":"43210","state":"OH"}}}]},"transactions":[{"amount":{"total":"0.47","currency":"USD","details":{"subtotal":"0.41","tax":"0.03","shipping":"0.03"}},"description":"This
>> is the payment transaction description."}]}
>> 
>>  
>>
>>
>> However following is the actual wire log when sending.
>>
>> {"intent":"sale","payer":{"payment_method":"credit_card","funding_instruments":{"credit_card":{"number":"4417119669820331","type":"visa","expire_month":"11","expire_year":"2018","cvv2":"874","first_name":"Joe","last_name":"Shopper","billing_address":{"line1":"52
>> N Main
>> ST","city":"Johnstown","country_code":"US","postal_code":"43210","state":"OH","transactions":{"amount":{"total":"0.47","currency":"USD","details":{"subtotal":"0.41","tax":"0.03","shipping":"0.03"}},"description":"This
>> is the payment transaction description."}}[\r][\n]"
>>
>>
>> I noticed that the '[' and ']'  are missing when sending to paypal. I
>> guess this is because it transforms the JSON to XML and XML to JSON before
>> sending. It is causing this.
>>
>> Any idea to solve this?
>>
>> thx
>>
>> --
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> T: +1 408 754 7388
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>>
>
>
>
> --
> *Ravi Undupitiya*
> Software Engineer; WSO2 Inc.; http://wso2.com
> *
> *
> *E-mail: r...@wso2.com
> **M: **+94 772 930 712*
> *
> *Lean . Enterprise . Middleware
>



-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)777219209**
*[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Gokul

[Chanika Geeganage]

Congratzzz Gokul !


On Thu, Aug 29, 2013 at 12:59 PM, Dunith Dhanushka  wrote:

> Congratulations Gokul!
>
>
> On Thu, Aug 29, 2013 at 12:44 PM, Gayan Dhanushka  wrote:
>
>> Congratzz Gokul...!!!
>>
>>
>> On Thu, Aug 29, 2013 at 12:39 PM, Ishara Premadasa wrote:
>>
>>> Congratulations Gokul :)
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:58 AM, Susinda Perera wrote:
>>>
 Congratulations Gokul.


 On Thu, Aug 29, 2013 at 11:36 AM, Asanka Sanjeewa wrote:

> Congratulations Gokul.
>
> Regards,
> AsankaS.
>
>
> On Thu, Aug 29, 2013 at 11:19 AM, Pulasthi Supun wrote:
>
>> Congratz Goku(l)!! :)
>>
>>
>> On Thu, Aug 29, 2013 at 11:11 AM, Shameera Rathnayaka <
>> shame...@wso2.com> wrote:
>>
>>> Congratulation Gokul !!!
>>>
>>>
>>> On Wed, Aug 28, 2013 at 9:01 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>
 Congrats Gokul !!!


 Regards,
 Mohan


 On Wed, Aug 28, 2013 at 6:11 PM, Manoj Kumara wrote:

> Congratulations Gokul ...
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Wed, Aug 28, 2013 at 6:07 PM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Congratulations Gokul !!!
>>
>>
>> On Wed, Aug 28, 2013 at 5:57 PM, Chanaka Fernando <
>> chana...@wso2.com> wrote:
>>
>>> Congrats Gokul 
>>>
>>>
>>>
>>> On Wed, Aug 28, 2013 at 5:30 PM, Maninda Edirisooriya <
>>> mani...@wso2.com> wrote:
>>>
 Congratulations Gokul. :-)

 *
 Maninda Edirisooriya*
 Software Engineer
 *WSO2, Inc.
 *lean.enterprise.middleware.

 *Blog* : http://maninda.blogspot.com/
 *Phone* : +94 777603226


 On Wed, Aug 28, 2013 at 5:15 PM, Bhathiya Jayasekara <
 bhath...@wso2.com> wrote:

> Congratulations Gokul...
>
>
> On Wed, Aug 28, 2013 at 5:07 PM, Darshana Gunawardana <
> darsh...@wso2.com> wrote:
>
>> Congratulations Gokul...!!!
>>
>>
>>  On Wed, Aug 28, 2013 at 4:59 PM, Anjana Fernando <
>> anj...@wso2.com> wrote:
>>
>>> Hi everyone,
>>>
>>> It's my pleasure to announce Gokul as a WSO2 commiter. Gokul
>>> has done many contributions in improving the BAM product. And 
>>> I'm sure he
>>> will continue to be a key member in the team. Gokul, welcome 
>>> aboard and
>>> keep it up! ..
>>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> --
>>> *Anjana Fernando*
>>> Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> *
>> Darshana Gunawardana
>> *Software Engineer
>> WSO2 Inc.; http://wso2.com*
>> E-mail: darsh...@wso2.com
>> **Mobile: +94718566859
>> *Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com*
> *
> *
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj*
> *Twitter: https://twitter.com/bhathiyax*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

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


>>>
>>>
>>> --
>>> --
>>>

[Dev] Fwd: [AF][Update] - Meeting Notes of mid milestone 4 review

[Manisha Gayathri]

-- Forwarded message --
From: Manisha Gayathri 
Date: Thu, Aug 29, 2013 at 2:47 PM
Subject: Re: [Dev][AF][Update] - Meeting Notes of mid milestone 4 review
To: Dimuthu Leelarathne 
Cc: Shiroshica Kulatilake , Amila Maha Arachchi <
ami...@wso2.com>, Asanka Dissanayake , Ashansa Perera <
asha...@wso2.com>, Danushka Fernando , Janaka Ranabahu <
jan...@wso2.com>, Nihanth Joseph , Ramith Jayasinghe <
ram...@wso2.com>, Sameera Perera , Sanjiva Weerawarana <
sanj...@wso2.com>, Paul Fremantle , Ajanthan Balachandran <
ajant...@wso2.com>, Shamika Ariyawansa , Punnadi
Gunarathna , WSO2 Developers' List 


I am already in the process on writing one article around the webinar done
by Manjula and myself in last April.
Will be handing over the content to Dassa by Monday.

Thanks
Manisha


On Thu, Aug 29, 2013 at 2:33 PM, Dimuthu Leelarathne wrote:

> Hi all,
>
> Adding more.
>
> 1 - We need to do a screen cast and a script and hand over to marketting
> 2 - We need to write articles and marketting will help us to publish in
> DZone, InfoQ and other external sites
>
> So any volunteers?
>
> thanks,
> dimuthu
>
>
>
> On Thu, Aug 29, 2013 at 11:39 AM, Shiroshica Kulatilake wrote:
>
>> Hi,
>>
>> We also had a product review with Paul on the 27th and the points that
>> were discussed are listed below.
>> Dimuthu has already added these to the road map.
>>
>> *Improvements:*
>> 1. Jenkins should not have security holes - i.e when building an
>> application there should be mechanisms to make sure whether there are no
>> malicious scripts running
>> 2. Usage of OAuth instead of mutual SSL for accessing the admin services
>> 3. Application roles in AF 1.0 enables good use cases for private
>> installations - hence a similar role based concept should be available in
>> aPaaS. (Using tenant roles instead as mentioned in the mail above would be
>> a solution to this)
>>
>> *Features:*
>> 1. Each tenant should be able to link to their own preferred issue
>> tracker
>> 2. There needs to be a graphical way to govern life cycles and bpels
>> 3. There should be a way where user who is trying out aPaaS to be able to
>> sign up easily - possibly without having to create a tenant. (Having a
>> default tenant in the preview which is for all OT account holders as
>> mentioned in the email above would be a solution to this)
>>
>> Thank you,
>> Shiro
>>
>>
>> On Thu, Aug 29, 2013 at 10:22 AM, Shiroshica Kulatilake 
>> wrote:
>>
>>> Hi,
>>>
>>> We had our 4th mid milestone review yesterday. The review was conducted
>>> in 2 stages. The first being a demonstration of the AF 1.0 version to James
>>> and the second a quick review of work ongoing in milestone 4. Below are the
>>> discussion points that came up during the meeting.
>>>
>>> *AF 1.0 review:*
>>> Features:
>>> 1. Currently the 3rd party systems that we connect to have their own
>>> look and feel - a question was raised whether the same Look and feel (of
>>> AF) is required for the 3rd party eco system products
>>> 2. Linking of the bug tracker to the SCM system - this is a feature
>>> which makes the life of a developer using AF comfortable. A user should be
>>> able to click on the bug and be directed to the relevant file/module in SCM.
>>> 3. When code is checked in to the SCM this should ideally be checked as
>>> to whether the build is not broken and only then should the commit go
>>> through.
>>> 4. Debugging facilities within AF
>>> 5. Social features within AF
>>>
>>> Improvements:
>>> 1. AF needs to connect through SSO to all other systems i.e. SCM, Build
>>> system, Issue tracker etc.
>>> 2. In the governance page currently the the promote/demote buttons do
>>> not indicate that once they are clicked an option list would pop-up - check
>>> list of items that need to be done in order to go through with a promote or
>>> a demote should be visible on the page itself.
>>> 3. Branch/Version naming should be anything
>>>
>>> *Mid milestone 4 review:*
>>> 1. There should be a default tenant created for all OT users - this will
>>> allow people who already have an OT account to simply try out aPaaS without
>>> having to create a new tenant.
>>> 2. Though application specific roles have been removed, tenant roles
>>> indicating devs, QA etc should be in place with the necessary permissions.
>>>
>>>
>>> @AF team, please add any missing details if any.
>>>
>>> Thank you,
>>> Shiro
>>>
>>> --
>>> Shiroshica Kulatilake
>>>
>>> Architect,
>>> WSO2, Inc. http://wso2.com/
>>> Phone: +94 776523867
>>>
>>
>>
>>
>> --
>> Shiroshica Kulatilake
>>
>> Architect,
>> WSO2, Inc. http://wso2.com/
>> Phone: +94 776523867
>>
>
>
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
~Regards
*Manisha Eleperuma*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware

*blog:  http://manisha-eleperuma.blogspot.com/*
*mobile:  +94 71

[Dev] For which port this WARN log comes when I start ELB in default ports 80/443

[Chamara Ariyarathne]

[2013-08-29 09:45:13,373]  INFO - PassThroughHttpSSLListener Starting
Pass-through HTTPS Listener...
[2013-08-29 09:45:13,386]  INFO - PassThroughHttpSSLListener Pass-through
HTTPS Listener started on 0:0:0:0:0:0:0:0:443
[2013-08-29 09:45:13,387]  INFO - PassThroughHttpListener Starting
Pass-through HTTP Listener...
[2013-08-29 09:45:13,391]  INFO - PassThroughHttpListener Pass-through HTTP
Listener started on 0.0.0.0:80
[2013-08-29 09:45:13,394]  WARN - PassThroughHttpListener System may be
unstable: HTTP ListeningIOReactor encountered a checked exception : Address
already in use
java.net.BindException: Address already in use
 at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
 at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
 at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processSessionRequests(DefaultListeningIOReactor.java:237)
 at
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:146)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
 at
org.apache.synapse.transport.passthru.PassThroughHttpListener$4.run(PassThroughHttpListener.java:251)
at java.lang.Thread.run(Thread.java:724)


-- 
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Meeting Notes - Product Review of CEP

[Mohanadarshan Vivekanandalingam]

Hi All,

We (CEP Team) had a product review meeting with Paul regarding the CEP
3.0.0 and future on 29th August 2013. Please find the meeting notes below..

*Things Discussed*

   - Architecture of CEP 3.0.0
   - User interfaces of the CEP 3.0.0
   - Naming conventions used in CEP
   - Improvements in Siddhi engine

*Ideas come up*

   - Change the name from"Transport Adaptor" to "Adaptor"
   - Use the current modular architecture of CEP 3.0.0 to move forward for
   distributed processing in future


@Suho, Rajeev and Lasantha - Please add if i missed anything..

Thanks & Regards,
Mohan

-- 
*V. Mohanadarshan*
*Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] For which port this WARN log comes when I start ELB in default ports 80/443

[Isuru Udana]

Hi Chamara,

The issue is explained in following threads @dev

ESB Integration Test Cases Fail
IOReactor shutdown issues with ESB integration test


On Thu, Aug 29, 2013 at 3:18 PM, Chamara Ariyarathne wrote:

> [2013-08-29 09:45:13,373]  INFO - PassThroughHttpSSLListener Starting
> Pass-through HTTPS Listener...
> [2013-08-29 09:45:13,386]  INFO - PassThroughHttpSSLListener Pass-through
> HTTPS Listener started on 0:0:0:0:0:0:0:0:443
> [2013-08-29 09:45:13,387]  INFO - PassThroughHttpListener Starting
> Pass-through HTTP Listener...
> [2013-08-29 09:45:13,391]  INFO - PassThroughHttpListener Pass-through
> HTTP Listener started on 0.0.0.0:80
> [2013-08-29 09:45:13,394]  WARN - PassThroughHttpListener System may be
> unstable: HTTP ListeningIOReactor encountered a checked exception : Address
> already in use
> java.net.BindException: Address already in use
>  at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:444)
> at sun.nio.ch.Net.bind(Net.java:436)
>  at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>  at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
> at
> org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processSessionRequests(DefaultListeningIOReactor.java:237)
>  at
> org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:146)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
>  at
> org.apache.synapse.transport.passthru.PassThroughHttpListener$4.run(PassThroughHttpListener.java:251)
> at java.lang.Thread.run(Thread.java:724)
>
>
> --
> *Chamara Ariyarathne*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; *+94772786766*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] How to run integration tests on tenant mode

[Krishantha Samaraweera]

Hi all,

Seems like some product teams unaware of this option. Same integration
tests which run on super user mode can be executed on tenant mode also.

To do that you have to edit automation.properties file and set execution.
mode=tenant.

There could be some cases which doesn't execute OOB, those cases can be
skipped from execution by setting @SetEnviroment annotation introduced in
test framework.

We can enable all tests to run on tenant and user mode by default though
test framework. However this will not practical since enabling all modes
will double integration test execution time.

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

[Dev] Why we have two synapse version in 4.2.0 platform branch?

[Shameera Rathnayaka]

Hi,

There are two version for synapse in 4.2.0 branch,

   - 
2.1.1-wso2v8/
   - 
2.2.0-wso2v1/

Only 2.1.1-wso2v8 is used. Is there any reason that we have new version
2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other
than new version?

Thanks,
Shameera.

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/

-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why we have two synapse version in 4.2.0 platform branch?

[Nuwan Dias]

Hi,

ESB team is doing some major re-factoring/improvements to Synapse. Since
there are some products using 2.1.1-wso2v8 and are releasing recently (ELB,
APIM), these improvements will be done on the 2.2.0-wso2v1 version.

If it requires patching 2.1.1-wso2v8 after today's release, a 2.1.1-wso2v9
will be created and used. Those patches will also have to be applied to
2.2.0-wso2v1.

Thanks,
NuwanD.


On Thu, Aug 29, 2013 at 4:10 PM, Shameera Rathnayaka wrote:

> Hi,
>
> There are two version for synapse in 4.2.0 branch,
>
>- 
> 2.1.1-wso2v8/
>- 
> 2.2.0-wso2v1/
>
> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version
> 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other
> than new version?
>
> Thanks,
> Shameera.
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why we have two synapse version in 4.2.0 platform branch?

[Isuru Udana]

Hi Shameera,

This is explained in following thread.
[Dev] Maintaining Synapse Versions in 4.2.0 Branch

Thanks.


On Thu, Aug 29, 2013 at 4:10 PM, Shameera Rathnayaka wrote:

> Hi,
>
> There are two version for synapse in 4.2.0 branch,
>
>- 
> 2.1.1-wso2v8/
>- 
> 2.2.0-wso2v1/
>
> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version
> 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other
> than new version?
>
> Thanks,
> Shameera.
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Why we have two synapse version in 4.2.0 platform branch?

[Shameera Rathnayaka]

Hi Nuwan/Isuru,

Thansk for explanation. Shouldn't this goes to trunk only ? can we remove
it from branch ?

Thanks,
Shameera.


On Thu, Aug 29, 2013 at 4:20 PM, Isuru Udana  wrote:

> Hi Shameera,
>
> This is explained in following thread.
> [Dev] Maintaining Synapse Versions in 4.2.0 Branch
>
> Thanks.
>
>
> On Thu, Aug 29, 2013 at 4:10 PM, Shameera Rathnayaka wrote:
>
>> Hi,
>>
>> There are two version for synapse in 4.2.0 branch,
>>
>>- 
>> 2.1.1-wso2v8/
>>- 
>> 2.2.0-wso2v1/
>>
>> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version
>> 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other
>> than new version?
>>
>> Thanks,
>> Shameera.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/
>>
>> --
>> *Software Engineer - WSO2 Inc.*
>> *email: shameera AT wso2.com  , shameera AT 
>> apache.org
>> *
>> *phone:  +9471 922 1454*
>> *
>> *
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter : *https://twitter.com/Shameera_R
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maintaining Synapse Versions in 4.2.0 Branch

[Shameera Rathnayaka]

Hi Ishan,

Is there any reason to have this in branch instead of turnk?

Thanks,
Shameera.


On Mon, Aug 26, 2013 at 2:01 PM, Ishan Jayawardena  wrote:

> Hi,
> We created a new version of Synapse here[1] and we will continue to
> develop it from now on. Mainly we are adding ESB Connector related fixes to
> this version of Synapse.
>
> If ELB or APIM requires a new Synapse version we suggest that you create
> the v2.1.1-wso2v9. Please make sure to apply any fixes that you work on to
> both versions.
>
> We will also apply any significant fixes that should go to ELB, and APIM
> in v2.1.1-wso2v9 at the same time.
>
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.2.0-wso2v1
>
>
> Thanks,
> Ishan.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why we have two synapse version in 4.2.0 platform branch?

[Kasun Indrasiri]

On Thu, Aug 29, 2013 at 4:29 PM, Shameera Rathnayaka wrote:

> Hi Nuwan/Isuru,
>
> Thansk for explanation. Shouldn't this goes to trunk only ? can we remove
> it from branch ?
>
> We will be having an ESB release on branch  with 2.2.

> Thanks,
> Shameera.
>
>
> On Thu, Aug 29, 2013 at 4:20 PM, Isuru Udana  wrote:
>
>> Hi Shameera,
>>
>> This is explained in following thread.
>> [Dev] Maintaining Synapse Versions in 4.2.0 Branch
>>
>> Thanks.
>>
>>
>> On Thu, Aug 29, 2013 at 4:10 PM, Shameera Rathnayaka 
>> wrote:
>>
>>> Hi,
>>>
>>> There are two version for synapse in 4.2.0 branch,
>>>
>>>- 
>>> 2.1.1-wso2v8/
>>>- 
>>> 2.2.0-wso2v1/
>>>
>>> Only 2.1.1-wso2v8 is used. Is there any reason that we have new version
>>> 2.2.0-wso2v1 there? or we can remove it? BTW why we use older version other
>>> than new version?
>>>
>>> Thanks,
>>> Shameera.
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/
>>>
>>> --
>>> *Software Engineer - WSO2 Inc.*
>>> *email: shameera AT wso2.com  , shameera AT
>>> apache.org *
>>> *phone:  +9471 922 1454*
>>> *
>>> *
>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>>> *Twitter : *https://twitter.com/Shameera_R
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> *
>>  *
>> Senior *
>> Software Engineer
>> *
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Governance Registry Integration Test and JIRA status

[Eranda Sooriyabandara]

tests-metadata test is now passing with 126/126.

Eranda


On Wed, Aug 28, 2013 at 9:41 PM, Shelan Perera  wrote:

> Hi,
>
> Module Ran failed skipped tests 778 5 0 tests-extensibility 159 12 
> 30tests-metadata12754tests-permissions4610tests-governance-api1300tests-jiras7800tests-lifecycle15800tests-resources23400tests-search-version21900tests-ui2400tests-new21300
>
> Following are the integration test failures upto now. Tests extensibility
> has been fixed for most of the failures and will be committed soon.
>
> *L1/L2 count*
>
> We have following L2 which is documentation bug which will be fixed soon.
> So effectively we have 0.
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>


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

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/



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

Re: [Dev] Governance Registry Integration Test and JIRA status

[Shelan Perera]

Hi

Excellent progress Lasith and Eranda.

@Eranda

Has the fixes been committed?

Thanks


On Thu, Aug 29, 2013 at 5:17 PM, Eranda Sooriyabandara wrote:

> tests-metadata test is now passing with 126/126.
>
> Eranda
>
>
> On Wed, Aug 28, 2013 at 9:41 PM, Shelan Perera  wrote:
>
>> Hi,
>>
>>  Module Ran failed skipped tests 778 5 0 tests-extensibility 159 12 
>> 30tests-metadata12754tests-permissions4610tests-governance-api1300tests-jiras7800tests-lifecycle15800tests-resources23400tests-search-version21900tests-ui2400tests-new21300
>>
>> Following are the integration test failures upto now. Tests extensibility
>> has been fixed for most of the failures and will be committed soon.
>>
>> *L1/L2 count*
>>
>> We have following L2 which is documentation bug which will be fixed soon.
>> So effectively we have 0.
>>
>>
>> --
>> *Shelan Perera*
>>
>> Senior Software Engineer
>> **
>> Integration Technology Group
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :   blog.shelan.org
>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>> *Twitter* :https://twitter.com/#!/shelan
>>
>> *Mobile*  : +94 772 604 402
>>
>>
>
>
> --
> *Eranda Sooriyabandara
> *Senior Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> E-mail: eranda AT wso2.com
> Mobile: +94 716 472 816
> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
> Blog: http://emsooriyabandara.blogspot.com/
>
>
>
> *
> *
>



-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

*Mobile*  : +94 772 604 402
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Patch for https://wso2.org/jira/browse/WSAS-1599

[Geeth Munasinghe]

Hi Sameera

Please apply this patch.

Thanks
Geeth


*G. K. S. Munasinghe
*
*Software Engineer,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: ge...@wso2.com
phone:(+94) 777911226
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Governance Registry Integration Test and JIRA status

[Eranda Sooriyabandara]

yes


On Thu, Aug 29, 2013 at 5:20 PM, Shelan Perera  wrote:

> Hi
>
> Excellent progress Lasith and Eranda.
>
> @Eranda
>
> Has the fixes been committed?
>
> Thanks
>
>
> On Thu, Aug 29, 2013 at 5:17 PM, Eranda Sooriyabandara wrote:
>
>> tests-metadata test is now passing with 126/126.
>>
>> Eranda
>>
>>
>> On Wed, Aug 28, 2013 at 9:41 PM, Shelan Perera  wrote:
>>
>>> Hi,
>>>
>>>  Module Ran failed skipped tests 778 5 0 tests-extensibility 159 12 
>>> 30tests-metadata12754tests-permissions4610tests-governance-api1300tests-jiras7800tests-lifecycle15800tests-resources23400tests-search-version21900tests-ui2400tests-new21300
>>>
>>> Following are the integration test failures upto now. Tests
>>> extensibility has been fixed for most of the failures and will be committed
>>> soon.
>>>
>>> *L1/L2 count*
>>>
>>> We have following L2 which is documentation bug which will be fixed
>>> soon. So effectively we have 0.
>>>
>>>
>>> --
>>> *Shelan Perera*
>>>
>>> Senior Software Engineer
>>> **
>>> Integration Technology Group
>>> *WSO2, Inc. : wso2.com*
>>> lean.enterprise.middleware.
>>>
>>> *Blog* :   blog.shelan.org
>>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>>> *Twitter* :https://twitter.com/#!/shelan
>>>
>>> *Mobile*  : +94 772 604 402
>>>
>>>
>>
>>
>> --
>> *Eranda Sooriyabandara
>> *Senior Software Engineer;
>> Integration Technologies Team;
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> E-mail: eranda AT wso2.com
>> Mobile: +94 716 472 816
>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>> Blog: http://emsooriyabandara.blogspot.com/
>>
>>
>>
>> *
>> *
>>
>
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>


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

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/



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

Re: [Dev] How to run integration tests on tenant mode

[Senaka Fernando]

Hi G-Reg team,

Please make sure we run tests with these settings to ensure that the MT
aspects are covered.

Thanks,
Senaka.


On Thu, Aug 29, 2013 at 3:46 PM, Krishantha Samaraweera  wrote:

> Hi all,
>
> Seems like some product teams unaware of this option. Same integration
> tests which run on super user mode can be executed on tenant mode also.
>
> To do that you have to edit automation.properties file and set execution.
> mode=tenant.
>
> There could be some cases which doesn't execute OOB, those cases can be
> skipped from execution by setting @SetEnviroment annotation introduced in
> test framework.
>
> We can enable all tests to run on tenant and user mode by default though
> test framework. However this will not practical since enabling all modes
> will double integration test execution time.
>
> Thanks,
> Krishantha
>



-- 
* 
*
*
*
*Senaka Fernando*
Senior Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

[Dev] - Weird behaviors observed when worker/manager separated setups are fronted by and ELB

[Evanthika Amarasiri]

Hi,

We see some weird behaviors as reported in [1] & [2] when our clusters are
fronted by an ELB. These scenarios work fine on a standalone setup.

[1] - https://wso2.org/jira/browse/LB-103
[2] - https://wso2.org/jira/browse/WSAS-1556

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

Re: [Dev] [API Manager] Class loading issue after adding multi profiles

[Shelan Perera]

Hi,

What is the solution for this? We are getting this in one of the profiles
of the GReg too.
https://wso2.org/jira/browse/REGISTRY-1837

Thanks


On Wed, Aug 28, 2013 at 9:23 PM, Sanjeewa Malalgoda wrote:

> We were able to isolated and fix the problem. Thank you very much Amani
> for your help :)
>
> Thanks,
> Sanjeewa.
>
>
> On Wed, Aug 28, 2013 at 8:22 AM, Amani Soysa  wrote:
>
>> Hi Sanjeewa,
>>
>> CarbonMemoryAppender is in org.wso2.carbon.logging.service bundle, Not
>> really sure why this issue is coming only for worker profiles. I will get
>> the API Manager packs and have a look at this issue.
>>
>>
>>
>>
>> On Tue, Aug 27, 2013 at 6:35 PM, Sanjeewa Malalgoda wrote:
>>
>>> Hi All,
>>> I'm getting following error after creating new profiles. I added
>>> features available in api manager default profile and other necessary
>>> features. Default profile working as expected. Cannot diagnose this issue
>>> further because run time did not initialized properly. So we cannot use
>>> OSGI commands here. In logs i can see some class loading issues. But i can
>>> see necessary jar files available inside distribution and also those jar
>>> files there in profile configuration/org.eclipse.equinox.simpleconfigurator/
>>> bundles.info file. Also i noticed that CarbonMemoryAppender class is no
>>> more there in org.wso2.carbon.logging.appender jar. Please point me what we
>>> missed here.
>>>
>>>
>>> Thanks,
>>> Sanjeewa.
>>>
>>>
>>> log4j:ERROR Could not instantiate class
>>> [org.wso2.carbon.utils.logging.TenantAwarePatternLayout].
>>> java.lang.ClassNotFoundException:
>>> org.wso2.carbon.utils.logging.TenantAwarePatternLayout
>>>  at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>  at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>  at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:169)
>>>  at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
>>> at
>>> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
>>>  at
>>> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
>>> at
>>> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:641)
>>>  at
>>> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
>>> at
>>> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
>>>  at
>>> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
>>> at
>>> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
>>>  at
>>> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
>>> at org.apache.log4j.LogManager.(LogManager.java:122)
>>>  at org.apache.log4j.Logger.getLogger(Logger.java:104)
>>> at
>>> org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:289)
>>>  at
>>> org.apache.commons.logging.impl.Log4JLogger.(Log4JLogger.java:109)
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>>  at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>> at
>>> org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1116)
>>>  at
>>> org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:914)
>>> at
>>> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
>>>  at
>>> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
>>> at
>>> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:310)
>>>  at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
>>> at
>>> org.wso2.carbon.h2.osgi.console.H2DatabaseManager.(H2DatabaseManager.java:40)
>>>  at
>>> org.wso2.carbon.h2.osgi.H2ConsoleServiceActivator.start(H2ConsoleServiceActivator.java:30)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
>>>  at java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundl

Re: [Dev] Please start smoke testing

[Lasith Chandrasekara]

Hi,

Webdav : after adding resources we can access them via Webdav but not the
other way around. This issue is already reported and we will be fixing it
on 5.0.0 [1].
Ws-i .net integration: I couldn't run related sample due to environment
issue. @Senaka, as we discussed could you please follow on it?


[1]https://wso2.org/jira/browse/REGISTRY-1319

Regards,
-Lasith.


On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera  wrote:

> Following are the areas that i have found to test please mention if you
> are planning to do more. Do not try to repeat what has been covered by
> integration tests.
>
> 1) Chandana - Life cycle related activities ( admin , non admin, new
> lifecycle etc.) , Version and copy executors etc.  (Can you run your
> performance benchmark once these are done?)
>
> 2) Vijitha - Subscription, Resource permission, reporting , CMIS
>
> 3) Lasith - Webdav , basic smoke test on Windows in major functionality.
>
> 4) Eranda - Checkin client, SCM , WS discovery
>
> 5) Ajith - UDDI, Rest
>
> 6) Shelan - APIM promotion, Mounting,  Multi profiles
>
> 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning (Help
> Isuruwan with IDE testing too)
>
> 8) Isuruwan - Test with IDE (WSo2 Developer testing)
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Axiom] Different axiom/antlr versions used by features and causes to runtime issues

[Shelan Perera]

Hi Sameera,

It seems this patch has not been applied. Could you please apply it and
resolve this?

https://wso2.org/jira/browse/REGISTRY-1837


On Wed, Aug 28, 2013 at 6:11 PM, Sanjeewa Malalgoda wrote:

> Attaching fix for API manager profile start up issue here(axiom version
> changes). Please apply patches in idp feature and apim product level.
>
> Thanks,
> Sanjeewa.
>
>
> On Wed, Aug 28, 2013 at 5:57 PM, Sameera Jayasoma wrote:
>
>> We should use all the latest versions for this release..
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Wed, Aug 28, 2013 at 11:10 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi Team,
>>> I can see following features are using different axiom versions and that
>>> causes to have multiple axiom jars in distribution. Also found that order
>>> of these jars cause to some problems when we start-up servers.
>>>
>>>
>>>
>>> ./features/idp-mgt/org.wso2.carbon.idp.mgt.ui.feature/4.2.0/pom.xml:1.2.11.wso2v3
>>>
>>> ./features/stratos/cartridge-agent/org.wso2.carbon.cartridge.agent.server.feature/1.0.0/pom.xml:1.2.11.wso2v4
>>> ./features/jaggery/0.9.0.ALPHA4.wso2v1/features/pom.xml:
>>>  1.2.11.wso2v4
>>>
>>>
>>> Also found that antlr is also having different versions in following
>>> features.
>>> *2.7.7.wso2v1*
>>> ./features/rule/service/org.wso2.carbon.rule.service.server.feature/4.2.0/pom.xml:
>>> 2.7.7.wso2v1
>>> ./features/rule/mediation/org.wso2.carbon.rule.mediation.server.feature/4.2.0/pom.xml:
>>> 2.7.7.wso2v1
>>> ./features/rule/service/org.wso2.carbon.rule.service.server.feature/4.2.0/pom.xml:
>>>
>>> ./features/rule/mediation/org.wso2.carbon.rule.mediation.server.feature/4.2.0/pom.xml:
>>>
>>> ./features/jaggery/0.9.0.ALPHA4.wso2v1/features/pom.xml:
>>>
>>> *3.2.0.wso2v1*
>>> ./features/cassandra/pom.xml:
>>>  3.2.0.wso2v1
>>>
>>> ./features/cassandra-explorer/pom.xml:3.2.0.wso2v1
>>> ./features/logging-mgt/pom.xml:
>>>  3.2.0.wso2v1
>>> ./features/analytics/org.wso2.carbon.analytics.hive.server.feature/4.2.0/pom.xml:
>>>
>>> ./features/analytics/org.wso2.carbon.analytics.hive.server.feature/4.2.0/pom.xml:
>>>
>>> ./features/bpel/pom.xml:
>>>
>>>
>>> Shouldn't we change this?
>>>
>>> Thanks,
>>> Sanjeewa.
>>> --
>>> *
>>> *
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>  blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://sameera.adahas.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

*Mobile*  : +94 772 604 402
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please start smoke testing

[Shelan Perera]

Completed smoke testing for Registry multi-profiles, APIM integration with
GReg and Basic Registry mounting.

Thanks


On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara wrote:

> Hi,
>
> Webdav : after adding resources we can access them via Webdav but not the
> other way around. This issue is already reported and we will be fixing it
> on 5.0.0 [1].
>  Ws-i .net integration: I couldn't run related sample due to environment
> issue. @Senaka, as we discussed could you please follow on it?
>
>
> [1]https://wso2.org/jira/browse/REGISTRY-1319
>
> Regards,
> -Lasith.
>
>
> On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera  wrote:
>
>> Following are the areas that i have found to test please mention if you
>> are planning to do more. Do not try to repeat what has been covered by
>> integration tests.
>>
>> 1) Chandana - Life cycle related activities ( admin , non admin, new
>> lifecycle etc.) , Version and copy executors etc.  (Can you run your
>> performance benchmark once these are done?)
>>
>> 2) Vijitha - Subscription, Resource permission, reporting , CMIS
>>
>> 3) Lasith - Webdav , basic smoke test on Windows in major functionality.
>>
>> 4) Eranda - Checkin client, SCM , WS discovery
>>
>> 5) Ajith - UDDI, Rest
>>
>> 6) Shelan - APIM promotion, Mounting,  Multi profiles
>>
>> 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning (Help
>> Isuruwan with IDE testing too)
>>
>> 8) Isuruwan - Test with IDE (WSo2 Developer testing)
>>
>>
>> --
>> *Shelan Perera*
>>
>> Senior Software Engineer
>> **
>> Integration Technology Group
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :   blog.shelan.org
>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>> *Twitter* :https://twitter.com/#!/shelan
>>
>> *Mobile*  : +94 772 604 402
>>
>>
>


-- 
*Shelan Perera*

Senior Software Engineer
**
Integration Technology Group
*WSO2, Inc. : wso2.com*
lean.enterprise.middleware.

*Blog* :   blog.shelan.org
*Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
*Twitter* :https://twitter.com/#!/shelan

*Mobile*  : +94 772 604 402
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please start smoke testing

[Pulasthi Supun]

Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
versioning with RC4 pack

Regards,
Pulasthi


On Thu, Aug 29, 2013 at 11:07 PM, Shelan Perera  wrote:

> Completed smoke testing for Registry multi-profiles, APIM integration with
> GReg and Basic Registry mounting.
>
> Thanks
>
>
> On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara wrote:
>
>> Hi,
>>
>> Webdav : after adding resources we can access them via Webdav but not the
>> other way around. This issue is already reported and we will be fixing it
>> on 5.0.0 [1].
>>  Ws-i .net integration: I couldn't run related sample due to environment
>> issue. @Senaka, as we discussed could you please follow on it?
>>
>>
>> [1]https://wso2.org/jira/browse/REGISTRY-1319
>>
>> Regards,
>> -Lasith.
>>
>>
>> On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera  wrote:
>>
>>> Following are the areas that i have found to test please mention if you
>>> are planning to do more. Do not try to repeat what has been covered by
>>> integration tests.
>>>
>>> 1) Chandana - Life cycle related activities ( admin , non admin, new
>>> lifecycle etc.) , Version and copy executors etc.  (Can you run your
>>> performance benchmark once these are done?)
>>>
>>> 2) Vijitha - Subscription, Resource permission, reporting , CMIS
>>>
>>> 3) Lasith - Webdav , basic smoke test on Windows in major functionality.
>>>
>>> 4) Eranda - Checkin client, SCM , WS discovery
>>>
>>> 5) Ajith - UDDI, Rest
>>>
>>> 6) Shelan - APIM promotion, Mounting,  Multi profiles
>>>
>>> 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning (Help
>>> Isuruwan with IDE testing too)
>>>
>>> 8) Isuruwan - Test with IDE (WSo2 Developer testing)
>>>
>>>
>>> --
>>> *Shelan Perera*
>>>
>>> Senior Software Engineer
>>> **
>>> Integration Technology Group
>>> *WSO2, Inc. : wso2.com*
>>> lean.enterprise.middleware.
>>>
>>> *Blog* :   blog.shelan.org
>>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>>> *Twitter* :https://twitter.com/#!/shelan
>>>
>>> *Mobile*  : +94 772 604 402
>>>
>>>
>>
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>


-- 
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please start smoke testing

[Chandana Napagoda]

Completed Life cycle , Subscription and notification related tests and
executed life cycle related integration test for user and tenant.

Regards,
Chandana
On Aug 29, 2013 11:23 PM, "Pulasthi Supun"  wrote:

> Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
> versioning with RC4 pack
>
> Regards,
> Pulasthi
>
>
> On Thu, Aug 29, 2013 at 11:07 PM, Shelan Perera  wrote:
>
>> Completed smoke testing for Registry multi-profiles, APIM integration
>> with GReg and Basic Registry mounting.
>>
>> Thanks
>>
>>
>> On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara wrote:
>>
>>> Hi,
>>>
>>> Webdav : after adding resources we can access them via Webdav but not
>>> the other way around. This issue is already reported and we will be fixing
>>> it on 5.0.0 [1].
>>>  Ws-i .net integration: I couldn't run related sample due to environment
>>> issue. @Senaka, as we discussed could you please follow on it?
>>>
>>>
>>> [1]https://wso2.org/jira/browse/REGISTRY-1319
>>>
>>> Regards,
>>> -Lasith.
>>>
>>>
>>> On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera  wrote:
>>>
 Following are the areas that i have found to test please mention if you
 are planning to do more. Do not try to repeat what has been covered by
 integration tests.

 1) Chandana - Life cycle related activities ( admin , non admin, new
 lifecycle etc.) , Version and copy executors etc.  (Can you run your
 performance benchmark once these are done?)

 2) Vijitha - Subscription, Resource permission, reporting , CMIS

 3) Lasith - Webdav , basic smoke test on Windows in major functionality.

 4) Eranda - Checkin client, SCM , WS discovery

 5) Ajith - UDDI, Rest

 6) Shelan - APIM promotion, Mounting,  Multi profiles

 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning (Help
 Isuruwan with IDE testing too)

 8) Isuruwan - Test with IDE (WSo2 Developer testing)


 --
 *Shelan Perera*

 Senior Software Engineer
 **
 Integration Technology Group
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Blog* :   blog.shelan.org
 *Linked-i*n  :
 http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402


>>>
>>
>>
>> --
>> *Shelan Perera*
>>
>> Senior Software Engineer
>> **
>> Integration Technology Group
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :   blog.shelan.org
>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>> *Twitter* :https://twitter.com/#!/shelan
>>
>> *Mobile*  : +94 772 604 402
>>
>>
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [API Manager] Class loading issue after adding multi profiles

[Sanjeewa Malalgoda]

Fix this by avoiding having multiple axiom versions inside pack.

Thanks,
Sanjeewa.


On Thu, Aug 29, 2013 at 8:55 PM, Shelan Perera  wrote:

> Hi,
>
> What is the solution for this? We are getting this in one of the profiles
> of the GReg too.
> https://wso2.org/jira/browse/REGISTRY-1837
>
> Thanks
>
>
> On Wed, Aug 28, 2013 at 9:23 PM, Sanjeewa Malalgoda wrote:
>
>> We were able to isolated and fix the problem. Thank you very much Amani
>> for your help :)
>>
>> Thanks,
>> Sanjeewa.
>>
>>
>> On Wed, Aug 28, 2013 at 8:22 AM, Amani Soysa  wrote:
>>
>>> Hi Sanjeewa,
>>>
>>> CarbonMemoryAppender is in org.wso2.carbon.logging.service bundle, Not
>>> really sure why this issue is coming only for worker profiles. I will get
>>> the API Manager packs and have a look at this issue.
>>>
>>>
>>>
>>>
>>> On Tue, Aug 27, 2013 at 6:35 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi All,
 I'm getting following error after creating new profiles. I added
 features available in api manager default profile and other necessary
 features. Default profile working as expected. Cannot diagnose this issue
 further because run time did not initialized properly. So we cannot use
 OSGI commands here. In logs i can see some class loading issues. But i can
 see necessary jar files available inside distribution and also those jar
 files there in profile 
 configuration/org.eclipse.equinox.simpleconfigurator/
 bundles.info file. Also i noticed that CarbonMemoryAppender class is
 no more there in org.wso2.carbon.logging.appender jar. Please point me what
 we missed here.


 Thanks,
 Sanjeewa.


 log4j:ERROR Could not instantiate class
 [org.wso2.carbon.utils.logging.TenantAwarePatternLayout].
 java.lang.ClassNotFoundException:
 org.wso2.carbon.utils.logging.TenantAwarePatternLayout
  at
 org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
 at
 org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
  at
 org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
 at
 org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:169)
  at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
 at
 org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
  at
 org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
 at
 org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:641)
  at
 org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
 at
 org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
  at
 org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
 at
 org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
  at
 org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
 at org.apache.log4j.LogManager.(LogManager.java:122)
  at org.apache.log4j.Logger.getLogger(Logger.java:104)
 at
 org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:289)
  at
 org.apache.commons.logging.impl.Log4JLogger.(Log4JLogger.java:109)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
 at
 org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1116)
  at
 org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:914)
 at
 org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
  at
 org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
 at
 org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:310)
  at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
 at
 org.wso2.carbon.h2.osgi.console.H2DatabaseManager.(H2DatabaseManager.java:40)
  at
 org.wso2.carbon.h2.osgi.H2ConsoleServiceActivator.start(H2ConsoleServiceActivator.java:30)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
  at java.security.AccessController.doPrivileged(Native Method)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:7

[Dev] WHy we have a build directory in the platform

[Srinath Perera]

Mistake?

platform/build/setup/is/repository/conf/tomcat
Aplatform/build/setup/is/repository/conf/etc
Aplatform/build/setup/is/repository/conf/etc/jmx.xml
Aplatform/build/setup/is/bin
Aplatform/build/setup/is/bin/wso2server.sh
Aplatform/build/compile.sh
Aplatform/build/stratos_config_full.xml
Aplatform/build/stratos-setup.pl
Aplatform/build/stratos.sh
Aplatform/patch-releases

-- 

Srinath Perera, Ph.D.
  Director, Research, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
   Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WHy we have a build directory in the platform

[Amila Maha Arachchi]

First, this was used to maintain the Stratos setup scripts (Stratos 1.x). I
think it is still being used for that purpose (now for Stratos 2).


On Fri, Aug 30, 2013 at 8:38 AM, Srinath Perera  wrote:

> Mistake?
>
> platform/build/setup/is/repository/conf/tomcat
> Aplatform/build/setup/is/repository/conf/etc
> Aplatform/build/setup/is/repository/conf/etc/jmx.xml
> Aplatform/build/setup/is/bin
> Aplatform/build/setup/is/bin/wso2server.sh
> Aplatform/build/compile.sh
> Aplatform/build/stratos_config_full.xml
> Aplatform/build/stratos-setup.pl
> Aplatform/build/stratos.sh
> Aplatform/patch-releases
>
> --
> 
> Srinath Perera, Ph.D.
>   Director, Research, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>Phone: 0772360902
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

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

[Dev] Removing ESB's rest API editor ui from API manager management console

[Sanjeewa Malalgoda]

Hi Team,
We have embedded rest API editor UI inside API manager management console.
 This causes to several issues. Main problem is this is default rest
API uiavailable in
ESB(not specifically designed for AM). So this component does not aware
about API manager specific handlers and api created by this ui does not
behave as APIs created by publisher UI(do not have authorization,
throttling, usage metering and extension handler support). In addition to
that we cannot use graphical ui editor to this as  we have stripped out
mediator, sequence and other ESB UI elements. If someone want to edit API
definition manually they can use source view editor for that. After having
internal team discussion we came up with idea of removing this uicomponent.
WDYT?


Thanks,
Sanjeewa.

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

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

Re: [Dev] Please start smoke testing

[Isuruwan Herath]

Testing done with developer studio IDE:

Resource browser - uploading txt and wsdl files
Create Registry Filter project - adding it as a dependency of a carbon
project
Create Registry Resources project - adding a resource from file system

But creating Resources Handler project caused the IDE to hang.

Regards,
Isuruwan


On Fri, Aug 30, 2013 at 7:01 AM, Chandana Napagoda wrote:

> Completed Life cycle , Subscription and notification related tests and
> executed life cycle related integration test for user and tenant.
>
> Regards,
> Chandana
> On Aug 29, 2013 11:23 PM, "Pulasthi Supun"  wrote:
>
>> Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
>> versioning with RC4 pack
>>
>> Regards,
>> Pulasthi
>>
>>
>> On Thu, Aug 29, 2013 at 11:07 PM, Shelan Perera  wrote:
>>
>>> Completed smoke testing for Registry multi-profiles, APIM integration
>>> with GReg and Basic Registry mounting.
>>>
>>> Thanks
>>>
>>>
>>> On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara 
>>> wrote:
>>>
 Hi,

 Webdav : after adding resources we can access them via Webdav but not
 the other way around. This issue is already reported and we will be fixing
 it on 5.0.0 [1].
  Ws-i .net integration: I couldn't run related sample due to
 environment issue. @Senaka, as we discussed could you please follow on it?


 [1]https://wso2.org/jira/browse/REGISTRY-1319

 Regards,
 -Lasith.


 On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera  wrote:

> Following are the areas that i have found to test please mention if
> you are planning to do more. Do not try to repeat what has been covered by
> integration tests.
>
> 1) Chandana - Life cycle related activities ( admin , non admin, new
> lifecycle etc.) , Version and copy executors etc.  (Can you run your
> performance benchmark once these are done?)
>
> 2) Vijitha - Subscription, Resource permission, reporting , CMIS
>
> 3) Lasith - Webdav , basic smoke test on Windows in major
> functionality.
>
> 4) Eranda - Checkin client, SCM , WS discovery
>
> 5) Ajith - UDDI, Rest
>
> 6) Shelan - APIM promotion, Mounting,  Multi profiles
>
> 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning
> (Help Isuruwan with IDE testing too)
>
> 8) Isuruwan - Test with IDE (WSo2 Developer testing)
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :
> http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>

>>>
>>>
>>> --
>>> *Shelan Perera*
>>>
>>> Senior Software Engineer
>>> **
>>> Integration Technology Group
>>> *WSO2, Inc. : wso2.com*
>>> lean.enterprise.middleware.
>>>
>>> *Blog* :   blog.shelan.org
>>> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
>>> *Twitter* :https://twitter.com/#!/shelan
>>>
>>> *Mobile*  : +94 772 604 402
>>>
>>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running G-Reg integrations tests with different DB config

[Krishantha Samaraweera]

I think all G-Reg tests are stable now. It's better to do the $subject for
RC5 packs.

Also testing mounted G-Reg instance using integration tests is possible,
you have to follow the same steps mentioned.

 In this way you can test mounted G-Reg instance with different DB
configurations as well.

Thanks,
Krishantha.


On Mon, Aug 26, 2013 at 3:16 PM, Nuwan Wimalasekara  wrote:

> All the test is passed in tests-new module now and it contains bellow
> packages
> org.wso2.carbon.registry.app.test
> org.wso2.carbon.registry.subscription.test
>
> Tests run: 213, Failures: 0, Errors: 0, Skipped: 0
>
> Disabled one test class since it leads to make other tests fail. Refer
> JIRA [1]
>
> [1] https://wso2.org/jira/browse/REGISTRY-1818
>
> Thanks,
> Nuwanw
>
>
> On Sun, Aug 25, 2013 at 8:28 AM, Nuwan Wimalasekara wrote:
>
>> Fixed the test execution flow of all the registry tests modules by
>> downgrading the testng version and setting parallel test false in pomfiles.
>> in next reports we have to investigate the failures to ensure whether it
>> is test failure or greg issue.
>>
>> It is better to have alwaysRun = true in BeforeClass( @BeforeClass(
>> alwaysRun = true) ) and AfterClass methods to make sure It is running
>> always.
>> I added it to some classes.
>>
>>
>> On Thu, Aug 22, 2013 at 5:22 PM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Hi Ajith,
>>>
>>> Can you list down the modules which have this problem
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
>>> On Thu, Aug 22, 2013 at 11:20 AM, Ajith Vitharana wrote:
>>>
 +1. But we are observing weird behavior in the test framework (may be
 TestNG issue)  even with the default pack. The main problem is test
 framework load all the test cases in all the packages and execute randomly.
 This makes the different results at each time we run all the tests
 together.

 Thanks
 Ajith.


 On Thu, Aug 22, 2013 at 11:06 AM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> Hi All,
>
> I think we can easily run G-Reg integration test with different DB
> configs. We have to get G-Reg pack and edit DB configs, then compress
> it and put it to the correct location and execute tests.
>
> We can generate a pack with all integration tests and point and run
> but, but all test cases depends on the run time configuration changes will
> be skipped, To get the full benefit of automated tests I highly recommend
> to run the tests on the branch.
>
> Thanks,
> Krishantha.
>



 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please start smoke testing

[Eranda Sooriyabandara]

Hi Isuruwan,
Please check with the Dev studio guys who sits right next to us.

thanks
Eranda


On Fri, Aug 30, 2013 at 10:26 AM, Isuruwan Herath  wrote:

> Testing done with developer studio IDE:
>
> Resource browser - uploading txt and wsdl files
> Create Registry Filter project - adding it as a dependency of a carbon
> project
> Create Registry Resources project - adding a resource from file system
>
> But creating Resources Handler project caused the IDE to hang.
>
> Regards,
> Isuruwan
>
>
> On Fri, Aug 30, 2013 at 7:01 AM, Chandana Napagoda wrote:
>
>> Completed Life cycle , Subscription and notification related tests and
>> executed life cycle related integration test for user and tenant.
>>
>> Regards,
>> Chandana
>> On Aug 29, 2013 11:23 PM, "Pulasthi Supun"  wrote:
>>
>>> Completed smoke tests for Multi tenancy, Scheduled tasks, Resource
>>> versioning with RC4 pack
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> On Thu, Aug 29, 2013 at 11:07 PM, Shelan Perera  wrote:
>>>
 Completed smoke testing for Registry multi-profiles, APIM integration
 with GReg and Basic Registry mounting.

 Thanks


 On Thu, Aug 29, 2013 at 9:12 PM, Lasith Chandrasekara 
 wrote:

> Hi,
>
> Webdav : after adding resources we can access them via Webdav but not
> the other way around. This issue is already reported and we will be fixing
> it on 5.0.0 [1].
>  Ws-i .net integration: I couldn't run related sample due to
> environment issue. @Senaka, as we discussed could you please follow on it?
>
>
> [1]https://wso2.org/jira/browse/REGISTRY-1319
>
> Regards,
> -Lasith.
>
>
> On Thu, Aug 29, 2013 at 9:47 AM, Shelan Perera wrote:
>
>> Following are the areas that i have found to test please mention if
>> you are planning to do more. Do not try to repeat what has been covered 
>> by
>> integration tests.
>>
>> 1) Chandana - Life cycle related activities ( admin , non admin, new
>> lifecycle etc.) , Version and copy executors etc.  (Can you run your
>> performance benchmark once these are done?)
>>
>> 2) Vijitha - Subscription, Resource permission, reporting , CMIS
>>
>> 3) Lasith - Webdav , basic smoke test on Windows in major
>> functionality.
>>
>> 4) Eranda - Checkin client, SCM , WS discovery
>>
>> 5) Ajith - UDDI, Rest
>>
>> 6) Shelan - APIM promotion, Mounting,  Multi profiles
>>
>> 7) Pulasthi - Multi tenancy, Scheduled tasks, Resource versioning
>> (Help Isuruwan with IDE testing too)
>>
>> 8) Isuruwan - Test with IDE (WSo2 Developer testing)
>>
>>
>> --
>> *Shelan Perera*
>>
>> Senior Software Engineer
>> **
>> Integration Technology Group
>> *WSO2, Inc. : wso2.com*
>> lean.enterprise.middleware.
>>
>> *Blog* :   blog.shelan.org
>> *Linked-i*n  :
>> http://www.linkedin.com/pub/shelan-perera/a/194/465
>> *Twitter* :https://twitter.com/#!/shelan
>>
>> *Mobile*  : +94 772 604 402
>>
>>
>


 --
 *Shelan Perera*

 Senior Software Engineer
 **
 Integration Technology Group
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Blog* :   blog.shelan.org
 *Linked-i*n  :
 http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402


>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>
>


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

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/



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

Re: [Dev] [AS 5.2] Datasource lookup fails after tenant creation

[Piyum Fernando]

Hi Ramith, Nihanth,

Root cause for this problem is, CarbonContextCreatorValve identify your
request as a tenant request,  because requestURI contains "/t/".
Things become more complicated because it contains "/t/"
too. When your request is coming through CarbonContextCreatorValve it sets
the current tenantId according to the tenant domain you are sending. Then
your webapp will be treated as a tenant webapp of that particular tenant so
that your datasource will not be available for the web app.

As a simple solution you can change your webapp's relative context to
something other than "/t"
(change the jaxrs server address in cxf-servlet.xml).

@Sameera,Azeez,
Anyway IMO it's better to modify the logic inside
CarbonContextCreatorValve. If not it will create more complications and
security issues when the URL having "/t"

Thanks.







On Thu, Aug 29, 2013 at 10:48 AM, Afkham Azeez  wrote:

> One thing you should do is, use the ThreadLocal CC. Don't use the
> getCurrentContext method. You should also ensure that the correct tenant CC
> is set as the ThreadLocal.
>
>
> On Thu, Aug 29, 2013 at 10:31 AM, Ramith Jayasinghe wrote:
>
>> I came across this error in AS 5.1.0 as well.
>> What happens is, In this (web) application we do this from super tenant
>> space:
>>
>> UserRealmService realmService =
>> (UserRealmService)
>> PrivilegedCarbonContext.getCurrentContext()
>>
>> .getOSGiService(UserRealmService.class);
>>
>>   int tenantId =
>> realmService.getTenantManager().getTenantId(tenantDomain);
>>
>>
>> Now some where down the line we do this:
>>
>> Context initCtx = new InitialContext();
>> (DataSource) initCtx.lookup(dataSourceName);
>>
>> Which throws an error.
>> Reason is somehow datasource is being search in the tenant space (which
>> we got the tenant ID) instead of super tenant.
>>
>> I think this is a critical bug.
>>
>>
>>
>>
>>
>> On Thu, Aug 29, 2013 at 6:43 AM, Nihanth Joseph  wrote:
>>
>>> Hi,
>>> I am getting following exception after the tenant is created. BD
>>> credential is configured in supertenant.
>>> After tenant created db lookup is happening in tenant space, due to
>>> that it fails.
>>>
>>>
>>>
>>> [2013-08-28 21:34:30,461] ERROR {org.wso2.carbon.issue.tracker.server.
>>> impl.IssueServiceImpl} -  Error while get comments for issue
>>> java.lang.RuntimeException: Error in looking up data source: Name 
>>> [jdbc/IssueTrackerDB]
>>> is not bound in this Context. Unable to find [jdbc].
>>>  at org.wso2.carbon.issue.tracker.util.DBConfiguration.lookupDataSource(
>>> DBConfiguration.java:57)
>>>  at org.wso2.carbon.issue.tracker.util.DBConfiguration.Initialize(
>>> DBConfiguration.java:39)
>>>  at org.wso2.carbon.issue.tracker.util.DBConfiguration.getDBConnection(
>>> DBConfiguration.java:70)
>>>  at org.wso2.carbon.issue.tracker.dao.impl.IssueDAOImpl.getIssueByKey(
>>> IssueDAOImpl.java:177)
>>>  at org.wso2.carbon.issue.tracker.server.impl.IssueServiceImpl.getIssue(
>>> IssueServiceImpl.java:61)
>>>  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.apache.cxf.service.invoker.AbstractInvoker.performInvocation(
>>> AbstractInvoker.java:180)
>>>  at org.apache.cxf.service.invoker.AbstractInvoker.invoke(
>>> AbstractInvoker.java:96)
>>>  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
>>>  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>>>  at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(
>>> ServiceInvokerInterceptor.java:57)
>>>  at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(
>>> ServiceInvokerInterceptor.java:93)
>>>  at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
>>> PhaseInterceptorChain.java:271)
>>>  at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
>>> ChainInitiationObserver.java:121)
>>>  at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(
>>> AbstractHTTPDestination.java:239)
>>>  at org.apache.cxf.transport.servlet.ServletController.invokeDestination
>>> (ServletController.java:223)
>>>  at org.apache.cxf.transport.servlet.ServletController.invoke(
>>> ServletController.java:203)
>>>  at org.apache.cxf.transport.servlet.ServletController.invoke(
>>> ServletController.java:137)
>>>  at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(
>>> CXFNonSpringServlet.java:159)
>>>  at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(
>>> AbstractHTTPServlet.java:286)
>>>  at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(
>>> AbstractHTTPServlet.java:211)
>>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
>>>  at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(
>>> AbstractHTTPServlet.java:262)
>>

[Dev] Invitation: Code Review - Enterprise Store Advanced search, Category ... @ Fri Aug 30, 2013 11am - 12pm (ta...@wso2.com)

[Tanya Madurapperuma]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20130830T053000Z
DTEND:20130830T063000Z
DTSTAMP:20130830T051259Z
ORGANIZER;CN=ta...@wso2.com:mailto:ta...@wso2.com
UID:gvtofibjrcoeo6sap551s5e...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Udara Rathnayake;X-NUM-GUESTS=0:mailto:uda...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Ruchira Wageesha;X-NUM-GUESTS=0:mailto:ruch...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Tanya Madurapperuma;X-NUM-GUESTS=0:mailto:ta...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Chamath Bogahawatta;X-NUM-GUESTS=0:mailto:cham...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Madhuka Udantha;X-NUM-GUESTS=0:mailto:madh...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Praveena Sarathchandra;X-NUM-GUESTS=0:mailto:pravee...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sameera Medagammaddegedara;X-NUM-GUESTS=0:mailto:samee...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Manuranga Perera;X-NUM-GUESTS=0:mailto:m...@wso2.com
CREATED:20130830T051259Z
DESCRIPTION:This is to review the following functionality implementations o
 f Enterprise store.\n1. Advanced search functionality\n2. Category support 
 for assets\n3. E-book asset introduction\nView your event at http://www.goo
 gle.com/calendar/event?action=VIEW&eid=Z3Z0b2ZpYmpyY29lbzZzYXA1NTFzNWV1cWcg
 ZGV2QHdzbzIub3Jn&tok=MTQjdGFueWFAd3NvMi5jb203YzgzYTMzYjkzYmYzNGM0MDMxNjk0NT
 UwYmFhNDE3ZDQ2NjdkZTBl&ctz=Asia/Colombo&hl=en.
LAST-MODIFIED:20130830T051259Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Code Review - Enterprise Store Advanced search\, Category support a
 nd Ebook asset introduction
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


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

[Dev] Cassandra Counter Columns and TTL support added to Storage Server

[Bhathiya Jayasekara]

Hi devs,

As per the requirement in JIRA [1], Storage Server now supports Counter
columns and TTL in Cassandra.

This is committed to the trunk and will be released with WSO2SS-1.1.0.

[1] https://wso2.org/jira/browse/SS-87

Thanks,

-- 
*Bhathiya Jayasekara*
*Software Engineer,*
*WSO2 inc., http://wso2.com*
*
*
*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj*
*Twitter: https://twitter.com/bhathiyax*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing ESB's rest API editor ui from API manager management console

[Nuwan Dias]

Since we have the Source View editor anyway, I don't think this will be an
issue. So +1.

Thanks,
NuwanD.


On Fri, Aug 30, 2013 at 10:18 AM, Sanjeewa Malalgoda wrote:

> Hi Team,
> We have embedded rest API editor UI inside API manager management
> console.  This causes to several issues. Main problem is this is default
> rest API ui available in ESB(not specifically designed for AM). So this
> component does not aware about API manager specific handlers and api
> created by this ui does not behave as APIs created by publisher UI(do not
> have authorization, throttling, usage metering and extension handler
> support). In addition to that we cannot use graphical ui editor to this
> as  we have stripped out mediator, sequence and other ESB UI elements. If
> someone want to edit API definition manually they can use source view
> editor for that. After having internal team discussion we came up with idea
> of removing this ui component. WDYT?
>
>
> Thanks,
> Sanjeewa.
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog :http://sanjeewamalalgoda.
> blogspot.com/ 
>
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing ESB's rest API editor ui from API manager management console

[Sumedha Rubasinghe]

+1 for this release.


On Fri, Aug 30, 2013 at 10:18 AM, Sanjeewa Malalgoda wrote:

> Hi Team,
> We have embedded rest API editor UI inside API manager management
> console.  This causes to several issues. Main problem is this is default
> rest API ui available in ESB(not specifically designed for AM). So this
> component does not aware about API manager specific handlers and api
> created by this ui does not behave as APIs created by publisher UI(do not
> have authorization, throttling, usage metering and extension handler
> support). In addition to that we cannot use graphical ui editor to this
> as  we have stripped out mediator, sequence and other ESB UI elements. If
> someone want to edit API definition manually they can use source view
> editor for that. After having internal team discussion we came up with idea
> of removing this ui component. WDYT?
>
>
> Thanks,
> Sanjeewa.
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog :http://sanjeewamalalgoda.
> blogspot.com/ 
>
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.3.0 Milestone 4 Released !

[Asanka Sanjeewa]

Hi All,

We have WSO2 Developer Studio 3.3.0 Milestone 4  ready to be downloaded at
[1]. Installed eclipse distributions available at [2]

This release includes following improvements and bug fixes.

Improvements

   - [TOOLS-1871 ] - Remove
   Diagram menu item and Diagram Toolbar from ESB Diagram Editor
   - [TOOLS-1872 ] - Remove Zoom
   tool and Note tool from ESB editor toolbar palette

Bug Fixes

   - [TOOLS-1720 ] - Developer
   Studio erases outSequence from Proxy Service
   - [TOOLS-1860 ] - Cannot refer
   address endpoint in Callout Mediator
   - [TOOLS-1867 ] - Row name is
   required in query result mapping
   - [TOOLS-1873 ] -
   markforsuspension property is missing
   - [TOOLS-1874 ] - Mediator flow
   break when it has dynamic or registry refer sequence

Sub-tasks

   - [TOOLS-1771 ] - Avoid default
   value serialization (if user hasn't specify any value for such attributes)
   - [TOOLS-1782 ] - Java 7
   compiled DevS running in java 6 machine gave some exceptions
   - [TOOLS-1801 ] - Template
   endpoint is missing in endpoint types
   - [TOOLS-1803 ] - Editing issue
   from zoomed out view
   - [TOOLS-1806 ] - Do not make
   property names unnecessarily long in property mediator
   - [TOOLS-1810 ] - Named
   sequence support in Proxy services (inSeq and outSeq can define externally)
   - [TOOLS-1822 ] - Rename
   Addressing Endpoint
   - [TOOLS-1832 ] - XML
   validation (payload factory mediator format window) on Ok button click
   - [TOOLS-1833 ] - Callout
   mediator does not have envelope source type, security policies which was
   added recently
   - [TOOLS-1835 ] - Serializing
   and deserializing doesn’t work in urlRewrite mediator
   - [TOOLS-1880 ] - Function
   Declaration
   - [TOOLS-1882 ] - If else
   Statement
   - [TOOLS-1883 ] - While
   statement
   - [TOOLS-1884 ] - For statement
   - [TOOLS-1886 ] - Switch Case
   Statement
   - [TOOLS-1887 ] - Break
   Statement
   - [TOOLS-1888 ] - Continue
   statement
   - [TOOLS-1889 ] - Return
   Statement
   - [TOOLS-1890 ] - include and
   include_once statement
   - [TOOLS-1892 ] - Print
   statement


Your feedbacks are most welcome. Please report issues at [3] and specify
the affect version as 3.3.0 M4.

[1]
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/M4/wso2-developer-studio_3.3.0.zip
[2]
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/M4/Dev-Studio-Pre-installed-Eclipse/
[3] https://wso2.org/jira/browse/TOOLS


Thanks and Regards,
WSO2 Developer Studio Team.

-- 
*Asanka Sanjeewa*
Senior Software Engineer
Mobile: +94772532924
WSO2 Inc. http://wso2.com/
Blog: http://asanka-tech-blog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Appfactory] common object in the seesion to hold data related to an applicaiton

[Asanka Dissanayake]

Hi,
I think it is better to have $subject in appfactory. ATM there is no common
place to get info of the application.Now it is bit hard to keep tracks on
where are the details we want , for example Logged in user, tenant id,
tenant domain.
I will start implementing it with a object called "APPLICATION_INFO" which
is in the session , and have planned to store following information.

-Logged in User
-Application Owners
-Tenant domain
-Tenant Id

Please add if I have missed anything.

cheers!!
Asanka D

-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing ESB's rest API editor ui from API manager management console

[Ruwan Yatawara]

+1 on this. would only lead to conflicts if we keep it.

Thanks and Regards,

Ruwan Yatawara

Software Engineer,
WSO2 Inc.
lean . enterprise . middleware

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com



On Fri, Aug 30, 2013 at 11:40 AM, Sumedha Rubasinghe wrote:

> +1 for this release.
>
>
> On Fri, Aug 30, 2013 at 10:18 AM, Sanjeewa Malalgoda wrote:
>
>> Hi Team,
>> We have embedded rest API editor UI inside API manager management
>> console.  This causes to several issues. Main problem is this is default
>> rest API ui available in ESB(not specifically designed for AM). So this
>> component does not aware about API manager specific handlers and api
>> created by this ui does not behave as APIs created by publisher UI(do
>> not have authorization, throttling, usage metering and extension handler
>> support). In addition to that we cannot use graphical ui editor to this
>> as  we have stripped out mediator, sequence and other ESB UI elements.
>> If someone want to edit API definition manually they can use source view
>> editor for that. After having internal team discussion we came up with idea
>> of removing this ui component. WDYT?
>>
>>
>> Thanks,
>> Sanjeewa.
>>
>> --
>> *
>> *
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog :http://sanjeewamalalgoda.
>> blogspot.com/ 
>>
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev