[Dev] Shall we remove the WS-AddressingEndpoint from Endpoint Tool Pallet in DevStudio?
Hi All, I think we $Subject because now that Send mediator is embedding the endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty Send mediator indicates the WS-Addressing scenario just like in the Mgt Console. So I'm proposing $Subject. WDYT? Thanks and Regards, Harshana -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AM] Unable to install Key Manager (APIM) features in IS 4.6.0
Hi Sumedha, It seems that the hosted p2-repo has an incorrect jar. Checked with p2-repo in builder machine [1] and the hosted one and it seems there is a difference. (The p2-repo in builder machine has correct md5sum for the relevant jar) Guess we would have to re-host the p2-repo. For now, maybe you can use the p2-repo from the builder machine[1] as a temporary workaround? [1] http://107.22.190.5/chunk-06/RC3/p2-repo/ Thanks, Lasantha On 4 January 2014 11:28, Kishanthan Thangarajah kishant...@wso2.com wrote: Can you check whether those jars were downloaded correctly / they are not corrupted ones? On Sat, Jan 4, 2014 at 2:55 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi all, The reason is a mismatch of md5sum of two jars [1]. The md5 sums of these jars are different from the ones defined in the artifacts.xml [2]. What is the correct resolution for this issue..? [1] Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.client,1.2.0. MD5 hash is not as expected. Expected: c80993a541f5cd4a356b2da69edefc90 and found 442b547c177c4206e34d028c81980466. Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.publisher,1.2.0. MD5 hash is not as expected. Expected: dfcae32b8615ed989843a8f130ceb154 and found 8f07a81607f348c1485f7cef08a4a1cb. [2] artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.client' version='1.2.0' properties size='3' property name='artifact.size' value='57002'/ property name='download.size' value='57002'/ property name='download.md5' value='c80993a541f5cd4a356b2da69edefc90'/ /properties /artifact artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.publisher' version='1.2.0' properties size='3' property name='artifact.size' value='40455'/ property name='download.size' value='40455'/ property name='download.md5' value='dfcae32b8615ed989843a8f130ceb154'/ /properties /artifact Thanks SumeddhaS On Thu, Jan 2, 2014 at 10:36 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi all, $subject. I tried to install features using [1] but I get the attached exception. Any idea on this..? [1] http://dist.wso2.org/p2/carbon/releases/turing/ Thanks SumedhaS -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: CEP 3.0.0 download link
I'm trying to write a script to download and setup CEP 3.0.0. Where can I find the direct download link for CEP 3.0.0? CEP 3.0.0 isn't available here: http://dist.wso2.org/downloads/ I've tried using CEP 3.0.0 from the maven repo: http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/cep/wso2cep/3.0.0/wso2cep-3.0.0.zip However, version 3.0.0 from the maven site throws a load of startup errors, which don't occur with version 3.0.0 that I manually downloaded from http://wso2.com/products/complex-event-processor/ Many thanks, Chris ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk07 - BUILD FAILURE - (ode.wso2)
Hi Nandika, Sure I'll check and confirm asap. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Sat, Jan 4, 2014 at 1:48 AM, Nandika Jayawardana nand...@wso2.comwrote: Hi Isuru, Updated the ui feature to use new version of ode. @Amal, Can you update nexus with ode dependencies released with chunk05. Seems like the nexus deployment is not complete. Also check the other stuff released in chunk05 to make sure that everything is deployed properly. Regards Nandika On Fri, Jan 3, 2014 at 3:04 PM, Isuru Udana isu...@wso2.com wrote: Hi Nandika, I am getting this when building chunk-07 [INFO] [INFO] Total time: 3:56.843s [INFO] Finished at: Fri Jan 03 13:55:08 IST 2014 [INFO] Final Memory: 587M/972M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.bpel.ui.feature: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.bpel.ui.feature:pom:4.2.1: The following artifacts could not be resolved: org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-wso2v10, org.wso2.bpel:ode-dao-hibernate-db:jar:1.3.5-wso2v10: Failure to find org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-wso2v10 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced - [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. It looks to me ode 1.3.5-wso2v10[1] is not deployed to nexus yet even though it is released in chunk-05[2]. We also can update org.wso2.carbon.bpel.ui.feature 4.2.1 feature to use latest ode version (1.3.5-wso2v11) to fix this build issue. [1] http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/bpel/ode/ [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/product-releases/chunk-05/dependencies/pom.xml Thanks. On Fri, Jan 3, 2014 at 1:25 PM, Malaka Silva mal...@wso2.com wrote: Thx Nandika. Sure will do On Fri, Jan 3, 2014 at 1:11 PM, Nandika Jayawardana nand...@wso2.comwrote: Hi Malaka, Actually, the issue was due to corrupted jar. Now the chunk07 is building fine. Can you check whether the bps build issue is fixed now. Regards Nandika On Fri, Jan 3, 2014 at 1:06 PM, Nandika Jayawardana nand...@wso2.comwrote: I am getting the following build error when building chunk07. Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-feature-gen (4-p2-feature-generation) on project org.apache.synapse.wso2.feature: Bundle-SymbolicName cannot be found in the bundle: /home/nandika/software/repo/org/wso2/throttle/wso2throttle-core/3.3.0/wso2throttle-core-3.3.0.jar Regards Nandika On Fri, Jan 3, 2014 at 12:06 PM, Nandika Jayawardana nand...@wso2.com wrote: Sure, Will do. Regards Nandika On Fri, Jan 3, 2014 at 12:00 PM, Malaka Silva mal...@wso2.comwrote: Hi Guys, After manually building the following error is gone. turing/dependencies/ode/1.3.5-wso2v10 However still the chunk07 fails due to bps/3.2.0. Please check. Thank you. On Thu, Jan 2, 2014 at 4:25 PM, Malaka Silva mal...@wso2.comwrote: I'm getting the following error while building the chunk07. [ERROR] Failed to execute goal on project ode: Could not resolve dependencies for project org.apache.ode.wso2:ode:bundle:1.3.5.wso2v11: The following artifacts could not be resolved: org.wso2.bpel:ode-axis2:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-api-jca:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-api:jar:1.3.5-wso2v10, org.wso2.bpel:ode-scheduler-simple:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-compiler:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-connector:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-dao:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-ql:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-schemas:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-store:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-runtime:jar:1.3.5-wso2v10, org.wso2.bpel:ode-dao-jpa:jar:1.3.5-wso2v10, org.wso2.bpel:ode-jacob:jar:1.3.5-wso2v10, org.wso2.bpel:ode-jca-ra:jar:1.3.5-wso2v10, org.wso2.bpel:ode-jca-server:jar:1.3.5-wso2v10, org.wso2.bpel:ode-utils:jar:1.3.5-wso2v10, org.wso2.bpel:ode-agents:jar:1.3.5-wso2v10, org.wso2.bpel:ode-dao-hibernate:jar:1.3.5-wso2v10, org.wso2.bpel:ode-dao-hibernate-db:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-obj:jar:1.3.5-wso2v10, org.wso2.bpel:ode-bpel-epr:jar:1.3.5-wso2v10, org.wso2.bpel.extensions:ode-bpel-extensions-e4x:jar:1.0.0-wso2v10, org.wso2.bpel.extensions:ode-bpel-extensions-long-running:jar:1.0.0-wso2v10: Failure to find org.wso2.bpel:ode-axis2:jar:1.3.5-wso2v10 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was
Re: [Dev] [AM] Unable to install Key Manager (APIM) features in IS 4.6.0
Hi Lasantha, Yes, It worked. @Ruwan, There is another issue related to APIM. When installing features it shows APIM as 1.5.0 and I think it should be 1.6.0. Also the jars installed by the key manager feature are older versions (checked only with Key Manager). That is the versions of jars related to APIM are not the ones released with APIM 1.6.0. Please have a look at this. Thanks SumedhaS On Sun, Jan 5, 2014 at 8:53 AM, Lasantha Fernando lasan...@wso2.com wrote: Hi Sumedha, It seems that the hosted p2-repo has an incorrect jar. Checked with p2-repo in builder machine [1] and the hosted one and it seems there is a difference. (The p2-repo in builder machine has correct md5sum for the relevant jar) Guess we would have to re-host the p2-repo. For now, maybe you can use the p2-repo from the builder machine[1] as a temporary workaround? [1] http://107.22.190.5/chunk-06/RC3/p2-repo/ Thanks, Lasantha On 4 January 2014 11:28, Kishanthan Thangarajah kishant...@wso2.comwrote: Can you check whether those jars were downloaded correctly / they are not corrupted ones? On Sat, Jan 4, 2014 at 2:55 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi all, The reason is a mismatch of md5sum of two jars [1]. The md5 sums of these jars are different from the ones defined in the artifacts.xml [2]. What is the correct resolution for this issue..? [1] Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.client,1.2.0. MD5 hash is not as expected. Expected: c80993a541f5cd4a356b2da69edefc90 and found 442b547c177c4206e34d028c81980466. Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.publisher,1.2.0. MD5 hash is not as expected. Expected: dfcae32b8615ed989843a8f130ceb154 and found 8f07a81607f348c1485f7cef08a4a1cb. [2] artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.client' version='1.2.0' properties size='3' property name='artifact.size' value='57002'/ property name='download.size' value='57002'/ property name='download.md5' value='c80993a541f5cd4a356b2da69edefc90'/ /properties /artifact artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.publisher' version='1.2.0' properties size='3' property name='artifact.size' value='40455'/ property name='download.size' value='40455'/ property name='download.md5' value='dfcae32b8615ed989843a8f130ceb154'/ /properties /artifact Thanks SumeddhaS On Thu, Jan 2, 2014 at 10:36 AM, Sumedha Kodithuwakku sumed...@wso2.com wrote: Hi all, $subject. I tried to install features using [1] but I get the attached exception. Any idea on this..? [1] http://dist.wso2.org/p2/carbon/releases/turing/ Thanks SumedhaS -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += SumedhaS
Congrats Sumedha ! On Sun, Jan 5, 2014 at 9:22 AM, Gokul Balakrishnan go...@wso2.com wrote: Congrats Sumedha!! On 3 January 2014 13:58, Amila Maha Arachchi ami...@wso2.com wrote: Hi All, It's my pleasure to welcome Sumedha Kodithuwakku as a WSO2 Committer. SumedhaS has been a valuable contributor to the Cloud team during the last few months. He worked on the Cloud Preview deployment and also developed the HeartBeat tool for it. In addition to that he has worked on many other Cloud related development work. In recognition of his contributions, SumedhaS has been voted as a WSO2 committer. SumedhaS, Welcome aboard and keep up the good work! Regards, AmilaM. -- *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 -- *Balakrishnan Gokulakrishnan* Software Engineer, WSO2, Inc.; http://wso2.com Tel: 0094 11 214 5345 | Fax: 0094 11 214 5300 Twitter: http://twitter.com/gokulbs Mobile: 0094 77 593 5789 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- 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] [AM] Unable to install Key Manager (APIM) features in IS 4.6.0
Hi Sumedha, There was a issue with the nested categories. I did a fix locally and re-compiled a feature repo on the builder machine. Please try with the link @ [1], You will be able to see the latest Jars listed under the API Manager 1.6.0 category. [1] - http://107.22.190.5/chunk-06_POSTMORTEM/p2-repo/ Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Mon, Jan 6, 2014 at 3:03 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi Lasantha, Yes, It worked. @Ruwan, There is another issue related to APIM. When installing features it shows APIM as 1.5.0 and I think it should be 1.6.0. Also the jars installed by the key manager feature are older versions (checked only with Key Manager). That is the versions of jars related to APIM are not the ones released with APIM 1.6.0. Please have a look at this. Thanks SumedhaS On Sun, Jan 5, 2014 at 8:53 AM, Lasantha Fernando lasan...@wso2.comwrote: Hi Sumedha, It seems that the hosted p2-repo has an incorrect jar. Checked with p2-repo in builder machine [1] and the hosted one and it seems there is a difference. (The p2-repo in builder machine has correct md5sum for the relevant jar) Guess we would have to re-host the p2-repo. For now, maybe you can use the p2-repo from the builder machine[1] as a temporary workaround? [1] http://107.22.190.5/chunk-06/RC3/p2-repo/ Thanks, Lasantha On 4 January 2014 11:28, Kishanthan Thangarajah kishant...@wso2.comwrote: Can you check whether those jars were downloaded correctly / they are not corrupted ones? On Sat, Jan 4, 2014 at 2:55 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi all, The reason is a mismatch of md5sum of two jars [1]. The md5 sums of these jars are different from the ones defined in the artifacts.xml [2]. What is the correct resolution for this issue..? [1] Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.client,1.2.0. MD5 hash is not as expected. Expected: c80993a541f5cd4a356b2da69edefc90 and found 442b547c177c4206e34d028c81980466. Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.publisher,1.2.0. MD5 hash is not as expected. Expected: dfcae32b8615ed989843a8f130ceb154 and found 8f07a81607f348c1485f7cef08a4a1cb. [2] artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.client' version='1.2.0' properties size='3' property name='artifact.size' value='57002'/ property name='download.size' value='57002'/ property name='download.md5' value='c80993a541f5cd4a356b2da69edefc90'/ /properties /artifact artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.publisher' version='1.2.0' properties size='3' property name='artifact.size' value='40455'/ property name='download.size' value='40455'/ property name='download.md5' value='dfcae32b8615ed989843a8f130ceb154'/ /properties /artifact Thanks SumeddhaS On Thu, Jan 2, 2014 at 10:36 AM, Sumedha Kodithuwakku sumed...@wso2.com wrote: Hi all, $subject. I tried to install features using [1] but I get the attached exception. Any idea on this..? [1] http://dist.wso2.org/p2/carbon/releases/turing/ Thanks SumedhaS -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org
Re: [Dev] [AM] Unable to install Key Manager (APIM) features in IS 4.6.0
Hi Ruwan, It's working with the above link. No issues while installing features. Thanks SumedhaS On Sun, Jan 5, 2014 at 6:10 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi Sumedha, There was a issue with the nested categories. I did a fix locally and re-compiled a feature repo on the builder machine. Please try with the link @ [1], You will be able to see the latest Jars listed under the API Manager 1.6.0 category. [1] - http://107.22.190.5/chunk-06_POSTMORTEM/p2-repo/ Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Mon, Jan 6, 2014 at 3:03 AM, Sumedha Kodithuwakku sumed...@wso2.comwrote: Hi Lasantha, Yes, It worked. @Ruwan, There is another issue related to APIM. When installing features it shows APIM as 1.5.0 and I think it should be 1.6.0. Also the jars installed by the key manager feature are older versions (checked only with Key Manager). That is the versions of jars related to APIM are not the ones released with APIM 1.6.0. Please have a look at this. Thanks SumedhaS On Sun, Jan 5, 2014 at 8:53 AM, Lasantha Fernando lasan...@wso2.comwrote: Hi Sumedha, It seems that the hosted p2-repo has an incorrect jar. Checked with p2-repo in builder machine [1] and the hosted one and it seems there is a difference. (The p2-repo in builder machine has correct md5sum for the relevant jar) Guess we would have to re-host the p2-repo. For now, maybe you can use the p2-repo from the builder machine[1] as a temporary workaround? [1] http://107.22.190.5/chunk-06/RC3/p2-repo/ Thanks, Lasantha On 4 January 2014 11:28, Kishanthan Thangarajah kishant...@wso2.comwrote: Can you check whether those jars were downloaded correctly / they are not corrupted ones? On Sat, Jan 4, 2014 at 2:55 AM, Sumedha Kodithuwakku sumed...@wso2.com wrote: Hi all, The reason is a mismatch of md5sum of two jars [1]. The md5 sums of these jars are different from the ones defined in the artifacts.xml [2]. What is the correct resolution for this issue..? [1] Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.client,1.2.0. MD5 hash is not as expected. Expected: c80993a541f5cd4a356b2da69edefc90 and found 442b547c177c4206e34d028c81980466. Problems downloading artifact: osgi.bundle,org.wso2.carbon.apimgt.usage.publisher,1.2.0. MD5 hash is not as expected. Expected: dfcae32b8615ed989843a8f130ceb154 and found 8f07a81607f348c1485f7cef08a4a1cb. [2] artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.client' version='1.2.0' properties size='3' property name='artifact.size' value='57002'/ property name='download.size' value='57002'/ property name='download.md5' value='c80993a541f5cd4a356b2da69edefc90'/ /properties /artifact artifact classifier='osgi.bundle' id='org.wso2.carbon.apimgt.usage.publisher' version='1.2.0' properties size='3' property name='artifact.size' value='40455'/ property name='download.size' value='40455'/ property name='download.md5' value='dfcae32b8615ed989843a8f130ceb154'/ /properties /artifact Thanks SumeddhaS On Thu, Jan 2, 2014 at 10:36 AM, Sumedha Kodithuwakku sumed...@wso2.com wrote: Hi all, $subject. I tried to install features using [1] but I get the attached exception. Any idea on this..? [1] http://dist.wso2.org/p2/carbon/releases/turing/ Thanks SumedhaS -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Sumedha Kodithuwakku* Software Engineer WSO2 Inc. : wso2.com lean . enterprise . middleware Email: sumed...@wso2.com; Mobile: +94 71 808 1124 | +1 602 388 0160 Blog: http://sumedhask.blogspot.com/
Re: [Dev] Shall we remove the WS-AddressingEndpoint from Endpoint Tool Pallet in DevStudio?
Hi, +1 WS-Addresing Endpoint is no longer needed. So we can remove it from tool palette. Created a public Jira [1] to track this. [1] - https://wso2.org/jira/browse/TOOLS-2274 Thanks, Viraj. On Sun, Jan 5, 2014 at 2:23 PM, Harshana Martin harsh...@wso2.com wrote: Hi All, I think we $Subject because now that Send mediator is embedding the endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty Send mediator indicates the WS-Addressing scenario just like in the Mgt Console. So I'm proposing $Subject. WDYT? Thanks and Regards, Harshana -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- 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] Shall we remove the WS-AddressingEndpoint from Endpoint Tool Pallet in DevStudio?
+1 On Mon, Jan 6, 2014 at 9:50 AM, Viraj Rajaguru vi...@wso2.com wrote: Hi, +1 WS-Addresing Endpoint is no longer needed. So we can remove it from tool palette. Created a public Jira [1] to track this. [1] - https://wso2.org/jira/browse/TOOLS-2274 Thanks, Viraj. On Sun, Jan 5, 2014 at 2:23 PM, Harshana Martin harsh...@wso2.com wrote: Hi All, I think we $Subject because now that Send mediator is embedding the endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty Send mediator indicates the WS-Addressing scenario just like in the Mgt Console. So I'm proposing $Subject. WDYT? Thanks and Regards, Harshana -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- 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 -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we remove the WS-AddressingEndpoint from Endpoint Tool Pallet in DevStudio?
And we may be able to fix [1] as well. [1] - https://wso2.org/jira/browse/TOOLS-2271 On Mon, Jan 6, 2014 at 9:59 AM, Susinda Perera susi...@wso2.com wrote: +1 On Mon, Jan 6, 2014 at 9:50 AM, Viraj Rajaguru vi...@wso2.com wrote: Hi, +1 WS-Addresing Endpoint is no longer needed. So we can remove it from tool palette. Created a public Jira [1] to track this. [1] - https://wso2.org/jira/browse/TOOLS-2274 Thanks, Viraj. On Sun, Jan 5, 2014 at 2:23 PM, Harshana Martin harsh...@wso2.comwrote: Hi All, I think we $Subject because now that Send mediator is embedding the endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty Send mediator indicates the WS-Addressing scenario just like in the Mgt Console. So I'm proposing $Subject. WDYT? Thanks and Regards, Harshana -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 -- 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 -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while using jaggery post method.
Hi guys,
I tried the xhr client to send my B64 encoded + URL encoded saml assertion.
However it alters some of the content during the transfer process.
Below is the code bit that im using,
var endpoint = config.oauthConfiguration.tokenEndpoint;
var headers = {
Authorization: Basic +basicAuthToken,
Content-Type:
application/x-www-form-urlencoded;charset=UTF-8
};
var data = {
grant_type:urn:ietf:params:oauth:grant-type:saml2-bearer,
assertion:encodedSAMLToken
};
var response = post(endpoint,data,headers,text);
SAML assertion attached. I intercepted the request using tcp mon. when
json is used as type the assertion being truncated. when the type is
'text' the whole assertion get transferred, but still decoding errors.
you can use,
http://meyerweb.com/eric/tools/dencoder/
http://www.base64decode.org/
for testing purposes. Any help would be much appreciated.. :)
Thanks,
--Pradeep
Re: [Dev] Error while using jaggery post method.
Hi, It seems that, post method in jaggery URL encodes the body by default. Is this the correct behaviour.? curl doesnt do that sort of thing. workaround was, not to URL encode SAML assertion. thanks, --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
