Re: [Resin-interest] php.ini and include_path

2010-08-30 Thread Alexandre Bertails
2010/8/27 Emil Ong e...@caucho.com: Hi Alexandre, Sorry, I still don't understand one point.  What are you expecting ${RESIN} to be?  Are you setting this as an environment variable or is that something you think the container should set? Aside from that point, relative include paths are

Re: [Resin-interest] java.io.IOException: can't clear response after writing headers

2010-08-30 Thread Aaron Freeman
This is unrelated, but worth mentioning to other people converting over from Resin 3.0.x: We had this problem when converting over from Resin 3.0.x.: The problem is that Resin 4.0.x now outputs white space in each iteration of c:forEach .../c:forEach loops, and other places where Resin

Re: [Resin-interest] java.io.IOException: can't clear response after writing headers

2010-08-30 Thread Scott Ferguson
Morawetz, Martin wrote: Resin is being more strict about conforming to the servlet/JSP spec. Is there an output flush() anywhere before that clear()? -- Scott Yes there is, and removing the out.flush() resolves the issue. Was that 'being more strict' a recent change? The same code

Re: [Resin-interest] php.ini and include_path

2010-08-30 Thread Emil Ong
Hi Alexandre, That's much clearer -- I got thrown by the word RESIN and that you planned to use Jetty. Unfortunately the variable isn't available at in php.ini at the moment. Of course you're right that the include path is relative to the current script, so that's not a real solution. I've

Re: [Resin-interest] php.ini and include_path

2010-08-30 Thread Alexandre Bertails
2010/8/30 Emil Ong e...@caucho.com: Hi Alexandre, That's much clearer -- I got thrown by the word RESIN and that you planned to use Jetty.  Unfortunately the variable isn't available at in php.ini at the moment.  Of course you're right that the include path is relative to the current script,