Which versions of JSTL tag to use ? el or -rt
If I am constantly moving variables and objects between JSP and JSTL, should I consider switching to the -rt version of the tag. I am not sure what is there performance implications of rtexprvalue - tag lib. Is it advisable to mix them both. All most all the doc I have seen on JSTL only talk about the EL version. Are there any recommendations that you can come with, given the nature of the code and the page content what version of the JSTL tag lib is better suited. By reading JSTL Action book seem to prefer the core EL version. JSTL is the best of thing that has happened to the JAVA, It really opens up of lot of options with JSP. Some of these tags makes the JSP pages very powerful, like the sql, import, and iteration tags. JSTL is very good for developing content management, template based architecture or any data driven web application. I can't wait to see JSTL become part of standard JAVA. -dave
Struts/CTLX/dreamweaver integration
Dear all, I try again now to ask...;-) I have the problem to get this struts taglibs work within dreamwaever. Short description: I followed the documentation from Dan which can be found in the ctlx section of jakarta. I can choose a tag lib from the poplist box within dw4 (struts, struts-bean etc.) BUT when I press 'Use Tag Library' I get an error message like 'Tag lib xy is not found on server'. The tomcat console shows a connection time out. I tried to recontruct what the useTabLibs.js (part of the dreamweaver extension) does. The 'query' to fill fill the poplist in dw can be executed with a browser (http://localhost:8080/TLDParser/servlet/TLDParser?mode=tdlist). The result is 'the list' of the three .tld files within the CATINA_HOMEwebapps/TLDParser/tlds/ directory. The second 'query' resp. the command to 'use taglibs' fails within dw4 and in a browser (http://localhost:8080/TLDParser/servlet/TLDParser?mode=ultradevprefix=struts (struts or struts-bean etc)). Nothing happens if you enter this as an URL... Any ideas what is missing / wrong configured?? Is a parser (Xerces) missing? Any further configuration needed Thanks for any hint!!! Best wishes, olli P.S. I tried on a WinNT, W2K and WinXP localhost and a tomcat on Solaris -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: c:import full windows path
On Fri, 9 Aug 2002, Amarant Merah wrote: Is it possible to import a file based on full path? e.g. E:/somepath/myfile.xml I understand it is possible to import using full http url or relative to webapp like these: c:import url=http://domain.com/somepath/myfile.xml; var=xml/ c:import url=/somepath/myfile.xml var=xml/ I need something like c:import url=E:/abc/somepath/myfile.xml var=xml/ and the above doesn't work. Yes, you'd use a 'file' URL, as with a browser. For instance: c:import url=file:///e:/abc/somepath/myfile.xml / -- Shawn Bayern JSTL in Action http://www.jstlbook.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
problems using dbtags with Tomcat4.0
Hi there! I am using dbtags lib for accessing database from client side (jsp). It works fine with Tomcat3.0, but when I use the same thing in Tomcat4.0 it's falling over. The error reads - java.lang.VerifyError: (class: org/apache/jsp/log$jsp, method: _jspService signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Incompatible object argument for function call at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:237) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.load(JspServlet.java:138) . .. .. I don't understand why it's happening as the only thing I did was to move from Tomcat3.0 to Tomcat4.0. In web.xml, withinn webapp tag- I had the taglib property value tag as the last one. Any ideas what I am missing or where I am going wrong?? Any help would be greatly appreciated.Thanks. regards, Madhavi -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
