Re: [Dev] Error building carbon
Hi, I am using java 6 and I have tried with a clean repo build. I got the following error stack trace. [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2 publisher return code was 13 - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2 publisher return code was 13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher return code was 13 at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210) at org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 13 at org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255) at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204) ... 22 more Thanks, Nipuni On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando danush...@wso2.com wrote: Hi What is the java version you are using? Is it java 6 or java 7? If its 7 try with java 6. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera nip...@wso2.com wrote: Hi, [INFO] Reactor Summary: [INFO] [INFO] WSO2 Carbon Core - Distribution ... FAILURE [7:30.905s] [INFO] WSO2 Carbon - Integration . SKIPPED [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED [INFO] WSO2 Carbon - Integration Core SKIPPED [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED [INFO] WSO2 Carbon - Integration Tests ... SKIPPED [INFO] WSO2 Carbon - Product Parent .. SKIPPED [INFO] WSO2 Carbon - UI styles ... SKIPPED [INFO] WSO2 Carbon - Style Feature ... SKIPPED [INFO] WSO2 Carbon - Profile Generation .. SKIPPED [INFO] WSO2 Carbon - Distribution SKIPPED [INFO] Distribution-Aggregate SKIPPED [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7:32.532s [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014 [INFO] Final Memory: 33M/1217M [INFO] [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product (materialize-product) on project wso2carbon-core: Cannot generate P2 metadata: P2 publisher return code was 13 - [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
Re: [Dev] [Dev Studio] Adding In Out mediators within a sequence doesn't get saved
Hi Ishara, Developer Studio does not allow you to put In/Out mediators inside any arbitrary Sequence or any Proxy service. But if you create the main sequence using DevS, it will contain In/Out mediators because we definitely need In/Out mediators inside the main sequence. This limitation was introduced because it is almost impossible to represent the meaning of In/Out mediators inside a Sequence graphically. In/Out mediators represent in path and out path and we may need to divide sequence diagram into two parts to represent this forward and reverse message flow if we allow In/Out mediators. After discussing with ESB team, we decided not to support In/Out mediators for sequences except main sequence since users have alternatives to accomplish this. But I understand that there is a limitation in DevS according to the ESB config specification. You can use service chaining for your use case instead of In/Out mediators. Thanks, Viraj. On Fri, Jul 18, 2014 at 9:57 AM, Ishara Premadasa ish...@wso2.com wrote: Hi, When i add the below config inside a sequence.xml file in Developer Studio 3.7.0, once the file is saved and open the source view back, all the configs are wiped out. sequence xmlns=http://ws.apache.org/ns/synapse; name=TestSequence in log level=custom property name=seq in value=msg came to seq in/property /log send endpoint http method=post uri-template= http://localhost:9764/jaxrs_starbucks_service/services/Starbucks_Outlet_Service/orders/ /http /endpoint /send /in out log level=full property name=seq_out value=response came seq out mediator/property /log /out /sequence However when use ESB UI editor to create this config it is supported there. May i please know how to create In,Out mediators from Dev studio, as i have several sequences which invokes external API endpoints at the In and need to get the response into Out. Thanks! Ishara -- 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/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error building carbon
Hi Nipuni, Build with a clean Maven repo using Maven3. Thanks ! On Fri, Jul 18, 2014 at 11:51 AM, Harsha Kumara hars...@wso2.com wrote: Hi Nipuni, May be the maven version you using can be the issue here. What's your maven version? Thanks, Harsha On Fri, Jul 18, 2014 at 11:47 AM, Nipuni Perera nip...@wso2.com wrote: Hi, I am using java 6 and I have tried with a clean repo build. I got the following error stack trace. [ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2 publisher return code was 13 - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2 publisher return code was 13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher return code was 13 at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210) at org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher return code was 13 at org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255) at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204) ... 22 more Thanks, Nipuni On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando danush...@wso2.com wrote: Hi What is the java version you are using? Is it java 6 or java 7? If its 7 try with java 6. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera nip...@wso2.com wrote: Hi, [INFO] Reactor Summary: [INFO] [INFO] WSO2 Carbon Core - Distribution ... FAILURE [7:30.905s] [INFO] WSO2 Carbon - Integration . SKIPPED [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED [INFO] WSO2 Carbon - Integration Core SKIPPED [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED [INFO] WSO2 Carbon - Integration Tests ... SKIPPED [INFO] WSO2 Carbon - Product Parent .. SKIPPED [INFO] WSO2 Carbon - UI styles ... SKIPPED [INFO] WSO2 Carbon - Style Feature ... SKIPPED [INFO] WSO2 Carbon - Profile Generation .. SKIPPED [INFO] WSO2 Carbon - Distribution SKIPPED [INFO] Distribution-Aggregate SKIPPED [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 7:32.532s [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014 [INFO] Final Memory: 33M/1217M [INFO]
[Dev] Including identity.xml into the ES pack
Hi, Currently we keep a copy of identity.xml in ES source and pack it with the ES distribution. This causes to override the identity.xml file comes with IS [01], and we have to manually update the file to sync with IS. The reason we keep a local copy is that identity.xml file packed with IS does not contains commits[02][03] that we require for ES pack. What would be the best way to continue with managing this 'identity.xml' file. - commit the changes to IS /if it is OK to merge the changes[04] - continue with managing a copy and update manually - is there any other way to handle this? [01] https://wso2.org/jira/browse/STORE-472 [02] https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 [03] https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 [04] https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Including identity.xml into the ES pack
Hi, I think if you want to manage your own version of the such files the way to do it would be to keep your copy in a place like modules/distribution/src/main/resources/carbon-home/ in the ES and copy from there using the bin.xml. Overwriting the file added by the IS feature will cause problems to all the other products that tries to install your feature. Regards, Pulasthi On Fri, Jul 18, 2014 at 2:01 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Currently we keep a copy of identity.xml in ES source and pack it with the ES distribution. This causes to override the identity.xml file comes with IS [01], and we have to manually update the file to sync with IS. The reason we keep a local copy is that identity.xml file packed with IS does not contains commits[02][03] that we require for ES pack. What would be the best way to continue with managing this 'identity.xml' file. - commit the changes to IS /if it is OK to merge the changes[04] - continue with managing a copy and update manually - is there any other way to handle this? [01] https://wso2.org/jira/browse/STORE-472 [02] https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 [03] https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 [04] https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Cannot Install ES feature when building with greg-changes-master branch in ES
Hi , We cannot build the Greg pack when we use the greg-changes-master branch of ES. The product can be built without any errors with the 1.2.0 branch. But we cannot use the 1.2.0 branch currently because the fixes to stop the ES feature from overriding the RXT files are not merged to this branch. Can you please fix the greg-changes-master branch or update the 1.2.0 branch with the fixes. This is blocking the progress of the GReg 5.0.0 since we are still unable to properly install and use the store features. Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Including identity.xml into the ES pack
Adding SameeraM. @Pulasthi, According to the off-line discussion with Johann, we will be able to get rid of the local changes. or we can add changes to the identity.xml file during the build time. I am working on it. Thank you! On Fri, Jul 18, 2014 at 2:13 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi, I think if you want to manage your own version of the such files the way to do it would be to keep your copy in a place like modules/distribution/src/main/resources/carbon-home/ in the ES and copy from there using the bin.xml. Overwriting the file added by the IS feature will cause problems to all the other products that tries to install your feature. Regards, Pulasthi On Fri, Jul 18, 2014 at 2:01 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Currently we keep a copy of identity.xml in ES source and pack it with the ES distribution. This causes to override the identity.xml file comes with IS [01], and we have to manually update the file to sync with IS. The reason we keep a local copy is that identity.xml file packed with IS does not contains commits[02][03] that we require for ES pack. What would be the best way to continue with managing this 'identity.xml' file. - commit the changes to IS /if it is OK to merge the changes[04] - continue with managing a copy and update manually - is there any other way to handle this? [01] https://wso2.org/jira/browse/STORE-472 [02] https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 [03] https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 [04] https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Including identity.xml into the ES pack
AFAIK these two properties are also used in IS. DefaultSAMLSSOSigner is a identity class. So as the name suggests it should be the default and we also should be using the same. There should be no need for changing this property if it not different from IS. UserAuthenticatedUserDomainCrypto property was added in chunk-11 release for backward compatibility with saml2 sso aauthenticators. Default is false. So if you are using the saml2 sso authenticators from chunk-11 release or after you should be able to have it as false. However if you have some differences and need to change these values it is recommended that you change these values during the product build time and not by having a separate file. Check in IS product modules/distribution/pom.xml as to how we modify the carbon.xml that comes from kernel to change the HostName and MgtHostName. But ideally I don't think you will need it. Regards, Johann. On Fri, Jul 18, 2014 at 2:01 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Currently we keep a copy of identity.xml in ES source and pack it with the ES distribution. This causes to override the identity.xml file comes with IS [01], and we have to manually update the file to sync with IS. The reason we keep a local copy is that identity.xml file packed with IS does not contains commits[02][03] that we require for ES pack. What would be the best way to continue with managing this 'identity.xml' file. - commit the changes to IS /if it is OK to merge the changes[04] - continue with managing a copy and update manually - is there any other way to handle this? [01] https://wso2.org/jira/browse/STORE-472 [02] https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 [03] https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 [04] https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- Thanks Regards, *Johann Dilantha Nallathamby* Associate Technical Lead Product Lead of WSO2 Identity Server Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Including identity.xml into the ES pack
Hi, Ok, That would be better, Regards, Pulasthi On Fri, Jul 18, 2014 at 2:29 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Adding SameeraM. @Pulasthi, According to the off-line discussion with Johann, we will be able to get rid of the local changes. or we can add changes to the identity.xml file during the build time. I am working on it. Thank you! On Fri, Jul 18, 2014 at 2:13 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi, I think if you want to manage your own version of the such files the way to do it would be to keep your copy in a place like modules/distribution/src/main/resources/carbon-home/ in the ES and copy from there using the bin.xml. Overwriting the file added by the IS feature will cause problems to all the other products that tries to install your feature. Regards, Pulasthi On Fri, Jul 18, 2014 at 2:01 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Currently we keep a copy of identity.xml in ES source and pack it with the ES distribution. This causes to override the identity.xml file comes with IS [01], and we have to manually update the file to sync with IS. The reason we keep a local copy is that identity.xml file packed with IS does not contains commits[02][03] that we require for ES pack. What would be the best way to continue with managing this 'identity.xml' file. - commit the changes to IS /if it is OK to merge the changes[04] - continue with managing a copy and update manually - is there any other way to handle this? [01] https://wso2.org/jira/browse/STORE-472 [02] https://github.com/wso2/enterprise-store/commit/74d33514bc3078e9bd8794f32eaf46978ab044b1 [03] https://github.com/wso2/enterprise-store/commit/1062d2ae349206cc5190a450a1a1c8d0324b9ee8 [04] https://github.com/wso2/enterprise-store/commits/1.2.0/modules/distribution/src/repository/conf/identity.xml -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot Install ES feature when building with greg-changes-master branch in ES
Adding to this, When we had the GReg 5.0.0 pack built with 1.2.0 branch, we couldn't access the publisher or get into the sign in page of store. When clicked on the publisher HTTP Status 405 - HTTP method POST is not supported by this URL is shown. @SameeraM : Further in a fresh ES 1.2.0-SNAPSHOT pack I could add a service from the management console. But after that I can't add a service from the publisher service UI. When I clicked the Add Service button, the add service view is not displayed and following error is shown. HTTP Status 500 - org.mozilla.javascript.WrappedException: Wrapped org.jaggeryjs.scriptengine.exceptions.ScriptException: org.mozilla.javascript.EcmaError: TypeError: Cannot read property overview_pr overview_provider from undefined (asset#15) (/publisher/controllers/ref_assets_router.jag#54) Am I missing out something here? ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ESB Build Error in resolving org.apache.ws.security.wss4j.1.5.11-wso2v6.jar
Hi, I was getting a maven error for resolving the following when building the ESB from the source. File : 'carbon/platform/tags/turing-chunk07/products/esb/4.8.1/modules/integration/core/pom.xml' dependency groupIdorg.apache.ws.security/groupId artifactIdwss4j/artifactId version1.5.11-wso2v6/version /dependency This dependency is not there in the maven repository but is available in the org.apache.ws.security.wso2 package. So after changing the pom file at 'carbon/platform/tags/turing-chunk07/products/esb/4.8.1/modules/integration/core/pom.xml' to the following I was able to go pass this. dependency groupIdorg.apache.ws.security.wso2/groupId artifactIdwss4j/artifactId version1.5.11.wso2v6/version /dependency Are these the same jars? The name is also different (1.5.11-wso2v6 vs 1.5.11.wso2v6). If so it looks like the pom file needs to change? -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] What is the impact of following WARN message in ELB
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Moving Social component from ES to carbon-??
Hi all, At the moment social-component resides within the ES product[1]. We (Manu, KasunG and me) had a off-line discussion on the $Subject. Thought of sharing the out-come here. Move current social component to a separate repo(eg :- carbon-social). But right now most(not sure this is most or all) of the products do have a separate repo other than the product repo to maintain product specific components. Eg:- product-bam/ carbon-analytics, product-as/ carbon-deployment Can we apply the same model to the ES product as well? So in that case we can't use a specific name like social to name this repo.(carbon-social) Component Version - Found that we have already version-ed our components using the same Carbon Platform Version. Is this model correct? How are we going to release individual components in future? [1] https://github.com/wso2/enterprise-store/tree/master/modules/components/social Regards, UdaraR -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot Install ES feature when building with greg-changes-master branch in ES
Done On Fri, Jul 18, 2014 at 3:11 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Merge pull request from [01] to greg-changes-master. It will resolve the build failure. [01] https://github.com/wso2/enterprise-store/pull/116 On Fri, Jul 18, 2014 at 2:23 PM, Pulasthi Supun pulas...@wso2.com wrote: Hi , We cannot build the Greg pack when we use the greg-changes-master branch of ES. The product can be built without any errors with the 1.2.0 branch. But we cannot use the 1.2.0 branch currently because the fixes to stop the ES feature from overriding the RXT files are not merged to this branch. Can you please fix the greg-changes-master branch or update the 1.2.0 branch with the fixes. This is blocking the progress of the GReg 5.0.0 since we are still unable to properly install and use the store features. Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the impact of following WARN message in ELB
Hi Amila,
This means ELB has received a request form the client but it hasn't sent a
response back to the client within the socket timeout period.
On Fri, Jul 18, 2014 at 3:06 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the impact of following WARN message in ELB
Thanks Isuru.
So, this means something is wrong, right? Does the client retries in this
kind of a situation?
On Fri, Jul 18, 2014 at 3:14 PM, Isuru Udana isu...@wso2.com wrote:
Hi Amila,
This means ELB has received a request form the client but it hasn't sent a
response back to the client within the socket timeout period.
On Fri, Jul 18, 2014 at 3:06 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the impact of following WARN message in ELB
In a cloud like environment, may be we need to increase the socket timeout
a bit too.
On Fri, Jul 18, 2014 at 3:22 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
Thanks Isuru.
So, this means something is wrong, right? Does the client retries in this
kind of a situation?
On Fri, Jul 18, 2014 at 3:14 PM, Isuru Udana isu...@wso2.com wrote:
Hi Amila,
This means ELB has received a request form the client but it hasn't sent
a response back to the client within the socket timeout period.
On Fri, Jul 18, 2014 at 3:06 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
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
Re: [Dev] What is the impact of following WARN message in ELB
On Fri, Jul 18, 2014 at 3:28 PM, Nirmal Fernando nir...@wso2.com wrote:
In a cloud like environment, may be we need to increase the socket timeout
a bit too.
On Fri, Jul 18, 2014 at 3:22 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
Thanks Isuru.
So, this means something is wrong, right?
IMO, In a cloud environment, few random connections timeouts, connections
closes are normal to have as different clients accessing this environment.
But it is a problem if you see this so often.
Does the client retries in this kind of a situation?
That's depends on the client.
On Fri, Jul 18, 2014 at 3:14 PM, Isuru Udana isu...@wso2.com wrote:
Hi Amila,
This means ELB has received a request form the client but it hasn't sent
a response back to the client within the socket timeout period.
On Fri, Jul 18, 2014 at 3:06 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Build Error in resolving org.apache.ws.security.wss4j.1.5.11-wso2v6.jar
Hi Darshana, The bundle with group id org.apache.ws.security comes from [1] which is the wso2 fork of wss4j. It is then bundled at orbit [2] adding xmlsec and bouncycastle with group id org.apache.ws.security.wso2. The bundle from the orbit (which has group id org.apache.ws.security.wso2) is the correct one to use. [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/wss4j/1.5.11-wso2v6/ [2] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/orbit/wss4j/ On Fri, Jul 18, 2014 at 2:56 PM, Darshana Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi, I was getting a maven error for resolving the following when building the ESB from the source. File : 'carbon/platform/tags/turing-chunk07/products/esb/4.8.1/modules/integration/core/pom.xml' dependency groupIdorg.apache.ws.security/groupId artifactIdwss4j/artifactId version1.5.11-wso2v6/version /dependency This dependency is not there in the maven repository but is available in the org.apache.ws.security.wso2 package. So after changing the pom file at 'carbon/platform/tags/turing-chunk07/products/esb/4.8.1/modules/integration/core/pom.xml' to the following I was able to go pass this. dependency groupIdorg.apache.ws.security.wso2/groupId artifactIdwss4j/artifactId version1.5.11.wso2v6/version /dependency Are these the same jars? The name is also different (1.5.11-wso2v6 vs 1.5.11.wso2v6). If so it looks like the pom file needs to change? -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pulasthi Mahawithana* Software Engineer WSO2 Inc., http://wso2.com/ Mobile: +94-71-5179022 Blog: http://blog.pulasthi.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What is the impact of following WARN message in ELB
I see this log very often in ELB.
TID: [0] [ELB] [2014-07-18 03:41:42,450] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-8841
{org.apache.synapse.transport.passthru.SourceHandler}
TID: [0] [ELB] [2014-07-18 03:41:42,450] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-8841
{org.apache.synapse.transport.passthru.SourceHandler}
TID: [0] [ELB] [2014-07-18 03:41:43,213] INFO
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -
Failed over to Host:x.x.x.x, Remote Host:null, Port: 4000, HTTP:9763,
HTTPS:9443, Domain: wso2.xxx.domain, Sub-domain:mgt, Active:true
{org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}
TID: [0] [ELB] [2014-07-18 04:15:12,253] WARN
{org.apache.synapse.transport.passthru.TargetHandler} - http-outgoing-217:
Connection time out while in state: REQUEST_DONE
{org.apache.synapse.transport.passthru.TargetHandler}
TID: [0] [ELB] [2014-07-18 04:15:12,253] WARN
{org.apache.synapse.transport.passthru.TargetHandler} - http-outgoing-217:
Connection time out while in state: REQUEST_DONE
{org.apache.synapse.transport.passthru.TargetHandler}
TID: [0] [ELB] [2014-07-18 04:15:12,254] WARN
{SERVICE_LOGGER.__SynapseService} - ERROR_CODE : 101507 ERROR_MESSAGE :
Error in Sender {SERVICE_LOGGER.__SynapseService}
TID: [0] [ELB] [2014-07-18 04:15:12,254] WARN
{org.apache.synapse.endpoints.EndpointContext} - Endpoint :
DLB:x.x.x.x:4000:52e71693-f9fb-451b-b44b-d2e295abb9e2 will be marked
SUSPENDED as it failed {org.apache.synapse.endpoints.EndpointContext}
TID: [0] [ELB] [2014-07-18 04:15:12,254] WARN
{org.apache.synapse.endpoints.EndpointContext} - Endpoint :
DLB:x.x.x.x:4000:52e71693-f9fb-451b-b44b-d2e295abb9e2 will be marked
SUSPENDED as it failed {org.apache.synapse.endpoints.EndpointContext}
TID: [0] [ELB] [2014-07-18 04:15:12,254] WARN
{org.apache.synapse.endpoints.EndpointContext} - Suspending endpoint :
DLB:x.x.x.x:4000:52e71693-f9fb-451b-b44b-d2e295abb9e2 - current suspend
duration is : 3ms - Next retry after : Fri Jul 18 04:15:42 PDT 2014
{org.apache.synapse.endpoints.EndpointContext}
TID: [0] [ELB] [2014-07-18 04:15:12,254] WARN
{org.apache.synapse.endpoints.EndpointContext} - Suspending endpoint :
DLB:x.x.x.x:4000:52e71693-f9fb-451b-b44b-d2e295abb9e2 - current suspend
duration is : 3ms - Next retry after : Fri Jul 18 04:15:42 PDT 2014
{org.apache.synapse.endpoints.EndpointContext}
TID: [0] [ELB] [2014-07-18 04:15:12,254] INFO
{SERVICE_LOGGER.__SynapseService} - FaultHandler executing impl:
org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint$TenantDynamicLoadBalanceFaultHandlerImpl
{SERVICE_LOGGER.__SynapseService}
On Fri, Jul 18, 2014 at 3:47 PM, Isuru Udana isu...@wso2.com wrote:
On Fri, Jul 18, 2014 at 3:28 PM, Nirmal Fernando nir...@wso2.com wrote:
In a cloud like environment, may be we need to increase the socket
timeout a bit too.
On Fri, Jul 18, 2014 at 3:22 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
Thanks Isuru.
So, this means something is wrong, right?
IMO, In a cloud environment, few random connections timeouts, connections
closes are normal to have as different clients accessing this environment.
But it is a problem if you see this so often.
Does the client retries in this kind of a situation?
That's depends on the client.
On Fri, Jul 18, 2014 at 3:14 PM, Isuru Udana isu...@wso2.com wrote:
Hi Amila,
This means ELB has received a request form the client but it hasn't
sent a response back to the client within the socket timeout period.
On Fri, Jul 18, 2014 at 3:06 PM, Amila Maha Arachchi ami...@wso2.com
wrote:
TID: [0] [ELB] [2014-07-18 02:36:08,248] WARN
{org.apache.synapse.transport.passthru.SourceHandler} - Connection time
out after request is read: http-incoming-470
{org.apache.synapse.transport.passthru.SourceHandler}
Can I know $Subject?
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
*Isuru Udana*
Senior
* Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile:
[Dev] WSO2 AppFactory 2.0.1 Milestone 2 Released!
WSO2 AppFactory 2.0.1 Milestone 2 Released! WSO2 AppFactory team is pleased to announce the release of version 2.0.1 M2 of the WSO2 App Factory. WSO2 App Factory is a multi-tenant, elastic and self-service enterprise platform that enables multiple project teams to collaboratively create, run and manage enterprise applications. Combining complete application lifecycle management and Platform-as-a-Service (PaaS) capabilities, WSO2 App Factory makes it possible to develop, test, deploy to production and retire applications with a single click. It also provides an easy way to discover and consume apps and APIs through a user-friendly storefront. The distribution is available to download at [1] . Bug fixes in this release can be found at [2]. Puppet manifests for App Factory can be found at [3]. We encourage you to report issues, documentation faults and feature requests regarding WSO2 AppFactory through the public WSO2 AppFactory JIRA https://wso2.org/jira/browse/APPFAC. [1] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.0.1-M2/pack/wso2appfactory-2.0.1.zip [2] https://wso2.org/jira/secure/IssueNavigator.jspa?reset= truejqlQuery=project+%3D+APPFAC+AND+fixVersion+%3D+% 222.0.1-M2%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide [3] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.0.1-M2/appfactory_2.0.0/products/appfactory/2.0.0/modules/puppet-manifests/ -- WSO2 AppFactory Team -- Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Governance API for adding WADL
Hello, I want to add WADL file using Governance APIs present in GREG like how we add Wsdl using WsdlManager and Wsdl classes.I couldn't find such classes for WADLs. Can anyone please let me know which classes in GREG are used to add WADL in the GREG. Please share samples if there are any, Best regards, Arshia Nishath Contact: 630-613-0702 CI/WB-NA Robert Bosch Tool Co-orporation ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] using the visiblewhen tag in contextualizing the new option for dec_studio projects
Hi, On Fri, Jul 18, 2014 at 10:57 AM, Awanthika Senarath awanth...@wso2.com wrote: Hi, Im trying to contextualize the eclipse new project option in project (in projectExplorer) - rightclick - new - wso2projects (CEP project/ proxy service etc.) to make it more meaningful. I have been trying with the visiblewhen tag inside the extensionpoint=org.eclipse.ui.newWizards filtering by project nature in plugin.xml with no success. AFAIK, org.eclipse.ui.newWizards extension-point does not supports visibleWhen or activeWhen attributes. you can use org.eclipse.ui.navigator.navigatorContent extension point to achieve your requirements I guess. we are using it in many places inside DevS. please refer org.wso2.developerstudio.eclipse.artifact.axis2 component's plugin.xml [1] for a example. e.g. extension point=org.eclipse.ui.navigator.navigatorContent commonWizard type=new menuGroupId=1org.wso2.developerstudio.eclipse.artifact.webservice1 wizardId=org.wso2.developerstudio.eclipse.artifact.axis2.ui.wizard enablement or adapt type=org.eclipse.core.resources.IProject test property=org.eclipse.core.resources.projectNature value=org.wso2.developerstudio.eclipse.axis2.project.nature / /adapt adapt type=org.eclipse.jdt.core.IPackageFragment test property=org.wso2.developerstudio.projectNature value=org.wso2.developerstudio.eclipse.axis2.project.nature / /adapt /or /enablement /commonWizard /extension Thanks, Melan [1] https://github.com/wso2-dev/developer-studio/blob/master/app-server/org.wso2.developerstudio.eclipse.artifact.axis2/plugin.xml is there anyone who has previous experience in using this tag? OR any other way of getting it done? I also tried with the property-tester in eclipse. thanks and regards -- Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Melan Nimesh* Software Engineer; WSO2 Inc.; http://wso2.org E-mail: melan AT wso2.com; Mobile: +94 77 631 6759 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Inbound EP VFS Transport with WSO2 MB
Hi, I tried to integrate $subject. inboundEndpoint xmlns=http://ws.apache.org/ns/synapse; name=MB interval=5000 sequence=request onError=fault protocol=jms suspend=false parameters parameter name=transport.jms.SessionAcknowledgementSESSION_TRANSACTED/parameter parameter name=java.naming.factory.initialorg.wso2.andes.jndi.PropertiesFileInitialContextFactory/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueConnectionFactory/parameter parameter name=transport.jms.Passwordadmin/parameter parameter name=java.naming.provider.urlrepository/conf/jndi.properties/parameter parameter name=transport.jms.ConnectionFactoryTypequeue/parameter parameter name=transport.jms.UserNameadmin/parameter parameter name=transport.jms.DestinationResponseStore_Queue/parameter parameter name=transport.jms.CacheLevel5/parameter /parameters /inboundEndpoint I got the [2] error for the above configuration. However starting the esb 490 with [1] (suggested by HasithaH) seems to fix the issue. Is this the correct way to do this? This works well with current axis2 jms(481 without param). Did we miss anything for inbound implementation? [1] -Dqpid.dest_syntax=BURL [2] error [2014-07-18 23:06:44,759] ERROR - JMSConnectionFactory Created 'ResponseStore_Queue' on connection factory for 'QueueConnectionFactory'. [2014-07-18 23:06:44,768] ERROR - JMSPollingConsumer Error while receiving JMS message. The new addressing based sytanx is not supported for AMQP 0-8/0-9 versions java.lang.UnsupportedOperationException: The new addressing based sytanx is not supported for AMQP 0-8/0-9 versions at org.wso2.andes.client.AMQSession_0_8.handleAddressBasedDestination(AMQSession_0_8.java:577) at org.wso2.andes.client.AMQSession.registerConsumer(AMQSession.java:2875) at org.wso2.andes.client.AMQSession.access$500(AMQSession.java:109) at org.wso2.andes.client.AMQSession$5.execute(AMQSession.java:2068) at org.wso2.andes.client.AMQSession$5.execute(AMQSession.java:2034) at org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315) at org.wso2.andes.client.AMQConnection.executeRetrySupport(AMQConnection.java:621) at org.wso2.andes.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102) at org.wso2.andes.client.AMQSession.createConsumerImpl(AMQSession.java:2032) at org.wso2.andes.client.AMQSession.createConsumer(AMQSession.java:1019) at org.apache.synapse.protocol.jms.factory.JMSConnectionFactory.createMessageConsumer(JMSConnectionFactory.java:275) at org.apache.synapse.protocol.jms.factory.CachedJMSConnectionFactory.createMessageConsumer(CachedJMSConnectionFactory.java:117) at org.apache.synapse.protocol.jms.factory.CachedJMSConnectionFactory.getMessageConsumer(CachedJMSConnectionFactory.java:109) at org.apache.synapse.protocol.jms.JMSPollingConsumer.poll(JMSPollingConsumer.java:92) at org.apache.synapse.protocol.jms.JMSPollingConsumer.execute(JMSPollingConsumer.java:63) at org.apache.synapse.protocol.jms.JMSTask.execute(JMSTask.java:21) at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:73) at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) [2014-07-18 23:06:44,787] INFO - CarbonUIServiceComponent Mgt Console URL : https://192.168.17.101:9443/carbon/ [2014-07-18 23:06:54,402] ERROR - JMSConnectionFactory JMS Exception while creating consumer. Object org.wso2.andes.client.AMQSession_0_8@770cfd02 has been closed [2014-07-18 23:06:54,402] ERROR - JMSPollingConsumer Error while receiving JMS message. null java.lang.NullPointerException at org.apache.synapse.protocol.jms.JMSPollingConsumer.poll(JMSPollingConsumer.java:93) at org.apache.synapse.protocol.jms.JMSPollingConsumer.execute(JMSPollingConsumer.java:63) at org.apache.synapse.protocol.jms.JMSTask.execute(JMSTask.java:21) at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:73) at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at
Re: [Dev] Inbound EP Memory Issue (File)
Look at the strange behavior at 21.43 :$ On Friday, July 18, 2014, Malaka Silva mal...@wso2.com wrote: Hi Guys, I ran a load test with 10 File EPs. There heap seems to be increase over time slightly. I am checking this by doing changes. Any ideas? Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Sent from Gmail Mobile ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving Social component from ES to carbon-??
Hi Udara, On Fri, Jul 18, 2014 at 3:15 PM, Udara Rathnayake uda...@wso2.com wrote: Hi all, At the moment social-component resides within the ES product[1]. We (Manu, KasunG and me) had a off-line discussion on the $Subject. Thought of sharing the out-come here. Move current social component to a separate repo(eg :- carbon-social). But right now most(not sure this is most or all) of the products do have a separate repo other than the product repo to maintain product specific components. Eg:- product-bam/ carbon-analytics, product-as/ carbon-deployment Can we apply the same model to the ES product as well? +1. Please come with meaningful names for your component repo. So in that case we can't use a specific name like social to name this repo.(carbon-social) Component Version - Found that we have already version-ed our components using the same Carbon Platform Version. Is this model correct? How are we going to release individual components in future? We start the component versions in GIT with 4.3.0. The repos will diverge and will have their own versions after the first release. We cannot start from a lower version number because of osgi version range requirements. Regards, KasunG [1] https://github.com/wso2/enterprise-store/tree/master/modules/components/social Regards, UdaraR -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *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
[Dev] Start-up Delay with App-M Snapshot
Hi Ruwan, Is this a temporary thing? I noticed that the server waits for sometime before starting. Thanks, Senaka. -- *[image: http://wso2.com] http://wso2.comSenaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Start-up Delay with App-M Snapshot
Hi Senaka, We noticed this problem with earlier nightly builds. However I did not notice such delays in the pack I shared yesterday (@ [1]). I believe this might be partly due to all the kernel patches given so far not being added to the pack (we have only till about patch0004 I think). Will investigate further on this. Thanks, Ruwan - sent from my mobile [1] - http://builder1.us1.wso2.org/~appm/18-07-2014/wso2appmanager-1.0.0.zip On 19 Jul 2014 04:27, Senaka Fernando sen...@wso2.com wrote: Hi Ruwan, Is this a temporary thing? I noticed that the server waits for sometime before starting. Thanks, Senaka. -- *[image: http://wso2.com] http://wso2.comSenaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] wso2server.sh script does not stop the server when ssh terminates
Hi, I am working on jira issue[1]. I have tested this with a remote BAM server and couldn't reproduce the issue. If wso2server.sh has been executed over ssh as a nohup process, server does not stop after ssh process terminates. I have followed the steps below: 1. start ssh and connect to remote serrver : ssh -i private-key server-name -p password 2. start wso2server as a background process : sudo -E ./wso2server.sh start (this gives an error ps: write error: Bad file descriptor but server starts successfully 3. exit from the remote server and stop ssh 4. I can access server after ssh is stopped. I have tested it starting wso2server as a nohup process : nohup sudo -E ./wso2server.sh (This also works after ssh terminates) [1] https://wso2.org/jira/browse/CARBON-14813 Thanks, Nipuni -- Nipuni Perera Software Engineer; WSO2 Inc.; http://wso2.com Email: nip...@wso2.com Git hub profile: https://github.com/nipuni Mobile: +94 (71) 5626680 http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
