Thanks,
You have solved my problem. I will use this solution.
On the other hand, I have read in some place that when an absolute URI, like
http://java.sun.com/jstl/fmt, is used, it don't have to be added the taglib
element to web.xml ; the JSP container automatically locates the TLD inside
the
Hi all. I am new to the list and new to JSP/Custom Tags/JSTL, although I
have worked with another App Server (Dynamo) for a few years now. Just
trying to figure out how Tomcat/JSTL/Struts etc works.
I am using Tomcat 4.1.12 and the jakarta 1.0 JSTL.
I have simple custom tag that works fine - no
Good call on using the same text in an article, was about to transfer
suspicion to the piece of text in the article :)
So.. that suggests something odd in bean:write. As a quick check, because
I've got it setup, the following does work:
%@ taglib prefix=c uri=http://java.sun.com/jstl/core; %
%@
It's been discussed to add it to the Servlet spec a few times, but it
gets shut down every time because it's not obvious how it should look
like to handle all possible requirements and still be easier to use
than one of the existing third-party solutions (like Jason's filter
and parsing classes).
I downloaded the DateTime taglib yesterday and set it up for one of my
JSP's. But I got the following error message:
org.apache.jasper.JasperException: null(-1,-1) This absolute uri
(http://jakarta.apache.org/taglibs/datetime-1.0) cannot be resolved in
either web.xml or the jar files deployed
Well I know one thing for sure, uploading files is standard 'out of the box'
with ASP.net. That is one thing that makes me scratch my head about the Java
platform, there are many common things that are used constantly in web
programming that are not directly addressed in a reasonable manner:
On Thu, 7 Nov 2002, Stefan wrote:
Well I know one thing for sure, uploading files is standard 'out of the box'
with ASP.net. That is one thing that makes me scratch my head about the Java
platform, there are many common things that are used constantly in web
programming that are not
I also use a non-Latin language, Chinese, in my current project. Only time I get
question mark, if I can recall correctly, is
the key is not set up properly in the property file. In JSP file, I have the following
encode setting:
%@ page contentType='text/html; charset=UTF-8' %
I don't set
Sorry, I just got to get in on this!
Stefan wrote:
Well I know one thing for sure, uploading files is standard 'out of the box'
with ASP.net. That is one thing that makes me scratch my head about the Java
platform, there are many common things that are used constantly in web
programming that
Please Note, This is all in good taste! ;-) Just fueling the fires of
debate.
-Mark
Mark R. Diggory wrote:
Sorry, I just got to get in on this!
Stefan wrote:
Well I know one thing for sure, uploading files is standard 'out of
the box'
with ASP.net. That is one thing that makes me scratch
Okay, next attempt Calvin :)
%@ taglib prefix=bean uri=/WEB-INF/struts-bean.tld %
%@ taglib uri=http://jakarta.apache.org/taglibs/string-1.0; prefix=str %
%
session.setAttribute(foo, new java.util.EventObject(ga\nar) );
%
str:replace replace=NL with=br newlineToken=NLbean:write name=foo
IMHO a framework should provide the core functionality that most people will
need. Examples are session handling, parsing post and so on. I just believe
that there are many things like processing multipart form submissions that
have not been properly addressed. I think that file upload, automatic
Stefan wrote:
My 2 cents.
Please no flames, I'm just a poor little geek! :)
Stefan
I'm certainly not against speaking ones mind! ;-) I'm sure .NET is here
to stay as well. It certainly doesn't hurt to have alot of tools in your
tool box.
--
To unsubscribe, e-mail:
I wrote earlier today about being unable to use the datetime taglibs.
Now I just installed the dbtags and I am unable to use that as well. I'm
getting the same error message as before:
This absolute uri (http://jakarta.apache.org/taglibs/dbtags) cannot be
resolved in either web.xml or the jar
That works for me as well. Would it have something to do
with how it's store in MySQL? I've always treated newlines
as \n when working with MySQL and PHP and haven't had a
problem.
--- Henri Yandell [EMAIL PROTECTED] wrote:
Okay, next attempt Calvin :)
%@ taglib prefix=bean
Jeff Self wrote:
I downloaded the DateTime taglib yesterday and set it up for one of my
JSP's. But I got the following error message:
org.apache.jasper.JasperException: null(-1,-1) This absolute uri
(http://jakarta.apache.org/taglibs/datetime-1.0) cannot be resolved in
either web.xml or the jar
I have the same problem. I had a JSP with JSTL working fine on
Tomcat 4.1.12 running on W2000 and MacOSX. I moved the webapp to
the same version of Tomcat on a Linux and it bombed...
All three environments had different JVMs:
Win200 - JDK 1.4.0
MacOSX - JDK 1.3.1
LINUX - JDK 1.4.1
I've
I've ran into something like this error a few times. On MacOS X. Its
a really obscure little boo-boo that I don't really quite know exactly
how it happens, but I suspect it mainly has something to do with the
placement of the JAR files for the XML parser. Try making sure that
you don't have
Apologies if this is in one of the books on JSTL, I've only got Shawn's
and it's not in there afaik.
It's a little JSTL snippet which dumps a database table to the screen.
Such things in Java are easy enough to write, but I felt that one in JSTL
would be educational [for myself]. Posting here
Given the following code:
% taglib prefix=c uri=http://java.sun.com/jstl/core; %
c:if test=${param.one}
FOOO
/c:if
c:choose
c:when test=${param.two}
c:out value=BING/
/c:when
c:when test=${param.one}
c:out value=BONG/
/c:when
c:otherwise
c:out value=BANG/
/c:otherwise
/c:choose
Henri == Henri Yandell [EMAIL PROTECTED] writes:
Henri I'd like to do the following:
Henri jsp:forward page=somePage.jsp
Henri jsp:param name=id value=${param.id}/
Henri /jsp:forward
Henri Now, obviously this is not going to work until JSP 2.0.
Henri So then there's
On 7 Nov 2002, David M. Karr wrote:
Shouldn't it be the following instead?
c:if test=${!empty param.one}
FOOO
/c:if
c:choose
c:when test=${!empty param.two}
c:out value=BING/
/c:when
c:when test=${!empty param.one}
c:out value=BONG/
/c:when
c:otherwise
On 7 Nov 2002, David M. Karr wrote:
Just use different quotes at the other level:
jsp:forward page=somePage.jsp
jsp:param name=id value='c:out value=${param.id}/'/
/jsp:forward
Nope, not happy. I had:
jsp:forward page='c:out value=${param.goto}/'
jsp:param name=id value='c:out
Henri == Henri Yandell [EMAIL PROTECTED] writes:
Henri On 7 Nov 2002, David M. Karr wrote:
Just use different quotes at the other level:
jsp:forward page=somePage.jsp
jsp:param name=id value='c:out value=${param.id}/'/
/jsp:forward
Henri Nope, not happy. I
24 matches
Mail list logo
