Re: Update to the Servlet API
Ralph Goers wrote: So this is one way to get us motivated to get 2.2 out. Do you think it's still feasible to release 2.2 with only ECM+ and maven build? Probably trunk already passed 2.2 release point... Vadim
Re: Update to the Servlet API
Jean-Baptiste Quenot schrieb: * Carsten Ziegeler: I think we don't need to moch the whole spec but just the listener. So it's one interface. As soon as we use 2.3 for compilation we can't ensure So if I understand correctly, you suggest that I extract ServletContextListener and otherdependent classes from tools/jetty/lib/servlet-2.3.jar, and to put that interface in blocks/xsp/mocks? What would prevent developers from using the mock interfaces then? Of course nothing, but the mocks are only visible to the xsp block, so the scope is reduced and you only need the ServletContextListener and ServletContextEvent classes, so the features of 2.3 which are visible to the xsp block are reduced as well. Putting the 2.3 jar in the libs opens all new features to all blocks. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep compatibility with servlet 2.2, by making servlet2.3-requiring components optional. WDYT? -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: Update to the Servlet API
Jean-Baptiste Quenot schrieb: I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep compatibility with servlet 2.2, by making servlet2.3-requiring components optional. You can't check if a component uses 2.3 functionality, so if we just upgrade we might end up with a not 2.2 servlet compliant solution. (Or is there a way?) Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
Carsten Ziegeler wrote: Jean-Baptiste Quenot schrieb: I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep compatibility with servlet 2.2, by making servlet2.3-requiring components optional. You can't check if a component uses 2.3 functionality, so if we just upgrade we might end up with a not 2.2 servlet compliant solution. (Or is there a way?) Servlet 2.3 has been released more than 4 years ago[1]. IMO it is safe to consider that people using recent versions of Cocoon are running at least servlet 2.3 and most probably servlet 2.4. So depending on servlet 2.3 shouldn't be that much of a problem. Sylvain [1] http://www.jcp.org/en/jsr/detail?id=53 -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Update to the Servlet API
Sylvain Wallez wrote: Carsten Ziegeler wrote: Jean-Baptiste Quenot schrieb: I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep compatibility with servlet 2.2, by making servlet2.3-requiring components optional. You can't check if a component uses 2.3 functionality, so if we just upgrade we might end up with a not 2.2 servlet compliant solution. (Or is there a way?) Servlet 2.3 has been released more than 4 years ago[1]. IMO it is safe to consider that people using recent versions of Cocoon are running at least servlet 2.3 and most probably servlet 2.4. So depending on servlet 2.3 shouldn't be that much of a problem. Yes, that's why I said in an earlier response that we can vote on upgrading the requirements to servlet 2.3 officially. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
On 25.01.2006 15:37, Sylvain Wallez wrote: So depending on servlet 2.3 shouldn't be that much of a problem. But in 2.1 branch what 1. we assume is legacy, 2. we want to assure compatibility according to our versioning manifesto [1]. Jörg [1] http://cocoon.apache.org/versioning.html
Re: Update to the Servlet API
I'd be in favor of that but you cannot follow our versioning plan and introduce it in 2.1.9. We'd have to announce our intent first. On the other hand, we can always override that with a vote. Carsten Ziegeler wrote: Servlet 2.3 has been released more than 4 years ago[1]. IMO it is safe to consider that people using recent versions of Cocoon are running at least servlet 2.3 and most probably servlet 2.4. So depending on servlet 2.3 shouldn't be that much of a problem. Yes, that's why I said in an earlier response that we can vote on upgrading the requirements to servlet 2.3 officially. Carsten
Re: Update to the Servlet API
Joerg Heinicke wrote: On 25.01.2006 15:37, Sylvain Wallez wrote: So depending on servlet 2.3 shouldn't be that much of a problem. But in 2.1 branch what 1. we assume is legacy, 2. we want to assure compatibility according to our versioning manifesto [1]. Btw, Cocoon 2.2 is based on servlet 2.3. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
Carsten Ziegeler wrote: Sylvain Wallez wrote: So depending on servlet 2.3 shouldn't be that much of a problem. Yes, that's why I said in an earlier response that we can vote on upgrading the requirements to servlet 2.3 officially. Ok, let's vote! Sylvain -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Update to the Servlet API
Sylvain Wallez wrote: Carsten Ziegeler wrote: Sylvain Wallez wrote: So depending on servlet 2.3 shouldn't be that much of a problem. Yes, that's why I said in an earlier response that we can vote on upgrading the requirements to servlet 2.3 officially. Ok, let's vote! Why? What does it give us? It _may_ bring an incompatability for some users, so I'd want to understand what the benefits are. Personally, I think we should go 2.3 or even 2.4 with Cocoon 2.2, but stick as we are in 2.1.x. After all, it is becoming more of a maintenance release, and should have as little substantial change as possible. Regards, Upayavira
Re: Update to the Servlet API
Upayavira wrote: Sylvain Wallez wrote: Ok, let's vote! Why? What does it give us? It _may_ bring an incompatability for some users, so I'd want to understand what the benefits are. Personally, I think we should go 2.3 or even 2.4 with Cocoon 2.2, but stick as we are in 2.1.x. After all, it is becoming more of a maintenance release, and should have as little substantial change as possible. Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. Now for sure, we've been living without it for years... Sylvain -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Update to the Servlet API
Sylvain Wallez schrieb: Upayavira wrote: Sylvain Wallez wrote: Ok, let's vote! Why? What does it give us? It _may_ bring an incompatability for some users, so I'd want to understand what the benefits are. Personally, I think we should go 2.3 or even 2.4 with Cocoon 2.2, but stick as we are in 2.1.x. After all, it is becoming more of a maintenance release, and should have as little substantial change as possible. Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
* Carsten Ziegeler: Sylvain Wallez schrieb: Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Yes, I want to integrate a patch that allows to run an *optional* component on webapp startup to compile XSP. It's only for *compilation* that servlet 2.3 is needed, not for runtime, unless the user explicitly activates in web.xml the optional component (it's a SessionListener). Servlet 2.3 will *not* be required to run Cocoon. -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: Update to the Servlet API
Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Sylvain Wallez schrieb: Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Yes, I want to integrate a patch that allows to run an *optional* component on webapp startup to compile XSP. It's only for *compilation* that servlet 2.3 is needed, not for runtime, unless the user explicitly activates in web.xml the optional component (it's a SessionListener). Servlet 2.3 will *not* be required to run Cocoon. A mock sounds like a _much_ better way! Regards, Upayavira
Re: Update to the Servlet API
Upayavira wrote: Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Sylvain Wallez schrieb: Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Yes, I want to integrate a patch that allows to run an *optional* component on webapp startup to compile XSP. It's only for *compilation* that servlet 2.3 is needed, not for runtime, unless the user explicitly activates in web.xml the optional component (it's a SessionListener). Servlet 2.3 will *not* be required to run Cocoon. A mock sounds like a _much_ better way! Mocking a 4-year old specification. This is s dinosaurish in this web 2.0 world... Sylvain -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Update to the Servlet API
Sylvain Wallez wrote: Upayavira wrote: Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Sylvain Wallez schrieb: Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Yes, I want to integrate a patch that allows to run an *optional* component on webapp startup to compile XSP. It's only for *compilation* that servlet 2.3 is needed, not for runtime, unless the user explicitly activates in web.xml the optional component (it's a SessionListener). Servlet 2.3 will *not* be required to run Cocoon. A mock sounds like a _much_ better way! Mocking a 4-year old specification. This is s dinosaurish in this web 2.0 world... Hmm. If the whole spec is required, I can see where Jean-Baptiste is coming from. We could extend the build process to use servlet 2.3 for compilation, but keep the app running with servlet 2.2. Would that actually cause any backwards compatability issues? Regards, Upayavira
Re: Update to the Servlet API
Upayavira wrote: Mocking a 4-year old specification. This is s dinosaurish in this web 2.0 world... Hmm. If the whole spec is required, I can see where Jean-Baptiste is coming from. We could extend the build process to use servlet 2.3 for compilation, but keep the app running with servlet 2.2. Would that actually cause any backwards compatability issues? I think we don't need to moch the whole spec but just the listener. So it's one interface. As soon as we use 2.3 for compilation we can't ensure that noone else is using 2.3 features. With the same arguments we could just upgrade to jdk 1.4 in 2.1.x as well. 2.1.x *is* a maintenance branch. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
Upayavira wrote: Sylvain Wallez wrote: Upayavira wrote: Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Sylvain Wallez schrieb: Jean-Baptiste can elaborate on this, but AFAIU this is because an interesting XSP patch requires a servlet listener, which is something that was added in servlets 2.3. So, he could just add a mock class for the listener to the xsp block, add the listener and we are done with this. Yes, I want to integrate a patch that allows to run an *optional* component on webapp startup to compile XSP. It's only for *compilation* that servlet 2.3 is needed, not for runtime, unless the user explicitly activates in web.xml the optional component (it's a SessionListener). Servlet 2.3 will *not* be required to run Cocoon. A mock sounds like a _much_ better way! Mocking a 4-year old specification. This is s dinosaurish in this web 2.0 world... Hmm. If the whole spec is required, I can see where Jean-Baptiste is coming from. We could extend the build process to use servlet 2.3 for compilation, but keep the app running with servlet 2.2. Would that actually cause any backwards compatability issues? Applications aren't running with the servlet.jar that _we_ provide, as the servlet API is something that is implemented, and therefore provided, by the servlet engine. So our servlet.jar is useful *only* for compilation, and the only backwards compatibility issue that can happen is when the optional 2.3-specific features are used when Cocoon runs on a servlet engine that implements servlet 2.2. If we look at Tomcat, that means using Tomcat 3.3. Are there some people around using Cocoon 2.1.x on Tomcat 3.3? Sylvain -- Sylvain WallezAnyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Update to the Servlet API
So this is one way to get us motivated to get 2.2 out. Carsten Ziegeler said: I think we don't need to moch the whole spec but just the listener. So it's one interface. As soon as we use 2.3 for compilation we can't ensure that noone else is using 2.3 features. With the same arguments we could just upgrade to jdk 1.4 in 2.1.x as well. 2.1.x *is* a maintenance branch. Carsten
Update to the Servlet API
Hello, To implement a servlet context listener for COCOON-1170, I need to update servlet_2_2.jar to a newer version in branch 2.1. Anybody objects to this? Where do I find the « official » servlet jar? -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: Update to the Servlet API
Jean-Baptiste Quenot wrote: Hello, To implement a servlet context listener for COCOON-1170, I need to update servlet_2_2.jar to a newer version in branch 2.1. Anybody objects to this? Where do I find the « official » servlet jar? You can find version 2.3 in the tools/jetty/lib directory. Cocoon 2.1.x is based on version 2.2 of the servlet spec, so I'm not sure if we should change this requirement to 2.3 for a maintenance branch. We should either vote on this or you can add mock classes. For the same reasons I added some mock classes to the portals block (portlets require 2.3) Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Update to the Servlet API
* Carsten Ziegeler: Jean-Baptiste Quenot wrote: To implement a servlet context listener for COCOON-1170, I need to update servlet_2_2.jar to a newer version in branch 2.1. You can find version 2.3 in the tools/jetty/lib directory. Cocoon 2.1.x is based on version 2.2 of the servlet spec, so I'm not sure if we should change this requirement to 2.3 for a maintenance branch. Not necessarily a requirement, because the component I wish to add is optional. This is needed for compilation only. -- Jean-Baptiste Quenot http://caraldi.com/jbq/
