Synapse Build failure
Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031
Re: Synapse Build failure
2.1.0-SNAPSHOT? Did we release 2.0 already?? Sanjiva. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.com wrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
Re: Synapse Build failure
The trunk is having the version 2.1.0-SNAPSHOT. On Sun, Nov 21, 2010 at 6:32 PM, Sanjiva Weerawarana sanj...@opensource.lkwrote: 2.1.0-SNAPSHOT? Did we release 2.0 already?? Sanjiva. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.com wrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Regards, Heshan Suriyaarachchi http://heshans.blogspot.com/
Re: Synapse Build failure
The branch version is 2.0 and we did not release it yet. On Sun, Nov 21, 2010 at 7:03 PM, Heshan Suriyaarachchi heshan.suriyaarach...@gmail.com wrote: The trunk is having the version 2.1.0-SNAPSHOT. On Sun, Nov 21, 2010 at 6:32 PM, Sanjiva Weerawarana sanj...@opensource.lk wrote: 2.1.0-SNAPSHOT? Did we release 2.0 already?? Sanjiva. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.comwrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Regards, Heshan Suriyaarachchi http://heshans.blogspot.com/ -- Regards, Heshan Suriyaarachchi http://heshans.blogspot.com/
Re: Synapse Build failure
Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.com wrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031
httpcore and httpcore-nio jars not available when building synapse online
Hi, When building the nhttp module of synapse transports/core, there are two dependencies for httpcore-4.1-beta3-SNAPSHOT.jar and httpcore-nio-4.1-beta3-SNAPSHOT.jar. But these two are not available when buildinng online. I have checked in the two apache snapshot repositories, but there is no 4.1-beta3-SNAPSHOT available. Instead there is 4.0-beta3-SNAPSHOT. So, should the dependency be changed to 4.0-beta3-SNAPSHOT? Thanks, Amila.
Re: httpcore and httpcore-nio jars not available when building synapse online
On Sun, 2010-11-21 at 19:29 +0530, Amila Maha Arachchi wrote: Hi, When building the nhttp module of synapse transports/core, there are two dependencies for httpcore-4.1-beta3-SNAPSHOT.jar and httpcore-nio-4.1-beta3-SNAPSHOT.jar. But these two are not available when buildinng online. I have checked in the two apache snapshot repositories, but there is no 4.1-beta3-SNAPSHOT available. Instead there is 4.0-beta3-SNAPSHOT. So, should the dependency be changed to 4.0-beta3-SNAPSHOT? Thanks, Amila. Amila et al Please consider upgrading to the release version 4.1 instead. Oleg - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
Re: Synapse Build failure
Since HTTP Core has released the 4.1 version we can move to that version. I'll update the version. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:32 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.com wrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: Synapse Build failure
I've changed HTTP Core version to 4.1. Please take a svn update. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:41 PM, Supun Kamburugamuva supu...@gmail.comwrote: Since HTTP Core has released the 4.1 version we can move to that version. I'll update the version. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:32 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.comwrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: httpcore and httpcore-nio jars not available when building synapse online
I've updated the HTTP Core version to 4.1. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:40 PM, Oleg Kalnichevski ol...@apache.org wrote: On Sun, 2010-11-21 at 19:29 +0530, Amila Maha Arachchi wrote: Hi, When building the nhttp module of synapse transports/core, there are two dependencies for httpcore-4.1-beta3-SNAPSHOT.jar and httpcore-nio-4.1-beta3-SNAPSHOT.jar. But these two are not available when buildinng online. I have checked in the two apache snapshot repositories, but there is no 4.1-beta3-SNAPSHOT available. Instead there is 4.0-beta3-SNAPSHOT. So, should the dependency be changed to 4.0-beta3-SNAPSHOT? Thanks, Amila. Amila et al Please consider upgrading to the release version 4.1 instead. Oleg - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: Synapse Build failure
Thanks Supun. Amila. On Sun, Nov 21, 2010 at 7:46 PM, Supun Kamburugamuva supu...@gmail.comwrote: I've changed HTTP Core version to 4.1. Please take a svn update. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:41 PM, Supun Kamburugamuva supu...@gmail.comwrote: Since HTTP Core has released the 4.1 version we can move to that version. I'll update the version. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:32 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.comwrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
Re: Synapse configuration namespace
I'm +1 for a namespace change if we have changed the semantics of the synapse configuration language at a broader level. But since we haven't done any major change to the configuration language im 0 on this. So my opinion solely depend on what users will think and how they will get affected. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:35 AM, Ruwan Linton ruwan.lin...@gmail.comwrote: I found more incompatible changes :-( https://issues.apache.org/jira/browse/SYNAPSE-693?focusedCommentId=12934217page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12934217 I do not understand why you are opposing to changing the namespace with 2.0 release, while we have this sort of dangerous incompatibilities. Ruwan On Sun, Nov 21, 2010 at 6:43 AM, Sanjiva Weerawarana sanj...@opensource.lk wrote: On Sat, Nov 20, 2010 at 8:58 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Also, in general using namespaces to version XML schemas is generally considered bad practice. I don't think we are doing a versioning of the synapse configuration schema with the namespace, anyway most of Then what are you achieving with the namespace name change? the other schemas, like (WSDL, XSLT) have different namespaces for different versions. :-( Not correct .. WSDL 1.1 to 2.0 does do but in that case the languages and semantics are majorly different. The 2.0 language was also delivered by a whole different group instead of a small private club. XSLT was intentionally, carefully designed for forwards compatibility and has a version attribute: http://www.w3.org/TR/xslt#forwards http://www.w3.org/TR/xslt#forwardsThis was a James Clark masterpiece. Now see XSLT 2.0's section on backwards compatibility: http://www.w3.org/TR/xslt20/#backwards http://www.w3.org/TR/xslt20/#backwards Also there is more than the domain name or being a new TLP out from WS for this namespace change, which is, that Synapse is more than web services and it can handle many things apart from web services, as you know web services is just one connector among many other connectors for mediation, and that is why I do not want to limit the namespace to the ws.apache.org. Yes Synapse is much more than Web services. However, IMO, most users don't bother to give any quality time to looking at the namespace and making judgments based on that. I'm done pushing my position on this topic :). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
RE: Synapse configuration namespace
Well, I think I have to agree with Sanjiva’s statement about the meaning of namespaces for an end user. I also do not know many people really caring about namespaces as long as those namespaces are not causing any troubles. Maybe one should not look at a namespace change independent of other changes. If for whatever reason a configuration format and/or syntax has changed resulting in the possibility that some or even all the user’s configurations will no longer work with a newer software version and users receive a migration tool to convert their configurations using the old format into a new format, users also do not care whether there is a namespace change or not (as long as the migration tool works properly). API changes breaking existing custom extensions (in the case of Synapse primarily “mediators”) or (even more critical) changed runtime behaviour should normally affect end users much more. During the too long time without any release since the last release of Synapse in June 2008 (so about two and a half years ago) I’m pretty sure any of the above will be the case. Regards, Eric From: Supun Kamburugamuva [mailto:supu...@gmail.com] Sent: Sunday, November 21, 2010 3:25 PM To: dev@synapse.apache.org Cc: u...@synapse.apache.org Subject: Re: Synapse configuration namespace I'm +1 for a namespace change if we have changed the semantics of the synapse configuration language at a broader level. But since we haven't done any major change to the configuration language im 0 on this. So my opinion solely depend on what users will think and how they will get affected. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:35 AM, Ruwan Linton ruwan.lin...@gmail.commailto:ruwan.lin...@gmail.com wrote: I found more incompatible changes :-( https://issues.apache.org/jira/browse/SYNAPSE-693?focusedCommentId=12934217page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12934217 I do not understand why you are opposing to changing the namespace with 2.0 release, while we have this sort of dangerous incompatibilities. Ruwan On Sun, Nov 21, 2010 at 6:43 AM, Sanjiva Weerawarana sanj...@opensource.lkmailto:sanj...@opensource.lk wrote: On Sat, Nov 20, 2010 at 8:58 PM, Ruwan Linton ruwan.lin...@gmail.commailto:ruwan.lin...@gmail.com wrote: Also, in general using namespaces to version XML schemas is generally considered bad practice. I don't think we are doing a versioning of the synapse configuration schema with the namespace, anyway most of Then what are you achieving with the namespace name change? the other schemas, like (WSDL, XSLT) have different namespaces for different versions. :-( Not correct .. WSDL 1.1 to 2.0 does do but in that case the languages and semantics are majorly different. The 2.0 language was also delivered by a whole different group instead of a small private club. XSLT was intentionally, carefully designed for forwards compatibility and has a version attribute: http://www.w3.org/TR/xslt#forwards http://www.w3.org/TR/xslt#forwardsThis was a James Clark masterpiece. Now see XSLT 2.0's section on backwards compatibility: http://www.w3.org/TR/xslt20/#backwards http://www.w3.org/TR/xslt20/#backwards Also there is more than the domain name or being a new TLP out from WS for this namespace change, which is, that Synapse is more than web services and it can handle many things apart from web services, as you know web services is just one connector among many other connectors for mediation, and that is why I do not want to limit the namespace to the ws.apache.orghttp://ws.apache.org. Yes Synapse is much more than Web services. However, IMO, most users don't bother to give any quality time to looking at the namespace and making judgments based on that. I'm done pushing my position on this topic :). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.commailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.comhttp://supunk.blogspot.com
Re: Synapse configuration namespace
On Sun, Nov 21, 2010 at 9:22 PM, Hubert, Eric eric.hub...@foxmobile.comwrote: Well, I think I have to agree with Sanjiva’s statement about the meaning of namespaces for an end user. I also do not know many people really caring about namespaces as long as those namespaces are not causing any troubles. Maybe one should not look at a namespace change independent of other changes. +1. If for whatever reason a configuration format and/or syntax has changed resulting in the possibility that some or even all the user’s configurations will no longer work with a newer software version and users receive a migration tool to convert their configurations using the old format into a new format, users also do not care whether there is a namespace change or not (as long as the migration tool works properly). API changes breaking existing custom extensions (in the case of Synapse primarily “mediators”) or (even more critical) changed runtime behaviour should normally affect end users much more. During the too long time without any release since the last release of Synapse in June 2008 (so about two and a half years ago) I’m pretty sure any of the above will be the case. Right, v2.0 indicates that there are major, incompatible changes in the product. Namespace change is an unnecessary thing to support that as for most people the silly namespace thing is something to gloss over (and a PITA in general). In fact, I no longer believe that XML languages should use namespaces at all .. only an extreme case where the language is meant to be transparently embedded in other languages is a namespace name a necessity. Just use unqualified XML syntax and make life easier! Now, if you want to support a model of ignoring the namespace I'd totally +1 that! Qualified names can still be used for extensions of course; that makes crystal clear when one is using an extension vs. the core. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
Re: Synapse configuration namespace
OK We need to do the 2.0.0 release ASAP, it has been dragging way too much, and I don't want to delay it because of a namespace change and do not want to call another vote for this. Let me take your votes from this thread and try to summarize the decision on this. If I have interpreted this thread correctly, following people are for this NS change; Ruwan, Hiranya, Eric And even though after a long time there has been a huge oppose to this from the following people :-) Sanjiva, Paul, Jaeger I would consider Supun as (-0) with his statement, and Rajika to be neutral as I cannot interpret anything. With the above analysis, and the Apache way, I think we will have to revert the namespace change. I am working on the final documentation fixes for the release, once it is done I will revert the namespace change and remove the migration tool. My personal belief is that this is a step backwards and waste of a lot of work, with the migration tool and so forth. If you have any concerns over this decision please shout NOW and only NOW. Thanks, Ruwan On Mon, Nov 22, 2010 at 9:16 AM, Sanjiva Weerawarana sanj...@opensource.lkwrote: On Sun, Nov 21, 2010 at 9:22 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: Well, I think I have to agree with Sanjiva’s statement about the meaning of namespaces for an end user. I also do not know many people really caring about namespaces as long as those namespaces are not causing any troubles. Maybe one should not look at a namespace change independent of other changes. +1. If for whatever reason a configuration format and/or syntax has changed resulting in the possibility that some or even all the user’s configurations will no longer work with a newer software version and users receive a migration tool to convert their configurations using the old format into a new format, users also do not care whether there is a namespace change or not (as long as the migration tool works properly). API changes breaking existing custom extensions (in the case of Synapse primarily “mediators”) or (even more critical) changed runtime behaviour should normally affect end users much more. During the too long time without any release since the last release of Synapse in June 2008 (so about two and a half years ago) I’m pretty sure any of the above will be the case. Right, v2.0 indicates that there are major, incompatible changes in the product. Namespace change is an unnecessary thing to support that as for most people the silly namespace thing is something to gloss over (and a PITA in general). In fact, I no longer believe that XML languages should use namespaces at all .. only an extreme case where the language is meant to be transparently embedded in other languages is a namespace name a necessity. Just use unqualified XML syntax and make life easier! Now, if you want to support a model of ignoring the namespace I'd totally +1 that! Qualified names can still be used for extensions of course; that makes crystal clear when one is using an extension vs. the core. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton
Re: Synapse configuration namespace
On Mon, Nov 22, 2010 at 10:07 AM, Ruwan Linton ruwan.lin...@gmail.com wrote: OK We need to do the 2.0.0 release ASAP, it has been dragging way too much, and I don't want to delay it because of a namespace change and do not want to call another vote for this. Let me take your votes from this thread and try to summarize the decision on this. If I have interpreted this thread correctly, following people are for this NS change; Ruwan, Hiranya, Eric And even though after a long time there has been a huge oppose to this from the following people :-) Sanjiva, Paul, Jaeger I would consider Supun as (-0) with his statement, and Rajika to be neutral as I cannot interpret anything. With the above analysis, and the Apache way, I think we will have to revert the namespace change. I am working on the final documentation fixes for the release, once it is done I will revert the namespace change and remove the migration tool. My personal belief is that this is a step backwards and waste of a lot of work, with the migration tool and so forth. If you have any concerns over this decision please shout NOW and only NOW. I'm ok with reverting Thanks, Hiranya Thanks, Ruwan On Mon, Nov 22, 2010 at 9:16 AM, Sanjiva Weerawarana sanj...@opensource.lkwrote: On Sun, Nov 21, 2010 at 9:22 PM, Hubert, Eric eric.hub...@foxmobile.com wrote: Well, I think I have to agree with Sanjiva’s statement about the meaning of namespaces for an end user. I also do not know many people really caring about namespaces as long as those namespaces are not causing any troubles. Maybe one should not look at a namespace change independent of other changes. +1. If for whatever reason a configuration format and/or syntax has changed resulting in the possibility that some or even all the user’s configurations will no longer work with a newer software version and users receive a migration tool to convert their configurations using the old format into a new format, users also do not care whether there is a namespace change or not (as long as the migration tool works properly). API changes breaking existing custom extensions (in the case of Synapse primarily “mediators”) or (even more critical) changed runtime behaviour should normally affect end users much more. During the too long time without any release since the last release of Synapse in June 2008 (so about two and a half years ago) I’m pretty sure any of the above will be the case. Right, v2.0 indicates that there are major, incompatible changes in the product. Namespace change is an unnecessary thing to support that as for most people the silly namespace thing is something to gloss over (and a PITA in general). In fact, I no longer believe that XML languages should use namespaces at all .. only an extreme case where the language is meant to be transparently embedded in other languages is a namespace name a necessity. Just use unqualified XML syntax and make life easier! Now, if you want to support a model of ignoring the namespace I'd totally +1 that! Qualified names can still be used for extensions of course; that makes crystal clear when one is using an extension vs. the core. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Director Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2; http://wso2.com/ Founder Director; Thinkcube Systems; http://www.thinkcube.com/ Member; Apache Software Foundation; http://www.apache.org/ Member; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton google: http://www.google.com/profiles/ruwan.linton tweet: http://twitter.com/ruwanlinton -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
Re: Synapse Build failure
Thanks Supun. On Sun, Nov 21, 2010 at 7:54 PM, Amila Maha Arachchi ami...@wso2.comwrote: Thanks Supun. Amila. On Sun, Nov 21, 2010 at 7:46 PM, Supun Kamburugamuva supu...@gmail.comwrote: I've changed HTTP Core version to 4.1. Please take a svn update. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:41 PM, Supun Kamburugamuva supu...@gmail.comwrote: Since HTTP Core has released the 4.1 version we can move to that version. I'll update the version. Thanks, Supun.. On Sun, Nov 21, 2010 at 7:32 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, I have checked these dependencies in the repository. But there is no dependency by the version 4.1-beta3-SNAPSHOT. Instead there is 4.0-beta3-SNAPSHOT. I have put a separate email mentioning this. thanks, Amila. On Sun, Nov 21, 2010 at 2:54 PM, Ranga Siriwardena ra...@wso2.comwrote: Hi, When building Appache-Synapse version- 2.1.0-SNAPSHOT, it gives following error. What should I do to avoid the issue. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore:jar:4.1-beta3-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.httpcomponents -DartifactId=httpcore-nio -Dversion=4.1-beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.synapse:synapse-nhttp-transport:bundle:2.1.0-SNAPSHOT 2) org.apache.httpcomponents:httpcore-nio:jar:4.1-beta3-SNAPSHOT Thank you. -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031 -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Technical Lead, WSO2 Inc http://wso2.org supunk.blogspot.com -- Ranga Siriwardena Software Engineer WSO2 Inc. Mobile: +94 779808031
[jira] Updated: (SYNAPSE-618) [GSoC] Implement a Dead Letter Channel for Synapse
[ https://issues.apache.org/jira/browse/SYNAPSE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charith Dhanushka Wickramarachchi updated SYNAPSE-618: -- Attachment: messagestore_patch_11.diff Hi , In the current MessageStore implementation there is no method to remove the message store from the synapse configuration. this patch will resolve that. thanks, Charith [GSoC] Implement a Dead Letter Channel for Synapse -- Key: SYNAPSE-618 URL: https://issues.apache.org/jira/browse/SYNAPSE-618 Project: Synapse Issue Type: New Feature Components: Core, Endpoints Reporter: Hiranya Jayathilaka Assignee: Hiranya Jayathilaka Fix For: FUTURE Attachments: messagestore_patch_1.diff, messagestore_patch_10.diff, messagestore_patch_11.diff, messagestore_patch_11.diff, messagestore_patch_2.diff, messagestore_patch_3.diff, messagestore_patch_4.diff, messagestore_patch_5.diff, messagestore_patch_6.diff, messagestore_patch_7.diff, messagestore_patch_7.diff, messagestore_patch_8.diff, messagestore_patch_9.diff, synapse_sample_1.xml, synapse_sample_1.xml, synapse_sample_1.xml, synapse_sample_1.xml Currently when Synapse attempts to send a message and if it fails, following actions can be configured to deal with the error: * Execute a fault sequence and handle the failed request gracefully * Fail-over to a different endpoint In addition to these, Synapse ESB should support the dead letter channel enterprise integration pattern to deal with various errors that might occur during mediation or while sending. With the dead letter channel, the failed message will be put into a message store in the ESB. Later the ESB can retry to send the messages in the message store. We should be able to have multiple implementations of the actual message store and should be able to configure which store to use for a particular scenario. Users should be able to implement their own message stores and plug into the ESB easily. To start with we can have a simple in-memory message store and a persisting store based on JDBC or JMS. References: http://www.eaipatterns.com/DeadLetterChannel.html https://issues.apache.org/jira/browse/SYNAPSE-263 Possible Mentors: Hiranya Jayathilaka -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org
