Apache Karaf 2.3.0 vs 2.2.x
Just a question since I've seen that Karaf 2.3.0 is in the works. I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been fixed in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3.0 seems to have been upgrade to Proxy 1.0 (which should work). Are there any plans to release a Karaf 2.2.10 with a new proxy version? Otherwise, I believe many people may encounter the same problem I did when upgrading their JVM version. For me personally I'm waiting for the 2.3.0 to be released and then I'll upgrade my custom distribution. Not sure how people generally do this but a 2.2.10 with an upgraded proxy might be needed for some people. /Bengt
Re: Apache Karaf 2.3.0 vs 2.2.x
Hi Bengt, to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also includes the corresponding Bug-Fix and therefore should work. regards, Achim 2012/10/9 Bengt Rodehav be...@rodehav.com: Just a question since I've seen that Karaf 2.3.0 is in the works. I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been fixed in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3.0 seems to have been upgrade to Proxy 1.0 (which should work). Are there any plans to release a Karaf 2.2.10 with a new proxy version? Otherwise, I believe many people may encounter the same problem I did when upgrading their JVM version. For me personally I'm waiting for the 2.3.0 to be released and then I'll upgrade my custom distribution. Not sure how people generally do this but a 2.2.10 with an upgraded proxy might be needed for some people. /Bengt -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/
Re: HttpService overlapping paths
Hi Thomas, do you mind opening an issue for this at pax-web? This looks a lot like an issue there, it might be fixed with a newer version though I need to check. I'm gonna try to tackle this down asap. regards, Achim 2012/10/9 Thomas Zimmermann zimmermann@googlemail.com: Hi everybody. I am having trouble with the HttpService when servlet paths of registered servlets are overlapping. For example: I register servlets on /root and /root/path with the HttpService. The GET method of the servlet on /root is called when I access its URL in a browser (http://localhost:8181/root as default), so everything is fine. However, if I try to access /root/path, the servlet registered with /root is called and NOT the one registered on /root/path. Do I misunderstand the specification or am I doing something wrong? This is the code I am using to register both servlets. I am accessing the HttpService through blueprint, init and destroy are the init-method and destroy-method of the ServletRegisterer bean. I can attach a fully functional example project if that is needed. To reproduce: 1. Download Karaf 2.2.9 for windows 2. Run features:install http 3. Deploy the code above Thank you very much in advance, Karaf is great so far. :) -- View this message in context: http://karaf.922171.n3.nabble.com/HttpService-overlapping-paths-tp4026331.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/
Re: Apache Karaf 2.3.0 vs 2.2.x
OK - good. I wasn't aware that 0.3.1 fixed this issue. TBH I find it extremely hard to keep track of Aries different releases and what's included in what release. I can't even find any information about the 0.3.1 release on theire web site. I can't even find the release notes for the current (1.0.0?) release. As a developer it´s pretty hard to upgrade your Aries dependencies on your own since I have no idea which versions of which modules have actually been tested and verified together. This might have improved now but the idea of releasing every little module on its own instead of providing a complete set of modules that are known to work together is not very user friendly. I tend to rely on projects like Karaf and use the version of Aries that you use. So, I'm glad you guys solved it for me. Thanks, /Bengt 2012/10/9 Achim Nierbeck bcanh...@googlemail.com Hi Bengt, to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also includes the corresponding Bug-Fix and therefore should work. regards, Achim 2012/10/9 Bengt Rodehav be...@rodehav.com: Just a question since I've seen that Karaf 2.3.0 is in the works. I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been fixed in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3.0 seems to have been upgrade to Proxy 1.0 (which should work). Are there any plans to release a Karaf 2.2.10 with a new proxy version? Otherwise, I believe many people may encounter the same problem I did when upgrading their JVM version. For me personally I'm waiting for the 2.3.0 to be released and then I'll upgrade my custom distribution. Not sure how people generally do this but a 2.2.10 with an upgraded proxy might be needed for some people. /Bengt -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/
Re: Apache Karaf 2.3.0 vs 2.2.x
I can confirm that karaf 2.2.9 fixed our issues with jre 6u33+. kind regards, christoph On 09/10/12 14:16, Achim Nierbeck wrote: Hi Bengt, to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also includes the corresponding Bug-Fix and therefore should work. regards, Achim 2012/10/9 Bengt Rodehav be...@rodehav.com: Just a question since I've seen that Karaf 2.3.0 is in the works. I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been fixed in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3.0 seems to have been upgrade to Proxy 1.0 (which should work). Are there any plans to release a Karaf 2.2.10 with a new proxy version? Otherwise, I believe many people may encounter the same problem I did when upgrading their JVM version. For me personally I'm waiting for the 2.3.0 to be released and then I'll upgrade my custom distribution. Not sure how people generally do this but a 2.2.10 with an upgraded proxy might be needed for some people. /Bengt smime.p7s Description: S/MIME Cryptographic Signature
Re: Apache Karaf 2.3.0 vs 2.2.x
Thanks for letting me know. I'll upgrade to 2.2.9 or perhaps 2.3.0 in the near future. In the meantime I've downgraded Java to 6u32 :-) /Bengt 2012/10/9 Christoph Gritschenberger christoph.gritschenber...@gmail.com I can confirm that karaf 2.2.9 fixed our issues with jre 6u33+. kind regards, christoph On 09/10/12 14:16, Achim Nierbeck wrote: Hi Bengt, to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also includes the corresponding Bug-Fix and therefore should work. regards, Achim 2012/10/9 Bengt Rodehav be...@rodehav.com: Just a question since I've seen that Karaf 2.3.0 is in the works. I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been fixed in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3.0 seems to have been upgrade to Proxy 1.0 (which should work). Are there any plans to release a Karaf 2.2.10 with a new proxy version? Otherwise, I believe many people may encounter the same problem I did when upgrading their JVM version. For me personally I'm waiting for the 2.3.0 to be released and then I'll upgrade my custom distribution. Not sure how people generally do this but a 2.2.10 with an upgraded proxy might be needed for some people. /Bengt
