[Dev] [AppM] AppM load test on gateway using jmeter

[Sajith Abeywardhana]

Hi,

We are planning to start the $subject. So we configured a AppM cluster with
publisher, 2 store, 2 gateway and IDP. Each gateway instance(hosted as open
stack instance) dose have 2GB RAM and ubuntu 14.04 installed. We are
planning to load 4 sample web applications simultaneously. Please kind
enough to provide feedbacks on this.

*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge PR

[Rajith Roshan]

Hi,

Please review and merge PR[1] for JIRA issue [2] .

[1] - https://github.com/wso2/product-greg/pull/119

https://github.com/wso2/wso2-synapse/pull/251
[2] - https://wso2.org/jira/browse/REGISTRY-2665


Thanks,
Rajith

-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 %2B94-71-554-8430
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Automation Test coverage of ESB 4.9.0 new features

[Naasheer Ali]

Hi Malaka,

Please find the PR[1] for Kafka inbound EP.

[1]- https://github.com/wso2/product-esb/pull/228

Regards,
-- 

*Naasheer Ali* | Associate Software Engineer

WSO2, Inc |#218, Stanley Road, Jaffna, Sri Lanka

Email: naashe...@wso2.com

lean . enterprise . middleware

On Fri, Jul 10, 2015 at 11:43 AM, Malaka Silva mal...@wso2.com wrote:

 1. Kafka support in ESB - Kathees will send the PR on Monday
 2. MQTT Inbound transport - Elilmatha will send the PR today

 On Fri, Jul 10, 2015 at 11:37 AM, Ravi Undupitiya r...@wso2.com wrote:

 Hi Asanthi,

 For HTTP HEAD method we didn't have client support when this feature was
 done, but Chanaka has built a client with this support for HTTP PATCH. I'll
 use this to create a test case and let you know.


 On Fri, Jul 10, 2015 at 10:12 AM, Asanthi Kulasinghe asan...@wso2.com
 wrote:

 Hi  ESB Team,

 We are currently in the process of analyzing gaps between ESB 4.9.0
 manually executed and automated test cases.
 As a start we are looking into to the automation test case coverage of
 4.9.0 specific new features.
 Out of the feature list from [1] we couldn't find automation tests for
 some of the features mentioned below.

 *Features with automation tests*

- Add RabbitMQ transport receiver/sender
- Persisting Messages from ESB Message Store {jdbc storage to work
with MSSQL}
- Supporting Class mediators in Stratos
- OCSP/CRL Validation at Transport Listener
- Enabling HTTP Cache Control headers (Etag, etc)
- Coordination support for Message Stores and Processors
- For-each mediator
- Inbound Endpoints :

- Inbound HL7 Endpoint
- HTTP Inbound Endpoint
- HTTPS Inbound Endpoint
- HTTPS Inbound Endpoint
- CXF WS-RM Inbound Endpoint
- JMS
- File
- Custom

 *Features without automation tests*

- Dynamic SSL Profiles for sender and listener
- Support HTTP Patch
- HTTP HEAD Method support for REST API's
- Inbound Endpoints:

   - Kafka support in ESB
   - MQTT Inbound transport

 To my understanding there are tests for some of the above features that
 are yet to be merged.
 Could you please confirm the accuracy of the above lists (automation
 test availability)  and reason for the absence of automation tests for
 certain features  (Eg:  Not yet merged,  Automation is not possible  etc)

 [1] https://redmine.wso2.com/versions/43


 Thanks  Regards
 *Asanthi Kulasinghe*
 WSO2 Inc; http://www.wso2.com/.
 Mobile: +94777355522





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


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

 Lean . Enterprise . Middleware




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 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 mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB Kafka automation support

[Kathees Rajendram]

Hi All,

Is Kafka test support framework available in integration base? Now in the
integration we manually start the zookeeper and Kafka server.

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Factory] UX/UI Incorporation

[Mahesh Chinthaka]

adding RoshanD. He is doing  009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
 page.

On Mon, Jul 13, 2015 at 3:53 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:

 Hi All,

 We have added notification updates on below pages.

 1.  form_notification.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/form_notification.html

 2. block type notification - 009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html

 please be kind enough to merge above changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi All,

 We have added application notification pane to overview
 page(009_cloud_app_details_initial.html). please check.


 https://raw.githubusercontent.com/wso2-dev-ux/product-cloud/master/Markup/009_cloud_app_details_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 10:50 AM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika ,

 I remember the wireframes. Actually 2 things,

 1. Where can I find the markup for issues_initial_blank page (Actually
 for the button Report an Issue)?
 2. Last time when I took a git pull (before sending my last mail) create
 issue button was not there in the issues_initial page. Now its there :)
 thank you.


 On Wed, Jul 8, 2015 at 6:19 AM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi,

 this is the updated listing page..


 https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/issues_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 6:15 AM, Dakshika Jayathilaka daksh...@wso2.com
  wrote:

 Hi Mahesh,

 Its already there..(issues_initial_blank) seems you missed important
 points that we discussed on the meeting.. :). I have attached wireframes
 for further reference. please be kind enough to check. We usually update
 markup pages everyday. so please take pull and continue your work.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Jul 7, 2015 at 7:00 PM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika,

 In issue_initial.html  we dont have a Create Issue button.
 In our early UI we had a create issue (New Issue) button in index
 page of the issue tracker.
 With new UI where are we going to have that button or link for a user
 to create an issue ?

 In new UI if there are issues created , then those issues will be
 shown in the data table. When there are no issues,  data table will be
 empty.
 IMO we should have a button in index page to create issues. Otherwise
 how the user going to add an issue ?
 This is the initial landing page for a user when he clicks on the
 issue tracker link in the left side panel.

 Thanks.

 On Fri, Jul 3, 2015 at 4:41 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 We have added issues_new.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_new.html
  and issues_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_initial.html
  pages
 to git repo.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Fri, Jun 19, 2015 at 9:13 AM, Manisha Gayathri mani...@wso2.com
 wrote:

 Thanks Dakshika,

 Hasitha will carry on the work regarding app home page

 Thanks
 Manisha

 On Thu, Jun 18, 2015 at 5:04 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 I have added 009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
   to git repo. Please be kind enough to merge changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Jun 16, 2015 at 10:00 AM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 I have added 012_cloud_listing.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/012_cloud_listing.html
  to
 git repo. Please be kind enough to merge changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jun 10, 2015 at 2:33 PM, Danushka Fernando 
 danush...@wso2.com wrote:

 Hi Dakshika
 In Resource / Runtime Config pages we need some 

[Dev] [Fasttrack][Writing Carbon Component] - org.apache.axis2.AxisFault: The server did not recognise the action which it received

[Dinusha Boteju]

Hi all,

I'm trying to create a carbon component from [1] tutorial. I was able to
create the student mgt component mentioned in the tutorial and it was
successful. Now I'm trying to create another component following the same
steps. I've developed the server side, stubs and the client. When I access
the component from the wso2 AS I'm getting the exception [2] in the
browser. Any particular reason for this?

[1] -
http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/

[2]
*The following error details are available. Please refer logs for more
details.*
org.apache.axis2.AxisFault: The server did not recognise the action which
it received:
at
org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:359)
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.wso2.order.service.stub.OrderServiceStub.getOrder(OrderServiceStub.java:195)
at org.wso2.order.service.client.Client.getOrder(Client.java:27)
at
org.apache.jsp.order_002dmgt.index_jsp._jspService(org.apache.jsp.order_002dmgt.index_jsp:76)
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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:605)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:544)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1015)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:700)
at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at
org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at
org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at
org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at
org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_insertAttribute_7(org.apache.jsp.admin.layout.template_jsp:603)
at
org.apache.jsp.admin.layout.template_jsp._jspService(org.apache.jsp.admin.layout.template_jsp:335)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at 

Re: [Dev] [Fasttrack][Writing Carbon Component] - org.apache.axis2.AxisFault: The server did not recognise the action which it received

[Thusitha Thilina Dayaratne]

Hi Dinusha,

Check if the backend service url that you are giving is correct.
Thanks
/Thusitha

On Mon, Jul 13, 2015 at 2:20 PM, Dinusha Boteju dinus...@wso2.com wrote:

 Hi all,

 I'm trying to create a carbon component from [1] tutorial. I was able to
 create the student mgt component mentioned in the tutorial and it was
 successful. Now I'm trying to create another component following the same
 steps. I've developed the server side, stubs and the client. When I access
 the component from the wso2 AS I'm getting the exception [2] in the
 browser. Any particular reason for this?

 [1] -
 http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/

 [2]
 *The following error details are available. Please refer logs for more
 details.*
 org.apache.axis2.AxisFault: The server did not recognise the action which
 it received:
 at
 org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:359)
 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.wso2.order.service.stub.OrderServiceStub.getOrder(OrderServiceStub.java:195)
 at org.wso2.order.service.client.Client.getOrder(Client.java:27)
 at
 org.apache.jsp.order_002dmgt.index_jsp._jspService(org.apache.jsp.order_002dmgt.index_jsp:76)
 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
 at
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:605)
 at
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:544)
 at
 org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
 at
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1015)
 at
 org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:700)
 at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
 at
 org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
 at
 org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
 at
 org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
 at
 org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
 at
 org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
 at
 org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
 at
 org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
 at
 org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
 at
 

Re: [Dev] [App Factory] UX/UI Incorporation

[Dakshika Jayathilaka]

Hi All,

We have added notification updates on below pages.

1.  form_notification.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/form_notification.html

2. block type notification - 009_cloud_app_details_initial.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html

please be kind enough to merge above changes.

Regards,

*Dakshika Jayathilaka*
PMC Member  Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:

 Hi All,

 We have added application notification pane to overview
 page(009_cloud_app_details_initial.html). please check.


 https://raw.githubusercontent.com/wso2-dev-ux/product-cloud/master/Markup/009_cloud_app_details_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 10:50 AM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika ,

 I remember the wireframes. Actually 2 things,

 1. Where can I find the markup for issues_initial_blank page (Actually
 for the button Report an Issue)?
 2. Last time when I took a git pull (before sending my last mail) create
 issue button was not there in the issues_initial page. Now its there :)
 thank you.


 On Wed, Jul 8, 2015 at 6:19 AM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi,

 this is the updated listing page..


 https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/issues_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 6:15 AM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi Mahesh,

 Its already there..(issues_initial_blank) seems you missed important
 points that we discussed on the meeting.. :). I have attached wireframes
 for further reference. please be kind enough to check. We usually update
 markup pages everyday. so please take pull and continue your work.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Jul 7, 2015 at 7:00 PM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika,

 In issue_initial.html  we dont have a Create Issue button.
 In our early UI we had a create issue (New Issue) button in index page
 of the issue tracker.
 With new UI where are we going to have that button or link for a user
 to create an issue ?

 In new UI if there are issues created , then those issues will be
 shown in the data table. When there are no issues,  data table will be
 empty.
 IMO we should have a button in index page to create issues. Otherwise
 how the user going to add an issue ?
 This is the initial landing page for a user when he clicks on the
 issue tracker link in the left side panel.

 Thanks.

 On Fri, Jul 3, 2015 at 4:41 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 We have added issues_new.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_new.html
  and issues_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_initial.html
  pages
 to git repo.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Fri, Jun 19, 2015 at 9:13 AM, Manisha Gayathri mani...@wso2.com
 wrote:

 Thanks Dakshika,

 Hasitha will carry on the work regarding app home page

 Thanks
 Manisha

 On Thu, Jun 18, 2015 at 5:04 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 I have added 009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
   to git repo. Please be kind enough to merge changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Jun 16, 2015 at 10:00 AM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 I have added 012_cloud_listing.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/012_cloud_listing.html
  to
 git repo. Please be kind enough to merge changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jun 10, 2015 at 2:33 PM, Danushka Fernando 
 danush...@wso2.com wrote:

 Hi Dakshika
 In Resource / Runtime Config pages we need some changes to be
 done refer to [1] architecture@.

 [1] [AF] Removing Registry Mounts for the Dev, Test, Prod
 Registries

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

 On Wed, Jun 10, 2015 at 2:04 PM, 

Re: [Dev] Please review and merge PR

[Imesh Gunaratne]

Thanks Anuruddha! I have now merged the pull request.

On Mon, Jul 13, 2015 at 11:09 AM, Anuruddha Liyanarachchi 
anurudd...@wso2.com wrote:

 Hi,

 $subject please for PR [1].
 This containing changes to add Hbase and mysql configurations to DAS
 docker images.


 [1] https://github.com/wso2/product-private-paas/pull/102

 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 a thili...@wso2.comnurudd...@wso2.com




-- 
*Imesh Gunaratne*
Senior 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] Please review and merge the PR

[Vinod Kavinda]

hi,
Please merge the PR[1] for isuues [2], and [3].

[1] - https://github.com/wso2/carbon-business-process/pull/104
[2] - https://wso2.org/jira/browse/BPS-731
[3] - https://wso2.org/jira/browse/BPS-712

Thank You.
-- 
Vinod Kavinda
Software Engineer
*WSO2 Inc. - lean . enterprise . middleware http://www.wso2.com.*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Fasttrack][Writing Carbon Component] - org.apache.axis2.AxisFault: The server did not recognise the action which it received

[Dinusha Boteju]

Ops. I've missed that place. Thanks :)

On Mon, Jul 13, 2015 at 2:37 PM, Thusitha Thilina Dayaratne 
thusit...@wso2.com wrote:

 Hi Dinusha,

 Check if the backend service url that you are giving is correct.
 Thanks
 /Thusitha

 On Mon, Jul 13, 2015 at 2:20 PM, Dinusha Boteju dinus...@wso2.com wrote:

 Hi all,

 I'm trying to create a carbon component from [1] tutorial. I was able to
 create the student mgt component mentioned in the tutorial and it was
 successful. Now I'm trying to create another component following the same
 steps. I've developed the server side, stubs and the client. When I access
 the component from the wso2 AS I'm getting the exception [2] in the
 browser. Any particular reason for this?

 [1] -
 http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/

 [2]
 *The following error details are available. Please refer logs for more
 details.*
 org.apache.axis2.AxisFault: The server did not recognise the action which
 it received:
 at
 org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114)
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
 at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
 at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:359)
 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.wso2.order.service.stub.OrderServiceStub.getOrder(OrderServiceStub.java:195)
 at org.wso2.order.service.client.Client.getOrder(Client.java:27)
 at
 org.apache.jsp.order_002dmgt.index_jsp._jspService(org.apache.jsp.order_002dmgt.index_jsp:76)
 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
 at
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:605)
 at
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:544)
 at
 org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
 at
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1015)
 at
 org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:700)
 at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
 at
 org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
 at
 org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
 at
 org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
 at
 org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
 at
 org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
 at
 org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
 at
 org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
 at
 

Re: [Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Ishara Karunarathna]

Hi,

On Mon, Jul 13, 2015 at 6:44 PM, Nadeesha Meegoda nadees...@wso2.com
wrote:

 Hi all,

 I have a concern regarding the steps followed when configuring a New Key
 store in ES where ES authenticates via IS.

I think you have configured SSO with SAML.


 These are the steps followed :

 1. Created a Key store for ES, Imported the key to Client Trust store in ES
 2. Configured ES to work with the new Key store
 3. Added the ES key to IS Client Trust Store - Note that IS is having the
 default wso2carbon.jks


Here you have created a new keystore and import your public key to your
existing client-truststore.jks

And to work sso scenario you will have to import public cert of IS to your
new keystore

Thanks,
Ishara


 We thought following the above steps will be enough for the Key store
 configurations since ES has the default wso2carbon.jks imported to its
 Client Trust store anyway.

 However ES login via IS was not successful due to *not* having the IS
 public key details imported into the key that I created in ES.So ultimately
 the data decryption didn't happen successfully. My concern is that All the
 third party public keys should be imported in to the client trust store not
 to the main key itself. What we do here is we are importing the IS public
 key details to the main key of ES.

 My question is do we need to follow all the above with importing the IS
 public key to the main key of ES or 1,2,3 steps would be enough for the New
 key store to work?


 Thanks  Regards,
 Nadeesha

 --
 *Nadeesha Meegoda*
 Software Engineer - QA
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 email : nadees...@wso2.com
 mobile: +94783639540
 %2B94%2077%202273555

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




-- 
Ishara Karunarathna
Senior Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Factory] UX/UI Incorporation

[Dakshika Jayathilaka]

Hi All,

We have added  content loading methods to
cloud_app_details_initial_content_load.html
https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/cloud_app_details_initial_content_load.html
.
you can select any div and call 'show'/ 'hide' method.

*Sample: *

*$('selector').loading('show/hide');*

*Preview: *

https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/cloud_app_details_initial_content_load.html

Regards,

*Dakshika Jayathilaka*
PMC Member  Committer of Apache Stratos
Senior Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Mon, Jul 13, 2015 at 5:00 PM, Mahesh Chinthaka mahe...@wso2.com wrote:

 adding RoshanD. He is doing  009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
  page.

 On Mon, Jul 13, 2015 at 3:53 PM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi All,

 We have added notification updates on below pages.

 1.  form_notification.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/form_notification.html

 2. block type notification - 009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html

 please be kind enough to merge above changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 6:19 PM, Dakshika Jayathilaka daksh...@wso2.com
 wrote:

 Hi All,

 We have added application notification pane to overview
 page(009_cloud_app_details_initial.html). please check.


 https://raw.githubusercontent.com/wso2-dev-ux/product-cloud/master/Markup/009_cloud_app_details_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 10:50 AM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika ,

 I remember the wireframes. Actually 2 things,

 1. Where can I find the markup for issues_initial_blank page (Actually
 for the button Report an Issue)?
 2. Last time when I took a git pull (before sending my last mail)
 create issue button was not there in the issues_initial page. Now its there
 :) thank you.


 On Wed, Jul 8, 2015 at 6:19 AM, Dakshika Jayathilaka daksh...@wso2.com
  wrote:

 Hi,

 this is the updated listing page..


 https://cdn.rawgit.com/wso2-dev-ux/product-cloud/master/Markup/issues_initial.html

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Wed, Jul 8, 2015 at 6:15 AM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi Mahesh,

 Its already there..(issues_initial_blank) seems you missed important
 points that we discussed on the meeting.. :). I have attached wireframes
 for further reference. please be kind enough to check. We usually update
 markup pages everyday. so please take pull and continue your work.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Tue, Jul 7, 2015 at 7:00 PM, Mahesh Chinthaka mahe...@wso2.com
 wrote:

 Hi Dakshika,

 In issue_initial.html  we dont have a Create Issue button.
 In our early UI we had a create issue (New Issue) button in index
 page of the issue tracker.
 With new UI where are we going to have that button or link for a
 user to create an issue ?

 In new UI if there are issues created , then those issues will be
 shown in the data table. When there are no issues,  data table will be
 empty.
 IMO we should have a button in index page to create issues.
 Otherwise how the user going to add an issue ?
 This is the initial landing page for a user when he clicks on the
 issue tracker link in the left side panel.

 Thanks.

 On Fri, Jul 3, 2015 at 4:41 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 We have added issues_new.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_new.html
  and issues_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/issues_initial.html
  pages
 to git repo.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache Stratos
 Senior Software Engineer
 WSO2, Inc.
 lean.enterprise.middleware
 0771100911

 On Fri, Jun 19, 2015 at 9:13 AM, Manisha Gayathri mani...@wso2.com
  wrote:

 Thanks Dakshika,

 Hasitha will carry on the work regarding app home page

 Thanks
 Manisha

 On Thu, Jun 18, 2015 at 5:04 PM, Dakshika Jayathilaka 
 daksh...@wso2.com wrote:

 Hi All,

 I have added 009_cloud_app_details_initial.html
 https://github.com/wso2-dev-ux/product-cloud/blob/master/Markup/009_cloud_app_details_initial.html
   to git repo. Please be kind enough to merge changes.

 Regards,

 *Dakshika Jayathilaka*
 PMC Member  Committer of Apache 

Re: [Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Ishara Karunarathna]

On Tue, Jul 14, 2015 at 9:59 AM, Pavithra Madurangi pavit...@wso2.com
wrote:



 On Tue, Jul 14, 2015 at 9:52 AM, Ishara Karunarathna isha...@wso2.com
 wrote:

 Hi,

 On Mon, Jul 13, 2015 at 6:44 PM, Nadeesha Meegoda nadees...@wso2.com
 wrote:

 Hi all,

 I have a concern regarding the steps followed when configuring a New Key
 store in ES where ES authenticates via IS.

 I think you have configured SSO with SAML.


 These are the steps followed :

 1. Created a Key store for ES, Imported the key to Client Trust store in
 ES
 2. Configured ES to work with the new Key store
 3. Added the ES key to IS Client Trust Store - Note that IS is having
 the default wso2carbon.jks


 Here you have created a new keystore and import your public key to your
 existing client-truststore.jks

 And to work sso scenario you will have to import public cert of IS to
 your new keystore


 ​Normally we add certificates from other parties that we expect to
 communicate with​
 ​,​

 ​to trust store (trust store of ES in this case).​ So instead of doing so,
 why do we have to add it to key store of ES ?

For the SSL communication yes we add trusted public keys to
client-truststore.jks.
But this case we keep IDP public keys in our main keystore.


 Thanks,
 Ishara


 We thought following the above steps will be enough for the Key store
 configurations since ES has the default wso2carbon.jks imported to its
 Client Trust store anyway.

 However ES login via IS was not successful due to *not* having the IS
 public key details imported into the key that I created in ES.So ultimately
 the data decryption didn't happen successfully. My concern is that All the
 third party public keys should be imported in to the client trust store not
 to the main key itself. What we do here is we are importing the IS public
 key details to the main key of ES.

 My question is do we need to follow all the above with importing the IS
 public key to the main key of ES or 1,2,3 steps would be enough for the New
 key store to work?


 Thanks  Regards,
 Nadeesha

 --
 *Nadeesha Meegoda*
 Software Engineer - QA
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 email : nadees...@wso2.com
 mobile: +94783639540
 %2B94%2077%202273555

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




 --
 Ishara Karunarathna
 Senior Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791

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




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




-- 
Ishara Karunarathna
Senior Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Nadeesha Meegoda]

Thanks for the response Ishara. SSO works fine when the IS public key is
added to the main keystore in ES. Thanks for the clarification.

On Tue, Jul 14, 2015 at 10:10 AM, Ishara Karunarathna isha...@wso2.com
wrote:



 On Tue, Jul 14, 2015 at 9:59 AM, Pavithra Madurangi pavit...@wso2.com
 wrote:



 On Tue, Jul 14, 2015 at 9:52 AM, Ishara Karunarathna isha...@wso2.com
 wrote:

 Hi,

 On Mon, Jul 13, 2015 at 6:44 PM, Nadeesha Meegoda nadees...@wso2.com
 wrote:

 Hi all,

 I have a concern regarding the steps followed when configuring a New
 Key store in ES where ES authenticates via IS.

 I think you have configured SSO with SAML.


 These are the steps followed :

 1. Created a Key store for ES, Imported the key to Client Trust store
 in ES
 2. Configured ES to work with the new Key store
 3. Added the ES key to IS Client Trust Store - Note that IS is having
 the default wso2carbon.jks


 Here you have created a new keystore and import your public key to your
 existing client-truststore.jks

 And to work sso scenario you will have to import public cert of IS to
 your new keystore


 ​Normally we add certificates from other parties that we expect to
 communicate with​
 ​,​

 ​to trust store (trust store of ES in this case).​ So instead of doing
 so, why do we have to add it to key store of ES ?

 For the SSL communication yes we add trusted public keys to 
 client-truststore.jks.
 But this case we keep IDP public keys in our main keystore.


 Thanks,
 Ishara


 We thought following the above steps will be enough for the Key store
 configurations since ES has the default wso2carbon.jks imported to its
 Client Trust store anyway.

 However ES login via IS was not successful due to *not* having the IS
 public key details imported into the key that I created in ES.So ultimately
 the data decryption didn't happen successfully. My concern is that All the
 third party public keys should be imported in to the client trust store not
 to the main key itself. What we do here is we are importing the IS public
 key details to the main key of ES.

 My question is do we need to follow all the above with importing the IS
 public key to the main key of ES or 1,2,3 steps would be enough for the New
 key store to work?


 Thanks  Regards,
 Nadeesha

 --
 *Nadeesha Meegoda*
 Software Engineer - QA
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 email : nadees...@wso2.com
 mobile: +94783639540
 %2B94%2077%202273555

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




 --
 Ishara Karunarathna
 Senior Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791

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




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




 --
 Ishara Karunarathna
 Senior Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791




-- 
*Nadeesha Meegoda*
Software Engineer - QA
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
email : nadees...@wso2.com
mobile: +94783639540
%2B94%2077%202273555
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] H2 in-memory exception when shutting down server

[Pumudu Ruhunage]

Hi Akalanka,

it already have ;DB_CLOSE_ON_EXIT=FALSE in db url. have to check what was
causing the issue. opened a jira[1] to track progress.

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

Thanks,
Pumudu

On Mon, Jul 13, 2015 at 7:08 PM, Akalanka Pagoda Arachchi 
darsha...@wso2.com wrote:

 Hi Pumudu,

 This occurs when MB tries to access the H2 database even after the
 database is closed. If the database url does have the property mentioned in
 the error (;DB_CLOSE_ON_EXIT=FALSE) then we have the check the flow and
 see if MB somehow tries to access the database after database close is
 called.

 Thanks,
 Akalanka.

 On Mon, Jul 13, 2015 at 9:01 AM, Pumudu Ruhunage pum...@wso2.com wrote:

 Hi,

 I observed following sql exception[1] when starts MB in h2 in-memory
 mode. Following are the steps followed.
 1. Start MB node in in-memory mode.
 2. gracefully shutdown the server.

 Following exception[1] will appear. Even this exception appears server
 shuts down without hanging.
 Did anyone face this before?

 [1]
 WARN {org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl} -  Rollback
 failed on removing node information node id: NODElocalhost/127.0.0.1

 org.h2.jdbc.JdbcSQLException: Database is already closed (to disable
 automatic closing at VM shutdown, add ;DB_CLOSE_ON_EXIT=FALSE to the db
 URL) [90121-140]

 at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)

 at org.h2.message.DbException.get(DbException.java:167)

 at org.h2.message.DbException.get(DbException.java:144)

 at org.h2.message.DbException.get(DbException.java:133)

 at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1348)

 at
 org.h2.jdbc.JdbcConnection.checkClosedForWrite(JdbcConnection.java:1333)

 at org.h2.jdbc.JdbcConnection.rollback(JdbcConnection.java:435)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:606)

 at
 org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:71)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)

 at com.sun.proxy.$Proxy15.rollback(Unknown Source)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.rollback(RDBMSAndesContextStoreImpl.java:947)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:323)

 at
 org.wso2.andes.store.FailureObservingAndesContextStore.removeNodeData(FailureObservingAndesContextStore.java:168)

 at
 org.wso2.andes.server.cluster.ClusterManager.clearAllPersistedStatesOfDisappearedNode(ClusterManager.java:270)

 at
 org.wso2.andes.server.cluster.ClusterManager.shutDownMyNode(ClusterManager.java:170)

 at
 org.wso2.andes.kernel.disruptor.inbound.InboundKernelOpsEvent.gracefulShutdown(InboundKernelOpsEvent.java:235)

 at org.wso2.andes.kernel.Andes.shutDown(Andes.java:263)

 at
 org.wso2.andes.kernel.AndesKernelBoot.shutDownAndesKernel(AndesKernelBoot.java:311)

 at
 org.wso2.carbon.andes.internal.QpidServiceComponent$1.startingShutdown(QpidServiceComponent.java:170)

 at
 org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)

 at
 org.wso2.carbon.core.ServerManagement.startMaintenanceForShutDown(ServerManagement.java:97)

 at
 org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:878)

 at
 org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:901)

 [2015-07-13 17:54:03,604] ERROR
 {org.wso2.carbon.andes.internal.QpidServiceComponent} -  Error while
 shutting down Andes kernel.

 org.wso2.andes.kernel.AndesException: Error occurred while removing node
 information node id: NODElocalhost/127.0.0.1

 at
 org.wso2.andes.store.rdbms.RDBMSStoreUtils.convertSQLException(RDBMSStoreUtils.java:117)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:324)

 at
 

Re: [Dev] [AppM] App Manager POMs in GIT still have version 1.0.0-SNAPSHOT configured in 'em

[Ruwan Abeykoon]

Hi Prabath,
Yes, Still I have not committed/ created any PR for the above version bump,
as system is still unstable with C4.4.0 upgrade.
The classloader issue still haunts me. I will work with Carbon team today
to get thing sorted out.

Cheers,
Ruwam


On Tue, Jul 14, 2015 at 2:48 AM, Prabath Abeysekera praba...@wso2.com
wrote:

 Hi Dinusha,

 Okay Cool. I couldn't locate any branch other than release-1.0.0 in
 carbon-appmgt repo. Maybe RuwanA hasn't committed the migration stuff
 yet. Will talk to him tomorrow and get things sorted out. Thanks!

 On Tue, Jul 14, 2015 at 2:43 AM, Dinusha Senanayaka dinu...@wso2.com
 wrote:

 Hi Prabath,

 RuwanA has already created a separate branch and start working on this.
 He has done most of the migrate stuff, and has faced some class loading
 issue at server start up. Will ask him to talk to you tomorrow morning .

 Regards,
 Dinusha

 On Mon, Jul 13, 2015 at 5:09 PM, Prabath Abeysekera praba...@wso2.com
 wrote:

 Hi AppM team,

 Noticed $Subject while I was trying to migrate App Management related
 components to build on Carbon Kernel 4.4.0. What version do I increment
 them to?

 Cheers,
 Prabath
 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471




 --
 Dinusha Dilrukshi
 Associate Technical Lead
 WSO2 Inc.: http://wso2.com/
 Mobile: +94725255071
 Blog: http://dinushasblog.blogspot.com/




 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471




-- 

*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com http://wso2.com/ *
*lean.enterprise.middleware.*

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

Re: [Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Nadeesha Meegoda]

The following is the exception that can be seen if we donot import the
public key of IS to main key in ES. But note that we have imported the
public key to the client trust store of ES.

java.lang.NullPointerException
at
org.jaggeryjs.modules.sso.common.util.X509CredentialImpl.init(X509CredentialImpl.java:63)
at
org.jaggeryjs.modules.sso.common.util.Util.validateSignature(Util.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at
org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.sso.scripts.c0._c_anonymous_3(sso/scripts/sso.client.js:60)
at
org.jaggeryjs.rhino.sso.scripts.c0.call(sso/scripts/sso.client.js)
at
org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.store.controllers.c3._c_anonymous_1(/store/controllers/acs.jag:66)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at
org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at
org.jaggeryjs.rhino.store.controllers.c3._c_script_0(/store/controllers/acs.jag:20)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at
org.jaggeryjs.rhino.store.controllers.c3.exec(/store/controllers/acs.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:587)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:507)
at
org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at
org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at

Re: [Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Pavithra Madurangi]

On Tue, Jul 14, 2015 at 9:52 AM, Ishara Karunarathna isha...@wso2.com
wrote:

 Hi,

 On Mon, Jul 13, 2015 at 6:44 PM, Nadeesha Meegoda nadees...@wso2.com
 wrote:

 Hi all,

 I have a concern regarding the steps followed when configuring a New Key
 store in ES where ES authenticates via IS.

 I think you have configured SSO with SAML.


 These are the steps followed :

 1. Created a Key store for ES, Imported the key to Client Trust store in
 ES
 2. Configured ES to work with the new Key store
 3. Added the ES key to IS Client Trust Store - Note that IS is having the
 default wso2carbon.jks


 Here you have created a new keystore and import your public key to your
 existing client-truststore.jks

 And to work sso scenario you will have to import public cert of IS to your
 new keystore


​Normally we add certificates from other parties that we expect to
communicate with​
​,​

​to trust store (trust store of ES in this case).​ So instead of doing so,
why do we have to add it to key store of ES ?


 Thanks,
 Ishara


 We thought following the above steps will be enough for the Key store
 configurations since ES has the default wso2carbon.jks imported to its
 Client Trust store anyway.

 However ES login via IS was not successful due to *not* having the IS
 public key details imported into the key that I created in ES.So ultimately
 the data decryption didn't happen successfully. My concern is that All the
 third party public keys should be imported in to the client trust store not
 to the main key itself. What we do here is we are importing the IS public
 key details to the main key of ES.

 My question is do we need to follow all the above with importing the IS
 public key to the main key of ES or 1,2,3 steps would be enough for the New
 key store to work?


 Thanks  Regards,
 Nadeesha

 --
 *Nadeesha Meegoda*
 Software Engineer - QA
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 email : nadees...@wso2.com
 mobile: +94783639540
 %2B94%2077%202273555

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




 --
 Ishara Karunarathna
 Senior Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791

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




-- 
*Pavithra Madurangi*
Associate Technical Lead - QA.
WSO2 Inc.: http://wso2.com/
Mobile: 0777207357 / 0112747089
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Review and Merge the PR

[Hasanthi Purnima Dissanayake]

Hi,
Please review and merge the fix [1] for public jira [2].
[1]https://github.com/wso2/product-is/pull/146
[2]https://wso2.org/jira/browse/IDENTITY-3220

Thanks,

Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com nirosh...@wso2.com
M :0718407133| http://wso2.com http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Stratos] java.io.IOException: No space left on device in Docker containers

[Punnadi Gunarathna]

hi All,

I got below error in all the docker containers for the setup i just did and
haven't seen it before.

In WSO2AS:

TID: [2015-07-13 13:09:38,746]  INFO
{org.wso2.carbon.server.extensions.PatchInstaller} -  Patch changes
detected  {org.wso2.carbon.server.extensions.PatchInstaller}
TID: [2015-07-13 13:09:57,267]  INFO
{org.wso2.carbon.server.util.PatchUtils.console} -  Backed up plugins to
patch {org.wso2.carbon.server.util.PatchUtils.console}
TID: [2015-07-13 13:10:05,378] ERROR
{org.wso2.carbon.server.extensions.PatchInstaller} -  Error occurred while
applying patches {org.wso2.carbon.server.extensions.PatchInstaller}
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at org.wso2.carbon.server.util.FileUtils.copy(FileUtils.java:230)
at org.wso2.carbon.server.util.FileUtils.copyFile(FileUtils.java:152)
at
org.wso2.carbon.server.util.PatchUtils.copyServicepacksAndPatches(PatchUtils.java:90)
at
org.wso2.carbon.server.util.PatchUtils.applyServicepacksAndPatches(PatchUtils.java:45)
at
org.wso2.carbon.server.extensions.PatchInstaller.perform(PatchInstaller.java:58)
at org.wso2.carbon.server.Main.invokeExtensions(Main.java:152)
at org.wso2.carbon.server.Main.main(Main.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)

CA:
 [2015-07-13 13:10:29,565] DEBUG
{eventhandler.py:on_complete_tenant_event} - Processing Complete tenant
event...
 Traceback (most recent call last):
   File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
 self.flush()
   File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
 self.stream.flush()
 IOError: [Errno 28] No space left on device
 Logged from file eventhandler.py, line 221
 [2015-07-13 13:10:29,565] DEBUG
{eventhandler.py:on_complete_tenant_event} - Complete tenants:[]
 Traceback (most recent call last):
   File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
 self.flush()
   File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
 self.stream.flush()
 IOError: [Errno 28] No space left on device


Whenever I do a new setup, I always clean all the pods with kubernetes
client. Any thoughts on this?
-- 
Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com http://wso2
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300



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

[Dev] [MB] H2 in-memory exception when shutting down server

[Pumudu Ruhunage]

Hi,

I observed following sql exception[1] when starts MB in h2 in-memory mode.
Following are the steps followed.
1. Start MB node in in-memory mode.
2. gracefully shutdown the server.

Following exception[1] will appear. Even this exception appears server
shuts down without hanging.
Did anyone face this before?

[1]
WARN {org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl} -  Rollback
failed on removing node information node id: NODElocalhost/127.0.0.1

org.h2.jdbc.JdbcSQLException: Database is already closed (to disable
automatic closing at VM shutdown, add ;DB_CLOSE_ON_EXIT=FALSE to the db
URL) [90121-140]

at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)

at org.h2.message.DbException.get(DbException.java:167)

at org.h2.message.DbException.get(DbException.java:144)

at org.h2.message.DbException.get(DbException.java:133)

at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1348)

at org.h2.jdbc.JdbcConnection.checkClosedForWrite(JdbcConnection.java:1333)

at org.h2.jdbc.JdbcConnection.rollback(JdbcConnection.java:435)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at
org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)

at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

at
org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51)

at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

at
org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:71)

at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

at
org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153)

at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)

at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

at
org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)

at com.sun.proxy.$Proxy15.rollback(Unknown Source)

at
org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.rollback(RDBMSAndesContextStoreImpl.java:947)

at
org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:323)

at
org.wso2.andes.store.FailureObservingAndesContextStore.removeNodeData(FailureObservingAndesContextStore.java:168)

at
org.wso2.andes.server.cluster.ClusterManager.clearAllPersistedStatesOfDisappearedNode(ClusterManager.java:270)

at
org.wso2.andes.server.cluster.ClusterManager.shutDownMyNode(ClusterManager.java:170)

at
org.wso2.andes.kernel.disruptor.inbound.InboundKernelOpsEvent.gracefulShutdown(InboundKernelOpsEvent.java:235)

at org.wso2.andes.kernel.Andes.shutDown(Andes.java:263)

at
org.wso2.andes.kernel.AndesKernelBoot.shutDownAndesKernel(AndesKernelBoot.java:311)

at
org.wso2.carbon.andes.internal.QpidServiceComponent$1.startingShutdown(QpidServiceComponent.java:170)

at
org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)

at
org.wso2.carbon.core.ServerManagement.startMaintenanceForShutDown(ServerManagement.java:97)

at
org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:878)

at
org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:901)

[2015-07-13 17:54:03,604] ERROR
{org.wso2.carbon.andes.internal.QpidServiceComponent} -  Error while
shutting down Andes kernel.

org.wso2.andes.kernel.AndesException: Error occurred while removing node
information node id: NODElocalhost/127.0.0.1

at
org.wso2.andes.store.rdbms.RDBMSStoreUtils.convertSQLException(RDBMSStoreUtils.java:117)

at
org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:324)

at
org.wso2.andes.store.FailureObservingAndesContextStore.removeNodeData(FailureObservingAndesContextStore.java:168)

at
org.wso2.andes.server.cluster.ClusterManager.clearAllPersistedStatesOfDisappearedNode(ClusterManager.java:270)

at
org.wso2.andes.server.cluster.ClusterManager.shutDownMyNode(ClusterManager.java:170)

at
org.wso2.andes.kernel.disruptor.inbound.InboundKernelOpsEvent.gracefulShutdown(InboundKernelOpsEvent.java:235)

at org.wso2.andes.kernel.Andes.shutDown(Andes.java:263)

at
org.wso2.andes.kernel.AndesKernelBoot.shutDownAndesKernel(AndesKernelBoot.java:311)

at
org.wso2.carbon.andes.internal.QpidServiceComponent$1.startingShutdown(QpidServiceComponent.java:170)

at
org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)

at

Re: [Dev] [Stratos] java.io.IOException: No space left on device in Docker containers

[Punnadi Gunarathna]

Hi All,

Despite cleaning pods via kubernetes client, I noticed there are number of
old docker containers running on node-01 with below command:

docker ps -a


So I deleted them with below command:

docker ps -a | grep 'CREATED' | awk '{print $1}' | xargs
--no-run-if-empty docker rm -f

e.g:

docker ps -a | grep '3 hours ago' | awk '{print $1}' | xargs
--no-run-if-empty docker rm -f

Hope this will solve the problem.

On Mon, Jul 13, 2015 at 6:59 PM, Punnadi Gunarathna punn...@wso2.com
wrote:

 hi All,

 I got below error in all the docker containers for the setup i just did
 and haven't seen it before.

 In WSO2AS:

 TID: [2015-07-13 13:09:38,746]  INFO
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Patch changes
 detected  {org.wso2.carbon.server.extensions.PatchInstaller}
 TID: [2015-07-13 13:09:57,267]  INFO
 {org.wso2.carbon.server.util.PatchUtils.console} -  Backed up plugins to
 patch {org.wso2.carbon.server.util.PatchUtils.console}
 TID: [2015-07-13 13:10:05,378] ERROR
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Error occurred while
 applying patches {org.wso2.carbon.server.extensions.PatchInstaller}
 java.io.IOException: No space left on device
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:345)
 at org.wso2.carbon.server.util.FileUtils.copy(FileUtils.java:230)
 at org.wso2.carbon.server.util.FileUtils.copyFile(FileUtils.java:152)
 at
 org.wso2.carbon.server.util.PatchUtils.copyServicepacksAndPatches(PatchUtils.java:90)
 at
 org.wso2.carbon.server.util.PatchUtils.applyServicepacksAndPatches(PatchUtils.java:45)
 at
 org.wso2.carbon.server.extensions.PatchInstaller.perform(PatchInstaller.java:58)
 at org.wso2.carbon.server.Main.invokeExtensions(Main.java:152)
 at org.wso2.carbon.server.Main.main(Main.java:94)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
 at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)

 CA:
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Processing Complete tenant
 event...
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device
  Logged from file eventhandler.py, line 221
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Complete tenants:[]
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device


 Whenever I do a new setup, I always clean all the pods with kubernetes
 client. Any thoughts on this?
 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



  http://lalajisureshika.blogspot.com/




-- 
Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com http://wso2
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300



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

[Dev] [ES] Configuring a New Key store in ES 2.0 with SSO enabled via IS 5.0

[Nadeesha Meegoda]

Hi all,

I have a concern regarding the steps followed when configuring a New Key
store in ES where ES authenticates via IS.

These are the steps followed :

1. Created a Key store for ES, Imported the key to Client Trust store in ES
2. Configured ES to work with the new Key store
3. Added the ES key to IS Client Trust Store - Note that IS is having the
default wso2carbon.jks

We thought following the above steps will be enough for the Key store
configurations since ES has the default wso2carbon.jks imported to its
Client Trust store anyway.

However ES login via IS was not successful due to *not* having the IS
public key details imported into the key that I created in ES.So ultimately
the data decryption didn't happen successfully. My concern is that All the
third party public keys should be imported in to the client trust store not
to the main key itself. What we do here is we are importing the IS public
key details to the main key of ES.

My question is do we need to follow all the above with importing the IS
public key to the main key of ES or 1,2,3 steps would be enough for the New
key store to work?


Thanks  Regards,
Nadeesha

-- 
*Nadeesha Meegoda*
Software Engineer - QA
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
email : nadees...@wso2.com
mobile: +94783639540
%2B94%2077%202273555
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] H2 in-memory exception when shutting down server

[Akalanka Pagoda Arachchi]

Hi Pumudu,

This occurs when MB tries to access the H2 database even after the database
is closed. If the database url does have the property mentioned in the
error (;DB_CLOSE_ON_EXIT=FALSE) then we have the check the flow and see
if MB somehow tries to access the database after database close is called.

Thanks,
Akalanka.

On Mon, Jul 13, 2015 at 9:01 AM, Pumudu Ruhunage pum...@wso2.com wrote:

 Hi,

 I observed following sql exception[1] when starts MB in h2 in-memory mode.
 Following are the steps followed.
 1. Start MB node in in-memory mode.
 2. gracefully shutdown the server.

 Following exception[1] will appear. Even this exception appears server
 shuts down without hanging.
 Did anyone face this before?

 [1]
 WARN {org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl} -  Rollback
 failed on removing node information node id: NODElocalhost/127.0.0.1

 org.h2.jdbc.JdbcSQLException: Database is already closed (to disable
 automatic closing at VM shutdown, add ;DB_CLOSE_ON_EXIT=FALSE to the db
 URL) [90121-140]

 at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)

 at org.h2.message.DbException.get(DbException.java:167)

 at org.h2.message.DbException.get(DbException.java:144)

 at org.h2.message.DbException.get(DbException.java:133)

 at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1348)

 at org.h2.jdbc.JdbcConnection.checkClosedForWrite(JdbcConnection.java:1333)

 at org.h2.jdbc.JdbcConnection.rollback(JdbcConnection.java:435)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:606)

 at
 org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.wso2.carbon.ndatasource.rdbms.ConnectionRollbackOnReturnInterceptor.invoke(ConnectionRollbackOnReturnInterceptor.java:51)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:71)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:153)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)

 at
 org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)

 at
 org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)

 at com.sun.proxy.$Proxy15.rollback(Unknown Source)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.rollback(RDBMSAndesContextStoreImpl.java:947)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:323)

 at
 org.wso2.andes.store.FailureObservingAndesContextStore.removeNodeData(FailureObservingAndesContextStore.java:168)

 at
 org.wso2.andes.server.cluster.ClusterManager.clearAllPersistedStatesOfDisappearedNode(ClusterManager.java:270)

 at
 org.wso2.andes.server.cluster.ClusterManager.shutDownMyNode(ClusterManager.java:170)

 at
 org.wso2.andes.kernel.disruptor.inbound.InboundKernelOpsEvent.gracefulShutdown(InboundKernelOpsEvent.java:235)

 at org.wso2.andes.kernel.Andes.shutDown(Andes.java:263)

 at
 org.wso2.andes.kernel.AndesKernelBoot.shutDownAndesKernel(AndesKernelBoot.java:311)

 at
 org.wso2.carbon.andes.internal.QpidServiceComponent$1.startingShutdown(QpidServiceComponent.java:170)

 at
 org.wso2.carbon.core.ServerManagement.waitForServerTaskCompletion(ServerManagement.java:113)

 at
 org.wso2.carbon.core.ServerManagement.startMaintenanceForShutDown(ServerManagement.java:97)

 at
 org.wso2.carbon.core.init.CarbonServerManager.shutdownGracefully(CarbonServerManager.java:878)

 at
 org.wso2.carbon.core.init.CarbonServerManager$4.run(CarbonServerManager.java:901)

 [2015-07-13 17:54:03,604] ERROR
 {org.wso2.carbon.andes.internal.QpidServiceComponent} -  Error while
 shutting down Andes kernel.

 org.wso2.andes.kernel.AndesException: Error occurred while removing node
 information node id: NODElocalhost/127.0.0.1

 at
 org.wso2.andes.store.rdbms.RDBMSStoreUtils.convertSQLException(RDBMSStoreUtils.java:117)

 at
 org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.removeNodeData(RDBMSAndesContextStoreImpl.java:324)

 at
 org.wso2.andes.store.FailureObservingAndesContextStore.removeNodeData(FailureObservingAndesContextStore.java:168)

 at
 org.wso2.andes.server.cluster.ClusterManager.clearAllPersistedStatesOfDisappearedNode(ClusterManager.java:270)

 at
 org.wso2.andes.server.cluster.ClusterManager.shutDownMyNode(ClusterManager.java:170)

 at
 

Re: [Dev] [Stratos] java.io.IOException: No space left on device in Docker containers

[Punnadi Gunarathna]

Hi Manisha,

No it can't be done with puppet scripts at the moment. I was referring to
kubernets minion which had space issue. But sure I will have to figure out
a way to solve this.

On Tue, Jul 14, 2015 at 7:26 AM, Manisha Gayathri mani...@wso2.com wrote:

 If we are doing a new setup, we need to clean the old existing instances,
 don't we?

 Hope we can automate this step via puppet scripts.

 Thanks
 Manisha

 On Mon, Jul 13, 2015 at 7:22 PM, Punnadi Gunarathna punn...@wso2.com
 wrote:

 Hi All,

 Despite cleaning pods via kubernetes client, I noticed there are number
 of old docker containers running on node-01 with below command:

 docker ps -a


 So I deleted them with below command:

 docker ps -a | grep 'CREATED' | awk '{print $1}' | xargs
 --no-run-if-empty docker rm -f

 e.g:

 docker ps -a | grep '3 hours ago' | awk '{print $1}' | xargs
 --no-run-if-empty docker rm -f

 Hope this will solve the problem.

 On Mon, Jul 13, 2015 at 6:59 PM, Punnadi Gunarathna punn...@wso2.com
 wrote:

 hi All,

 I got below error in all the docker containers for the setup i just did
 and haven't seen it before.

 In WSO2AS:

 TID: [2015-07-13 13:09:38,746]  INFO
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Patch changes
 detected  {org.wso2.carbon.server.extensions.PatchInstaller}
 TID: [2015-07-13 13:09:57,267]  INFO
 {org.wso2.carbon.server.util.PatchUtils.console} -  Backed up plugins to
 patch {org.wso2.carbon.server.util.PatchUtils.console}
 TID: [2015-07-13 13:10:05,378] ERROR
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Error occurred while
 applying patches {org.wso2.carbon.server.extensions.PatchInstaller}
 java.io.IOException: No space left on device
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:345)
 at org.wso2.carbon.server.util.FileUtils.copy(FileUtils.java:230)
 at org.wso2.carbon.server.util.FileUtils.copyFile(FileUtils.java:152)
 at
 org.wso2.carbon.server.util.PatchUtils.copyServicepacksAndPatches(PatchUtils.java:90)
 at
 org.wso2.carbon.server.util.PatchUtils.applyServicepacksAndPatches(PatchUtils.java:45)
 at
 org.wso2.carbon.server.extensions.PatchInstaller.perform(PatchInstaller.java:58)
 at org.wso2.carbon.server.Main.invokeExtensions(Main.java:152)
 at org.wso2.carbon.server.Main.main(Main.java:94)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
 at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)

 CA:
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Processing Complete tenant
 event...
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device
  Logged from file eventhandler.py, line 221
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Complete tenants:[]
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device


 Whenever I do a new setup, I always clean all the pods with kubernetes
 client. Any thoughts on this?
 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



  http://lalajisureshika.blogspot.com/




 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



  http://lalajisureshika.blogspot.com/

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




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

 *blog:  http://manisha-eleperuma.blogspot.com/
 http://manisha-eleperuma.blogspot.com/*
 *mobile:  +94 71 8279777 %2B94%2071%208279777*




-- 
Thanks and Regards,

Punnadi Gunarathna
Senior Software Engineer,
WSO2, Inc.; http://wso2.com http://wso2
Blog: http://hi-my-world.blogspot.com/
Tel : 94 11 214 5345
Fax :94 11 2145300



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

Re: [Dev] [DEV] Running Intergration Tests On ESB 490 Cluster

[Saneth Dharmakeerthi]

Hi Yasassri,

 What you mean by ESB Cluster here. Are you goon to run the integration
test on ESB cluster with multiple nodes?

Thanks and Best Regards,

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

On Sun, Jul 12, 2015 at 11:54 PM, Yasassri Ratnayake yasas...@wso2.com
wrote:

 Hi Malaka,

 I ran the tests in an Open Stack Instances with Java 1.7.0_65.

 In the tests-mediator-1 module following tests failed

- CallOut-mediator-Test (2 Test Cases)
- Call-mediator-Test (2 Test Cases)
- Property-mediator-Test-1 (I Test Case)
- Fault-mediator-Test (1 Test Case)


 In tests-mediator-2 there was only one skipped test case (Above table
 should be corrected), and it has occurred due to an connection failure with
 the following exception.

 Unable to add local entry :: Error connecting to URL :
 https://svn.wso2.org/repos/wso2/trunk/commons/qa/qa-artifacts/esb/esb450/mediators/xslt/transform.xslt

 I have added both sure-fire reports, please have a look.

 With Regards,


 On Sun, Jul 12, 2015 at 8:07 PM, Malaka Silva mal...@wso2.com wrote:

 Hi Yasassri,

 There are some tests fails and we are currently fixing those. (There were
 few some commented tests and we uncomment it last week.)

 However tests-mediator-1 and tests-mediator-2 is passing all the tests
 in our ec2 instance.

 What is the environment and jdk you are running the tests?

 What are the failing test cases?

 What

 On Sun, Jul 12, 2015 at 4:53 PM, Yasassri Ratnayake yasas...@wso2.com
 wrote:

 Hi All,

 Before running the integration tests on the cluster I tried to run some
 of the test modules locally. I ran following two scenarios.

 1. Executed the integration tests after building the pack.
 2. Executed the integration tests by pointing to an already started ESB
 server with an offset.

 For the above scenarios I executed tests-mediator-1 and tests-mediator-2
 modules located at [1]

 In the second scenario I commented out the CarbonServerExtension and
 Axis2ServerExtension from the automation.xml and I started an Axis2
 Server locally by deploying the sample web-services available.

 After running the above scenarios following results were obtained.
 (Summary)

 *Scenario 01 (Running tests after building the pack) *

 *tests-mediator-1*

 StatusMethods
 PassedScenarios
 Passed# skipped# failedNo of Tests38238206

 *tests-mediator-2*

 StatusMethods
 PassedScenarios
 Passed# skipped# failedNo of Tests18518516


 *Scenario 02 (Running tests by pointing to a remote server)*

 *tests-mediator-1*

 StatusMethods
 PassedScenarios
 Passed# skipped# failedNo of Tests16216216066


 *tests-mediator-2*

 The test didn't complete and surefire reports were not generated.

 By looking at the above results it's clear that some of the test cases
 are not intended to executed in a remote manner or in a clustered
 environment. (Please note that I didn't analyze the results in-depth).

 @Automation Team:  Is there something I'm doing wrong here? Can I
 improve the above results and run it on the cluster? And if I'm running
 this on an ESB cluster how should I configure the back-end Axis2 Server? Do
 I need to start an Axis2 Server on each worker node?

 @ESB Team : Some test cases are failing in the 1st scenario, these need
 to be investigated and fixed.

 [1] -
 https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration

 With Regards,
 --
 Yasassri Ratnayake
 Software Engineer - QA
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware
 *Mobile : +94715933168 %2B94715933168*
 *Blogs : http://yasassriratnayake.blogspot.com
 http://yasassriratnayake.blogspot.com/*
 *http://wso2logs.blogspot.com http://wso2logs.blogspot.com*




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 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.




 --
 Yasassri Ratnayake
 Software Engineer - QA
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware
 *Mobile : +94715933168 %2B94715933168*
 *Blogs : http://yasassriratnayake.blogspot.com
 http://yasassriratnayake.blogspot.com/*
 *http://wso2logs.blogspot.com http://wso2logs.blogspot.com*

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


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

Re: [Dev] [Stratos] java.io.IOException: No space left on device in Docker containers

[Manisha Gayathri]

If we are doing a new setup, we need to clean the old existing instances,
don't we?

Hope we can automate this step via puppet scripts.

Thanks
Manisha

On Mon, Jul 13, 2015 at 7:22 PM, Punnadi Gunarathna punn...@wso2.com
wrote:

 Hi All,

 Despite cleaning pods via kubernetes client, I noticed there are number of
 old docker containers running on node-01 with below command:

 docker ps -a


 So I deleted them with below command:

 docker ps -a | grep 'CREATED' | awk '{print $1}' | xargs
 --no-run-if-empty docker rm -f

 e.g:

 docker ps -a | grep '3 hours ago' | awk '{print $1}' | xargs
 --no-run-if-empty docker rm -f

 Hope this will solve the problem.

 On Mon, Jul 13, 2015 at 6:59 PM, Punnadi Gunarathna punn...@wso2.com
 wrote:

 hi All,

 I got below error in all the docker containers for the setup i just did
 and haven't seen it before.

 In WSO2AS:

 TID: [2015-07-13 13:09:38,746]  INFO
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Patch changes
 detected  {org.wso2.carbon.server.extensions.PatchInstaller}
 TID: [2015-07-13 13:09:57,267]  INFO
 {org.wso2.carbon.server.util.PatchUtils.console} -  Backed up plugins to
 patch {org.wso2.carbon.server.util.PatchUtils.console}
 TID: [2015-07-13 13:10:05,378] ERROR
 {org.wso2.carbon.server.extensions.PatchInstaller} -  Error occurred while
 applying patches {org.wso2.carbon.server.extensions.PatchInstaller}
 java.io.IOException: No space left on device
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:345)
 at org.wso2.carbon.server.util.FileUtils.copy(FileUtils.java:230)
 at org.wso2.carbon.server.util.FileUtils.copyFile(FileUtils.java:152)
 at
 org.wso2.carbon.server.util.PatchUtils.copyServicepacksAndPatches(PatchUtils.java:90)
 at
 org.wso2.carbon.server.util.PatchUtils.applyServicepacksAndPatches(PatchUtils.java:45)
 at
 org.wso2.carbon.server.extensions.PatchInstaller.perform(PatchInstaller.java:58)
 at org.wso2.carbon.server.Main.invokeExtensions(Main.java:152)
 at org.wso2.carbon.server.Main.main(Main.java:94)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:63)
 at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:45)

 CA:
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Processing Complete tenant
 event...
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device
  Logged from file eventhandler.py, line 221
  [2015-07-13 13:10:29,565] DEBUG
 {eventhandler.py:on_complete_tenant_event} - Complete tenants:[]
  Traceback (most recent call last):
File /usr/lib/python2.7/logging/__init__.py, line 874, in emit
  self.flush()
File /usr/lib/python2.7/logging/__init__.py, line 834, in flush
  self.stream.flush()
  IOError: [Errno 28] No space left on device


 Whenever I do a new setup, I always clean all the pods with kubernetes
 client. Any thoughts on this?
 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



  http://lalajisureshika.blogspot.com/




 --
 Thanks and Regards,

 Punnadi Gunarathna
 Senior Software Engineer,
 WSO2, Inc.; http://wso2.com http://wso2
 Blog: http://hi-my-world.blogspot.com/
 Tel : 94 11 214 5345
 Fax :94 11 2145300



  http://lalajisureshika.blogspot.com/

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




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

*blog:  http://manisha-eleperuma.blogspot.com/
http://manisha-eleperuma.blogspot.com/*
*mobile:  +94 71 8279777*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM 2.0] Android Agent Moved to Gradle Build System

[Prabath Abeysekera]

Hi Kasun,

This is great! Thanks for looking into this.

Let's try to get this to build with maven so we can then integrate
android-agent module into the regular build system too.

Cheers,
Prabath

On Thu, Jul 9, 2015 at 3:58 PM, Kasun Dananjaya Delgolla kas...@wso2.com
wrote:

 Hi All,

 $subject has been done since the official Android developer support [1]
 totally moved from Eclipse to IntelliJ based new Android Studio. Android
 Studio uses Gradle[2] as its build system which makes developer's life
 easier by auto importing all the dependencies(from Jcenter repo) on project
 import and many more advantages.

 [1] - https://developer.android.com/sdk/index.html
 [2] - https://developer.android.com/sdk/installing/studio-build.html

 Thanks
 --
 Kasun Dananjaya Delgolla

 Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 Tel:  +94 11 214 5345
 Fax: +94 11 2145300
 Mob: + 94 771 771 015
 Blog: http://kddcodingparadise.blogspot.com
 Linkedin: *http://lk.linkedin.com/in/kasundananjaya
 http://lk.linkedin.com/in/kasundananjaya*




-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Supporting required attribute of RXT fields with Enterprise Store

[Chanaka Jayasena]

Hi All

Supporting required attribute of RXT fields with Enterprise Store is
implemented in the following manner. If the field defined as required then
at the creation step of the asset the field is not read-only. But at the
update step the field is read-only.

Also in order to facilitate the requirement to have a readonly property for
both create and edit steps we have introduce a new attribute from the
Enterprise Store side. The attribute name is auto where it can be true or
false. With a value of true will result in both create and edit steps to
behave in read-only mode. Field provider in gadget is a common use case
where it will be populated automatically without the users input.

By overriding the asset.configure method, extension developers can add this
extra attibute to each field in the RXT.

thanks,
Chanaka
-- 
Chanaka Jayasena
Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
email: chan...@wso2.com; cell: +94 77 785 5565
blog: http://chanaka3d.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AppM] App Manager POMs in GIT still have version 1.0.0-SNAPSHOT configured in 'em

[Prabath Abeysekera]

Hi AppM team,

Noticed $Subject while I was trying to migrate App Management related
components to build on Carbon Kernel 4.4.0. What version do I increment
them to?

Cheers,
Prabath
-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] App Manager POMs in GIT still have version 1.0.0-SNAPSHOT configured in 'em

[Dinusha Senanayaka]

Hi Prabath,

RuwanA has already created a separate branch and start working on this. He
has done most of the migrate stuff, and has faced some class loading issue
at server start up. Will ask him to talk to you tomorrow morning .

Regards,
Dinusha

On Mon, Jul 13, 2015 at 5:09 PM, Prabath Abeysekera praba...@wso2.com
wrote:

 Hi AppM team,

 Noticed $Subject while I was trying to migrate App Management related
 components to build on Carbon Kernel 4.4.0. What version do I increment
 them to?

 Cheers,
 Prabath
 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471




-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] App Manager POMs in GIT still have version 1.0.0-SNAPSHOT configured in 'em

[Prabath Abeysekera]

Hi Dinusha,

Okay Cool. I couldn't locate any branch other than release-1.0.0 in
carbon-appmgt repo. Maybe RuwanA hasn't committed the migration stuff
yet. Will talk to him tomorrow and get things sorted out. Thanks!

On Tue, Jul 14, 2015 at 2:43 AM, Dinusha Senanayaka dinu...@wso2.com
wrote:

 Hi Prabath,

 RuwanA has already created a separate branch and start working on this. He
 has done most of the migrate stuff, and has faced some class loading issue
 at server start up. Will ask him to talk to you tomorrow morning .

 Regards,
 Dinusha

 On Mon, Jul 13, 2015 at 5:09 PM, Prabath Abeysekera praba...@wso2.com
 wrote:

 Hi AppM team,

 Noticed $Subject while I was trying to migrate App Management related
 components to build on Carbon Kernel 4.4.0. What version do I increment
 them to?

 Cheers,
 Prabath
 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471




 --
 Dinusha Dilrukshi
 Associate Technical Lead
 WSO2 Inc.: http://wso2.com/
 Mobile: +94725255071
 Blog: http://dinushasblog.blogspot.com/




-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM 2.0] Android Agent Moved to Gradle Build System

[Kasun Dananjaya Delgolla]

Hi Prabath,

Now this already building with maven. It generates an unsigned release APK
and also copies the generated APK to MDM jaggery app download folder.

What's pending is, enabling a config entry for the user to get a signed APK
for production.

Thanks
On Jul 13, 2015 11:01 PM, Prabath Abeysekera praba...@wso2.com wrote:

 Hi Kasun,

 This is great! Thanks for looking into this.

 Let's try to get this to build with maven so we can then integrate
 android-agent module into the regular build system too.

 Cheers,
 Prabath

 On Thu, Jul 9, 2015 at 3:58 PM, Kasun Dananjaya Delgolla kas...@wso2.com
 wrote:

 Hi All,

 $subject has been done since the official Android developer support [1]
 totally moved from Eclipse to IntelliJ based new Android Studio. Android
 Studio uses Gradle[2] as its build system which makes developer's life
 easier by auto importing all the dependencies(from Jcenter repo) on project
 import and many more advantages.

 [1] - https://developer.android.com/sdk/index.html
 [2] - https://developer.android.com/sdk/installing/studio-build.html

 Thanks
 --
 Kasun Dananjaya Delgolla

 Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware
 Tel:  +94 11 214 5345
 Fax: +94 11 2145300
 Mob: + 94 771 771 015
 Blog: http://kddcodingparadise.blogspot.com
 Linkedin: *http://lk.linkedin.com/in/kasundananjaya
 http://lk.linkedin.com/in/kasundananjaya*




 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471

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

Re: [Dev] Regarding ESB message stores

[Nayomi Dayarathne]

Then i would like to suggest to include that in 4.9.0 documents since 4.9.0
documents doesn't specifically say anything like that about in memory
message stores. :)

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 +94+(0)+775246619

*nay...@wso2.com nay...@wso2.com*

On Mon, Jul 13, 2015 at 10:40 AM, Shafreen Anfar shafr...@wso2.com wrote:

 It is disabled because there is nothing much to be edited for in memory
 message store. You can either create it or delete it. :)

 On Mon, Jul 13, 2015 at 10:20 AM, Nayomi Dayarathne nay...@wso2.com
 wrote:

 i checked in both 4.8 and 4.9 versions.both having the same effect for in
 memory message stores

 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 +94+(0)+775246619

 *nay...@wso2.com nay...@wso2.com*

 On Mon, Jul 13, 2015 at 10:14 AM, Shafreen Anfar shafr...@wso2.com
 wrote:

 What is the ESB version ?

 On Mon, Jul 13, 2015 at 9:59 AM, Nayomi Dayarathne nay...@wso2.com
 wrote:

 Hi Shafreen,

 The reason why i asked so because, when i create an in memory message
 store from management console the edit button always shows in disabled
 mode. but all the other types are able to edit.so just wanted to make sure
 whether its a bug.

 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 +94+(0)+775246619

 *nay...@wso2.com nay...@wso2.com*

 On Mon, Jul 13, 2015 at 9:47 AM, Shafreen Anfar shafr...@wso2.com
 wrote:

 Hi Nayomi,

 Yeah. Normally when we implement Message-Stores, we also implement the
 web UI part as well.

 On Mon, Jul 13, 2015 at 9:29 AM, Nayomi Dayarathne nay...@wso2.com
 wrote:

 Hi ESB team,

 Are all message stores in ESB should be able to edit from UI
 regardless of their type ?

 Regards,
 Nayomi.





 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 +94+(0)+775246619

 *nay...@wso2.com nay...@wso2.com*




 --
 Regards,
 *Shafreen*
 Software Engineer
 WSO2 Inc
 Mobile : 077-556-395-1





 --
 Regards,
 *Shafreen*
 Software Engineer
 WSO2 Inc
 Mobile : 077-556-395-1





 --
 Regards,
 *Shafreen*
 Software Engineer
 WSO2 Inc
 Mobile : 077-556-395-1

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

Re: [Dev] Please Merge the pull request

[Lakshman Udayakantha]

jira for this is [2]

[2] https://wso2.org/jira/browse/STORE-894

On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha lakshm...@wso2.com
wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




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

Re: [Dev] Please Merge the pull request

[Udara Rathnayake]

Hi Lakshman,

Is there any possibility to use the store feature instead of es one? We
initially created this es feature for AM team to facilitate keeping both ES
store/publisher apps and API manager store/publisher apps. Eg:- es-store
coming form es feature and store is coming from am store feature

Seems es feature is bit outdated and might get dropped in future. Let us
know the possibility of moving from es feature to store.

Regards,
UdaraR

On Mon, Jul 13, 2015 at 12:10 PM, Lakshman Udayakantha lakshm...@wso2.com
wrote:

 jira for this is [2]

 [2] https://wso2.org/jira/browse/STORE-894

 On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha lakshm...@wso2.com
 wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*


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

Re: [Dev] Please Merge the pull request

[Udara Rathnayake]

BTW I have merged the PR.

On Mon, Jul 13, 2015 at 12:24 PM, Udara Rathnayake uda...@wso2.com wrote:

 Hi Lakshman,

 Is there any possibility to use the store feature instead of es one? We
 initially created this es feature for AM team to facilitate keeping both ES
 store/publisher apps and API manager store/publisher apps. Eg:- es-store
 coming form es feature and store is coming from am store feature

 Seems es feature is bit outdated and might get dropped in future. Let us
 know the possibility of moving from es feature to store.

 Regards,
 UdaraR

 On Mon, Jul 13, 2015 at 12:10 PM, Lakshman Udayakantha lakshm...@wso2.com
  wrote:

 jira for this is [2]

 [2] https://wso2.org/jira/browse/STORE-894

 On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha lakshm...@wso2.com
  wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*



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

Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack

[Aparna Karunarathna]

tenant-mgt.xml file is included under repository/conf/multitenancy
directory in the ES200 pack.

@Johann/ SameeraJ / SameeraM, Have we changed the location of
tenant-mgt.xml file
or is this an error?

Regards,
Aparna.

On Mon, Jul 13, 2015 at 12:36 PM, Aparna Karunarathna apa...@wso2.com
wrote:

 Even IS 510 M3 pack doesn't have the tenant-mgt.xml file.

 Regards,
 Aparna


 On Mon, Jul 13, 2015 at 11:35 AM, Thayalan thaya...@wso2.com wrote:

 Hi Team,

 As per the mail discussion in [1]  [2] what I understood was
 tenant-mgt.xml file has to be included with all the products. But, I'm not
 clear on the final verdict whether to include $Subject with all the
 products that we ship including GREG. Please confirm.

 The same issue persist with the latest GREG pack as well.

 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon
 packs?
 2. Is it possible to re-factor current 'product distribution process'
 --
 Regards,
 Thayalan Sivapaleswararajah
 Associate Technical Lead - QA
 Mob: +94(0)777872485
 Tel : +94(0)(11)2145345
 Fax : +94(0)(11)2145300
 Email: thaya...@wso2.com


 *Disclaimer*: *This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, retransmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.*




 --
 *Regards,*

 *Aparna Karunarathna.*


 *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 0714002533*




-- 
*Regards,*

*Aparna Karunarathna.*


*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack

[Thayalan]

Hi Team,

As per the mail discussion in [1]  [2] what I understood was
tenant-mgt.xml file has to be included with all the products. But, I'm not
clear on the final verdict whether to include $Subject with all the
products that we ship including GREG. Please confirm.

The same issue persist with the latest GREG pack as well.

1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon packs?
2. Is it possible to re-factor current 'product distribution process'
-- 
Regards,
Thayalan Sivapaleswararajah
Associate Technical Lead - QA
Mob: +94(0)777872485
Tel : +94(0)(11)2145345
Fax : +94(0)(11)2145300
Email: thaya...@wso2.com


*Disclaimer*: *This communication may contain privileged or other
confidential information and is intended exclusively for the addressee/s.
If you are not the intended recipient/s, or believe that you may have
received this communication in error, please reply to the sender indicating
that fact and delete the copy you received and in addition, you should not
print, copy, retransmit, disseminate, or otherwise use the information
contained in this communication. Internet communications cannot be
guaranteed to be timely, secure, error or virus-free. The sender does not
accept liability for any errors or omissions.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AppM]Please review and merge PR for APPM-1020

[Sajith Abeywardhana]

Hi Team,

Please merge https://github.com/wso2/product-app-manager/pull/245 for
https://wso2.org/jira/browse/APPM-1020

*Sajith Abeywardhana* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka.
Mobile: +94772260485
Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM]Please review and merge PR for APPM-1020

[Rushmin Fernando]

Done

On Mon, Jul 13, 2015 at 11:45 AM, Sajith Abeywardhana saji...@wso2.com
wrote:

 Hi Team,

 Please merge https://github.com/wso2/product-app-manager/pull/245 for
 https://wso2.org/jira/browse/APPM-1020

 *Sajith Abeywardhana* | Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka.
 Mobile: +94772260485
 Email: saji...@wso2.com mahe...@wso2.com | Web: www.wso2.com




-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc. http://wso2.com/ - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Deploying an ESB Connector with a cApp?

[Viraj Rajaguru]

Hi,

We are going to implement including connectors into CApp feature in DevS
side.

Currently, we can import a connector into DevS using import connector
wizard. Imported connector will be stored in shared location for all the
ESB projects in workplace. That means, once you import a connector it will
be visible to all the ESB projects.
To facilitate to include these connectors into CApp, we can list all the
connectors that are available in this location in the Composite Application
project's pom file editor. Then users can select required connectors and
create a CApp.

Using above mentioned approach, we can support the use case mentioned by
Kasun.
- We want to invoke a Twitter operation.
- Import the Twitter connector from connector-store(into DevS) and use the
Twitter connector operation in our mediation logic.
- Include connector and the artifact(API, Proxy service, Sequence) into
CApp and deploy the CApp.

And also currently there is no option to remove imported connectors. There
is only Import connectors wizard. We are going to change this wizard to
Manage connectors which will allow users to import and remove connectors
to/from DevS.

Thanks,
Viraj.

On Fri, Jul 10, 2015 at 9:55 AM, Kasun Indrasiri ka...@wso2.com wrote:

 Good progress Shakila. Lets get the end-to-end use case working.

 On Thu, Jul 9, 2015 at 5:27 PM, Shakila Sivagnanarajah shak...@wso2.com
 wrote:

 Hi Malaka,

 I have tested the scenarios [1] and [2]. [1] is working fine and to test
 [2], I am unable to bundle connector and proxy-service in a CApp. If I add
 those two in to the config project, the CApp will contain proxy-service
 only.

 [1]  Including more than one connector in CApp.
 [2] Use the connector inside a proxy service, Api and sequence that are
 included in the same CApp.

 Thank you.

 On Thu, Jul 9, 2015 at 10:20 AM, Shakila Sivagnanarajah shak...@wso2.com
  wrote:

 Hi Malaka,

 As you noted, I will test for possible scenarios.

 Thank you.

 On Thu, Jul 9, 2015 at 10:10 AM, Malaka Silva mal...@wso2.com wrote:

 Hi Shakila,

 Good Progress on this.

 Let's verify some scenario similar to following,

1. Include more that one connector.
2. Use the connector inside a proxy service, Api and sequence that
are included in the same capp.


 On Wed, Jul 8, 2015 at 6:23 PM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi all,

 I have done the connector deployment from CApp.

 Thank you

 On Wed, Jul 8, 2015 at 10:25 AM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi all,

 Please find the CApp [1].

 This is my progress:

 1. I added the connector zip in to the CApp as an artifact and
 specified the artifact type as zip.
 2. As the same way to deploy the artifact, I have implemented a
 method to deploy the synapse library in [2] (Still testing).
 3. I have added some constants in [3].

 I am following the way that Dushan noted. Initially I am doing this
 with a single connector. As the first step, Now I am doing the connector
 deployment (CAR --  upload --  deploy connector).

 [1]
 https://drive.google.com/a/wso2.com/file/d/0B3SvJgvWs9I_eWY5UEJhM3pzb0k/view?usp=sharing

 [2]
 CARBON-MEDIATION-HOME/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java

 [3]
 CARBON-MEDIATION-HOME/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployerConstants.java


 Thank you.

 On Wed, Jul 8, 2015 at 6:02 AM, Dushan Abeyruwan dus...@wso2.com
 wrote:



 On Tue, Jul 7, 2015 at 8:07 AM, Jasintha Dasanayake 
 jasin...@wso2.com wrote:

 @viraj

 Shall we enable this in ESB project level , since there is a option
 already in ESB project , that we can improve to pack connector into 
 capp
 when adding the ESB project into Capp ?

  +1 this should be feasible with ESB Project level as its already
 there in DevS

 Shashika, could please provide more detail (design and
 implementation detail/changes you have done) how you planned to 
 integrate
 this ?

 however, please note that we need manage depdenencies correctly

 CAR --  upload --  deploy connector/s --- [[*critical:* monitor
 the status of connector deployment]] -- if success --- execute
 connector-meta-import  -- if success --  then deploy other
 synapse-artifacts

 *guess, the difficulty can be holding synapse artifact deployment
 till connector's uploaded successfully and import connector meta data, 
 have
 found solution for this ?*



 Thanks and Regards
 /Jasintha

 On Tue, Jul 7, 2015 at 4:33 PM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi Kasun,

 Since there is no feature in developer studio to import connector
 zip into the CApp, I have manually added the zip in to car. Now I
 am debugging and modifying the code [1]. I think I am going well with 
 the
 task.

 [1]
 

[Dev] Please Review and Merge PRs

[Chamila Wijayarathna]

Hi,

Please review and merge following PRs.
https://github.com/wso2/carbon4-kernel/pull/293
https://github.com/wso2/carbon-identity/pull/610

Thank You!

-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please Merge the pull request

[Lalaji Sureshika]

Hi Udara,

For the moment,we are copying jaggery apps from es.feature.Yes,we can use
store feature to copy those apps,instead es.feature as we have included
both of them to our p2-profile pom. As per your reply,does that mean,we can
fully get rid of es.feature and use store.feature only in our pom
references?

Thanks

On Mon, Jul 13, 2015 at 2:54 AM, Udara Rathnayake uda...@wso2.com wrote:

 Hi Lakshman,

 Is there any possibility to use the store feature instead of es one? We
 initially created this es feature for AM team to facilitate keeping both ES
 store/publisher apps and API manager store/publisher apps. Eg:- es-store
 coming form es feature and store is coming from am store feature

 Seems es feature is bit outdated and might get dropped in future. Let us
 know the possibility of moving from es feature to store.

 Regards,
 UdaraR

 On Mon, Jul 13, 2015 at 12:10 PM, Lakshman Udayakantha lakshm...@wso2.com
  wrote:

 jira for this is [2]

 [2] https://wso2.org/jira/browse/STORE-894

 On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha lakshm...@wso2.com
  wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*



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




-- 
Lalaji Sureshika
WSO2, Inc.;  http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack

[Aparna Karunarathna]

Even IS 510 M3 pack doesn't have the tenant-mgt.xml file.

Regards,
Aparna


On Mon, Jul 13, 2015 at 11:35 AM, Thayalan thaya...@wso2.com wrote:

 Hi Team,

 As per the mail discussion in [1]  [2] what I understood was
 tenant-mgt.xml file has to be included with all the products. But, I'm not
 clear on the final verdict whether to include $Subject with all the
 products that we ship including GREG. Please confirm.

 The same issue persist with the latest GREG pack as well.

 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon packs
 ?
 2. Is it possible to re-factor current 'product distribution process'
 --
 Regards,
 Thayalan Sivapaleswararajah
 Associate Technical Lead - QA
 Mob: +94(0)777872485
 Tel : +94(0)(11)2145345
 Fax : +94(0)(11)2145300
 Email: thaya...@wso2.com


 *Disclaimer*: *This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, retransmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.*




-- 
*Regards,*

*Aparna Karunarathna.*


*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Deploying an ESB Connector with a cApp?

[Jasintha Dasanayake]

On Mon, Jul 13, 2015 at 12:16 PM, Viraj Rajaguru vi...@wso2.com wrote:

 Hi,

 We are going to implement including connectors into CApp feature in DevS
 side.

 Currently, we can import a connector into DevS using import connector
 wizard. Imported connector will be stored in shared location for all the
 ESB projects in workplace. That means, once you import a connector it will
 be visible to all the ESB projects.
 To facilitate to include these connectors into CApp, we can list all the
 connectors that are available in this location in the Composite Application
 project's pom file editor. Then users can select required connectors and
 create a CApp.


+1 for this approach  , we also have to think about importing scenarios  ,
if user import esb project which already added connectors  then we need to
properly handle it



 Using above mentioned approach, we can support the use case mentioned by
 Kasun.
 - We want to invoke a Twitter operation.
 - Import the Twitter connector from connector-store(into DevS) and use the
 Twitter connector operation in our mediation logic.
 - Include connector and the artifact(API, Proxy service, Sequence) into
 CApp and deploy the CApp.

 And also currently there is no option to remove imported connectors. There
 is only Import connectors wizard. We are going to change this wizard to
 Manage connectors which will allow users to import and remove connectors
 to/from DevS.


 +1  for renaming the name but first we  should think where we initiate
this wizard based on that we can decide the name

Thanks and Regards
/Jasintha


Thanks,
 Viraj.

 On Fri, Jul 10, 2015 at 9:55 AM, Kasun Indrasiri ka...@wso2.com wrote:

 Good progress Shakila. Lets get the end-to-end use case working.

 On Thu, Jul 9, 2015 at 5:27 PM, Shakila Sivagnanarajah shak...@wso2.com
 wrote:

 Hi Malaka,

 I have tested the scenarios [1] and [2]. [1] is working fine and to test
 [2], I am unable to bundle connector and proxy-service in a CApp. If I add
 those two in to the config project, the CApp will contain proxy-service
 only.

 [1]  Including more than one connector in CApp.
 [2] Use the connector inside a proxy service, Api and sequence that are
 included in the same CApp.

 Thank you.

 On Thu, Jul 9, 2015 at 10:20 AM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi Malaka,

 As you noted, I will test for possible scenarios.

 Thank you.

 On Thu, Jul 9, 2015 at 10:10 AM, Malaka Silva mal...@wso2.com wrote:

 Hi Shakila,

 Good Progress on this.

 Let's verify some scenario similar to following,

1. Include more that one connector.
2. Use the connector inside a proxy service, Api and sequence that
are included in the same capp.


 On Wed, Jul 8, 2015 at 6:23 PM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi all,

 I have done the connector deployment from CApp.

 Thank you

 On Wed, Jul 8, 2015 at 10:25 AM, Shakila Sivagnanarajah 
 shak...@wso2.com wrote:

 Hi all,

 Please find the CApp [1].

 This is my progress:

 1. I added the connector zip in to the CApp as an artifact and
 specified the artifact type as zip.
 2. As the same way to deploy the artifact, I have implemented a
 method to deploy the synapse library in [2] (Still testing).
 3. I have added some constants in [3].

 I am following the way that Dushan noted. Initially I am doing this
 with a single connector. As the first step, Now I am doing the connector
 deployment (CAR --  upload --  deploy connector).

 [1]
 https://drive.google.com/a/wso2.com/file/d/0B3SvJgvWs9I_eWY5UEJhM3pzb0k/view?usp=sharing

 [2]
 CARBON-MEDIATION-HOME/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java

 [3]
 CARBON-MEDIATION-HOME/components/application-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployerConstants.java


 Thank you.

 On Wed, Jul 8, 2015 at 6:02 AM, Dushan Abeyruwan dus...@wso2.com
 wrote:



 On Tue, Jul 7, 2015 at 8:07 AM, Jasintha Dasanayake 
 jasin...@wso2.com wrote:

 @viraj

 Shall we enable this in ESB project level , since there is a
 option already in ESB project , that we can improve to pack connector 
 into
 capp when adding the ESB project into Capp ?

  +1 this should be feasible with ESB Project level as its already
 there in DevS

 Shashika, could please provide more detail (design and
 implementation detail/changes you have done) how you planned to 
 integrate
 this ?

 however, please note that we need manage depdenencies correctly

 CAR --  upload --  deploy connector/s --- [[*critical:* monitor
 the status of connector deployment]] -- if success --- execute
 connector-meta-import  -- if success --  then deploy other
 synapse-artifacts

 *guess, the difficulty can be holding synapse artifact deployment
 till connector's uploaded successfully and import connector meta data, 
 have
 found solution for this ?*



 

Re: [Dev] Please Merge the pull request

[Udara Rathnayake]

Hi Lalaji,

Yes. I just had a look at the diff of those two features. There is no
difference other than the app-naming and latest additions to the store
feature.
So we should be able to get rid of the es feature usage.

Regards,
UdaraR

On Mon, Jul 13, 2015 at 12:37 PM, Lalaji Sureshika lal...@wso2.com wrote:

 Hi Udara,

 For the moment,we are copying jaggery apps from es.feature.Yes,we can use
 store feature to copy those apps,instead es.feature as we have included
 both of them to our p2-profile pom. As per your reply,does that mean,we can
 fully get rid of es.feature and use store.feature only in our pom
 references?

 Thanks

 On Mon, Jul 13, 2015 at 2:54 AM, Udara Rathnayake uda...@wso2.com wrote:

 Hi Lakshman,

 Is there any possibility to use the store feature instead of es one? We
 initially created this es feature for AM team to facilitate keeping both ES
 store/publisher apps and API manager store/publisher apps. Eg:- es-store
 coming form es feature and store is coming from am store feature

 Seems es feature is bit outdated and might get dropped in future. Let us
 know the possibility of moving from es feature to store.

 Regards,
 UdaraR

 On Mon, Jul 13, 2015 at 12:10 PM, Lakshman Udayakantha 
 lakshm...@wso2.com wrote:

 jira for this is [2]

 [2] https://wso2.org/jira/browse/STORE-894

 On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha 
 lakshm...@wso2.com wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*



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




 --
 Lalaji Sureshika
 WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com



--- /home/udara/wso2/git/fork/carbon-store/features/org.wso2.es.feature/pom.xml
+++ 
/home/udara/wso2/git/fork/carbon-store/features/org.wso2.store.feature/pom.xml
@@ -16,16 +16,14 @@
 --
 
 project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
-
 parent
 groupIdorg.wso2.carbon.store/groupId
 artifactIdcarbon-store/artifactId
 version2.3.1-SNAPSHOT/version
 relativePath../../pom.xml/relativePath
 /parent
-
 modelVersion4.0.0/modelVersion
-artifactIdorg.wso2.es.feature/artifactId
+artifactIdorg.wso2.store.feature/artifactId
 packagingpom/packaging
 nameWSO2 Enterprise Store Feature/name
 urlhttp://wso2.org/url
@@ -38,17 +36,14 @@
 groupIdorg.apache.httpcomponents.wso2/groupId
 artifactIdhttpcore/artifactId
 /dependency
-
 dependency
 groupIdorg.wso2.carbon.store/groupId
 artifactIdorg.wso2.store.bamclient/artifactId
 /dependency
-
 dependency
 groupIdorg.wso2.carbon.store/groupId
 artifactIdorg.wso2.store.util/artifactId
 /dependency
-
 /dependencies
 build
 plugins
@@ -63,7 +58,7 @@
 goalp2-feature-gen/goal
 /goals
 configuration
-idorg.wso2.es/id
+idorg.wso2.store/id
 
propertiesFile../etc/feature.properties/propertiesFile
 bundles
 
bundleDefslf4j.wso2:slf4j:${slf4j.wso2.version}/bundleDef
@@ -152,6 +147,10 @@
 importFeatureDef
 
org.wso2.carbon.registry.contentsearch.server:${carbon.registry.version}
 /importFeatureDef
+!--importFeatureDef
+
org.wso2.carbon.jaxws.webapp.mgt.server:${carbon.platform.version}
+/importFeatureDef--
+!-- SSO --
 importFeatureDef
 
org.wso2.carbon.security.mgt:${carbon.identity.version}
 /importFeatureDef
@@ -167,6 +166,9 @@
 feaureArtifactDef
 
org.wso2.carbon.identity.sso.saml.server:${carbon.identity.version}
 /feaureArtifactDef
+!--feaureArtifactDef
+
org.wso2.stratos.identity.saml2.sso.mgt.server:${carbon.platform.version}
+/feaureArtifactDef--
 feaureArtifactDef
 

Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack

[Prasad Tissera]

Hi All,

We fixed this issue in product-is master branch.

Regards,
Prasad.

On Mon, Jul 13, 2015 at 12:48 PM, Aparna Karunarathna apa...@wso2.com
wrote:


 tenant-mgt.xml file is included under repository/conf/multitenancy
 directory in the ES200 pack.

 @Johann/ SameeraJ / SameeraM, Have we changed the location of tenant-
 mgt.xml file or is this an error?

 Regards,
 Aparna.

 On Mon, Jul 13, 2015 at 12:36 PM, Aparna Karunarathna apa...@wso2.com
 wrote:

 Even IS 510 M3 pack doesn't have the tenant-mgt.xml file.

 Regards,
 Aparna


 On Mon, Jul 13, 2015 at 11:35 AM, Thayalan thaya...@wso2.com wrote:

 Hi Team,

 As per the mail discussion in [1]  [2] what I understood was
 tenant-mgt.xml file has to be included with all the products. But, I'm not
 clear on the final verdict whether to include $Subject with all the
 products that we ship including GREG. Please confirm.

 The same issue persist with the latest GREG pack as well.

 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon
 packs?
 2. Is it possible to re-factor current 'product distribution process'
 --
 Regards,
 Thayalan Sivapaleswararajah
 Associate Technical Lead - QA
 Mob: +94(0)777872485
 Tel : +94(0)(11)2145345
 Fax : +94(0)(11)2145300
 Email: thaya...@wso2.com


 *Disclaimer*: *This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, retransmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.*




 --
 *Regards,*

 *Aparna Karunarathna.*


 *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 0714002533*




 --
 *Regards,*

 *Aparna Karunarathna.*


 *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*

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




-- 
Prasad Tissera
Software Engineer.
Mobile : +94777223444
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please Merge the pull request

[Lakshman Udayakantha]

create a jira [1] to track this

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

On Mon, Jul 13, 2015 at 1:21 PM, Udara Rathnayake uda...@wso2.com wrote:

 Hi Lalaji,

 Yes. I just had a look at the diff of those two features. There is no
 difference other than the app-naming and latest additions to the store
 feature.
 So we should be able to get rid of the es feature usage.

 Regards,
 UdaraR


 On Mon, Jul 13, 2015 at 12:37 PM, Lalaji Sureshika lal...@wso2.com
 wrote:

 Hi Udara,

 For the moment,we are copying jaggery apps from es.feature.Yes,we can use
 store feature to copy those apps,instead es.feature as we have included
 both of them to our p2-profile pom. As per your reply,does that mean,we can
 fully get rid of es.feature and use store.feature only in our pom
 references?

 Thanks

 On Mon, Jul 13, 2015 at 2:54 AM, Udara Rathnayake uda...@wso2.com
 wrote:

 Hi Lakshman,

 Is there any possibility to use the store feature instead of es one? We
 initially created this es feature for AM team to facilitate keeping both ES
 store/publisher apps and API manager store/publisher apps. Eg:- es-store
 coming form es feature and store is coming from am store feature

 Seems es feature is bit outdated and might get dropped in future. Let us
 know the possibility of moving from es feature to store.

 Regards,
 UdaraR

 On Mon, Jul 13, 2015 at 12:10 PM, Lakshman Udayakantha 
 lakshm...@wso2.com wrote:

 jira for this is [2]

 [2] https://wso2.org/jira/browse/STORE-894

 On Mon, Jul 13, 2015 at 1:03 AM, Lakshman Udayakantha 
 lakshm...@wso2.com wrote:

 Hi ES Team,

 $subject please for [1]

 [1] https://github.com/wso2/carbon-store/pull/94

 Thanks

 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*




 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0711241005*



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




 --
 Lalaji Sureshika
 WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com






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