David,
As you suspected, this is related to having a flush in your applet.
The simple solution is to extend your ServletOutputStream with a flush()
method that does nothing.
In the future, please ask usage questions on the struts-user list. This
list is intended for issues related to developing
Perhaps this belongs on the user list, but I think it is relevant for
the discussion at hand. You all seem to regard all of the Struts taglibs
as one item, for which JSTL is an alternative. While this is certainly
true for the logic: and bean: tags, I have not seen a replacement for
the
html: form
For what my non-contributor opinion's worth, I totally agree with David.
So far as I know, while JSTL is not _required_ by the standard for JSP
1.2, it does not _require_ 1.2 -- and can be used with 1.1 containers;
so saying use JSTL does not translate to upgrade to Servlet 2.3.
Shai.
Like this http://issues.apache.org/bugzilla/show_bug.cgi?id=21603 ?
While this is not an attempt to define general extensibility mechanisms,
it does seem to address some of Edgar's and Tero's concerns... I think
it is a good example of the kind of extensibility needed. The bug asks
for a specific
Bill,
It appears that you are confusing request attributes with query
parameters. The latter are what is picked up by parameter= For
request attributes, my guess is you need logic:present name= I
am also guessing that the form triggering this action has a field named
invNum on it.
I am
Ask in the user list. Struts users may be relying on these methods, even
if Struts itself doesn't.
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 03:57
To: [EMAIL PROTECTED]
Subject: Refactoring RequestUtils
The movement of JSP specific
Katie,
You are doing only one thing wrong -- this is the developer's list, and
usage questions should be addressed to the users list. For your
question, the problem is not with the tags, but rather with your bean:
In your scenario, the populate() method does the equivalent of
Hi all,
I ran into the same problem as mentioned in
http://www.mail-archive.com/[EMAIL PROTECTED]/msg72240.html
and I was able to track it down. In summary, the user has a control in
his JSP page:
html:text property=apache.org /
And while presenting an existing bean works fine, trying to
Hi guys,
We are developing a web application with a number of complex pages and
dozens of controls. These controls' readonly status should be set,
individually, at runtime. With the current (1.1) struts-html, out pages
should come out as a repetition of
html:text property=someName
