the information is wrong!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
-- Pierre
Jan Luehe wrote:
I'd like to resume discussion on a proposal circulated by James
Strachan on March 13, 2002, about turning the implementation of JSTL's
expression language (EL) into a reusable component and moving it from
the Standard Taglib, an implementation of JSTL
Casey Lucas wrote:
Looking at the rendered jsp - java files in the work directory
(and noticing the calls to Tag.release), I realized that Jasper
is not reusing tags that it creates. So, my question is:
Has there been any conversations about implementing tag
reuse in Jasper?
To my
Casey Lucas wrote:
Ok, I'll bite. Where's the best place to start looking?
Code that does the rendering? Wasn't there at one point talk
of making the renderer more "pluggable"?
Great!
Since you asked, here are some ideas:
As a first step, I'd make sure to clearly understand all the spec
Alex,
Until the expert group rules on this, one workaround (that will always work)
is to simply do the following (assuming a property of type Object):
instead of:
mytags:foo bar="abc"/
use:
mytags:foo bar='%="abc"%'/
Another way is to define a PropertyEditor associated
+1
-- Pierre
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 12:16 PM
To: [EMAIL PROTECTED]
Subject: [VOTE] New Committer: Kief Morris
Kief has recently proposed improvements to the session management code
in
Tomcat 3.3 Release Plan Ballot:
[ ] +1I am in favor of this plan and will help
[X] +0I am in favor of this plan, but am unable to help
[ ] -0I am not in favor of this plan
[ ] -1I am against this plan being executed, and my
reason is:
--
+1 for Shai Fultheim
-- Pierre
Hi Costin,
JspInterceptor is not "enabled" in 3.2 - it was one of the changes I
wanted to spend more time into and make sure it's stable enough. It'll be
used in 3.3 - or whatever will be called.
Thanks for the clarification. However since it is being compiled in the
build, it is "somewhat"
[EMAIL PROTECTED] wrote:
BTW, did you fixed the command line compiler ? JspInterceptor is based on
the command line compiler, so if you fix the first it'll be very easy for
me to fix the 3.3 interceptor.
Sorry, my radar must have missed this one. If you can give me pointers/info,
Trying to close a few Jasper bugs before the holiday break.
I'd appreciate at least another pair of eyes to review what I believe
should be done on that one... -- Pierre
-
Bug #55
-
Synopsis:
Default for included files is 8859_1, with no option to set otherwise.
Report
Hans,
What about the javac encoding? I believe it's currently hardcoded
as "UTF8" (in Compiler at least). I'm not sure what it should be
in case different included pages specify different charsets ...
If you refer to bug report #269, I have a fix coming in the next few minutes.
[testing it
Hans Bergsten wrote:
...
So,
the only possible remaining thing I can think of is to make
sure the encoding specified by jspEncoding is also used as
the "-encoding" argument to the javac command.
It is.
-- Pierre
Tried to back port the last fix I made to Jasper in tomcat 4.0
to tomcat 3.2 (the fix related to bug report #269 -- java encoding).
Was almost there until I realized there is a new class
"JspInterceptor" in tomcat 3.2 that is impacted by that fix.
Unfortunately, I'm not too knowledgeable about
Maybe I'm not reading carefully enough (and I haven't had time to trace the
code) but I don't understand what you mean in your "modifications".
The correct behavior seems to me that when a file is included, a 'fake'
JspReader should be created to scan the file for a @page directive with
+1 for Vasile Gaburici
+1 for Petr Jiricka
+1 for Marc Saegesser
-- Pierre
This seems right. I'll put the fix in tomorrow unless someone objects.
[no need to send a patch].
-- Pierre
"Bucknam, Brian" wrote:
It's a long story, but I'm working on a project where Jasper 3.x is embedded
inside a servlet, which can then be deployed to the container of our
cga wrote:
Hi there,
I was thinking "There is a way to speed up jps". I mean if I take out
white spaces and other unnecesary text out of the html part of a jsp, the
server will send less bytes to the browser so it will be faster.
I am pretending to do a Reader that takes out
Hans Bergsten wrote:
[EMAIL PROTECTED] wrote:
pierred 00/12/09 21:56:44
Modified:jasper/src/share/org/apache/jasper Constants.java
jasper/src/share/org/apache/jasper/compiler
BeanGenerator.java JspParseEventListener.java
Hans Bergsten wrote:
Pierre Delisle wrote:
Hans Bergsten wrote:
[EMAIL PROTECTED] wrote:
pierred 00/12/09 21:56:44
Modified:jasper/src/share/org/apache/jasper Constants.java
jasper/src/share/org/apache/jasper/compiler
Please vote for Dan Milstein as a new commiter for tomcat.
Great! +1
-- Pierre
Hans,
I just tried the examples on tomcat 4.0, and the only
problem I could see is with the source code of
the "number guess" example.
The link in num/numguess.html should be changed from
"/examples/jsp/source.jsp?/jsp/num/numguess.jsp"
to
"numguess.txt"
Otherwise, everything
The JSP spec is quite clear on the subject:
"The only types of properties that can be assigned to from String
constants and request parameter values are those listed in TABLE 2-4; the conversion
applied
is that shown in the table. Request-time expressions can be assigned to properties of
any
(1) Build and release Tomcat 3.2 final on Wednesday 11/29/2000
+1
(2) Ongoing Support Plan for Tomcat 3.2
+1
(3) Release Manager for Tomcat 3.2.x Maintenance Releases
+1
-- Pierre
Rob Saccoccio wrote:
Would it be possible to change the generated _jspService() method to catch
Throwable instead of Exception? JSP 1.2 is taking this direction (excerpt
and patch below).
Just committed the fix in tomcat-4.0 (since this is JSP1.2).
+
Christian,
Thanks for the patch. I've just aplied it to tomcat-4.0.
As for tomcat-3.2, I will be porting patches there *only* if this
is approved by Craig (since we are so close to an official release
of 3.2).
-- Pierre
"Schmitt, Christian" wrote:
Hi all,
we've been working with TC
Larry Isaacs wrote:
When applying Gareth Morgan's bug fix for JspRuntimeLibrary in the Tomcat MAIN
branch, a difference between the tomcat_32 and MAIN versions revealed that
Tomcat 3.2 still has the bug discovered by Glenn Nielsen. This is where:
jsp:setProperty name="bean"
Bug report #412 has just been filed.
Synopsis:
public void removeAttribute(String name) does not work properly
Description:
lt. spec from sun this method is required to remove
the attribute from every scope. in class PageContextImpl
however this only removes attributes from the page
Larry Isaacs wrote:
...
I'll try to commit a patch that fixes just the following:
1) Fix value="" without allowing param="..." to set.
2) For a String array property, make "?prop=prop=text" set the
property for property="*". Currently property="*" handling
assumes only simple
Larry Isaacs wrote:
I'm +1 on fixing the jsp:setProperty name="bean" property="prop" value=""/
bug in Tomcat 3.2.
+1
If the desired behavior for indexed properties can be
determined, I can try to fix that too.
Sent email to Eduardo to try to get a clarification.
-- Pierre
To: 'Pierre Delisle '
Cc: '[EMAIL PROTECTED]'
Sent: 11/15/00 9:55 PM
Subject: RE: lock
Hi Pierre,
I saw the same thing a little after 5:00 PM when I tried a commit some
changes to this directory. After about 5 minutes of this, I aborted and
logged out of jakarta.apache.org. I have tried
Brian Bucknam wrote:
Craig says all the critical bugs are fixed, and it seems maybe they are.
However, there is still a problem (see bug #215) in TagLibraryInfoImpl which makes
it so that tag libraries cannot be packaged in .jar files. (3.2b7 (and 3.1) at least
not on Windows, have not
Boyd,
I cannot really use the XML representation, because the jsp:cdata tag
doesn't work with current Tomcat-4.0-devel. I get classCastExceptions if
I try to use this tag.
But you could still use ![CDATA[ ... ]] for your CDATA.
jsp:cdata should be in tomcat-4.0 befroe the end of the
33 matches
Mail list logo
