[Dev] Need help adding a simple transformation in API Cloud
Hi, I tried to find this in documentation but got confused - so asking over email. I have a backend web service that for some calls returns URLs related to the webservice. I am trying to use WSO2 API Cloud to proxy that webservice. Obviously, I now need the gateway to modify the calls so instead of private URLs - the public (gateway) ones are returned. So this would be a fairly simple regex. Now... where and how do I put this regex? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] SSL error in direct call to github via integration framework
we are experiencing following issue when make direct call via integration
base to github. when we use this with normal java client its worked fine.
but when taken in to integration framework gives following error. Pls advice
on this.
Note: we follow the same approach on other SSL backends and this is the
first time we experience this issue.
Source :
/**
* Positive test case for getBlob method with mandatory parameters.
*
*/
@Test(priority = 1, description = github {getBlob} integration test
with mandatory parameters.)
public void testGetBlobWithMandatoryParameters() throws IOException,
JSONException{
esbRequestHeadersMap.put(Action, urn:getBlob);
apiRequestHeadersMap.put(Accept-Charset, UTF-8);
apiRequestHeadersMap.put(Content-Type,
application/x-www-form-urlencoded);
apiRequestHeadersMap.put(Authorization, token
ed25f732c08905e6638ff0abd77f2ae6f4316701);
RestResponseJSONObject esbRestResponse =
sendJsonRestRequest(getProxyServiceURL(github), POST,
esbRequestHeadersMap, esb_getBlob_mandatory.json);
System.out.println(ESB Output :
+esbRestResponse.getBody().toString());
String apiEndPoint = connectorProperties.getProperty(githubApiUrl)
+ /repos/ +
connectorProperties.getProperty(owner)+/+connectorProperties.getProperty(repo)+/git/blobs/+connectorProperties.getProperty(blobSHA);
System.out.println(End Point URL : + apiEndPoint);
RestResponseJSONObject apiRestResponse =
sendJsonRestRequest(apiEndPoint, GET, apiRequestHeadersMap);
System.out.println(API==+apiRestResponse.getBody().toString());
}
Integration Test Log:
ESB Output :
{content:Q29udGVudCBvZiB0aGUgYmxvYg==\n,sha:929246f65aab4d636cb229c790f966afc332c124,encoding:base64,url:https://api.github.com/repos/wso2connector/Test/git/blobs/929246f65aab4d636cb229c790f966afc332c124,size:19}
End Point URL :
https://api.github.com/repos/wso2connector/Test/git/blobs/929246f65aab4d636cb229c790f966afc332c124
[2014-05-16 12:07:42,725] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
[2014-05-16 12:07:42,725] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} -
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
[2014-05-16 12:07:42,725] INFO
{org.wso2.carbon.automation.core.PlatformTestManager} - --Tests
Failed
org.wso2.carbon.connector.integration.test.dropbox.DropboxConnectorIntegrationTest.testGetBlobWithMandatoryParameters
FAILED: testGetBlobWithMandatoryParameters
github {getBlob} integration test with mandatory parameters.
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at
sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1902)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1338)
at
sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:154)
at
sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
at
sun.security.ssl.Handshaker.process_record(Handshaker.java:804)
at
sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1032)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1328)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1355)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:515)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1299)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:490)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:277)
at
Re: [Dev] Need help adding a simple transformation in API Cloud
Thanks Nuwan. I guess I will try to learn a little more about writing the sequence files and will get back to you if I have issues placing them into API Cloud. Thanks again for the quick responce! Dmitry On Tue, May 20, 2014 at 2:31 PM, Nuwan Dias nuw...@wso2.com wrote: Hi Dimitry, How you can do this is by writing a custom out sequence that would do the url transformations for you and save that out sequence (xml file) in the appropriate registry location so that you can apply that sequence in the response path of the API. The document at [1] has more details about this capability. [1] - https://docs.wso2.org/display/AM160/Adding+a+Mediation+Extension Thanks, NuwanD. On Tue, May 20, 2014 at 1:17 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Hi, I tried to find this in documentation but got confused - so asking over email. I have a backend web service that for some calls returns URLs related to the webservice. I am trying to use WSO2 API Cloud to proxy that webservice. Obviously, I now need the gateway to modify the calls so instead of private URLs - the public (gateway) ones are returned. So this would be a fairly simple regex. Now... where and how do I put this regex? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Manager: Resource-level authorization
Is there a way within API Manager to do resource-level permissions? For example, for a particular resource users from one role can only do GET, and from another also have POST? I found a way to assign the whole API to a role, but not individual resources. For resources, as far as I understand, I can only set max tier and level of authentication. Is there a way to achieve this selective verb access based on user role? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Check the status of file processing in VFS transport
Hi All, While a VFS transport happens is there a way to check whether the file processing happens or not? Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager: Resource-level authorization
Hi Dimitry, No, right now we do not have this support. But in the upcoming release of the API Manager this would be possible with the introduction of scopes (OAuth2). Thanks, NuwanD. On Tue, May 20, 2014 at 4:01 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Is there a way within API Manager to do resource-level permissions? For example, for a particular resource users from one role can only do GET, and from another also have POST? I found a way to assign the whole API to a role, but not individual resources. For resources, as far as I understand, I can only set max tier and level of authentication. Is there a way to achieve this selective verb access based on user role? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Check the status of file processing in VFS transport
Hi Sohani, I guess you are talking about ESB. If that is the case, you can specify below parameters to make sure your file is processed or not. ex: *transport.vfs.MoveAfterFailure* - Where to move the files after processing if ActionAfterFailure is MOVE. Please refer the parameters section of the below link, https://docs.wso2.org/display/ESB481/VFS+Transport Thanks, Chanaka On Tue, May 20, 2014 at 4:06 PM, Sohani Weerasinghe soh...@wso2.com wrote: Hi All, While a VFS transport happens is there a way to check whether the file processing happens or not? Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Chanaka Fernando Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 773337238 Blog : http://soatutorials.blogspot.com LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 Twitter:https://twitter.com/chanakaudaya Wordpress:http://chanakaudaya.wordpress.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager: Resource-level authorization
Upcoming meaning 1.7 that's coming soon? Is there documentation describing how to set up this resource-level access by roles with the scopes? Dmitry On Tue, May 20, 2014 at 4:37 PM, Nuwan Dias nuw...@wso2.com wrote: Hi Dimitry, No, right now we do not have this support. But in the upcoming release of the API Manager this would be possible with the introduction of scopes (OAuth2). Thanks, NuwanD. On Tue, May 20, 2014 at 4:01 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Is there a way within API Manager to do resource-level permissions? For example, for a particular resource users from one role can only do GET, and from another also have POST? I found a way to assign the whole API to a role, but not individual resources. For resources, as far as I understand, I can only set max tier and level of authentication. Is there a way to achieve this selective verb access based on user role? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Required changes in EMM Android Agent
Hi Krishanthi, Please find my comments on above options. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? 2. +1 for this change, but still I feel Domain sounds clear than Group. Here are my comments on Improvements section: 1. +1 for this, these information should be sent be the server probably in SENDER_ID request and then we can show/bypass pin setting. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. Thanks On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe krishant...@wso2.com wrote: Hi Shan, As we discussed, we are going to do following changes: 1. Change the message in setting server IP screen. Change from *Set your server address here to start registration, i.e : www.abc.com http://www.abc.com* to *Set your MDM server address* 2. In login screen, currently we have inputs as following order: i. Domain ii. Username iii Password We are going to change it as: i. Username ii. Password iii. Group (We are using this for tenancy) *Note:* Here I have attached the server IP screen(setServerIP.png) and the login screen(login.png). *Improvements:* 1. We should allow to add pin code, only for users who is able to wipe the device. For that we(Android agent) need to get that information from the server side *after the login*, but *before completing the registration*. Then there will be changes in both server side and android agent. 2. We should allow user to do the registration even *without seeing license agreement* if *he/she requires*. There cannot be any screen between the registration and registration successful screens. For that we need to include a check box. We need to decide the screen where we have to add this. If we are going to implement this, since there are many logical implementation based on the license agreement in Android Agent, we have to do a major change in Android Agent. Please let me know, if I have missed any point. Others opinions are welcome. Please give your comments to proceed on this. Thank you. -- Best Regards, Krishanthi Bhagya Samarasinghe Senior Software engineer Mobile: +94 716028280 -- Kasun Dananjaya Delgolla Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Tel: +94 11 214 5345 Fax: +94 11 2145300 Mob: + 94 777 997 850 Blog: http://kddcodingparadise.blogspot.com Linkedin: *http://lk.linkedin.com/in/kasundananjaya http://lk.linkedin.com/in/kasundananjaya* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager: Resource-level authorization
Yes 1.7. The docs are still under construction and not publicly available. Basically at the time of creating the API, you will be able to define scopes for an API and associate user roles for the scopes. You can then assign a scope to a particular resource. Which would indirectly mean that you assign a role for a resource. At the time of requesting a token, you provide the list of scopes that you require. The token that you get, will only bear the scopes that you are permitted to access. Meaning that you will not be able to use that token for accessing resources that you are not permitted to. Thanks, NuwanD. On Tue, May 20, 2014 at 4:47 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Upcoming meaning 1.7 that's coming soon? Is there documentation describing how to set up this resource-level access by roles with the scopes? Dmitry On Tue, May 20, 2014 at 4:37 PM, Nuwan Dias nuw...@wso2.com wrote: Hi Dimitry, No, right now we do not have this support. But in the upcoming release of the API Manager this would be possible with the introduction of scopes (OAuth2). Thanks, NuwanD. On Tue, May 20, 2014 at 4:01 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Is there a way within API Manager to do resource-level permissions? For example, for a particular resource users from one role can only do GET, and from another also have POST? I found a way to assign the whole API to a role, but not individual resources. For resources, as far as I understand, I can only set max tier and level of authentication. Is there a way to achieve this selective verb access based on user role? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] What should be the correct behavior in publishing services from G-Reg to APIM
Hi, I tried “Integrating APIM with WSO2 Governance Registry Services” scenario with G-Reg 4.6.0 and API Manager 1.7.0 18th May pack . Configurations are added accordingly as mentioned in the docs. “ https://docs.wso2.org/display/AM160/Integrating+with+WSO2+Governance+Registry+Services” and I have added the following patch to the G-Reg https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch0155 . Once I publish a service to APIM using G-reg , The service is published to to the APIM – Publisher page in created state. But according to the document is says it should publish in APIM Store. What should be the correct expected behavior and status in this scenario? Thanks and Regards, Chathurika -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What should be the correct behavior in publishing services from G-Reg to APIM
On Tue, May 20, 2014 at 5:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Hi, I tried “Integrating APIM with WSO2 Governance Registry Services” scenario with G-Reg 4.6.0 and API Manager 1.7.0 18th May pack . Configurations are added accordingly as mentioned in the docs. “ https://docs.wso2.org/display/AM160/Integrating+with+WSO2+Governance+Registry+Services” and I have added the following patch to the G-Reg https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch0155 . Once I publish a service to APIM using G-reg , The service is published to to the APIM – Publisher page in created state. But according to the document is says it should publish in APIM Store. What should be the correct expected behavior and status in this scenario? It should be the publisher state, because the informations are available in G-Reg side is not enough to publish as a complete API to store. Thanks. Ajith. Thanks and Regards, Chathurika -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager: Resource-level authorization
You can try a nightly build. On Tue, May 20, 2014 at 5:45 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Thanks a lot Nuwan! Dmitry On Tue, May 20, 2014 at 5:05 PM, Nuwan Dias nuw...@wso2.com wrote: Yes 1.7. The docs are still under construction and not publicly available. Basically at the time of creating the API, you will be able to define scopes for an API and associate user roles for the scopes. You can then assign a scope to a particular resource. Which would indirectly mean that you assign a role for a resource. At the time of requesting a token, you provide the list of scopes that you require. The token that you get, will only bear the scopes that you are permitted to access. Meaning that you will not be able to use that token for accessing resources that you are not permitted to. Thanks, NuwanD. On Tue, May 20, 2014 at 4:47 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Upcoming meaning 1.7 that's coming soon? Is there documentation describing how to set up this resource-level access by roles with the scopes? Dmitry On Tue, May 20, 2014 at 4:37 PM, Nuwan Dias nuw...@wso2.com wrote: Hi Dimitry, No, right now we do not have this support. But in the upcoming release of the API Manager this would be possible with the introduction of scopes (OAuth2). Thanks, NuwanD. On Tue, May 20, 2014 at 4:01 PM, Dmitry Sotnikov dmi...@wso2.comwrote: Is there a way within API Manager to do resource-level permissions? For example, for a particular resource users from one role can only do GET, and from another also have POST? I found a way to assign the whole API to a role, but not individual resources. For resources, as far as I understand, I can only set max tier and level of authentication. Is there a way to achieve this selective verb access based on user role? -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What should be the correct behavior in publishing services from G-Reg to APIM
Thanks for the update Ajith. Adding Nirdesha : This should be update in documents https://docs.wso2.org/display/AM170/Integrating+with+WSO2+Governance+Registry+Services Regards, Chathurika On Tue, May 20, 2014 at 6:02 PM, Ajith Vitharana aji...@wso2.com wrote: On Tue, May 20, 2014 at 5:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Hi, I tried “Integrating APIM with WSO2 Governance Registry Services” scenario with G-Reg 4.6.0 and API Manager 1.7.0 18th May pack . Configurations are added accordingly as mentioned in the docs. “ https://docs.wso2.org/display/AM160/Integrating+with+WSO2+Governance+Registry+Services” and I have added the following patch to the G-Reg https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch0155 . Once I publish a service to APIM using G-reg , The service is published to to the APIM – Publisher page in created state. But according to the document is says it should publish in APIM Store. What should be the correct expected behavior and status in this scenario? It should be the publisher state, because the informations are available in G-Reg side is not enough to publish as a complete API to store. Thanks. Ajith. Thanks and Regards, Chathurika -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Required changes in EMM Android Agent
+1 for changing the text of fields for usability. A small concern on Kasun's comment about License agreement - I thought we all agreed that there is no license agreement for COPE devices. Did this change? Cheers~ On Tue, May 20, 2014 at 5:15 PM, Harshan Liyanage hars...@wso2.com wrote: Hi, Please find my comments inline. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? I think we should guide the user as before. 2. +1 for this change, but still I feel Domain sounds clear than Group. I think we should add a help screen to let the users to know what is meant by these fields (domain/group). So then there won't be any clarification issues. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. I also agree with Kasun. Users must know what the EMM client app is capable of. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 4:55 PM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi Krishanthi, Please find my comments on above options. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? 2. +1 for this change, but still I feel Domain sounds clear than Group. Here are my comments on Improvements section: 1. +1 for this, these information should be sent be the server probably in SENDER_ID request and then we can show/bypass pin setting. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. Thanks On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe krishant...@wso2.com wrote: Hi Shan, As we discussed, we are going to do following changes: 1. Change the message in setting server IP screen. Change from *Set your server address here to start registration, i.e : www.abc.com http://www.abc.com* to *Set your MDM server address* 2. In login screen, currently we have inputs as following order: i. Domain ii. Username iii Password We are going to change it as: i. Username ii. Password iii. Group (We are using this for tenancy) *Note:* Here I have attached the server IP screen(setServerIP.png) and the login screen(login.png). *Improvements:* 1. We should allow to add pin code, only for users who is able to wipe the device. For that we(Android agent) need to get that information from the server side *after the login*, but *before completing the registration*. Then there will be changes in both server side and android agent. 2. We should allow user to do the registration even *without seeing license agreement* if *he/she requires*. There cannot be any screen between the registration and registration successful screens. For that we need to include a check box. We need to decide the screen where we have to add this. If we are going to implement this, since there are many logical implementation based on the license agreement in Android Agent, we have to do a major change in Android Agent. Please let me know, if I have missed any point. Others opinions are welcome. Please give your comments to proceed on this. Thank you. -- Best Regards, Krishanthi Bhagya Samarasinghe Senior Software engineer Mobile: +94 716028280 -- Kasun Dananjaya Delgolla Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Tel: +94 11 214 5345 Fax: +94 11 2145300 Mob: + 94 777 997 850 Blog: http://kddcodingparadise.blogspot.com Linkedin: *http://lk.linkedin.com/in/kasundananjaya http://lk.linkedin.com/in/kasundananjaya* -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com
[Dev] Fwd: Request to share BRS.2.1.0 Test Cases and load test results
Hi Nandika Got a request asking to share BRS test cases from an outside party do we do that Regards,shavantha -- Forwarded message -- From: Bala Sidda Reddy (Google Sheets) bala.re...@bizruntime.com Date: May 20, 2014 7:17 PM Subject: Request to share BRS.2.1.0 Test Cases and load test results To: shavan...@wso2.com Cc: Request to share [image: Spreadsheet] BRS.2.1.0 Test Cases and load test resultshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com You are the owner of this item and bala.re...@bizruntime.com has asked that you share this item with: + bala.re...@bizruntime.com Add these people in Sharing settingshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com . Google Sheets: Create and edit spreadsheets online. [image: Logo for Google Sheets] https://drive.google.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Request to share BRS.2.1.0 Test Cases and load test results
Hi Evanthika Accidently addressed the previous mail to Nandika. However, I Got a request asking to share BRS test cases from an outside party do we do that. Also I wonder how out side people saw this sheet shared within wso2 Regards,shavantha On May 20, 2014 8:06 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Nandika Got a request asking to share BRS test cases from an outside party do we do that Regards,shavantha -- Forwarded message -- From: Bala Sidda Reddy (Google Sheets) bala.re...@bizruntime.com Date: May 20, 2014 7:17 PM Subject: Request to share BRS.2.1.0 Test Cases and load test results To: shavan...@wso2.com Cc: Request to share [image: Spreadsheet] BRS.2.1.0 Test Cases and load test resultshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com You are the owner of this item and bala.re...@bizruntime.com has asked that you share this item with: + bala.re...@bizruntime.com Add these people in Sharing settingshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com . Google Sheets: Create and edit spreadsheets online. [image: Logo for Google Sheets] https://drive.google.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Required changes in EMM Android Agent
Hi Chan, It's not about showing the license for all users. This is about bypassing the license screen by* choosing bypass option* if the user wants to do so. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 8:08 PM, Chan duli...@wso2.com wrote: +1 for changing the text of fields for usability. A small concern on Kasun's comment about License agreement - I thought we all agreed that there is no license agreement for COPE devices. Did this change? Cheers~ On Tue, May 20, 2014 at 5:15 PM, Harshan Liyanage hars...@wso2.comwrote: Hi, Please find my comments inline. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? I think we should guide the user as before. 2. +1 for this change, but still I feel Domain sounds clear than Group. I think we should add a help screen to let the users to know what is meant by these fields (domain/group). So then there won't be any clarification issues. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. I also agree with Kasun. Users must know what the EMM client app is capable of. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 4:55 PM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi Krishanthi, Please find my comments on above options. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? 2. +1 for this change, but still I feel Domain sounds clear than Group. Here are my comments on Improvements section: 1. +1 for this, these information should be sent be the server probably in SENDER_ID request and then we can show/bypass pin setting. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. Thanks On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe krishant...@wso2.com wrote: Hi Shan, As we discussed, we are going to do following changes: 1. Change the message in setting server IP screen. Change from *Set your server address here to start registration, i.e : www.abc.com http://www.abc.com* to *Set your MDM server address* 2. In login screen, currently we have inputs as following order: i. Domain ii. Username iii Password We are going to change it as: i. Username ii. Password iii. Group (We are using this for tenancy) *Note:* Here I have attached the server IP screen(setServerIP.png) and the login screen(login.png). *Improvements:* 1. We should allow to add pin code, only for users who is able to wipe the device. For that we(Android agent) need to get that information from the server side *after the login*, but *before completing the registration*. Then there will be changes in both server side and android agent. 2. We should allow user to do the registration even *without seeing license agreement* if *he/she requires*. There cannot be any screen between the registration and registration successful screens. For that we need to include a check box. We need to decide the screen where we have to add this. If we are going to implement this, since there are many logical implementation based on the license agreement in Android Agent, we have to do a major change in Android Agent. Please let me know, if I have missed any point. Others opinions are welcome. Please give your comments to proceed on this. Thank you. -- Best Regards, Krishanthi Bhagya Samarasinghe Senior Software engineer Mobile: +94 716028280 -- Kasun
Re: [Dev] Required changes in EMM Android Agent
Hi, I believe license itself needs to be there for BYOD devices unless tenant admin wants to skip that through a configuration and disable it for entire tenant itself. What is the purpose of having the license if it can be skipped? That means BYOD devices can register without it and violate the company policies? Regards, Dilshan On Tue, May 20, 2014 at 8:16 PM, Harshan Liyanage hars...@wso2.com wrote: Hi Chan, It's not about showing the license for all users. This is about bypassing the license screen by* choosing bypass option* if the user wants to do so. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 8:08 PM, Chan duli...@wso2.com wrote: +1 for changing the text of fields for usability. A small concern on Kasun's comment about License agreement - I thought we all agreed that there is no license agreement for COPE devices. Did this change? Cheers~ On Tue, May 20, 2014 at 5:15 PM, Harshan Liyanage hars...@wso2.comwrote: Hi, Please find my comments inline. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? I think we should guide the user as before. 2. +1 for this change, but still I feel Domain sounds clear than Group. I think we should add a help screen to let the users to know what is meant by these fields (domain/group). So then there won't be any clarification issues. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. I also agree with Kasun. Users must know what the EMM client app is capable of. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 4:55 PM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi Krishanthi, Please find my comments on above options. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? 2. +1 for this change, but still I feel Domain sounds clear than Group. Here are my comments on Improvements section: 1. +1 for this, these information should be sent be the server probably in SENDER_ID request and then we can show/bypass pin setting. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. Thanks On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe krishant...@wso2.com wrote: Hi Shan, As we discussed, we are going to do following changes: 1. Change the message in setting server IP screen. Change from *Set your server address here to start registration, i.e : www.abc.com http://www.abc.com* to *Set your MDM server address* 2. In login screen, currently we have inputs as following order: i. Domain ii. Username iii Password We are going to change it as: i. Username ii. Password iii. Group (We are using this for tenancy) *Note:* Here I have attached the server IP screen(setServerIP.png) and the login screen(login.png). *Improvements:* 1. We should allow to add pin code, only for users who is able to wipe the device. For that we(Android agent) need to get that information from the server side *after the login*, but *before completing the registration*. Then there will be changes in both server side and android agent. 2. We should allow user to do the registration even *without seeing license agreement* if *he/she requires*. There cannot be any screen between the registration and registration successful screens. For that we need to include a check box. We need to decide the screen where we have to add this. If we are going
Re: [Dev] Required changes in EMM Android Agent
Hi, +1 for skipping license through config. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 8:32 PM, Dilshan Edirisuriya dils...@wso2.comwrote: Hi, I believe license itself needs to be there for BYOD devices unless tenant admin wants to skip that through a configuration and disable it for entire tenant itself. What is the purpose of having the license if it can be skipped? That means BYOD devices can register without it and violate the company policies? Regards, Dilshan On Tue, May 20, 2014 at 8:16 PM, Harshan Liyanage hars...@wso2.comwrote: Hi Chan, It's not about showing the license for all users. This is about bypassing the license screen by* choosing bypass option* if the user wants to do so. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 8:08 PM, Chan duli...@wso2.com wrote: +1 for changing the text of fields for usability. A small concern on Kasun's comment about License agreement - I thought we all agreed that there is no license agreement for COPE devices. Did this change? Cheers~ On Tue, May 20, 2014 at 5:15 PM, Harshan Liyanage hars...@wso2.comwrote: Hi, Please find my comments inline. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? I think we should guide the user as before. 2. +1 for this change, but still I feel Domain sounds clear than Group. I think we should add a help screen to let the users to know what is meant by these fields (domain/group). So then there won't be any clarification issues. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. I also agree with Kasun. Users must know what the EMM client app is capable of. Thanks, Best Regards, Lakshitha Harshan Software Engineer Mobile: *+94724423048* Email: hars...@wso2.com Blog : http://harshanliyanage.blogspot.com/ *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. On Tue, May 20, 2014 at 4:55 PM, Kasun Dananjaya Delgolla kas...@wso2.com wrote: Hi Krishanthi, Please find my comments on above options. 1. How do the user know the format to type in the domain. What if he type http://abc.com;? I think we should guide him in the screen as it was before. And the title MDM Server does not sound right to me because we all agreed on the single name EMM and why do we deviate from that in Agent? 2. +1 for this change, but still I feel Domain sounds clear than Group. Here are my comments on Improvements section: 1. +1 for this, these information should be sent be the server probably in SENDER_ID request and then we can show/bypass pin setting. 2. -1 for this change. I think all the users should see the license agreement. Otherwise this can be an issue later (Ex:If his/her phone get wipes off for some reason, he might complain about it negatively). I don't see any complication in showing the agreement because they can simply accept it and go ahead if they want. I think showing the agreement is anyways better and safe in legal aspects as well. So I strongly -1 on this change. Thanks On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe krishant...@wso2.com wrote: Hi Shan, As we discussed, we are going to do following changes: 1. Change the message in setting server IP screen. Change from *Set your server address here to start registration, i.e : www.abc.com http://www.abc.com* to *Set your MDM server address* 2. In login screen, currently we have inputs as following order: i. Domain ii. Username iii Password We are going to change it as: i. Username ii. Password iii. Group (We are using this for tenancy) *Note:* Here I have attached the server IP screen(setServerIP.png) and the login screen(login.png). *Improvements:* 1. We should allow to add pin code, only for users who is able to wipe the device. For that we(Android agent) need to get that information from the server side *after the login*, but *before completing the registration*. Then there will be changes in
Re: [Dev] WSO2MB topics where messages are automatically cleared
Hi Udara, Can you please tell us what is your exact requirement? In general if you use normal topics the messages will be discarded anyway if there is no consumer currently available. However if you use queues/durable topics WSO2 MB do not delete the messages regardless of they have consumers or not. They will be persisted in the broker till a consumer comes sometime and receives them. There is a JMS message header called 'JMSExpiration' where JMS providers ( the broker) set this field when a message is sent. When a message's expiration time is reached, the provider should discard it [1]. However we currently do not support this feature yet. Thanks! Ishara [1] http://docs.oracle.com/javaee/5/api/javax/jms/Message.html#getJMSExpiration%28%29 On Tue, May 20, 2014 at 8:38 PM, Udara Liyanage ud...@wso2.com wrote: Hi, Is there any type of queue/topic in MB where messages are deleted automatically after sometime if they are not consumed. Please point me to a doc if available. Touched, not typed. Erroneous words are a feature, not a typo. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadilMobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] PostgreSQL Connection error when starting up API Manager 1.6.0
Hi Chamara, Where do you have the database server? Locally or remote? If it's remote you will have to enable TCP/IP connections for db server ( *tcpip_socket=true* in postgresql.conf) and allow connections from APIM machine. You can do this by adding a host entry to *pg_hba.conf.* Thanks, Bhathiya On Tue, May 20, 2014 at 7:50 AM, Chamara Ariyarathne chama...@wso2.comwrote: Has anyone seen this error before with a WSO2 product? I'm getting this connection error when API Manager is configured to use a postgresql database. [2014-05-20 17:14:36,796] FATAL - DatabaseCreator Failed to create database tables for registry resource store. FATAL: no pg_hba.conf entry for host 10.100.1.90, user chamara, database am160carbon, SSL off org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host 10.100.1.90, user chamara, database am160carbon, SSL off at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:289) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:106) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64) at org.postgresql.jdbc2.AbstractJdbc2Connection.init(AbstractJdbc2Connection.java:123) at org.postgresql.jdbc3.AbstractJdbc3Connection.init(AbstractJdbc3Connection.java:28) at org.postgresql.jdbc3g.AbstractJdbc3gConnection.init(AbstractJdbc3gConnection.java:19) at org.postgresql.jdbc4.AbstractJdbc4Connection.init(AbstractJdbc4Connection.java:28) at org.postgresql.jdbc4.Jdbc4Connection.init(Jdbc4Connection.java:22) at org.postgresql.Driver.makeConnection(Driver.java:391) at org.postgresql.Driver.connect(Driver.java:265) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635) at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188) at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:128) at org.wso2.carbon.utils.dbcreator.DatabaseCreator.createRegistryDatabase(DatabaseCreator.java:58) at org.wso2.carbon.user.core.common.DefaultRealmService.initializeDatabase(DefaultRealmService.java:278) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:90) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114) at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69) at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [2014-05-20 17:14:36,797] ERROR - Activator Cannot start User Manager Core bundle java.lang.Exception: Error in creating the database at org.wso2.carbon.user.core.common.DefaultRealmService.initializeDatabase(DefaultRealmService.java:285) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:90) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114) at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69) at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at
Re: [Dev] PostgreSQL Connection error when starting up API Manager 1.6.0
On Tue, May 20, 2014 at 9:31 AM, Bhathiya Jayasekara bhath...@wso2.comwrote: Hi Chamara, Where do you have the database server? Locally or remote? If it's remote you will have to enable TCP/IP connections for db server ( *tcpip_socket=true* in postgresql.conf) and allow connections from APIM machine. You can do this by adding a host entry to *pg_hba.conf.* Refer http://www.postgresql.org/docs/8.2/static/auth-pg-hba-conf.html Thanks, Bhathiya On Tue, May 20, 2014 at 7:50 AM, Chamara Ariyarathne chama...@wso2.comwrote: Has anyone seen this error before with a WSO2 product? I'm getting this connection error when API Manager is configured to use a postgresql database. [2014-05-20 17:14:36,796] FATAL - DatabaseCreator Failed to create database tables for registry resource store. FATAL: no pg_hba.conf entry for host 10.100.1.90, user chamara, database am160carbon, SSL off org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host 10.100.1.90, user chamara, database am160carbon, SSL off at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:289) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:106) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64) at org.postgresql.jdbc2.AbstractJdbc2Connection.init(AbstractJdbc2Connection.java:123) at org.postgresql.jdbc3.AbstractJdbc3Connection.init(AbstractJdbc3Connection.java:28) at org.postgresql.jdbc3g.AbstractJdbc3gConnection.init(AbstractJdbc3gConnection.java:19) at org.postgresql.jdbc4.AbstractJdbc4Connection.init(AbstractJdbc4Connection.java:28) at org.postgresql.jdbc4.Jdbc4Connection.init(Jdbc4Connection.java:22) at org.postgresql.Driver.makeConnection(Driver.java:391) at org.postgresql.Driver.connect(Driver.java:265) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635) at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188) at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:128) at org.wso2.carbon.utils.dbcreator.DatabaseCreator.createRegistryDatabase(DatabaseCreator.java:58) at org.wso2.carbon.user.core.common.DefaultRealmService.initializeDatabase(DefaultRealmService.java:278) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:90) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114) at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69) at org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [2014-05-20 17:14:36,797] ERROR - Activator Cannot start User Manager Core bundle java.lang.Exception: Error in creating the database at org.wso2.carbon.user.core.common.DefaultRealmService.initializeDatabase(DefaultRealmService.java:285) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:90) at org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114) at org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69) at
Re: [Dev] Fwd: Request to share BRS.2.1.0 Test Cases and load test results
Hi Shavantha, On Tue, May 20, 2014 at 7:44 AM, Shavantha Weerasinghe shavan...@wso2.comwrote: Hi Evanthika Accidently addressed the previous mail to Nandika. However, I Got a request asking to share BRS test cases from an outside party do we do that. Also I wonder how out side people saw this sheet shared within wso2 I could remember this was shared recently. Just had a search for it and found it in dev list [1]. [1] [Dev] Business Rule Server 2.1.0 (Ch-11) - Testing update Thanks, Bhathiya Regards,shavantha On May 20, 2014 8:06 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Nandika Got a request asking to share BRS test cases from an outside party do we do that Regards,shavantha -- Forwarded message -- From: Bala Sidda Reddy (Google Sheets) bala.re...@bizruntime.com Date: May 20, 2014 7:17 PM Subject: Request to share BRS.2.1.0 Test Cases and load test results To: shavan...@wso2.com Cc: Request to share [image: Spreadsheet] BRS.2.1.0 Test Cases and load test resultshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com You are the owner of this item and bala.re...@bizruntime.com has asked that you share this item with: + bala.re...@bizruntime.com Add these people in Sharing settingshttps://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharinguserstoinvite=bala.re...@bizruntime.com . Google Sheets: Create and edit spreadsheets online. [image: Logo for Google Sheets] https://drive.google.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* *Blog: http://movingaheadblog.blogspot.com http://movingaheadblog.blogspot.com/* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Update on Gsoc Project - BAM Toolbox for WSO2 Business Process Server
Hi, I was able to write a sample HumanTaskEventListener and able to see the information of human task instance transitions. Currently I am working on the BPELTaskEventListener. Once I complete the event listeners, I will work on the data publisher. Then I will be able to work on the BAM dashboard and I am hoping to complete the above before the mid review which is on 23rd June. After the mid review I will work on ODE Execution events. On Mon, May 12, 2014 at 12:36 AM, Thilini Ishaka thil...@wso2.com wrote: Hi Pubudu, Some more materials are given below. Please update the thread with the current progress. *Data Publisher1. https://docs.wso2.org/display/BAM241/Data+Publisher https://docs.wso2.org/display/BAM241/Data+Publisher 2. https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/data-agents/org.wso2.carbon.bam.service.data.publisher/4.2.1/src/main/java/org/wso2/carbon/bam/service/data/publisher/publish/EventPublisher.java https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/data-agents/org.wso2.carbon.bam.service.data.publisher/4.2.1/src/main/java/org/wso2/carbon/bam/service/data/publisher/publish/EventPublisher.java Sending event to BAM * 3. Through the REST API https://docs.wso2.org/display/BAM241/Sending+Events+through+the+REST+API 4. Samples https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/bps/3.2.0/modules/samples/product/ *Monitoring with BAM *5. http://wso2.com/library/articles/2013/06/monitor-your-kpis-using-wso2-bam/ 6. https://docs.wso2.org/display/BAM240/Monitoring+key+Performance+Indicators 7. Creating a custom toolbox https://docs.wso2.org/display/BAM241/Creating+a+Custom+Toolbox Thanks Thilini On Wed, May 7, 2014 at 4:49 AM, Pubudu Gunatilaka pubudu...@gmail.comwrote: Hi Hasitha, Thank you for the information. I did not write a sample event listener yet. Still trying to get some idea about BPEL and Human task processes. I will work on what you have mentioned and let you know the progress. Thanks. On Wed, May 7, 2014 at 4:31 PM, Hasitha Aravinda hasi...@wso2.comwrote: Hi Pubudu, For BPEL processes, you can enable ODE events via deploy.xml. Please refer [1] for more information. Similar to HumanTask you can register ODE event listener to BPS using bps.xml. were you able to write a sample HumanTaskEventListener ? Also try to write sample BPELEventListener and see what kind of information you can get from events about HumanTask/BPEL instances. The idea is to identify data, which we are going to publish to the BAM. Also study about BAM data publishers. [2] will be a good point to start. Thanks, Hasitha. [1] - http://ode.apache.org/ode-execution-events.html [2] - http://wso2.com/library/articles/2012/07/creating-custom-agents-publish-events-bamcep/ On Wed, May 7, 2014 at 1:47 PM, Pubudu Gunatilaka pubudu...@gmail.comwrote: Hi, These days I am working with samples that are in WSO2 BPS in order to get some idea about BPEL and Human task processes. Some of the processes generate events and some do not. For the processes which generate events can use HumanTaskEventListener and BPELEventListener classes to write a custom event listener. But for the processes that do not generate events have to do using ODE Execution events. According to [1] this component can be added separately to BPS. I would really appreciate if you can provide me some useful materials in order to move forward. [1]- http://tryitnw.blogspot.com/2013/05/humantask-event-listeners-wso2-bps.html -- Regards P.C. Gunatilaka Undergraduate, Department of Computer Science And Engineering, University of Moratuwa, Sri Lanka. Web http://reddragonspace.blogspot.com/ , Facebookhttps://www.facebook.com/djpc4everhttps://www.facebook.com/djpc4ever, LinkedIn http://lk.linkedin.com/pub/pubudu-gunatilaka/32/2b8/20b , Google+ https://plus.google.com/113204823932612396731/posts , Twitterhttp://twitter.com/#!/PubuduSpace , About.me http://about.me/pubudugunatilaka -- Hasitha Aravinda, Software Engineer, WSO2 Inc. Email: hasi...@wso2.com Mobile: +94 71 8 210 200 -- Regards P.C. Gunatilaka Undergraduate, Department of Computer Science And Engineering, University of Moratuwa, Sri Lanka. Web http://reddragonspace.blogspot.com/ , Facebookhttps://www.facebook.com/djpc4everhttps://www.facebook.com/djpc4ever, LinkedIn http://lk.linkedin.com/pub/pubudu-gunatilaka/32/2b8/20b , Google+ https://plus.google.com/113204823932612396731/posts , Twitterhttp://twitter.com/#!/PubuduSpace , About.me http://about.me/pubudugunatilaka -- Thilini Ishaka Senior Software Engineer Phone: +94 11 214 5345 WSO2 Inc. http://wso2.com blog: thiliniishaka.blogspot.com linkedin: http://lk.linkedin.com/in/thiliniishaka twitter: https://twitter.com/#!/ThiliniIsh -- Regards P.C. Gunatilaka Undergraduate, Department of Computer Science And Engineering, University of
[Dev] [Blocker][APIM-1.7][IS-5.0] After IS As a Key Manager feature installation master-datasources.xml doesn't contain userstore datasource
Hi All,
$subject. After installing the key manager features in IS, IS doesn't start
up [1] since it could not find the userstore datasource definition. And
AFAIS userstore datasource is not there in master-datasources.xml file.
I'm using the p2-repo release on 19-05-2014.
[1]
TID: [0] [IS] [2014-05-20 21:09:13,338] ERROR
{org.wso2.carbon.user.core.internal.Activator} - Cannot start User Manager
Core bundle {org.wso2.carbon.user.core.internal.Activator}
java.lang.RuntimeException: Error in looking up data source: Name
[userstore] is not bound in this Context. Unable to find [userstore].
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:86)
at
org.wso2.carbon.user.core.util.DatabaseUtil.createRealmDataSource(DatabaseUtil.java:172)
at
org.wso2.carbon.user.core.util.DatabaseUtil.getRealmDataSource(DatabaseUtil.java:66)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:89)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: javax.naming.NameNotFoundException: Name [userstore] is not
bound in this Context. Unable to find [userstore].
at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
at org.apache.naming.NamingContext.lookup(NamingContext.java:831)
at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.doLookup(InitialContext.java:284)
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:84)
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: [ANNOUNCE] Apache CXF 3.0.0 released!
FYI, -- Forwarded message -- From: Daniel Kulp dk...@apache.org Date: Wed, May 21, 2014 at 1:29 AM Subject: [ANNOUNCE] Apache CXF 3.0.0 released! To: us...@cxf.apache.org, d...@cxf.apache.org The Apache CXF community is proud to announce that CXF 3.0.0 has been released. After a very long development cycle, 2 “milestone” releases, and lots of testing efforts, we’re glad to say that 3.0.0 is now available. CXF 3.0.0 contains several new features: * JAX-RS 2.0 support * Bean Validation support * A completely re-written “spring free” JMS transport * New WebSocket based transport * New HTTP transports based on Net * Completely new WS-Security engine based on StAX (WSS4J 2.0) * WS-RM 1.1 updates * much much more……. In addition, much of the old deprecated code has been removed and cleaned up, the required third party dependencies have been reduced, several of the API’s have been simplified, etc… For a more complete list of changes required to migrate to CXF 3.0, see: http://cxf.apache.org/docs/30-migration-guide.html Downloads are available from: http://cxf.apache.org/download.html For more information see: * Website: http://cxf.apache.org/ * Mailing lists: http://cxf.apache.org/mailing-lists.html If you have feedback, questions or would like to get involved in the CXF project please join the mailing lists and let us know your thoughts. The Apache CXF Team http://cxf.apache.org/ -- ~~~***'***~~~ *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com, *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org/ *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker][APIM-1.7][IS-5.0] After IS As a Key Manager feature installation master-datasources.xml doesn't contain userstore datasource
Sorry for the noise, this seems to be a local issue to me.
On Wed, May 21, 2014 at 2:50 AM, Nirmal Fernando nir...@wso2.com wrote:
Hi All,
$subject. After installing the key manager features in IS, IS doesn't
start up [1] since it could not find the userstore datasource definition.
And AFAIS userstore datasource is not there in master-datasources.xml file.
I'm using the p2-repo release on 19-05-2014.
[1]
TID: [0] [IS] [2014-05-20 21:09:13,338] ERROR
{org.wso2.carbon.user.core.internal.Activator} - Cannot start User Manager
Core bundle {org.wso2.carbon.user.core.internal.Activator}
java.lang.RuntimeException: Error in looking up data source: Name
[userstore] is not bound in this Context. Unable to find [userstore].
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:86)
at
org.wso2.carbon.user.core.util.DatabaseUtil.createRealmDataSource(DatabaseUtil.java:172)
at
org.wso2.carbon.user.core.util.DatabaseUtil.getRealmDataSource(DatabaseUtil.java:66)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:89)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: javax.naming.NameNotFoundException: Name [userstore] is not
bound in this Context. Unable to find [userstore].
at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
at org.apache.naming.NamingContext.lookup(NamingContext.java:831)
at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.doLookup(InitialContext.java:284)
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:84)
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk-11 Build Failure
Getting the following compilation error. Please look into this. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10:13.735s [INFO] Finished at: Tue May 20 21:01:17 UTC 2014 [INFO] Final Memory: 1268M/1875M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.apimgt.keymgt: Compilation failure: Compilation failure: [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[56,37] cannot find symbol [ERROR] symbol : variable APP_USER_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[69,41] cannot find symbol [ERROR] symbol : variable APP_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.apimgt.keymgt Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker][APIM-1.7][IS-5.0] After IS As a Key Manager feature installation master-datasources.xml doesn't contain userstore datasource
This is due to not installing the features on a fresh pack.
On Wed, May 21, 2014 at 2:57 AM, Nirmal Fernando nir...@wso2.com wrote:
Sorry for the noise, this seems to be a local issue to me.
On Wed, May 21, 2014 at 2:50 AM, Nirmal Fernando nir...@wso2.com wrote:
Hi All,
$subject. After installing the key manager features in IS, IS doesn't
start up [1] since it could not find the userstore datasource definition.
And AFAIS userstore datasource is not there in master-datasources.xml file.
I'm using the p2-repo release on 19-05-2014.
[1]
TID: [0] [IS] [2014-05-20 21:09:13,338] ERROR
{org.wso2.carbon.user.core.internal.Activator} - Cannot start User Manager
Core bundle {org.wso2.carbon.user.core.internal.Activator}
java.lang.RuntimeException: Error in looking up data source: Name
[userstore] is not bound in this Context. Unable to find [userstore].
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:86)
at
org.wso2.carbon.user.core.util.DatabaseUtil.createRealmDataSource(DatabaseUtil.java:172)
at
org.wso2.carbon.user.core.util.DatabaseUtil.getRealmDataSource(DatabaseUtil.java:66)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:89)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: javax.naming.NameNotFoundException: Name [userstore] is not
bound in this Context. Unable to find [userstore].
at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
at org.apache.naming.NamingContext.lookup(NamingContext.java:831)
at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.doLookup(InitialContext.java:284)
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:84)
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM1.7] Same port used in ThriftServerPort and ThriftClientPort
Hi, In api-manager.xml, I've noticed $subject. Is this a bug? KeyValidatorClientTypeThriftClient/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServertrue/EnableThriftServer -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk 11 - Nightly Build Packs (20/05/2014)
Hi All, Please find the $subject at: http://54.83.58.35/chunk11/20-05-2014/packs/ Included products are: BRS-2.1.0 ELB-2.1.1 IS-5.0.0 MB-2.2.0 P2 Repo at: http://54.83.58.35/chunk11/20-05-2014/p2-repo Built from revision: 203518. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 11 - Nightly Build Packs (20/05/2014)
Please note that AM-1.7.0 was not built due to the build failure mentioned in the mail: Chunk-11 Build Failure sent to @dev today. On Wed, May 21, 2014 at 7:37 AM, Dulanja Liyanage dula...@wso2.com wrote: Hi All, Please find the $subject at: http://54.83.58.35/chunk11/20-05-2014/packs/ Included products are: BRS-2.1.0 ELB-2.1.1 IS-5.0.0 MB-2.2.0 P2 Repo at: http://54.83.58.35/chunk11/20-05-2014/p2-repo Built from revision: 203518. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] App Factory Feature Upgrade
Hi, We have upgraded App Factory to newest released and to be released features. That includes following upgrades and we have done the smoke tests with them. org.wso2.carbon.ntask.feature - 4.2.2 org.wso2.carbon.user.mgt.feature - 4.2.2 org.wso2.carbon.service.mgt.feature - 4.2.2 org.wso2.carbon.registry.core.feature - 4.2.1 org.wso2.carbon.registry.community.features.feature - 4.2.0 org.wso2.carbon.event.server.feature - 4.2.2 org.wso2.carbon.event.feature - 4.2.2 org.wso2.carbon.logging.mgt.feature - 4.2.2 When building chunk 12 make sure that you build chunk 11 as well because we have integrated some of the featured to be released with chunk 11. Regards, -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika*https://twitter.com/Amila_Shamika *linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk-11 Build Failure
This is due to a partial update. Probably the update was taken half way down the commit. You shouldn't have see this if the org.wso2.carbon.apimgt.impl component had been updated. Thanks, NuwanD. On Wed, May 21, 2014 at 3:04 AM, Dulanja Liyanage dula...@wso2.com wrote: Getting the following compilation error. Please look into this. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10:13.735s [INFO] Finished at: Tue May 20 21:01:17 UTC 2014 [INFO] Final Memory: 1268M/1875M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.apimgt.keymgt: Compilation failure: Compilation failure: [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[56,37] cannot find symbol [ERROR] symbol : variable APP_USER_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[69,41] cannot find symbol [ERROR] symbol : variable APP_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.apimgt.keymgt Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Appfactory] BAM upgrade
Hi Shamika, Setup scripts still refer to BAM 2.3.0. So in-effect BAM is not upgraded. thanks, dimuthu On Thu, Apr 24, 2014 at 6:31 PM, Shamika Ariyawansa sham...@wso2.comwrote: Hi all, BAM server in App Factory current installation is upgraded to BAM 2.4.1 RC3. Regards -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika*https://twitter.com/Amila_Shamika * linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 11 - Nightly Build Packs (20/05/2014)
We did a build around 11.30pm and it was fine. No one committed into this after that.Getting a svn up. On Wed, May 21, 2014 at 7:42 AM, Dulanja Liyanage dula...@wso2.com wrote: Please note that AM-1.7.0 was not built due to the build failure mentioned in the mail: Chunk-11 Build Failure sent to @dev today. On Wed, May 21, 2014 at 7:37 AM, Dulanja Liyanage dula...@wso2.comwrote: Hi All, Please find the $subject at: http://54.83.58.35/chunk11/20-05-2014/packs/ Included products are: BRS-2.1.0 ELB-2.1.1 IS-5.0.0 MB-2.2.0 P2 Repo at: http://54.83.58.35/chunk11/20-05-2014/p2-repo Built from revision: 203518. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk-11 Build Failure
Pretty weird. I took an SVN up in the builder machine just before building the packs few hours back. Thanks Dulanja On Wed, May 21, 2014 at 9:02 AM, Nuwan Dias nuw...@wso2.com wrote: This is due to a partial update. Probably the update was taken half way down the commit. You shouldn't have see this if the org.wso2.carbon.apimgt.impl component had been updated. Thanks, NuwanD. On Wed, May 21, 2014 at 3:04 AM, Dulanja Liyanage dula...@wso2.comwrote: Getting the following compilation error. Please look into this. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10:13.735s [INFO] Finished at: Tue May 20 21:01:17 UTC 2014 [INFO] Final Memory: 1268M/1875M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.apimgt.keymgt: Compilation failure: Compilation failure: [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[56,37] cannot find symbol [ERROR] symbol : variable APP_USER_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[69,41] cannot find symbol [ERROR] symbol : variable APP_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.apimgt.keymgt Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk-11 Build Failure
We did a build on another builder machine after an svn update at 11.30pm. That build was successful. So probably an update has failed or something. Thanks, NuwanD. On Wed, May 21, 2014 at 9:47 AM, Dulanja Liyanage dula...@wso2.com wrote: Pretty weird. I took an SVN up in the builder machine just before building the packs few hours back. Thanks Dulanja On Wed, May 21, 2014 at 9:02 AM, Nuwan Dias nuw...@wso2.com wrote: This is due to a partial update. Probably the update was taken half way down the commit. You shouldn't have see this if the org.wso2.carbon.apimgt.impl component had been updated. Thanks, NuwanD. On Wed, May 21, 2014 at 3:04 AM, Dulanja Liyanage dula...@wso2.comwrote: Getting the following compilation error. Please look into this. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10:13.735s [INFO] Finished at: Tue May 20 21:01:17 UTC 2014 [INFO] Final Memory: 1268M/1875M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.apimgt.keymgt: Compilation failure: Compilation failure: [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[56,37] cannot find symbol [ERROR] symbol : variable APP_USER_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] [ERROR] /build/chunk-11/platform/turing/components/apimgt/org.wso2.carbon.apimgt.keymgt/1.2.2/src/main/java/org/wso2/carbon/apimgt/keymgt/handlers/ScopesIssuer.java:[69,41] cannot find symbol [ERROR] symbol : variable APP_SCOPE_CACHE [ERROR] location: class org.wso2.carbon.apimgt.impl.APIConstants [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.apimgt.keymgt Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 11 - Nightly Build Packs (20/05/2014)
It was broken by the commit around 12.30 on revision: 203491. Some constants were removed. Thanks regards, -Prabath On Wed, May 21, 2014 at 9:29 AM, Sumedha Rubasinghe sume...@wso2.comwrote: We did a build around 11.30pm and it was fine. No one committed into this after that.Getting a svn up. On Wed, May 21, 2014 at 7:42 AM, Dulanja Liyanage dula...@wso2.comwrote: Please note that AM-1.7.0 was not built due to the build failure mentioned in the mail: Chunk-11 Build Failure sent to @dev today. On Wed, May 21, 2014 at 7:37 AM, Dulanja Liyanage dula...@wso2.comwrote: Hi All, Please find the $subject at: http://54.83.58.35/chunk11/20-05-2014/packs/ Included products are: BRS-2.1.0 ELB-2.1.1 IS-5.0.0 MB-2.2.0 P2 Repo at: http://54.83.58.35/chunk11/20-05-2014/p2-repo Built from revision: 203518. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 11 - Nightly Build Packs (20/05/2014)
Yes, that's the case. Fixed and committed now. Thanks, NuwanD. On Wed, May 21, 2014 at 9:59 AM, Prabath Siriwardena prab...@wso2.comwrote: It was broken by the commit around 12.30 on revision: 203491. Some constants were removed. Thanks regards, -Prabath On Wed, May 21, 2014 at 9:29 AM, Sumedha Rubasinghe sume...@wso2.comwrote: We did a build around 11.30pm and it was fine. No one committed into this after that.Getting a svn up. On Wed, May 21, 2014 at 7:42 AM, Dulanja Liyanage dula...@wso2.comwrote: Please note that AM-1.7.0 was not built due to the build failure mentioned in the mail: Chunk-11 Build Failure sent to @dev today. On Wed, May 21, 2014 at 7:37 AM, Dulanja Liyanage dula...@wso2.comwrote: Hi All, Please find the $subject at: http://54.83.58.35/chunk11/20-05-2014/packs/ Included products are: BRS-2.1.0 ELB-2.1.1 IS-5.0.0 MB-2.2.0 P2 Repo at: http://54.83.58.35/chunk11/20-05-2014/p2-repo Built from revision: 203518. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM1.7] Same port used in ThriftServerPort and ThriftClientPort
This is not a bug. When server runs standalone mode thrift server start up on server port and client is using client port to connect it. So both should be same. Thanks, sanjeewa. On Wed, May 21, 2014 at 3:20 AM, Nirmal Fernando nir...@wso2.com wrote: Hi, In api-manager.xml, I've noticed $subject. Is this a bug? KeyValidatorClientTypeThriftClient/KeyValidatorClientType ThriftClientPort10397/ThriftClientPort ThriftClientConnectionTimeOut1/ThriftClientConnectionTimeOut ThriftServerPort10397/ThriftServerPort !--ThriftServerHostlocalhost/ThriftServerHost-- EnableThriftServertrue/EnableThriftServer -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Appfactory] BAM upgrade
Hi, I have updated the setup.conf to use BAM 2.4.1 by default. Regards, On Wed, May 21, 2014 at 9:22 AM, Dimuthu Leelarathne dimut...@wso2.comwrote: Hi Shamika, Setup scripts still refer to BAM 2.3.0. So in-effect BAM is not upgraded. thanks, dimuthu On Thu, Apr 24, 2014 at 6:31 PM, Shamika Ariyawansa sham...@wso2.comwrote: Hi all, BAM server in App Factory current installation is upgraded to BAM 2.4.1 RC3. Regards -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika*https://twitter.com/Amila_Shamika * linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika*https://twitter.com/Amila_Shamika *linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Artifact relavant to chunk-09 is missing in p2-repo
Hi BAM Team, I cannot find relevant features for chunk-09 release under [1]. Appreciate you guys can check. [1] http://dist.wso2.org/p2/carbon/releases/turing/ Thanks, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
