Re: [Resin-interest] SAXParseException when using (jakarta's) JSTL in JSP (Resin 3.1)
Olaf Krische wrote: > Hello, > > currently i am trying to make my application of mine Resin 3.1 ready, while > it can still run on Resin 2.1. For this i use the jakarta standard tag > library (1.0.6), not for the tag implementations, but for its > EvaluationManager to be able to use EL in my tags. > > Ok, this is what i do: > > 1. Download Resin 3.1 snapshot (resin-3.1.s080126) > 2. Starting with "java -jar lib/resin.jar start" > 3. http://localhost:8080/resin-doc/index.jsp > > Works perfectly. > > 4. Now i add to resin-doc a new file "indexXML.jsp". > 5. I add the standard.jar (1.0.6) to resin-doc/WEB-INF/lib/ > 6. Receiving now a SAXParseException, when calling > http://localhost:8080/resin-doc/indexXML.jsp > > I dont know, what exactly is broken here. Any idea? > > This is the complete exception message (jsp source is below) > > 500 Servlet Exception > > /indexXML.jsp:1: org.xml.sax.SAXParseException: The prefix "c" for element > "c:set" is not bound. > > 1: > 2: http://www.w3.org/1999/xhtml"; > xmlns:jsp="http://java.sun.com/JSP/Page"; > xmlns:c="http://java.sun.com/jstl/core"; version="2.1"> > 3: > > I think in resin 3.1.x you should use http://java.sun.com/jsp/jstl/core for the "c" JSTL tags. (note the extra "/jsp/") - Erik - ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] SAXParseException when using (jakarta's) JSTL in JSP (Resin 3.1)
It seems to work better if you use Rein's XML parser, i.e. add this to your resin.conf: javax.xml.parsers.DocumentBuilderFactory="com.caucho.xml.parsers.XmlDocumentBuilderFactory" /> javax.xml.parsers.SAXParserFactory="com.caucho.xml.parsers.XmlSAXParserFactory" /> There is a bug that looks very similar to this: http://bugs.caucho.com/view.php?id=1647 that was marked as fixed in version 3.1.1 -- maybe it's not completely fixed after all? - Erik - Olaf Krische wrote: Hello Erik, thank you for your answer. And yes, you were right about the missing 'jsp' . My heart started to bump. I have changed the example accordingly. Sadly, the error will not disappear: /indexXML.jsp:1: org.xml.sax.SAXParseException: The prefix "c" for element "c:set" is not bound. 1: 2: http://www.w3.org/1999/xhtml"; xmlns:jsp="http://java.sun.com/JSP/Page"; xmlns:c="http://java.sun.com/jsp/jstl/core"; version="2.1"> 3: Erik Forkalsrud wrote: Olaf Krische wrote: 1. Download Resin 3.1 snapshot (resin-3.1.s080126) 2. Starting with "java -jar lib/resin.jar start" 3. http://localhost:8080/resin-doc/index.jsp Works perfectly. 4. Now i add to resin-doc a new file "indexXML.jsp". 5. I add the standard.jar (1.0.6) to resin-doc/WEB-INF/lib/ 6. Receiving now a SAXParseException, when calling http://localhost:8080/resin-doc/indexXML.jsp I think in resin 3.1.x you should use http://java.sun.com/jsp/jstl/core for the "c" JSTL tags. (note the extra "/jsp/") The changed indexXML.jsp: http://www.w3.org/1999/xhtml"; xmlns:jsp="http://java.sun.com/JSP/Page"; xmlns:c="http://java.sun.com/jsp/jstl/core"; version="2.1"> de_AT ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin & Wildcard SSL Certs?
We have used wildcard SSL certificates with resin 2.1.x using both OpenSSL and JSSE, and that worked fine. I don't remember if I have tested it specifically for 3.1.x, but I see no reason why it wouldn't work. - Erik - On 06/23/2009 02:34 PM, Rob Lockstone wrote: > Does anyone know if Resin (Pro 3.1.9 64-bit with OpenSSL) would have > any problems handling a wildcard ssl certificate, as opposed to a > domain specific cert, e.g. *.blahblah.com vs. poolOne.blahblah.com, > poolTwo.blahblah.com, poolThree.blahblah.com. > > We're considering getting one because a few of our pools require ssl > and it's easier to manage, though more expensive, to get just one > certificate for all of them rather than deal with multiple different > certs for the different pools (i.e. remembering to renew them and make > sure they're deployed, etc). > > We know it works with IIS, but have never tried a wildcard cert with > Resin and OpenSSL. I wouldn't anticipate there being a problem, but > obviously we'd rather not spend the money only to find out it won't > work for some reason. Anyone know? > > Rob > > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Documentation bug?
The documentation for the tag (http://caucho.com/resin-3.1/doc/server-tags.xtp#keepalive-max) states: "A value of -1 disables keepalives." I tried this with resin-3.1.8 and it appears to still use keep-alive with that setting. If I follow the source code correctly, resin will use an effective setting of 256 if the config file specifies a value less than zero. However, a setting of "0" (zero) appears to disable keepalives. -- Erik ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
