Re: JSF Newbie
Here's the solution from Hans Bergsten: quote Hiroshi, I recommended your book at the Tomcat mailing list: quote Try this: http://www.hansbergsten.com/downloadjsf.jsp This is perfect and easy to use. Thanks, but the problem this guy describes has nothing to do with JSF, actually. Most likely he has an old version of the JSP JAR file in the standard extensions directory, typically JAVA_HOME/jre/ext. JAR files from this directory overrides all others, so he's not picking up the later JSP version bundled with Tomcat 5. That's why he get the exception. Hans /quote Younes El Moumen wrote: Hi, I'm using Tomcat 5.0.27 J2sdk 1.4.2_04 jsf1_1 I'm Trying to use JSF, I've tried many Tutorials examples and installed many Tomcat Versions but i become every Time the same error can anybody help me? Thanks. StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception java.lang.NoSuchMethodError: javax.servlet.jsp.tagext.TagAttributeInfo.init(Ljava/lang/String;ZLjava/lang/String;ZZ)V at org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java:568) at org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java:401) at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:248) at org.apache.jasper.compiler.TagLibraryInfoImpl.init(TagLibraryInfoImpl.java:179) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) at org.apache.jasper.compiler.Parser.parse(Parser.java:126) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:101) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:470) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312) at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:147) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at
Is the Tomcat5 documentation correct for this?
Hi, http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html says: Pathname to a scratch directory to be provided by this Context for temporary read-write use by servlets within the associated web application. This directory will be made visible to servlets in the web application by a servlet context attribute (of type java.io.File) named javax.servlet.context.tempdir as described in the Servlet Specification. If not specified, a suitable directory underneath $CATALINA_HOME/work will be provided. I have a setup where I have multiple Tomcat instances using the same $CATALINA_HOME, but each get's a different $CATALINA_BASE set on startup. For each Tomcat instance I have a work directory below $CATALINA_BASE, not a combined one for all instances in my binaries CATALINA_HOME. I doubt it would work if \work\Catalina\localhost has e.g. the temp jsp class files of all Tomcat instances. So I guess it must be: If not specified, a suitable directory underneath $CATALINA_BASE/work will be provided. Greetings Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is the Tomcat5 documentation correct for this?
Ignore this... I skipped reading this part: The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references. :) Michael Echerer wrote: Hi, http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html says: Pathname to a scratch directory to be provided by this Context for temporary read-write use by servlets within the associated web application. This directory will be made visible to servlets in the web application by a servlet context attribute (of type java.io.File) named javax.servlet.context.tempdir as described in the Servlet Specification. If not specified, a suitable directory underneath $CATALINA_HOME/work will be provided. I have a setup where I have multiple Tomcat instances using the same $CATALINA_HOME, but each get's a different $CATALINA_BASE set on startup. For each Tomcat instance I have a work directory below $CATALINA_BASE, not a combined one for all instances in my binaries CATALINA_HOME. I doubt it would work if \work\Catalina\localhost has e.g. the temp jsp class files of all Tomcat instances. So I guess it must be: If not specified, a suitable directory underneath $CATALINA_BASE/work will be provided. Greetings Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dipl.-Inf. (FH) Michael Echerer TNG Technology Consulting GmbH, http://www.tngtech.com Betastr. 13a, 85774 Unterföhring bei München, Tel. +49 89 2158996-0, Fax. +49 89 2158996-9, Mobile +49 176 20088854 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
migrating from 4.1 to 5.0
Hi, During developement I tries to copy my app from 4.1/webapps to 5.0/webapps, only my application won't start: Jul 24, 2004 11:45:04 AM org.apache.catalina.core.StandardHostDeployer start: INFO: standardHost.start /tutim Jul 24, 2004 11:45:04 AM org.apache.catalina.core.StandardContext resourcesStart SEVERE: Error starting static Resources java.lang.IllegalArgumentException: Document base /var/struts/jakarta-tomcat-5.0.27/server/webapps/tutim does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:138) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4138) at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:830) at org.apache.catalina.core.StandardHost.start(StandardHost.java:991) at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1322) at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:530) at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:104) . I checked permisions and they are ok - Did I miss something? Cheers, Ron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: getReader() BUG in tomcat 4.1.30 and beyond ?
Yoav Shapira wrote thusly: I saw your message on tomcat-user. Several other Tomcat developers also follow that list. I personally looking at the stack trace chose to discard your message for a few reasons: You reply is retarded; more signifantly you are not and have never been a core developer ON THE JSP CODE. What you choose to do is irrelevant. The bug is very real. That my twice posted message (on both dev and user) got no response from core developers is frightening. - The AJP connector in the stack trace indicates Apache in front of Tomcat, making Apache and the AJP connector possible culprits. Unless you reproduce this with Tomcat standalone, I'm not convinced. A simple servlet using the same setup does not display the bug. I can getInputStream() OR getReader() from a servlet's doPost method and print out the entire POST'ed body. The bug only happens for JSP's in tomcat 4.1.30 and beyond. - The fact it's 4.1.30, which is a mature branch that's been in the market for a while, and if what you're reporting is really true we would have heard about it via bug reports a long time ago. 'tis better to remain silent and appear a fool than to speak and remove all doubt ... (and your above statement removes all doubt). - Also being on a 4.x release, I'm not as interested, because only 5.x is being actively developed. If you reported this error on 5.0.27 standalone tomcat I suspect you would have gotten replies on the tomcat- user list from me and others. Don't matter if you are interested or not. The bug is real and needs to be fixed by the core developers for the hundreds of thousands of people who are using the stable 4.1.x branch today. And if the core developers are so cock-sure that this is not a bug, then why don't they at least say that they could NOT replicate this ? After all, the sample jsp that shows the bug is only a few lines long and extremely simple to test. Again, I don't know what is more troubling: the severity of this bug, your post, or the total lack of response from the core jsp developers (one way or another) Best regards, --j __ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat5 Win32 binaries location
In the doc, it talks about using the windows installer to install Tomcat5. I cannot find a 'release' or any other distribution which uses the Windows Installer (.msi file type). If anyone can send me a URL which points to the Win32 inary distribution, I would appreciate it. Thnaks
Re: getReader() BUG in tomcat 4.1.30 and beyond ?
FWIW (I must have too much free time) I tried your hello world example as a recipient of a posted form and it seems to work just fine for me with either request.getReader or request.getInputStream. Though I was using TC 5.0.25 (standalone) and even tried it in IBM WAS 5.1 Test Environment. Works fine everywhere from what I can see. Mike j.random.programmer wrote: Yoav Shapira wrote thusly: I saw your message on tomcat-user. Several other Tomcat developers also follow that list. I personally looking at the stack trace chose to discard your message for a few reasons: You reply is retarded; more signifantly you are not and have never been a core developer ON THE JSP CODE. What you choose to do is irrelevant. The bug is very real. That my twice posted message (on both dev and user) got no response from core developers is frightening. - The AJP connector in the stack trace indicates Apache in front of Tomcat, making Apache and the AJP connector possible culprits. Unless you reproduce this with Tomcat standalone, I'm not convinced. A simple servlet using the same setup does not display the bug. I can getInputStream() OR getReader() from a servlet's doPost method and print out the entire POST'ed body. The bug only happens for JSP's in tomcat 4.1.30 and beyond. - The fact it's 4.1.30, which is a mature branch that's been in the market for a while, and if what you're reporting is really true we would have heard about it via bug reports a long time ago. 'tis better to remain silent and appear a fool than to speak and remove all doubt ... (and your above statement removes all doubt). - Also being on a 4.x release, I'm not as interested, because only 5.x is being actively developed. If you reported this error on 5.0.27 standalone tomcat I suspect you would have gotten replies on the tomcat- user list from me and others. Don't matter if you are interested or not. The bug is real and needs to be fixed by the core developers for the hundreds of thousands of people who are using the stable 4.1.x branch today. And if the core developers are so cock-sure that this is not a bug, then why don't they at least say that they could NOT replicate this ? After all, the sample jsp that shows the bug is only a few lines long and extremely simple to test. Again, I don't know what is more troubling: the severity of this bug, your post, or the total lack of response from the core jsp developers (one way or another) Best regards, --j - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to know which xml file (under directory webapp) causes SAXParseException ?
Howdy, When TC gets SAXParseException (such as following ), how to know *which* XML file , usually under $TC$webapp/, cause the error? It seems there is no file info about the XML file. TIA == SAXParseException fatal: Parse Error at line 2 column 74: Document root element web-app, must match DOCTYPE root null. org.xml.sax.SAXParseException: Document root element web-app, must match DOCTYPE root null. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ... ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jk2, apache2, tomcat5, on redhat 9 issue
Hello; I am trying to install tomcat so that many of my users can use jsp with there virtual hosts in apache. I have looked through the archives and docs on this and there seems to be good info, but I am running into a strange problem when I try to build the mod_jk2 for apache I have no apxs installed on my system. what is the apxs? and why do I not have it anywere on my system. I have apache2 installed via rpm and I cannont build the mod_jk2 Is there a binary that I can download for this? Any help building this module and setting up virtual hosts would be great! Thanks Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2, apache2, tomcat5, on redhat 9 issue
You will need to install the httpd-devel rpm as well. This will give you apxs and other material needed to compile mod_jk2. You might check on yum to see if mod_jk2 is already compiled. It is for Fedora Core 2. I don't know if it is for Redhat 9. I build my own Apache, mod_jk2, etc. from source so all I can tell you is what Synaptic, yum, and rhn tell me. /mde/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
