martinc 01/11/19 18:42:44
Modified:doc/userGuide resources.xml
Log:
Updated seminars and consultants entries.
PR: 4864, 4867, 4875
Submitted by: Mike Way, Tim Biernat, Joey Gibson
Revision ChangesPath
1.13 +4 -2
martinc 01/11/19 19:07:30
Modified:src/share/org/apache/struts/util LocalStrings.properties
Log:
Fixed a typo in message resources.
PR: 4836
Submitted by: Daniel Temme
Revision ChangesPath
1.5 +1 -1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4968.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
*whew* - much better! :)
Except that I don't prefer the method you describe because of its increased
footprint in struts-config.xml - but we've already covered that issue.
I'll try to submit the first two of the four dispatch base classes I
proposed in a day or so - they will just be a
well, but now, in case of using DispatchAcion this footprint is really
small,
I would say, that it is not much bigger, than implementing
getKeyMethodMap() ;-)
Right, you have one additional action mapping in struts-config than my
design.
I have mappings in the subclass via getKeyMethodMap,
I just don't feel that struts-config is the appropriate place to deal with
those kinds of mappings as they are very concrete to the action. A matter
of preference, I suppose.
Is that a fair enough summary?
Sure.
I still like my design better! :) But yours works and certainly is a viable
Hey,
What's the proper CVS tag to use for fixes for the 1.0.1 release?
Is it STRUTS_1_0 or STRUTS_1_0_BRANCH, or something else?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Struts 1.0.1 will be taken off the STRUTS_1_0_BRANCH branch, so that's where
you need to check in fixes for it. You should also make sure you check in
the same changes to the main trunk, so that they'll make it into Struts 1.1.
--
Martin Cooper
- Original Message -
From:
The tag should be STRUTS_1_0_1 to be consistent with the previous tag
names. Since we're releasing this off the 1.0 branch, be sure you tag
from a repository that is checked out there, instead of the HEAD branch.
Craig
On Tue, 20 Nov 2001, SCHACHTER,MICHAEL (HP-NewJersey,ex2) wrote:
Date:
Hi, just thought I'd offer up a minor patch to the stylesheet for
generating taglib documentation. I wanted to generate docs for my own
taglibs and found the struts approach perfect for my needs but I wanted
a couple of tweaks :-)
The patch causes the 'Required' and 'RT Expr' flags to be put
Hey,
I did a
cvs rtag -b -r STRUTS_1_0 STRUTS_1_0_1 jakarta-struts, thinking
it would create a local copy of STRUTS_1_0_1 stuff on my
machine and I created another branch on the CVS repository
called STRUTS_1_0_1... is there a way to get rid of that
branch, base it off of STRUTS_1_0_BRANCH
I'm a bit confused now... Was the STRUTS_1_0_1 branch put in
recently and I just thought I put it there? Did I actually
do anything? And if I didn't, I just committed multipart
changes to STRUTS_1_0_BRANCH, should I now re-commit them to the
STRUTS_1_0_1 branch? Am I just going crazy? Sorry
No, the STRUTS_1_0_1 wasn't there before - the rtag command created a new
branch. I need to figure out how to undo it, since I'll need to label (but
not branch) the Struts 1.0 branch for the 1.0.1 release tomorrow. In the
meantime, it might be better if you don't commit anything to the branch you
13 matches
Mail list logo
