i haven't found a resolution to a problem previously posted under another subject, since it fits this topic I thought i'd put it out there again.
I started my app using struts tags, and recently incorporated jstl. Unfortunately I get an error when I import both struts-bean.tld and c.tld c.tld: <uri>http://java.sun.com/jstl/core</uri>) struts-bean.tld: <uri>http://jakarta.apache.org/struts/tags-bean-1.0.2</uri>) i.e. when these 2 taglib directives appear on a single .jsp <%@ taglib uri="/WEB-INF/c.tld" prefix="c" %> <%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %> i get the following exception: jsp.error.tlv.invalid.page null: org.xml.sax.SAXParseException: Attribute "xmlns:bean" was already specified for element "jsp:root". FULL ERROR MESSAGE ``````````````````````````````````````````````````````````` HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: jsp.error.tlv.invalid.page null: org.xml.sax.SAXParseException: Attribute "xmlns:bean" was already specified for element "jsp:root". at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler. java:105) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:430 ) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:112 ) at org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:661) at org.apache.jasper.compiler.Validator.validate(Validator.java:613) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:230) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:369) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:4 73) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1 90) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) Loren Hall -----Original Message----- From: Siggelkow, Bill [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 11:23 AM To: 'Struts Users Mailing List' Subject: RE: Combining struts and JSTL tags... Basically, any of the struts tags that are "struts-aware" were not eliminated from Struts-EL -- specifically, the bean:message tag was not eliminated because it specifically looks in the application resources as specified in struts-config. The <fmt:message> can be made to look into that bundle but it does not by default the way the <bean:message> tag does. You might want to take a look at the my presentation http://www.jadecove.com/articles/jstl-and-struts.pdf to the Atlanta Struts User Group. In addition, be sure and read the readme file in the contrib/struts-el folder. -----Original Message----- From: Jarnot Voytek Contr AU HQ/SC [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 2:08 PM To: 'Struts Users Mailing List' Subject: RE: Combining struts and JSTL tags... fmt:message > -----Original Message----- > From: Paananen, Tero [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2003 1:07 PM > To: 'Struts Users Mailing List' > Subject: RE: Combining struts and JSTL tags... > > > > > I am using the "html" library from struts, otherwise use JSTL > > > libraries for my other requirements. I was curious if anybody > > > uses both these tag libraries together ? If so, which ones do > > > you use from which library and why ? Also, is there any > > > document/article comparing the 2 tag libraries ? > > > > The Struts web site recommends that you use JSTL instead of > > the bean and logic taglibs. > > I don't think there's an equivalent of the bean:message > tag in JSTL, if you want to continue using the > MessageResources mechanism. > > So it's JSTL instead of bean and logic, except for > bean:message? > > -TPP > > ----------------------------------------- > This email may contain confidential and privileged material > for the sole use of the intended recipient(s). Any review, > use, retention, distribution or disclosure by others is > strictly prohibited. If you are not the intended recipient > (or authorized to receive for the recipient), please contact > the sender by reply email and delete all copies of this > message. Also, email is susceptible to data corruption, > interception, tampering, unauthorized amendment and viruses. > We only send and receive emails on the basis that we are not > liable for any such corruption, interception, tampering, > amendment or viruses or any consequence thereof. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
