Tomcat 4.0.4 (and any Tomcat 4.x) supports JSP 1.2, and on JSP 1.2, you
should use doFinally() to clear any invocation-specific state.
Shawn
On 15 Oct 2002, Felipe Schnack wrote:
> Yes, but probably I'll have doFinally only when I migrate to tomcat
> 4.1.12 right? Right now I'm using tomcat 4
Shawn Bayern wrote:
> On 15 Oct 2002, Felipe Schnack wrote:
>
>
>>i don't know, but in my opinion, we shouldn't call release() at every
>>doEndTag(), but we should clean, for instance, tag attributes and these
>>such things.
>
>
> To reiterate, you should not reset tag attribute values in do
Yes, but probably I'll have doFinally only when I migrate to tomcat
4.1.12 right? Right now I'm using tomcat 4.0.4, I want the 4.1.x to
become more stable before I upgrade my systems. I just want to keep my
taglibs as much compliant as they can be with these versions...
what you gurus suggest
+1
I think this is an excellent suggestion.
Thomas Gideon
Sr. Software Developer
B2eMarkets
301.230.2236 Tel.
301.230.2248 Fax.
[EMAIL PROTECTED]
www.B2eMarkets.com
> -Original Message-
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 2002 4:21 PM
> To
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 2002 8:25 AM
> To: [EMAIL PROTECTED]
> Subject: Shortest date format
>
>
> Hi
>
> Is there any chance that JSTL could get a date format that's
> even shorter
> than "short"? I mean
On a somewhat related note, I've been wondering if the EL-functions as
discussed here shouldn't have an implicit pageContext argument.
For instance, if the TLD specified a function like:
isUserInRole
mypkg.MyFunctions
boolean isUserInRole(PageContext, String)
On 15 Oct 2002, Felipe Schnack wrote:
> i don't know, but in my opinion, we shouldn't call release() at every
> doEndTag(), but we should clean, for instance, tag attributes and these
> such things.
To reiterate, you should not reset tag attribute values in doEndTag().
doEndTag() should hardly
hmmm...
i don't know, but in my opinion, we shouldn't call release() at every
doEndTag(), but we should clean, for instance, tag attributes and these
such things. If you clean everything a tag uses in its lifecycle, you're
throwing away most of the advantage of tag reuse
On Tue, 2002-10-15 a
Halvorson, Loren wrote:
> Hans,
>
> I just had a look at the dbtags source and see why it worked. The release()
> method was already being called manually within most of the doEndTag()
> methods. Unfortunately their release() wasn't doing a complete job because
> it failed to call super.release(
Hans,
I just had a look at the dbtags source and see why it worked. The release()
method was already being called manually within most of the doEndTag()
methods. Unfortunately their release() wasn't doing a complete job because
it failed to call super.release().
Example from ResultSetTag.java
Adding super.release() solved it for me for both Tomcat 4.1.12 and WebLogic
6.1 SP2. I didn't delve deep into the lifecycle of each tag, but this fix
seemed to be exactly what the tags need. So any takers?
--Loren
-Original Message-
From: Hans Bergsten [mailto:[EMAIL PROTECTED]]
Sent:
Halvorson, Loren wrote:
> OK I think I have a handle on what is wrong with the dbtags.
>
> Almost every tag forgets to call super.release() In their release() method.
> This doesn't cause any problems if your container doesn't recycle tags.
>
> public void release() {
> super.release(); <
OK I think I have a handle on what is wrong with the dbtags.
Almost every tag forgets to call super.release() In their release() method.
This doesn't cause any problems if your container doesn't recycle tags.
public void release() {
super.release(); <--- this needs to be added
_positi
On Tue, 15 Oct 2002, Stefan wrote:
> Is it the eventual aim to eliminate the use of the in
> JSP, replacing them with taglibs?
It's hard to answer that question in general. From my perspective,
there's little reason to use as of JSTL 1.0, though there
are exceptions: is useful to instantiat
Is it the eventual aim to eliminate the use of the in JSP,
replacing them with taglibs?
Stef
- Original Message -
From: "Shawn Bayern" <[EMAIL PROTECTED]>
To: "Tag Libraries Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, October 15, 2002 1:10 PM
Subject: Re: Beefing up JSTL EL in JSP
> -Original Message-
> From: Hans Bergsten [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 14, 2002 3:26 PM
> To: Tag Libraries Users List
> Subject: Re: Beefing up JSTL EL in JSP 2
>
>
> Martin Cooper wrote:
> >
> >>-Original Message-
> >>From: Hans Bergsten [mailto:[EMAIL
Here's a little more information on the tag pooling problem we are having
with dbtags under Tomcat 4.1.12. I thought I'd try a work around that
avoided the statement and query tags altogether and just do them manually.
Now the second resultSet iterates and outputs all of the items from the
_first
On Tue, 15 Oct 2002, Wolfgang Röckelein wrote:
> I see that, too. JSP/JSTL/EL is DO and not OO. However, the decision
> remains how to deal with user input submissions which usually require
> some action (if it is not merely a change in a display format etc.,
> but e.g. a new entry, a changed ord
We are seeing some strange behavior from dbtags since we switched to Tomcat
4.1.12. I'm pretty sure it's related to the new tag pooling feature of
Tomcat. I am wondering if anyone else is having problems.
If we have two statements on the same page, where the first one returns
rows, but the secon
Hi,
just adding my cents...
Gideon, Thomas wrote:
> Maybe it's just me but I don't see JSP as intrinsically OO. Even if one
> tries to cram them, incorrectly in my mind, into the category of a 4GL
> technology. JSP as it relates to HTML, and even to a large extent XML, is
> about document orie
mm/dd have no logic
not to mention the metric system stuff :-)))
On Tue, 2002-10-15 at 13:40, Jon Archer wrote:
> > And frankly, I don't think I should code this by hand (the English having
> > mm/dd, most others having dd/mm) when usually gives me
> > all I need
>
> Eric, (and I apologise
> And frankly, I don't think I should code this by hand (the English having
> mm/dd, most others having dd/mm) when usually gives me
> all I need
Eric, (and I apologise in advance that this is no help whatsover) I thought
you ought to know that the English (and the British too ;-) use dd/mm, it'
Hi
Is there any chance that JSTL could get a date format that's even shorter
than "short"? I mean that I need the date just to be the day and the month.
And frankly, I don't think I should code this by hand (the English having
mm/dd, most others having dd/mm) when usually gives me all I need
:-)
Maybe it's just me but I don't see JSP as intrinsically OO. Even if one
tries to cram them, incorrectly in my mind, into the category of a 4GL
technology. JSP as it relates to HTML, and even to a large extent XML, is
about document oriented processing. I just don't see why you would want
method
With methods... one could say object.do() (and do OO) as oposed to
do(Object). The guide line for OO is noun.verb().
I wish it was methods.
Shawn Bayern wrote:
> On Tue, 15 Oct 2002, James Cook wrote:
>
>
>>I wonder why the unnecessary complication here? If they are going to
>>use reflection a
On Tue, 15 Oct 2002, James Cook wrote:
> I wonder why the unnecessary complication here? If they are going to
> use reflection anyway, why subject the users to creating these extra
> xml fragments. A nickname hardly seems worth it, and adding another
> point where a slight syntax problem in an XM
On Tue, 15 Oct 2002, Shawn wrote:
> xx<%=
> currentRow_questions.get("numb") %>
>
> currentRow_questions is a scripting variable (hashtable) in DbForms
> (open source rad).
>
> However the c:out value was incorrect. Am I just an idiot who can't
> do simple things correctly or is something go
Hi,
Sometimes I make the easiest problems hard. I was able to resolve the issue
today but just using some
Thanks,
Stef
- Original Message -
From: "Stefan" <[EMAIL PROTECTED]>
To: "Tag Libraries Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, October 15, 2002 1:48 AM
Subject: Re:
I wonder why the unnecessary complication here? If they are going to use
reflection anyway, why subject the users to creating these extra xml
fragments. A nickname hardly seems worth it, and adding another point
where a slight syntax problem in an XML document can cause additional
time deploying a
29 matches
Mail list logo
