Re: [Dev] Please provide an update on stabilizing the current branches chunks?

2014-01-26 Thread Afkham Azeez
DSS  AS folks,
You need to urgently attend to this matter. As we know, build failures stop
the world. This should be resolved by Monday.

Azeez


On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera krishan...@wso2.com
 wrote:

 Hi Isuruwan,

 Chunk 05 build failures are due to some backend/UI test failures. Seems
 like teams have released the products with integration test failures.
 Fixing those failure are not possible because code cannot be committed .
 And even skipping failure cases though testNG xml will take lot of effort
 because need to rewrite testNG xml and include all classes and exclude
 failure classes (TestNg supports only for class exclusion).

 Best option available now is to use 
 testFailureIgnorehttp://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnoreproperty.
  You can set this property with maven build command and ignore
 test failures to get the build passed.

 *DSS Backend failures - *

 build 23-Jan-201 23:45:42 Failed tests:
 initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
 Skipped: 4*

  *AS Backend Test failures - *

 Failed tests:
 testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/student/automationStudent
 build 23-Jan-2014 22:14:05  
 testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
 User belongs to invalid group was able to get the resource expected [true]
 but found [false]
 build 23-Jan-2014 22:14:05  
 testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/students
 build 23-Jan-2014 22:14:05  
 testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
 Input stream failure expected object to not be null
 build 23-Jan-2014 22:14:05
 *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
 Skipped: 5*

 *AS UI test failures -*

 build 23-Jan-2014 22:20:43 Failed tests:
 uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
 Web Application uploading failed expected:true but was:false
 build 23-Jan-2014 22:20:43
 build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0,
 Skipped: 2

 Thanks,
 Krishantha.


 On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 The actual issue is with APIM 1.6 profile generation.

 I could see the following lines in log. Because of generated build is
 unstable, server start-up at integration tests failed.

 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation .. FAILURE [4:41.977s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation Parent ... SUCCESS [1.697s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
  SUCCESS [2.548s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 ... SUCCESS [3:20.956s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 Parent  SUCCESS [0.112s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Test Module  FAILURE [7:41.465s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 UI Test Module . FAILURE [9:10.559s]
 build24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Tests .. SUCCESS [0.840s]

 Thanks,

 Krishantha.



 On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Krishantha,

 I executed all chunks with the with the feature to run UI tests
 remotely. Chunk02 was successfully built but there were failures in chunk05
 and chunk06 [1] . Noted the following exception in APIM UI tests in chunk06:

 error   24-Jan-2014 02:17:51at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
 error   24-Jan-2014 02:17:51Caused by: 

[Dev] pass optional parameters via ESB

2014-01-26 Thread krishantha
I am using ESB 4.8.0
My backend service is not accepting empty optional parameters. Means if
optional parameter is not supply then need to remove parameter name also
from URL encoding. 
For example



Let’s says “credentialFieldsame” is optional on above URL then it’s need to
come as



Means completely remove parameter. If we send like bellow it gives error



it is not possible to use fileters as I have 6 optional parameters. Means 64
combinations!!!
Is there any way to do this? Means remove empty parameters when
x-www-form-urlencoding
Note: I am using json payload as cannot use xml I need to use [ sing on
parameternames.
http method is POST

payload as follows






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


[Dev] remove empty parameters from payload - http post / json

2014-01-26 Thread krishantha
I am using ESB 4.8.0
My backend service is not accepting empty optional parameters. Means if
optional parameter is not supply then need to remove parameter name also
from URL encoding. 
For example

credentialFieldstypeName=IF_LOGINcredentialFieldsame=LOGINcredentialFieldsvalue=sha5.

Let’s says “credentialFieldsame” is optional on above URL then it’s need to
come as

credentialFieldstypeName=IF_LOGINcredentialFieldsvalue=sha5

Means completely remove parameter. If we send like bellow it gives error

credentialFieldstypeName=IF_LOGINcredentialFieldsame=credentialFieldsvalue=sha5

it is not possible to use fileters as I have 6 optional parameters. Means 64
combinations!!!
Is there any way to do this? Means remove empty parameters when
x-www-form-urlencoding
Note: I am using json payload as cannot use xml I need to use [  on
parameter names.
http method is POST

payload as follows

payloadFactory media-type=json
format
{
SessionToken: $1,
userToken: $2,
SiteAccId: $3,
}

/format
args

arg 
expression=get-property('uri.var.SessionToken') /
arg 
expression=get-property('uri.var.userToken') /
arg 
expression=get-property('uri.var.SiteAccId') /
/args
/payloadFactory

property name=messageType value=application/x-www-form-urlencoded
scope=axis2 /




--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/remove-empty-parameters-from-payload-http-post-json-tp91243.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [ESB] How to configure BAM Profile outside the Dashboard?

2014-01-26 Thread Imesh Gunaratne
Hi,

Subash, as I found the CAR file could be deployed via the file-system by
copying it to repository/deployment/server/carbonapps/ before starting the
ESB. Therefore I prefer the CAR file method over the G-Reg check-in tool.

Shavantha, yes I could test this approach during ESB 4.8.1 testing. If you
could give me shout when this should be done, I could test it.

Thanks
Imesh


On Sat, Jan 25, 2014 at 11:25 PM, Shavantha Weerasinghe
shavan...@wso2.comwrote:

 Hi imesh

 We can tryout this  approach during 4.8.1 testing

 Regards,shavantha
 On Jan 24, 2014 6:21 PM, Imesh Gunaratne im...@wso2.com wrote:

 Hi,

 I found a better approach than using the G-Reg check-in tool.
 We could create a CAR archive including a Registry Resources Project and
 deploy the CAR file directly in the ESB.

 Thanks


 On Thu, Jan 23, 2014 at 5:00 PM, Imesh Gunaratne im...@wso2.com wrote:

 Hi,

 I was able to do the following with G-Reg check-in tool and successfully
 configure the BAM Server Profile outside the ESB Dashboard:

 1. Start a fresh ESB instance.
 2. Checkout _system/config path to a local folder (A1) using check in
 client.
 3. Create bamServerProfiles folder at A1.
 4. Copy BAM Server Profile file to above bamServerProfiles folder.
 5. Add bamServerProfiles using check in client.
 6. Check in changes using check in client.

 Thanks
 Imesh


 On Thu, Jan 23, 2014 at 10:22 AM, Imesh Gunaratne im...@wso2.comwrote:

 Hi,

 As I found BAM Profiles in ESB are stored in the registry (ESB 4.8.0).
 Is there a way to configure this without accessing the ESB Dashboard
 (if we could export the required configuration to a file)?

 I tried to use the G-Reg check-in tool but it was not successful with
 the H2 database.

 Thanks

 --
 *Imesh Gunaratne*
 Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware




 --
 *Imesh Gunaratne*
 Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware




 --
 *Imesh Gunaratne*
 Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


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




-- 
*Imesh Gunaratne*
Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Issues with carbon v4.20 and other WSO2 products install

2014-01-26 Thread Jaymin Shah
Hi,

I wanted to evaluate Carbon products for multi-tenant back-end services for
customer who is providing various services on IBM portal. Therefore I have
attempted to install Carbon 4.2.0 with feature such as API Manager, App
server, Identity server, CEP, DSS, ESB etc on single box.

I have install Carbon 4.2.0 (latest release from WSO2) and tried Installing
features via the UI using http://dist.wso2.org/p2/carbon/releases/turing/from
http://wso2.com/projects/carbon/provisioning-wso2-carbon-with-equinox-p2/

While installing various products, I been facing one or the other tech
issues such as org.wso2.carbon.core.common.feature.group-4.2.0 is already
present because other installed software requires it  and/or
 org.wso2.carbon.ndatasource.ui.feature.group-4.2.2 will be ignored
because a newer version is already installed.
org.wso2.carbon.event.server.feature.group-4.2.1 is already present because
other installed software requires it.

Therefore, I have tried install using pom file. However, I could not find
any references of how I can install WSO2 products mentioned above in single
instance of Carbon for my evaluation purpose.

It seem that latest release is not able support all WSO2 products and/or
latest release of Carbon 4.20 is not backward compatible with other
products. Please confirm or correct my understanding.

I would really appreciate someone’s help in following right steps to
install these feature using UI and/or pom file.

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


Re: [Dev] Shouldn't we be switching to SLf4J for Carbon 5?

2014-01-26 Thread Isuru Perera
Hi,

On Fri, Jan 24, 2014 at 9:23 PM, Afkham Azeez az...@wso2.com wrote:

 The most appealing feature to me is the parametrized log messages, and
 there is no need to wrap statements in if(log.isDebugEnabled()),
 isInfoEnabled() and so on.

I think we must use guard conditions even with SLF4J [1],

http://stackoverflow.com/questions/8444266/even-with-slf4j-should-you-guard-your-logging



 On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez az...@wso2.com wrote:

 http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/

 We should go with SLF4J


 On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga sag...@wso2.comwrote:



 I'm not quite sure whether we can really compare SLF4J with Log4J where
 SLF4J is a logging API while Log4J is a logging implementation ( Log4J can
 be used with SLF4J and most common SLF4J binding as well), instead we
 should compare SLF4J API with Commons-Logging API. In my POV recent
 versions of both SLF4J and Commons-Logging are more or less similar. I
 don't have any objection to use SLF4J but have we consider JUL ?


 Please refer required dependencies for each option.

 - Commons-logging -  Need 2 dependencies on runtime as  Commons-logging
 API and implementation ( e.g -  SLF4J API, Commons-logging-LOG4J bridge)
 - SLF4J  -  Need 3 dependencies on run time as  SLF4J
 API, SLF4J-X binding, X logging framework ( e.g  - SLF4J API, SLF4J-LOG4J
 binding , LOG4J )
 - JUL -  0 dependencies just JDK

 If there is no found limitations I would prefer to use JUL and worth to
 consider it before make a conclusion.

 Thanks !


  On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez az...@wso2.com wrote:

  I was reading
 http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html;
  we could remove a lot of boiler plate code, and bring in any logging
 implementation if we use SLF4J. Thoughts?

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




 --
 Sagara Gunathunga

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




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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


Re: [Dev] ESB JSON support

2014-01-26 Thread Ishan Jayawardena
The JSON Support page is available here. [1]

Jackie, thanks a lot for improving the quality of the document.

[1] http://docs.wso2.org/display/ESB480/JSON+Support

Thanks,
Ishan.


On Fri, Dec 20, 2013 at 2:09 PM, Samisa Abeysinghe sam...@wso2.com wrote:

 Jira created: https://wso2.org/jira/browse/ESBJAVA-2851

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Fri, Dec 20, 2013 at 1:57 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 Great thanks

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Fri, Dec 20, 2013 at 1:48 PM, Ishan Jayawardena is...@wso2.comwrote:

 Hi Samisa,
 I understand. Currently, we are working on a similar document. I will
 update the thread once we add it to the wiki.

 Thanks,
 Ishan.


 On Fri, Dec 20, 2013 at 1:44 PM, Samisa Abeysinghe sam...@wso2.comwrote:

 So I am looking for a one stop shop info page on JSON. This thread has
 already pointed me to 5 links that I should look into.

 Like in the case of REST, or JMS, should we not have a nice landing
 page on JSON support?

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com



 On Fri, Dec 20, 2013 at 1:43 PM, Ravi Undupitiya r...@wso2.com wrote:

 ESB 4.8.0 docs also have updated Property[1], Filter[2], Switch and
 Log mediator explaining JSON path usage.  PF mediator docs also contain
 some JSON instructions.

 [1] - http://docs.wso2.org/display/ESB480/Property+Mediator
 [2] - http://docs.wso2.org/display/ESB480/Filter+Mediator
 [3] - http://docs.wso2.org/display/ESB480/PayloadFactory+Mediator


 On Fri, Dec 20, 2013 at 1:35 PM, Ishan Jayawardena is...@wso2.comwrote:

 Hi Samisa,
 I believe you are looking at this [1]. In addition to that the wiki
 has two samples on how to handle JSON within ESB [2] but ESB 4.8.0 has 
 more
 improved support for JSON and we will add more samples covering those 
 areas
 as well.

 [1] http://docs.wso2.org/display/ESB480/JSON+Support
 [2] http://docs.wso2.org/display/ESB480/Mediating+JSON+Messages

 Thanks,
 Ishan.



 On Fri, Dec 20, 2013 at 12:30 PM, Samisa Abeysinghe 
 sam...@wso2.comwrote:

 Does this doc has all the information on the kind of JSON support we
 have in the ESB?

  Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Training

 WSO2 Inc.
 http://wso2.com


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




 --
 Ishan Jayawardena
 Senior Software Engineer
 Mobile: +94 (77) 408 2330

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




 --
 *Ravi Undupitiya*
 Software Engineer; WSO2 Inc.; http://wso2.com


 *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712
 %2B94%C2%A0772%20930%20712*

 Lean . Enterprise . Middleware





 --
 Ishan Jayawardena
 Senior Software Engineer
 Mobile: +94 (77) 408 2330






-- 
Ishan Jayawardena
Senior Software Engineer
Mobile: +94 (77) 408 2330
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] remove empty parameters from payload - http post / json

2014-01-26 Thread indika prasad
You could be able to modify the payload using enrich mediator. Here is the
nice example [1]  for payload modification.

[1]
http://mrmalakasilva.blogspot.com/2013/04/use-of-enrich-mediator-to-modify-payload.html




--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/remove-empty-parameters-from-payload-http-post-json-tp91243p91254.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Shouldn't we be switching to SLf4J for Carbon 5?

2014-01-26 Thread Afkham Azeez
On Mon, Jan 27, 2014 at 6:44 AM, Isuru Perera isu...@wso2.com wrote:

 Hi,

 On Fri, Jan 24, 2014 at 9:23 PM, Afkham Azeez az...@wso2.com wrote:

 The most appealing feature to me is the parametrized log messages, and
 there is no need to wrap statements in if(log.isDebugEnabled()),
 isInfoEnabled() and so on.

 I think we must use guard conditions even with SLF4J [1],


No, we don't. If you read that thread you will realize that is only true if
the operations in the params are expensive, which is very rare. I don't
think we have a single instance like that in our entire codebase.



 http://stackoverflow.com/questions/8444266/even-with-slf4j-should-you-guard-your-logging



 On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez az...@wso2.com wrote:

 http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/

 We should go with SLF4J


 On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga sag...@wso2.comwrote:



 I'm not quite sure whether we can really compare SLF4J with Log4J where
 SLF4J is a logging API while Log4J is a logging implementation ( Log4J
 can be used with SLF4J and most common SLF4J binding as well), instead we
 should compare SLF4J API with Commons-Logging API. In my POV recent
 versions of both SLF4J and Commons-Logging are more or less similar. I
 don't have any objection to use SLF4J but have we consider JUL ?


 Please refer required dependencies for each option.

 - Commons-logging -  Need 2 dependencies on runtime as  Commons-logging
 API and implementation ( e.g -  SLF4J API, Commons-logging-LOG4J
 bridge)
 - SLF4J  -  Need 3 dependencies on run time as  SLF4J
 API, SLF4J-X binding, X logging framework ( e.g  - SLF4J API,
 SLF4J-LOG4J binding , LOG4J )
 - JUL -  0 dependencies just JDK

 If there is no found limitations I would prefer to use JUL and worth
 to consider it before make a conclusion.

 Thanks !


  On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez az...@wso2.com wrote:

  I was reading
 http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html;
  we could remove a lot of boiler
 plate code, and bring in any logging implementation if we use SLF4J.
 Thoughts?

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




 --
 Sagara Gunathunga

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




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
  Lean . Enterprise . Middleware

 about.me/chrishantha




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org
* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
http://lk.linkedin.com/in/afkhamazeez*

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


Re: [Dev] [ESB] Sending Binary data as request body

2014-01-26 Thread Ramindu Deshapriya
Essentially what I'm trying to do is, attach a file along with a REStful
PUT request, the same as you'd be able to do through a SOAPUI REST project.

Thanks.




--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Sending-Binary-data-as-request-body-tp90764p91256.html
Sent from the WSO2 Development mailing list archive at Nabble.com.___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Please provide an update on stabilizing the current branches chunks?

2014-01-26 Thread Anjana Fernando
Hi,

Chanika, can you check on this. As I remember, we didn't have any
integration test failures when we were releasing, the tests mentioned here
for DSS seems to be tests that require a working Internet connection, maybe
that has something to do with the failures.

Cheers,
Anjana.


On Sun, Jan 26, 2014 at 1:36 PM, Afkham Azeez az...@wso2.com wrote:

 DSS  AS folks,
 You need to urgently attend to this matter. As we know, build failures
 stop the world. This should be resolved by Monday.

 Azeez


 On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 Chunk 05 build failures are due to some backend/UI test failures. Seems
 like teams have released the products with integration test failures.
 Fixing those failure are not possible because code cannot be committed .
 And even skipping failure cases though testNG xml will take lot of effort
 because need to rewrite testNG xml and include all classes and exclude
 failure classes (TestNg supports only for class exclusion).

 Best option available now is to use 
 testFailureIgnorehttp://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnoreproperty.
  You can set this property with maven build command and ignore
 test failures to get the build passed.

 *DSS Backend failures - *

 build 23-Jan-201 23:45:42 Failed tests:
 initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
 Skipped: 4*

  *AS Backend Test failures - *

 Failed tests:
 testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/student/automationStudent
 build 23-Jan-2014 22:14:05  
 testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
 User belongs to invalid group was able to get the resource expected [true]
 but found [false]
 build 23-Jan-2014 22:14:05  
 testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/students
 build 23-Jan-2014 22:14:05  
 testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
 Input stream failure expected object to not be null
 build 23-Jan-2014 22:14:05
 *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
 Skipped: 5*

 *AS UI test failures -*

 build 23-Jan-2014 22:20:43 Failed tests:
 uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
 Web Application uploading failed expected:true but was:false
 build 23-Jan-2014 22:20:43
 build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0,
 Skipped: 2

 Thanks,
 Krishantha.


 On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 The actual issue is with APIM 1.6 profile generation.

 I could see the following lines in log. Because of generated build is
 unstable, server start-up at integration tests failed.

 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation .. FAILURE [4:41.977s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation Parent ... SUCCESS [1.697s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
  SUCCESS [2.548s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 ... SUCCESS [3:20.956s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 Parent  SUCCESS [0.112s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Test Module  FAILURE [7:41.465s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 UI Test Module . FAILURE [9:10.559s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Tests .. SUCCESS [0.840s]

 Thanks,

 Krishantha.



 On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Krishantha,

 I executed all chunks with the with the feature to run UI tests

Re: [Dev] We will also need to move Carbon 4.x kernel to GitHub

2014-01-26 Thread Eranda Sooriyabandara
Hi all,
I merged and moved the kernel code to github in [1]. Now it is building and
passing tests 24/1/0 where verifyAdminServiceSecurityTest class:
org.wso2.carbon.integration.tests test is failing and I am currently
looking in to it. Another concern is that we need to have an orbit location
for 4.3.0 (or we can directly put them in the nexus) but there is already
existing an orbit repo in github. Since no one is using that orbit I think
we should remove it and put the new orbit bundles there. WDYT?

thanks
Eranda

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

org.apache.axis2.AxisFault: Exception occurred while trying to invoke
service method verifyAdminServices
at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at 
org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at 
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:474)
at 
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:455)
at 
org.wso2.carbon.integration.framework.SecurityVerificationTest.verifyAdminServiceSecurity(SecurityVerificationTest.java:59)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)




On Mon, Jan 20, 2014 at 7:30 PM, Afkham Azeez az...@wso2.com wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




-- 

*Eranda Sooriyabandara*Senior Software Engineer;

Re: [Dev] Shouldn't we be switching to SLf4J for Carbon 5?

2014-01-26 Thread Kishanthan Thangarajah
On Sun, Jan 26, 2014 at 12:17 PM, Afkham Azeez az...@wso2.com wrote:

 Nice! Carbon 5 team, please add a RedMine item to track migration to SLF4J


Noted.



 On Sun, Jan 26, 2014 at 9:56 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 +1 for moving to SLF4J. See the following. [1] is the post from the
 creator of JCL, :).

 [1] http://radio-weblogs.com/0122027/2003/08/15.html
 [2]
 http://v4forums.wordpress.com/2008/12/27/slf4j-vs-jcl-dynamic-binding-vs-static-binding/
 [3]
 http://stackoverflow.com/questions/3222895/why-is-commons-logging-believed-to-be-unpopular

 Thanks,
 Senaka.


 On Sat, Jan 25, 2014 at 6:32 AM, Afkham Azeez az...@wso2.com wrote:




 On Fri, Jan 24, 2014 at 11:39 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 With C5 logging framework (based on Pax Logging [1]), the log4j is used
 as the logging back-end. But the framework support number of logging API's
 and SLF4J is also one of that. This allows us to use any logging API in the
 components we develop with C5.

 IMO, its a matter of deciding which API to use and follow it as a best
 practice. I'm +1 on using SLF4J.


 Excellent! Let's start converting all the log statements to slf4j syntax.



 Thanks,
 Kishanthan.
 [1] https://ops4j1.jira.com/wiki/display/paxlogging/Pax+Logging


 On Fri, Jan 24, 2014 at 9:23 PM, Afkham Azeez az...@wso2.com wrote:

 The most appealing feature to me is the parametrized log messages, and
 there is no need to wrap statements in if(log.isDebugEnabled()),
 isInfoEnabled() and so on.


 On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez az...@wso2.com wrote:

 http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/

 We should go with SLF4J


 On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga 
 sag...@wso2.comwrote:



 I'm not quite sure whether we can really compare SLF4J with Log4J
 where SLF4J is a logging API while Log4J is a logging implementation (
 Log4J can be used with SLF4J and most common SLF4J binding as well),
 instead we should compare SLF4J API with Commons-Logging API. In my POV
 recent versions of both SLF4J and Commons-Logging are more or less 
 similar.
 I don't have any objection to use SLF4J but have we consider JUL ?


 Please refer required dependencies for each option.

 - Commons-logging -  Need 2 dependencies on runtime as
  Commons-logging API and implementation ( e.g -  SLF4J API,
 Commons-logging-LOG4J bridge)
 - SLF4J  -  Need 3 dependencies on run time as
  SLF4J API, SLF4J-X binding, X logging framework ( e.g  - SLF4J
 API, SLF4J-LOG4J binding , LOG4J )
 - JUL -  0 dependencies just JDK

 If there is no found limitations I would prefer to use JUL
 and worth to consider it before make a conclusion.

 Thanks !


  On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez az...@wso2.comwrote:

  I was reading
 http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html;
  we could remove a lot of boiler
 plate code, and bring in any logging implementation if we use
 SLF4J. Thoughts?

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

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




 --
 Sagara Gunathunga

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




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 %2B94%2077%203320919 blog: *
 *http://blog.afkham.org* http://blog.afkham.org
 * twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 * linked-in: **http://lk.linkedin.com/in/afkhamazeez
 http://lk.linkedin.com/in/afkhamazeez*

 *Lean . Enterprise . Middleware*

 ___
 Dev mailing 

Re: [Dev] We will also need to move Carbon 4.x kernel to GitHub

2014-01-26 Thread Kishanthan Thangarajah
On Mon, Jan 27, 2014 at 9:18 AM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi all,
 I merged and moved the kernel code to github in [1]. Now it is building
 and passing tests 24/1/0 where verifyAdminServiceSecurityTest class:
 org.wso2.carbon.integration.tests test is failing and I am currently
 looking in to it. Another concern is that we need to have an orbit location
 for 4.3.0 (or we can directly put them in the nexus) but there is already
 existing an orbit repo in github. Since no one is using that orbit I think
 we should remove it and put the new orbit bundles there. WDYT?


Yes, we can clean this. We already discussed about releasing orbit bundles
right after creating them. There will be no need to separately build orbit
projects. This repo should be a place to track what are the orbit projects
we have released so far.


 thanks
 Eranda

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


 org.apache.axis2.AxisFault: Exception occurred while trying to invoke service 
 method verifyAdminServices
   at 
 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
   at 
 org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
   at 
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
   at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:474)
   at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:455)
   at 
 org.wso2.carbon.integration.framework.SecurityVerificationTest.verifyAdminServiceSecurity(SecurityVerificationTest.java:59)
   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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
   at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
   at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
   at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
   at 
 org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
   at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
   at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
   at org.testng.TestRunner.privateRun(TestRunner.java:757)
   at org.testng.TestRunner.run(TestRunner.java:608)
   at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
   at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
   at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
   at org.testng.SuiteRunner.run(SuiteRunner.java:240)
   at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
   at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
   at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
   at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
   at org.testng.TestNG.run(TestNG.java:999)
   at 
 org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
   at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
   at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
   at 
 org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)




 On Mon, Jan 20, 2014 at 7:30 PM, Afkham Azeez az...@wso2.com wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 *email: **az...@wso2.com* az...@wso2.com
 * cell: +94 77 3320919 

[Dev] Compilation errors in carbon 4.2.0 Kernel patch0004

2014-01-26 Thread Punnadi Gunarathna
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[35,28]
package org.wso2.carbon.utils does not exist
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[36,41]
package org.wso2.carbon.utils.multitenancy does not exist
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[24,22]
cannot find symbol
symbol  : class CarbonException
location: package org.wso2.carbon
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[29,22]
cannot find symbol
symbol  : class CarbonConstants
location: package org.wso2.carbon
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[30,22]
cannot find symbol
symbol  : class CarbonException
location: package org.wso2.carbon
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[35,30]
package org.wso2.carbon.context does not exist
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[36,30]
package org.wso2.carbon.context does not exist
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[61,62]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.config.ApplicationConfiguration
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[94,71]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.config.ApplicationConfiguration
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[134,70]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.config.ApplicationConfiguration
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[187,65]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.config.ApplicationConfiguration
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[65,76]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[92,65]
cannot find symbol
symbol  : class CarbonException
location: class
org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[28,22]
cannot find symbol
symbol  : class CarbonException
location: package org.wso2.carbon
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[36,28]
package org.wso2.carbon.utils does not exist
[ERROR]
/home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[37,28]
package org.wso2.carbon.utils does not exist
[ERROR]

[Dev] [UES] BUILD FAILURE

2014-01-26 Thread Udara Rathnayake
Hi all,

I'm getting following build error while trying to build UES since
tenant-mgt.xml file does not contains under the
org.wso2.carbon.stratos.common.server.feature 2.2.0.

After changing org.wso2.carbon:org.wso2.carbon.stratos.common.feature
version from 2.2.0 to 2.2.1 within p2 pom.xml I'm able to build UES without
any issues.

Has anyone came across the same problem?

Installation failed.
An error occurred while configuring the installed items
 session context was:(profile=default,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.stratos.common.server.feature.group 2.2.0,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/home/udara/wso2/tmp/ues/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.carbon.stratos.common.server_2.2.0/conf/tenant-mgt.xml
- see details.
Caused by:  java.io.IOException: Source:
/home/udara/wso2/tmp/ues/modules/p2-profile-gen/target/wso2carbon-core-4.2.0/repository/components/default/../features/org.wso2.carbon.stratos.common.server_2.2.0/conf/tenant-mgt.xmldoes
not exists
Application failed, log file location:
/home/udara/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1390799659192.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 User Engagement Server - Parent .. SUCCESS [0.145s]
[INFO] UES Server - UI styles  SUCCESS [2.755s]
[INFO] WSO2 UES - sso common module . SUCCESS [2.856s]
[INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS [0.009s]
[INFO] WSO2 Carbon - UES feature . SUCCESS [0.336s]
[INFO] UES - Profile Generation .. FAILURE [12.700s]
[INFO] WSO2 User Engagement Server - Distribution  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]


Regards,
UdaraR
-- 
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com

Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] ESB 4.8.1 Alpha Release

2014-01-26 Thread Malaka Silva
Find the $subject on following link

https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/27-01/

-- 

Best Regards,

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

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

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


[Dev] BPS 3.2.0 Release

2014-01-26 Thread Malaka Silva
https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/27-01/
wso2bps-3.2.0.ziphttps://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/27-01/wso2bps-3.2.0.zip

-- 

Best Regards,

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

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

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


Re: [Dev] BPS 3.2.0 Release

2014-01-26 Thread Malaka Silva
This is January 27th pack


On Mon, Jan 27, 2014 at 11:01 AM, Malaka Silva mal...@wso2.com wrote:

 https://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/27-01/
 wso2bps-3.2.0.ziphttps://svn.wso2.org/repos/wso2/people/malaka/ESB/ESB4.8.1/27-01/wso2bps-3.2.0.zip

 --

 Best Regards,

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

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

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.




-- 

Best Regards,

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

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

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


Re: [Dev] We will also need to move Carbon 4.x kernel to GitHub

2014-01-26 Thread Eranda Sooriyabandara
Hi Kicha,


On Mon, Jan 27, 2014 at 10:49 AM, Kishanthan Thangarajah 
kishant...@wso2.com wrote:




 On Mon, Jan 27, 2014 at 9:18 AM, Eranda Sooriyabandara era...@wso2.comwrote:

 Hi all,
 I merged and moved the kernel code to github in [1]. Now it is building
 and passing tests 24/1/0 where verifyAdminServiceSecurityTest class:
 org.wso2.carbon.integration.tests test is failing and I am currently
 looking in to it. Another concern is that we need to have an orbit location
 for 4.3.0 (or we can directly put them in the nexus) but there is already
 existing an orbit repo in github. Since no one is using that orbit I think
 we should remove it and put the new orbit bundles there. WDYT?


 Yes, we can clean this. We already discussed about releasing orbit bundles
 right after creating them. There will be no need to separately build orbit
 projects. This repo should be a place to track what are the orbit projects
 we have released so far.


+1

thanks
Eranda



 thanks
 Eranda

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

 org.apache.axis2.AxisFault: Exception occurred while trying to invoke 
 service method verifyAdminServices
  at 
 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
  at 
 org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnlyOperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
  at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
  at 
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
  at 
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
  at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:474)
  at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:455)
  at 
 org.wso2.carbon.integration.framework.SecurityVerificationTest.verifyAdminServiceSecurity(SecurityVerificationTest.java:59)
  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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
  at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
  at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
  at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
  at 
 org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
  at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
  at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
  at org.testng.TestRunner.privateRun(TestRunner.java:757)
  at org.testng.TestRunner.run(TestRunner.java:608)
  at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
  at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
  at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
  at org.testng.SuiteRunner.run(SuiteRunner.java:240)
  at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
  at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
  at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
  at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
  at org.testng.TestNG.run(TestNG.java:999)
  at 
 org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76)
  at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
  at 
 org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
  at 
 org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
  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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
  at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
  at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
  at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
  at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)




 On Mon, Jan 20, 2014 at 7:30 PM, Afkham Azeez az...@wso2.com wrote:

 $subject

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/*
 

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

2014-01-26 Thread Chanika Geeganage
Hi,

Yes, there wasn't. This is because of the changes of the website used for
web-scrapping in WebResourceSampleTestCase. Do we have to fix this in the
released branch?

Thanks


On Mon, Jan 27, 2014 at 8:37 AM, Anjana Fernando anj...@wso2.com wrote:

 Hi,

 Chanika, can you check on this. As I remember, we didn't have any
 integration test failures when we were releasing, the tests mentioned here
 for DSS seems to be tests that require a working Internet connection, maybe
 that has something to do with the failures.

 Cheers,
 Anjana.


 On Sun, Jan 26, 2014 at 1:36 PM, Afkham Azeez az...@wso2.com wrote:

 DSS  AS folks,
 You need to urgently attend to this matter. As we know, build failures
 stop the world. This should be resolved by Monday.

 Azeez


 On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 Chunk 05 build failures are due to some backend/UI test failures. Seems
 like teams have released the products with integration test failures.
 Fixing those failure are not possible because code cannot be committed .
 And even skipping failure cases though testNG xml will take lot of effort
 because need to rewrite testNG xml and include all classes and exclude
 failure classes (TestNg supports only for class exclusion).

 Best option available now is to use 
 testFailureIgnorehttp://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnoreproperty.
  You can set this property with maven build command and ignore
 test failures to get the build passed.

 *DSS Backend failures - *

 build 23-Jan-201 23:45:42 Failed tests:
 initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
 Skipped: 4*

  *AS Backend Test failures - *

 Failed tests:
 testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/student/automationStudent
 build 23-Jan-2014 22:14:05  
 testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
 User belongs to invalid group was able to get the resource expected [true]
 but found [false]
 build 23-Jan-2014 22:14:05  
 testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/students
 build 23-Jan-2014 22:14:05  
 testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
 Input stream failure expected object to not be null
 build 23-Jan-2014 22:14:05
 *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
 Skipped: 5*

 *AS UI test failures -*

 build 23-Jan-2014 22:20:43 Failed tests:
 uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
 Web Application uploading failed expected:true but was:false
 build 23-Jan-2014 22:20:43
 build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0,
 Skipped: 2

 Thanks,
 Krishantha.


 On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 The actual issue is with APIM 1.6 profile generation.

 I could see the following lines in log. Because of generated build is
 unstable, server start-up at integration tests failed.

 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation .. FAILURE [4:41.977s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation Parent ... SUCCESS [1.697s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
  SUCCESS [2.548s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 ... SUCCESS [3:20.956s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 Parent  SUCCESS [0.112s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Test Module  FAILURE [7:41.465s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 UI Test Module . FAILURE [9:10.559s]
 build  24-Jan-2014 03:02:03[INFO] 

[Dev] Twitter Connector SSL handshaking fails

2014-01-26 Thread Gayan Yalpathwala
Hi,

Twitter connector fails to init and throws the following exception.

TID: [0] [ESB] [2014-01-27 09:20:08,385] ERROR
{org.apache.synapse.transport.passthru.TargetHandler} -  I/O error: General
SSLEngine problem {org.apache.synapse.transport.passthru.TargetHandler}
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1362)
at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:513)
at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1177)
at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1149)
at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:220)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:254)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:380)
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:160)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
at java.lang.Thread.run(Thread.java:722)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1683)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:278)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
at
sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:808)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:806)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1299)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:238)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:270)
... 9 more
Caused by: sun.security.validator.ValidatorException: PKIX path building
failed: sun.security.provider.certpath.SunCertPathBuilderException: unable
to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
at
sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
at sun.security.validator.Validator.validate(Validator.java:260)
at
sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
at
sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:283)
at
sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:138)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1328)
... 17 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
at
sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
... 23 more
TID: [0] [ESB] [2014-01-27 09:20:08,402]  WARN
{org.apache.synapse.endpoints.EndpointContext} -  Endpoint :
AnonymousEndpoint will be marked SUSPENDED as it failed
{org.apache.synapse.endpoints.EndpointContext}
TID: [0] [ESB] [2014-01-27 09:20:08,403]  WARN
{org.apache.synapse.endpoints.EndpointContext} -  Suspending endpoint :
AnonymousEndpoint - current suspend duration is : 3ms - Next retry
after : Mon Jan 27 09:20:38 IST 2014
{org.apache.synapse.endpoints.EndpointContext}

I think this occurs due to a certificate change on twitter side. I was able
to overcome this issue by importing api.twitter.com[1] certificate
into client-truststore.jks. Is there a known workaround for this or what
further action can be taken?

[1] 
https://api.twitter.com/oauth2/tokenhttps://www.google.com/url?q=https%3A%2F%2Fapi.twitter.com%2Foauth2%2Ftokensa=Dsntz=1usg=AFQjCNE4_apO1KFJZjWn-dwt_6XfwAOR-Q

Thanks,

-- 
*Gayan Kaushalya Yalpathwala*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 71 8682704 http://asia14.wso2con.com/

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


Re: [Dev] Build failure while building GREG 4.6.0

2014-01-26 Thread Nuwan Silva
any update?


On Fri, Jan 24, 2014 at 4:33 PM, Nuwan Silva nuw...@wso2.com wrote:

 building from
 /platform/turing/products/greg/4.6.0

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Governance Registry - Distribution ... FAILURE
 [55.533s]
 [INFO] WSO2 Governance Registry - Integration Tests .. SKIPPED
 [INFO] WSO2 Governance Registry Test Framework - Registry Test Module
 Group  SKIPPED
 [INFO] Registry TCK Test Module .. SKIPPED
 [INFO] Registry TestNG Test Samples .. SKIPPED
 [INFO] Backward association handler Sample ... SKIPPED
 [INFO] Registry TestNG Test Module ... SKIPPED
 [INFO] Registry Resources TestNG Test Module . SKIPPED
 [INFO] Registry Metadata TestNG Test Module .. SKIPPED
 [INFO] Registry Extensibility TestNG Test Module . SKIPPED
 [INFO] Registry JIRA TestNG Test Module .. SKIPPED
 [INFO] Registry Lifecycle TestNG Test Module . SKIPPED
 [INFO] Registry Search and Versioning TestNG Test Module . SKIPPED
 [INFO] Registry Permissions TestNG Test Module ... SKIPPED
 [INFO] Registry Governance API TestNG Test Module  SKIPPED
 [INFO] Registry TestNG Test Module ... SKIPPED
 [INFO] Registry UI Test Module ... SKIPPED
 [INFO] Integration Test Reporting  SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 56.671s
 [INFO] Finished at: Fri Jan 24 13:55:28 IST 2014
 [INFO] Final Memory: 124M/1325M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
 on project wso2greg: Failed to create assembly: File to filter not found:
 /home/nuwan/wso2/qa/automation_sessions/platform/turing/products/greg/4.6.0/modules/distribution/../p2-profile-gen/target/wso2carbon-core-4.2.0/repository/deployment/server/jaggeryapps/publisher/publisherLogo/logo.png
 (No such file or directory) - [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/MojoExecutionException


 --


 *Nuwan Silva*
 *Senior Software Engineer - QA*
 Mobile: +94779804543

 WSO2 Inc.
 lean . enterprise . middlewear.
 http://www.wso2.com




-- 


*Nuwan Silva*
*Senior Software Engineer - QA*
Mobile: +94779804543

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


Re: [Dev] Twitter Connector SSL handshaking fails

2014-01-26 Thread Dushan Abeyruwan
HI
May be twitter trust certificates might have renewed and that's why once we
add twitter certificate to client-trust-store it started to work, we should
add this to documentation
   Need to get certificate from https://api.twitter.com/oauth2/token  and
adding to trust store.


On Mon, Jan 27, 2014 at 11:15 AM, Gayan Yalpathwala gay...@wso2.com wrote:

 Hi,

 Twitter connector fails to init and throws the following exception.

 TID: [0] [ESB] [2014-01-27 09:20:08,385] ERROR
 {org.apache.synapse.transport.passthru.TargetHandler} -  I/O error: General
 SSLEngine problem {org.apache.synapse.transport.passthru.TargetHandler}
 javax.net.ssl.SSLHandshakeException: General SSLEngine problem
 at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1362)
 at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:513)
  at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1177)
 at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1149)
  at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469)
 at
 org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:220)
  at
 org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:254)
 at
 org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:380)
  at
 org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:118)
 at
 org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:160)
  at
 org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:342)
 at
 org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
  at
 org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
 at
 org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
  at
 org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
 at java.lang.Thread.run(Thread.java:722)
 Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
 at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
 at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1683)
  at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:278)
 at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
  at
 sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
 at
 sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
 at sun.security.ssl.Handshaker$1.run(Handshaker.java:808)
  at sun.security.ssl.Handshaker$1.run(Handshaker.java:806)
 at java.security.AccessController.doPrivileged(Native Method)
  at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1299)
 at
 org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:238)
  at
 org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:270)
 ... 9 more
 Caused by: sun.security.validator.ValidatorException: PKIX path building
 failed: sun.security.provider.certpath.SunCertPathBuilderException: unable
 to find valid certification path to requested target
  at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
 at
 sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
  at sun.security.validator.Validator.validate(Validator.java:260)
 at
 sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
  at
 sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:283)
 at
 sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:138)
  at
 sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1328)
 ... 17 more
 Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
 unable to find valid certification path to requested target
  at
 sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
 at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
  at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
 ... 23 more
 TID: [0] [ESB] [2014-01-27 09:20:08,402]  WARN
 {org.apache.synapse.endpoints.EndpointContext} -  Endpoint :
 AnonymousEndpoint will be marked SUSPENDED as it failed
 {org.apache.synapse.endpoints.EndpointContext}
 TID: [0] [ESB] [2014-01-27 09:20:08,403]  WARN
 {org.apache.synapse.endpoints.EndpointContext} -  Suspending endpoint :
 AnonymousEndpoint - current suspend duration is : 3ms - Next retry
 after : Mon Jan 27 09:20:38 IST 2014
 {org.apache.synapse.endpoints.EndpointContext}

 I think this occurs due to a certificate change on twitter side. I was
 able to overcome this issue by importing api.twitter.com[1] certificate
 into client-truststore.jks. Is there a known workaround for this or what
 further action can be taken?

 [1] 
 

[Dev] [PayloadFactory] Impossible to provide arguments directly to format without any wrapper element

2014-01-26 Thread Subash Chaturanga
Hi,
My scenario is as follows. Following is not possible and cannot save . And
I have added the exception thrown. For the media type json I could save
the api.

payloadFactory media-type=xml
  format$1/format
  args
 arg evaluator=xml
expression=$body/root:rootelement/child::out/child::*/arg
  /args
   /payloadFactory


Following is the error. But if I add formatroot$1root/format then
it works fine and output is embedded inside root. But If I do not want a
such dummy root  element to be part of my response. Any idea to sort this
out ? Is it a bug ?


[2014-01-27 11:30:36,318] ERROR - RPCMessageReceiver Exception occurred
while trying to invoke service method updateApiFromString
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.rest.api.stub.RestApiAdminStub.updateApiFromString(RestApiAdminStub.java:3386)
at
org.wso2.carbon.rest.api.ui.client.RestApiAdminClient.updateApiFromString(RestApiAdminClient.java:230)
at
org.apache.jsp.api.savesource_002dajaxprocessor_jsp._jspService(org.apache.jsp.api.savesource_002dajaxprocessor_jsp:133)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at

Re: [Dev] Compilation errors in carbon 4.2.0 Kernel patch0004

2014-01-26 Thread Ashansa Perera
Hi,
I was able to build all the kernal patches without any issue.


On Mon, Jan 27, 2014 at 10:49 AM, Punnadi Gunarathna punn...@wso2.comwrote:

 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[35,28]
 package org.wso2.carbon.utils does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[36,41]
 package org.wso2.carbon.utils.multitenancy does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[24,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[29,22]
 cannot find symbol
 symbol  : class CarbonConstants
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[30,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[35,30]
 package org.wso2.carbon.context does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[36,30]
 package org.wso2.carbon.context does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[61,62]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[94,71]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[134,70]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[187,65]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[65,76]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[92,65]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[28,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[36,28]
 package org.wso2.carbon.utils does not exist
 [ERROR]
 

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

2014-01-26 Thread Supun Malinga
Hi,

All integration tests were successful at the release time for chunk05. We
checked in both the release builder and locally.. In case of failures I
have send mails to dev@ and got them resolved.. Shall we build from the tag
[0] and verify as well?.

[0] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk05/

thanks,


On Sun, Jan 26, 2014 at 1:36 PM, Afkham Azeez az...@wso2.com wrote:

 DSS  AS folks,
 You need to urgently attend to this matter. As we know, build failures
 stop the world. This should be resolved by Monday.

 Azeez


 On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 Chunk 05 build failures are due to some backend/UI test failures. Seems
 like teams have released the products with integration test failures.
 Fixing those failure are not possible because code cannot be committed .
 And even skipping failure cases though testNG xml will take lot of effort
 because need to rewrite testNG xml and include all classes and exclude
 failure classes (TestNg supports only for class exclusion).

 Best option available now is to use 
 testFailureIgnorehttp://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnoreproperty.
  You can set this property with maven build command and ignore
 test failures to get the build passed.

 *DSS Backend failures - *

 build 23-Jan-201 23:45:42 Failed tests:
 initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
 Skipped: 4*

  *AS Backend Test failures - *

 Failed tests:
 testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/student/automationStudent
 build 23-Jan-2014 22:14:05  
 testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
 User belongs to invalid group was able to get the resource expected [true]
 but found [false]
 build 23-Jan-2014 22:14:05  
 testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/students
 build 23-Jan-2014 22:14:05  
 testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
 Input stream failure expected object to not be null
 build 23-Jan-2014 22:14:05
 *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
 Skipped: 5*

 *AS UI test failures -*

 build 23-Jan-2014 22:20:43 Failed tests:
 uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
 Web Application uploading failed expected:true but was:false
 build 23-Jan-2014 22:20:43
 build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0,
 Skipped: 2

 Thanks,
 Krishantha.


 On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 The actual issue is with APIM 1.6 profile generation.

 I could see the following lines in log. Because of generated build is
 unstable, server start-up at integration tests failed.

 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation .. FAILURE [4:41.977s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation Parent ... SUCCESS [1.697s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
  SUCCESS [2.548s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 ... SUCCESS [3:20.956s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 Parent  SUCCESS [0.112s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Test Module  FAILURE [7:41.465s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 UI Test Module . FAILURE [9:10.559s]
 build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Tests .. SUCCESS [0.840s]

 Thanks,

 Krishantha.



 On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath isuru...@wso2.comwrote:

 Hi Krishantha,

 I executed 

Re: [Dev] Compilation errors in carbon 4.2.0 Kernel patch0004

2014-01-26 Thread Manoj Kumara
Hi Punnadi,

This should be building without any issue. Can you please check again.

Thanks
Manoj

Best Regards..


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

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


On Mon, Jan 27, 2014 at 10:49 AM, Punnadi Gunarathna punn...@wso2.comwrote:

 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[35,28]
 package org.wso2.carbon.utils does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/handler/DefaultAppDeployer.java:[36,41]
 package org.wso2.carbon.utils.multitenancy does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[24,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[29,22]
 cannot find symbol
 symbol  : class CarbonConstants
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[30,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[35,30]
 package org.wso2.carbon.context does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[36,30]
 package org.wso2.carbon.context does not exist
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[61,62]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[94,71]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[134,70]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/config/ApplicationConfiguration.java:[187,65]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.config.ApplicationConfiguration
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[65,76]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/persistence/CarbonAppPersistenceManager.java:[92,65]
 cannot find symbol
 symbol  : class CarbonException
 location: class
 org.wso2.carbon.application.deployer.persistence.CarbonAppPersistenceManager
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[28,22]
 cannot find symbol
 symbol  : class CarbonException
 location: package org.wso2.carbon
 [ERROR]
 /home/appfactory/carbon420/kernel/patches/patch0004/core/org.wso2.carbon.application.deployer/4.2.0/src/main/java/org/wso2/carbon/application/deployer/internal/ApplicationManager.java:[36,28]
 package org.wso2.carbon.utils does not exist
 [ERROR]
 

Re: [Dev] Please provide an update on stabilizing the current branches chunks?

2014-01-26 Thread Sagara Gunathunga
On Mon, Jan 27, 2014 at 11:58 AM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 All integration tests were successful at the release time for chunk05. We
 checked in both the release builder and locally.. In case of failures I
 have send mails to dev@ and got them resolved.. Shall we build from the
 tag [0] and verify as well?.


Thanks for confirmation Im tying to build the tag locally.

Thanks !


 [0] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk05/

 thanks,


 On Sun, Jan 26, 2014 at 1:36 PM, Afkham Azeez az...@wso2.com wrote:

 DSS  AS folks,
 You need to urgently attend to this matter. As we know, build failures
 stop the world. This should be resolved by Monday.

 Azeez


 On Sun, Jan 26, 2014 at 1:19 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 Chunk 05 build failures are due to some backend/UI test failures. Seems
 like teams have released the products with integration test failures.
 Fixing those failure are not possible because code cannot be committed .
 And even skipping failure cases though testNG xml will take lot of effort
 because need to rewrite testNG xml and include all classes and exclude
 failure classes (TestNg supports only for class exclusion).

 Best option available now is to use 
 testFailureIgnorehttp://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#testFailureIgnoreproperty.
  You can set this property with maven build command and ignore
 test failures to get the build passed.

 *DSS Backend failures - *

 build 23-Jan-201 23:45:42 Failed tests:
 initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 build 23-Jan-2014 23:45:42  
 selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
 expected:true but was:false
 *build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
 Skipped: 4*

  *AS Backend Test failures - *

 Failed tests:
 testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/student/automationStudent
 build 23-Jan-2014 22:14:05  
 testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
 User belongs to invalid group was able to get the resource expected [true]
 but found [false]
 build 23-Jan-2014 22:14:05  
 testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
 Server returned HTTP response code: 500 for URL:
 https://localhost:9443/services/StudentService/students
 build 23-Jan-2014 22:14:05  
 testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
 Input stream failure expected object to not be null
 build 23-Jan-2014 22:14:05
 *build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
 Skipped: 5*

 *AS UI test failures -*

 build 23-Jan-2014 22:20:43 Failed tests:
 uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
 Web Application uploading failed expected:true but was:false
 build 23-Jan-2014 22:20:43
 build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0,
 Skipped: 2

 Thanks,
 Krishantha.


 On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Hi Isuruwan,

 The actual issue is with APIM 1.6 profile generation.

 I could see the following lines in log. Because of generated build is
 unstable, server start-up at integration tests failed.

 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation .. FAILURE [4:41.977s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile 
 Generation Parent ... SUCCESS [1.697s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
  SUCCESS [2.548s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 ... SUCCESS [3:20.956s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
 Parent  SUCCESS [0.112s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Test Module  FAILURE [7:41.465s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 UI Test Module . FAILURE [9:10.559s]
 build  24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration 
 Tests ..