And remember, old ska bands never die, they just can't
pickitup-pickitup-pickitup anymore.
(Couldn't resist the chance to use my only ska-related joke).
Rick Reumann wrote:
Yea, it's not Friday. Just whining (with no cheese)..
Anyone else fed up with trying to keep up with all the stuff coming
I like the TreeMenu Pro control from Tigra/SoftComplex
www.softcomplex.com. It's a pure Javascript solution, not JSP specific,
but it's very fast and configurable (and browser neutral)
K.C.
Barnett, Brian W. wrote:
If you know of a good, configurable tree control tag library for use in jsp
pag
Do you have the option of using URL-rewriting instead of cookies for
your session tracking? If you've used or etc for
all your addresses, you should be able to just switch it on. Then, each
time a user hit a link that didn't have the jsessionid encoded, they'd
receive a new session when one
o ago. Search for
that as it has some instructions on setting up SWF to work with Struts.
K.C. Baltz
Dakota Jack wrote:
I have been taking another look at the AJAX stuff that Frank Zammetti
has provided. This stuff is revolutionary. Someone ought to be
taking a close look at integrating such
Done: http://issues.apache.org/bugzilla/show_bug.cgi?id=34460
K.C.
Joe Germuska wrote:
At 11:19 AM -0700 4/14/05, K.C. Baltz wrote:
I stand corrected and informed. Now that you mention it, I remember
looking into this before. I wish the Struts Users Guide HTML tag API
made the difference a
sent my email didn't make the difference clear. It didn't help
that the doc for :errors only mentions displaying an ActionErrors object
whereas the :messages one references ActionMessages and ActionErrors.
K.C.
Joe Germuska wrote:
At 8:55 AM -0700 4/14/05, K.C. Baltz wrote:
Perhap
The error is suggesting that it can't find an entry for "status" in the
page scope of your page. Do you still have the in there?
If you have the scope attribute, make sure it's set to page. Otherwise
you'll have to replace pageContext with request, or session depending on
your choice of sc
Absolutely and of course. I based this validator on the TwoFields
validator floating around. I never changed that property. I think
laterDate would be my pick. dateBefore is a good choice as well.
Thanks for the feedback,
K.C.
Dave Newton wrote:
If this is going to get into the distro could
I think Dave's got it. Use the struts-el tags if you want to have EL
expressions instead of RT expressions (<%= ... %>)
If you want/have to stick with RT, then you'd need this instead of
${status.index}
<%= ((javax.servlet.jsp.jstl.core.LoopTagStatus)
pageContext.getAttribute("status")).getIn
Perhaps you should be using to display your error messages
instead of
I think it depends on if you use saveErrors or saveMessages in your Action.
K.C.
Les Dunaway wrote:
I am having problems with Struts 1.2.4 ActionMessage / ActionError.
I'm using a setup like recommended on the wiki
Acti
Sure. I had figured to bring it to the -users list before anything -dev
related so I could get it reviewed. But I'm happy to put in an
enhancement.
Done. http://issues.apache.org/bugzilla/show_bug.cgi?id=34454
K.C. Baltz
James Mitchell wrote:
Thanks for your contribution. Any chance I
te it back so that others can find it and I can also get a
little extra scrutiny.
This was written for Struts 1.2.4
K.C. Baltz
== snippet from validator-rules.xml
=== Example entry in validatio
There must be a dozen possible answers to this one. I can tell you what
we do and say it works for us.
We use a combination of settings methods. Some web settings go in the
web.xml in a element. Things that are non-web specific
go into the Java System Preferences. I was initially skeptical
I agree with those who suggest inline updating use Javascript. I've
written some code to handle paging of a table this way so that flipping
to the next page of results doesn't result in a whole page refresh.
What I would add is that it can be very simple because Javascript allows
you to repla
I don't believe it should be necessary to manually add the bean to the
request attributes.
My guess is that you have not explicity set your Failure forward to
redirect="false". I'm not sure what the default value is, but if you
mistakenly set redirect="true", you'll lose all your form data.
I've never needed a "property" attribute with the html:cancel control.
Perhaps that's the problem? Make sure you have a cancel() method in
your DispatchAction
K.C.
Bing Qiao wrote:
Hi,
I am using Struts Validator for a LookupDispatchAction.
I'm using both client and server sides validation.
Th
How are you setting the value of "dispatch" in your page? A hidden
field? Is it hard-coded or do you set it when the button is clicked.
Is there more than one form in the page such that Enter might be
submitting a different form than you expect? You might need some
javascript to ensure that
I've run into an interesting problem involving dispatch actions and
(or tiles:insert). The problem is this. I have a page that
lists some files. The user can upload another file from this page, but
if the file is too large, Struts starts the error processing for the
action. Here are my two
f the "required"
validation when using validwhen? "required" doesn't accept values
that are nothing but whitespace whereas there's no way to test for
this when using validwhen.
K.C. Baltz
-
To unsubsc
quired" doesn't accept values that
are nothing but whitespace whereas there's no way to test for this when
using validwhen.
K.C. Baltz
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
20 matches
Mail list logo
