David,
Perhaps you missed my -1 on providing a means of saving errors in session
scope unless an *automatic* means of removing them at the appropriate time
can also be provided.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21408
--
Martin Cooper
<[EMAIL PROTECTED]> wrote in messag
>extensibility goes, something like this would greatly
> >improve on how custom tags can be extended, IMHO.
> >
> I doubt there would many any notiable impact on performance.
I agree *iff* we're careful about the way it's done. Some of the method
calls will pro
pical notation is PR# .
As long as you commit from the top level, you'll pick up the CVS template,
which provides the spaces for you to enter bug number and submitter.
--
Martin Cooper
>
> David
>
> --- [EMAIL PROTECTED] wrote:
> > mrdon 2003/08/11 16:51
low us to remove deprecated
> features. How would these change under a 1.2.x type of release scheme?
Point releases (e.g. going from 1.2.0 to 1.2.2) are indeed bug fixes only
and no new features. New features require a minor version increment (e.g.
1.2.0 to 1.3.0). When we do "something drast
'forwardPattern' attribute, and the
RequestUtils.forwardURL() method (especially the JavaDoc for the latter).
--
Martin Cooper
>
> There is no contextRelative attribute on the action config so you don't
get
> to choose (or change) how your forward works.
>
> Of
ng to that path.
That sounds rather dangerous to me, unless you have some additional control
over which JSP pages can be accessed in this way. From your description, it
sounds like this gives the client blanket access to all the JSP pages in
your app, which I certainly wouldn't want.
--
Martin C
his, other than on naming. I think ParameterDispatchAction is
definitely the wrong name for the last of these. People are *far* more
likely to think of the "Parameter" in the name as meaning a request
parameter than they are to think of the "parameter" action mapping
attribute.
This is a question for the struts-user list. The struts-dev list is for
discussion of the development of Struts itself.
--
Martin Cooper
"RODRIGO CARVALHO DOS SANTOS" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi All,
Does Struts have a standard
"success".
This already exists, in contrib:
org.apache.struts.scaffold.SuccessAction
or, as David pointed out, you could use ForwardAction instead.
--
Martin Cooper
>
> This is a very simple action, but I find it exceptionally useful,
> particularly in the early stage
"James Mitchell" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Don has been involved with Struts for quite some time and has submitted
> numerous patches and enhancements. I believe that as we move forward with
> development, having Don on our team would be a tremendous asset.
>
>
that their existing
apps should "just work" when dropped in as a non-default module. But if they
are accessing JSP pages without going through the controller, they will
suddenly find that the wrong message resources are being picked up. Wouldn't
it be better for them to see an error m
"David Graham" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> --- Martin Cooper <[EMAIL PROTECTED]> wrote:
> >
> > "Steve Peterson" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> > > While you
3-part numbering *after* Struts 1.1, not *with* Struts 1.1. So there
is no 1.1.0 release.
--
Martin Cooper
>
> S
>
> At 08:14 AM 7/22/2003 -0400, Ted Husted wrote:
> >Craig R. McClanahan wrote:
> >>Do we really want to wait that long? CAN we wait that long?
> >
Steve,
I don't have a problem with your patch. As I said in the bug report, I don't
believe we should be fixing the reported problem, but your patch does fix a
backwards compatibility issue with apps that don't use modules, which is
probably a good thing. ;-)
--
Martin Cooper
&l
"Craig R. McClanahan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>
> On Mon, 21 Jul 2003, Martin Cooper wrote:
>
> >
> > Given that we have struts-legacy on its own release cycle, I think we
need
> > to decouple the struts-lega
do 'ant clean dist' at the top
level and point to an existing struts-legacy release, but I can't do that
the way the builds are coupled right now.
I could have just gone in and undone the coupling that was done (and I still
could ;), but I'd like to underst
t* mean
moving the burden of quality assurance from the committers to the user
base. The above statement regarding "the nice thing" about more frequent
releases could be construed otherwise, so I felt a need to clearly state
my own position. :-}
--
Martin Cooper
>
> James
>
This copy of MindTerm is for non-commercial and personal use only.
Steve, let me know off-list if you want me to send you a copy of MindTerm
2.0.
--
Martin Cooper
>
> Here is my shell script I start for ssh tunneling :
> echo on
> ssh -L 2401:localhost:2401 -l rleland -N cvs.apache.
t for anyone else either).
>
> How about if we have a logo contest, with the goal of making
> the new logo
> one of the features of the first 1.2.0 release?
+1. Sounds like fun!
--
Martin Cooper
>
> > Regards,
> > Jacob Hookom
>
means that I always seem to miss at least one when I'm preparing for
a new release.
I don't have any brilliant solutions for this at the moment, but I'll
definitely be giving it some thought.
--
Martin Cooper
On Wed, 3 Jul 2003 [EMAIL PROTECTED] wrote:
> DO NOT REPLY TO THIS
t but if I do, just point me in the
> right direction.
I believe Craig is the only Struts committer who has the karma to do that. I
offered to help Pier with Bugzilla maintenance a while ago, but the offer
wasn't taken up (probably because I'm not enough of a *nix hacker to do the
whole
Erm, actually, I was referring to the new:
private String label = null;
versus the original (and exactly equivalent, AFAIK):
private String label;
--
Martin Cooper
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 01, 2003 9:3
Just curious - what's the reason for explicitly initialising members to
null, given that that's what happens anyway?
--
Martin Cooper
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 01, 2003 7:20 PM
> To: [EMAIL PRO
James, you'll need to update the Gump descriptor too, otherwise we're going
to start seeing Gump failure messages again. ;-(
--
Martin Cooper
"James Turner" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Ok, now that the dust is settling on 1.1, I'
updated binaries
without the sample applications, is available at:
http://www.apache.org/dist/jakarta/struts/library/
Details of the changes in this release are available in the Release Notes,
which can be found here:
http://jakarta.apache.org/struts/userGuide/release-notes-1.1.html
--
Martin
n favor of this release, and can help
> [ ] +0 - I am in favor of this release, but cannot help
> [ ] -0 - I am not in favor of this release
> [ ] -1 - I am against this proposal (must include a reason)
> ------
that
> invokes the legacy build locally and it still works.
Awesome! Thanks SO much, Stefan!
--
Martin Cooper
>
> Oh, and ...
>
> On Thu, 26 Jun 2003, Rob Leland <[EMAIL PROTECTED]> wrote:
>
> > The only funny thing is that the target is for the
> > strut
x27;ll get them all done at once.
--
Martin Cooper
>
> Craig
>
> -- Forwarded message --
> Date: Thu, 26 Jun 2003 21:54:10 +0200
> From: Thomas Diesler <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: struts-lagacy.jar on ibiblio/maven
>
> Hi
s, Ted, that's great.
FileUpload went out last night (or rather early this morning ;), so now
we have all of our Commons ducks in a row. Yahoo! (Can I say that, or is
it trademarked? :)
--
Martin Cooper
>
> -Ted.
>
> Martin Cooper wrote:
> >
> > On Wed, 25 Jun 2003, Ted Huste
help support it
> [ ] -0 I am not in favor of the release
> [ ] -1 I am against this proposal (must include a reason).
> -----
Yippee!
--
Martin Cooper
>
> I am +1 on the Struts 1.1 Fin
he plan and vote,
or are you going to finish that up? I don't mind doing it, but I haven't
started on it yet, and likely won't until I've finished with getting the
FileUpload release out the door.
Just let me know which way you'd like to go.
--
Martin Cooper
>
> -T
y customers at that time. ;-)
I was just thinking about pushing out the release plan myself, but if
you're already on it, great! It looks like I'll have time to do the
release itself this weekend, assuming we're ready.
--
Martin Cooper
>
> -Ted.
>
>
>
>
> --
sue is one of figuring out how
to modify the Struts Gump descriptor to build struts-legacy first, and
then have the main build refer to that. Any committer can check in the
change, we just need to figure out what that change looks like. ;-)
--
Martin Cooper
>
> >
> > -chris
> >
;t had a chance to follow up on that. You
should be able to find the message in the archives, if you're interested.
Rob Leland has taken a crack at fixing the Gump descriptor, but it appears
he hasn't hit quite the right recipe yet. ;-)
--
Martin
Forwarding a report of web site problems.
--
Martin Cooper
-- Forwarded message --
Date: Mon, 09 Jun 2003 12:13:21 -0400
From: Apache Software Foundation <[EMAIL PROTECTED]>
Reply-To: Jakarta Project Management Committee List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
On Tue, 17 Jun 2003, Craig R. McClanahan wrote:
>
>
> On Tue, 17 Jun 2003, Martin Cooper wrote:
>
> > Date: Tue, 17 Jun 2003 10:39:08 -0700 (PDT)
> > From: Martin Cooper <[EMAIL PROTECTED]>
> > Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> &
r. I fixed the reported bugs but we should be distributing
> commons-validator 1.0.2 not 1.1-dev.
I just checked, and the Validator jar in RC2 is definitely 1.0.2. If
people are reporting problems against later Validator code, then they've
either downloaded a later nightly of Validator,
! ;)
Regarding Validator, there was a similar issue with versions prior to
Validator 1.0.2, but I'm pretty sure there is no problem with 1.0.2, which
is what's bundled with Struts 1.1 RC2. If I'm wrong, someone please
correct me ASAP so that we can fix that too.
--
Martin Cooper
This should help you understand the process:
http://jakarta.apache.org/struts/faqs/helping.html
--
Martin Cooper
"Ben Sion" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> This is prolly, blaringly obvious to those that have done this before,
> but, after
On Sun, 8 Jun 2003, Martin Cooper wrote:
> We're responsible for our own Gump descriptor. ;-) So, I guess we need to
> create a new descriptor for struts-legacy, since it needs to be listed as
> a dependency for the regular Struts build. I'm not sure how this works
> wh
My apologies. Commons Logging now comes as two separate jars, and I
bundled the wrong one.
I've fixed the problem on the main Apache site. It'll take a little while
to propagate to the mirrors, so if you want to download it right away, you
probably want to go to the main site.
--
Mar
Husted for his help in preparing this release.
--
Martin Cooper
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ruts Gump descriptor. In this case, we need to create the descriptor for
struts-legacy, though. However, this gives me an idea - perhaps I can look
to the Commons descriptor for ideas on how to add struts-legacy to the
regular Struts descriptor.
--
Martin Cooper
>
> -T.
>
> Martin Coope
n case, I've built a release and created signatures and digests, and
even have a site2 update ready to go. If you'd like me to pick this up, I
think all I need to know is which testing still needs to happen. (I'd like
to avoid doing all of it, if possible, for
> -Original Message-
> From: Martin Cooper [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 08, 2003 5:26 PM
> To: 'Struts Developers List'
> Subject: RE: [VOTE] Convert RC2 to Beta 5
>
>
>
>
> > -Original Message-
> > From:
> -Original Message-
> From: Martin Cooper [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 08, 2003 4:56 PM
> To: 'Struts Developers List'
> Subject: RE: [VOTE] Convert RC2 to Beta 5
>
>
> I'm not going to vote right now, because I'm trying to
mainder of that test works fine on Tomcat 3.3.1. I propose to go ahead and
check that in unless I hear any objection.
Now I'm looking at the logic-compare.jsp problem. If anyone else has some
time to look into the problems, might I suggest looking at the Tiles-related
ones that Ted men
> -Original Message-
> From: Martin Cooper [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 08, 2003 10:24 AM
> To: 'Struts Developers List'
> Subject: RE: Status check? - Houston we have a problem
>
>
>
>
> > -Original Message-
&g
#x27;t be today.
--
Martin Cooper
> -Original Message-
> From: Craig McClanahan [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 08, 2003 2:34 AM
> To: [EMAIL PROTECTED]
> Subject: [GUMP] Build Failure - jakarta-struts
>
>
>
s
getters in the Tomcat CookieFacade class, whereas there is only a getter for
'name'. So this actually looks like some kind of JSP/reflection bug, not
related to Struts. (The tag must have worked, because we know
the tag is trying to access a cookie!)
--
Martin Cooper
>
On Sat, 7 Jun 2003, Ted Husted wrote:
> Martin Cooper wrote:
> > http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases
> >
> > I added the section on PGP 8.0 Freeware, since that's what I use, but you
> > can also use GPG, which I think is instal
On Sat, 7 Jun 2003, Ted Husted wrote:
> Martin Cooper wrote:
> > You'll find everything ready to go at ~martinc/struts-legacy on
> > cvs.a.o. I've created the .asc signature files, and the .md5 digest
> > files, but only for the .tar.gz and .zip files, since we
On Sat, 7 Jun 2003, Ted Husted wrote:
> Martin Cooper wrote:
> > http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases
> >
> > I added the section on PGP 8.0 Freeware, since that's what I use, but you
> > can also use GPG, which I think is instal
On Sat, 7 Jun 2003, Ted Husted wrote:
> Martin Cooper wrote:
> > I'm actually in the middle of adding that now. ;-) I remember you asked me
> > a while ago to make sure we list the explicit versions we use.
> >
> > The "What's Included" section se
o make sure we list the explicit versions we use.
The "What's Included" section seems like the logical place. My only
concern is that, because of the length of the "RC/Beta Fixes" section,
it's quite far down the page. But I don't know where else I would put
it..
I'm doing a cleanup pass over the release notes right now, fixing some
things and cleaning up the text in some places. Is it OK for me to go
ahead and check that in when I'm done, Ted?
--
Martin Cooper
On Sat, 7 Jun 2003, Ted Husted wrote:
> OK, the release-notes are updated. ]My,
"Ted Husted" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Martin Cooper wrote:
> > The tagging for the main Struts release will actually be a bit more
> > painful for RC2 since you can't just blanket-tag the Commons packages -
> > they&
t we don't need to build the releases with that.
--
Martin Cooper
>
> I'm installing 1.2 now, to at least be sure it still builds (as I
> remember, the nightlies are building on Craig's machine under 1.4).
>
> -Ted.
On Sat, 31 May 2003, Martin Cooper wrote:
>
> "Ted Husted" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Martin Cooper wrote:
> > > Now, about the Struts 1.1 RC2 release. The problem is the staging
> > > needed to get FileU
"David Graham" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'm fairly certain I voted +1 on this.
Yup.
http://marc.theaimsgroup.com/?l=struts-dev&m=105421605003516&w=2
--
Martin Cooper
>
> David
>
>
> >From: "James Turn
PG, which I think is installed on daedalus. The MD5 tool is
definitely installed on daedalus, since that's where I create the digests
for Struts releases.
If you're still having trouble, you could put the zip and tar.gz bundles
in your home directory on cvs and give me access, and
The tagging for the main Struts release will actually be a bit more
painful for RC2 since you can't just blanket-tag the Commons packages -
they'll have to be tagged individually to match the specific versions
we're bundling.
Hope this helps.
--
Martin Cooper
>
> Is that co
"Ted Husted" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Martin Cooper wrote:
> > Now, about the Struts 1.1 RC2 release. The problem is the staging
> > needed to get FileUpload out the door. It's currently at Beta 1, and
> > the c
ith FileUpload. I don't
expect you guys to do that at all.
Rant over. Now back to my "day job". (A "day job" at 11pm? What's wrong
with this picture?)
--
Martin Cooper
>
> James Turner
> Director of Software Development
> Benefit Systems, Inc.
.
>
> I thought struts "nightly build" was built with latest "nightly build" commons. Did
> I miss something ?
Hmm, it's certainly supposed to be. If that's not happening, then there
might be a problem with the build script. That's Craig's bailiwick,
the subject of a bug report
annoying, and I'd rather see that removed and replaced with the use of the
PatchAvailable keyword.
--
Martin Cooper
"Mohan Kishore" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I am sorry - i guess i was not very clear. i am jus
"Mohan Kishore" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> --- Martin Cooper <[EMAIL PROTECTED]> wrote:
> > 1) All of the tags in the logic taglib relate to flow control. There are
two
> > sets - conditionals and 'goto'
so impassioned about
cleaning up the logic taglib when he's usually the first person to suggest
that people forget that taglib and use JSTL instead. ;-) ;-)
--
Martin Cooper
"David Graham" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> IMHO, the and tags
s in one place.
Nope. I'd say is Struts-specific. ;-)
--
Martin Cooper
>
> I don't think we need to pull them, but I would be in favor of
> deprecating them as logic tags and placing them in the html taglib (next
> time around).
>
> David Graham wrote:
> > IMH
y. Otherwise Struts RC2
wouldn't be a true release candidate either.
--
Martin Cooper
>
> Is anyone working on Commons DBCP, Pool, or Logging?
>
> David
>
> >I've been somewhat absent from here for a while, primarily because I'm
> >working on getting Fil
Upload 1.0 Beta 2, then
remove the deprecated methods, go for RC1 and then Final, all in as short a
period as I can push it through.
Comments welcome.
--
Martin Cooper
>
> -T.
>
>
> Ted Husted wrote:
> > I'll update the plan and website later, but for now, the outstanding
should be going back
and reinstating the original value later. That being the case, we might as
well use LATER for what it's meant for, and leave Version for what it's
meant for.
And yes, I know that I can look at the Bug Activity to see the original
version, but unless I'm mistaken
o I'm guessing it is. It's worth
noting that (unless the spec dictates it somewhere) other containers may
not do the same thing. For example, Resin 3.0 still has both in a single
jar file.
--
Martin Cooper
>
> Revision ChangesPath
> 1.32 +6 -1 jakarta-struts/bu
On Thu, 6 Mar 2003, Mark wrote:
>
> I was looking for a "Get involved" or "Report bugs" link on the struts website, and
> could not find any.
I guess you missed this page:
http://jakarta.apache.org/struts/using.html
--
Martin Cooper
>
> I would like
I've made the change, but I don't have a handy JSP 1.1 to build against,
so could you try it, please, and make sure it's OK? It still builds fine
against JSP 1.2.
--
Martin Cooper
On Wed, 5 Mar 2003, David Graham wrote:
> When I try to build Struts I get this error:
>
s anyone else having this problem?
I'm not seeing the problem, but then I'm currently building against JSP 1.2.
You are correct that EVAL_BODY_AGAIN is a JSP 1.2 constant. The JSP 1.1
equivalent is EVAL_BODY_TAG, so that's what we need to be using.
Looking back at the recent commit messag
ghts?
I believe we should add support for specifying a bundle, but I don't think
support for arguments is necessary, given the nature of these attributes. I
agree with David K that the alternatives, such as the one you presented
above, reduce the maintainability of the JSP pages.
--
Martin Co
ther open issues against Validator that will
need to be addressed before we release a 1.0.2. There are 10 open bug
reports (including #17470), only 3 of which are enhancement requests.
--
Martin Cooper
>
> > -Original Message-
> > From: David Graham [mailto:[EMAIL PROT
Does this actually build properly? I see this structure:
Some text here.
Some more text here.
The second piece of text is not within a paragraph...
--
Martin Cooper
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> jmitchell2003/02/28
t
any
> action of the user, and lets you choose to submit it or not.
... which, FYI, is exactly what the spec says it should do.
See section 8 in:
http://www.ietf.org/rfc/rfc1867.txt
--
Martin Cooper
>
> -- Antoni
ther or not we would
have an additional RC build beyond that, just to pick up released versions
of all of our dependencies.
--
Martin Cooper
>
>Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've removed Commons Resources from the build, and also from the Gump
descriptor, and updated the docs so that they no longer refer to this
component. Struts no longer has any Commons Sandbox dependencies. :-)
--
Martin Cooper
"Martin Cooper" <[EMAIL PROTECTED]> wrote i
e for what you are
describing.
--
Martin Cooper
"Karr, David" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]
>
> On Thu, 27 Feb 2003, Karr, David wrote:
>
> > Fr
n itself may not be a problem, but not all of the
attributes should be exposed for every tag that extends the base class
(since they're not all valid for all HTML tags, for example).
Would it be possible to control something like that with XDoclet?
--
Martin Cooper
>
> But, more belo
mmunity have stricter guidelines?
Yes. See "Reporting Bugs and Feature Requests" here:
http://jakarta.apache.org/struts/using.html
Perhaps we should make it more obvious that the mailing list shouldn't be
used for that.
BTW, I'm horrified that we had unused imports! ;-) The last
s from within our own workspace, and I'm assuming
> we're going to use essentially the current HEAD branch plus critical bug
> fixes, and continue our plan to package struts-el in the "contrib"
> directory as we do today.
That's my working assumption too.
--
Martin Cooper
>
> Craig
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No. Jakarta ORO is a text processing package that Validator uses for its
regular expression functionality. Commons Net is an internet protocol suite.
Both packages did originate at ORO, Inc., though. ;-)
--
Martin Cooper
"Byrne, Steven" <[EMAIL PROTECTED]> wrote in mes
"David Graham" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Sorry I got off topic there. Why do we have a dependency on ORO? Does
one
> of the commons-* libraries use it?
Yes, Commons Validator uses it.
--
Martin Cooper
>
> Re nested: Arron
cat 4.0.6 and 3.3.1. So I, at least, have a much greater
degree of confidence in the builds of Commons components that are included
in the Struts RC1 release.
Now it's up to the rest of the Struts community to tell us where the
problems are. ;-)
--
Martin Cooper
"Gary Ashley" &
without the sample applications, is available at:
http://www.apache.org/dist/jakarta/struts/library/
Details of the changes in this release are available in the Release Notes,
which can be found here:
http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc1.html
--
Martin Cooper
the release is
up, and I'm about to send the announcement. Hurrah!
--
Martin Cooper
>
>
> --
> James Mitchell
> Software Engineer/Struts Evangelist
> http://www.open-tools.org/
>
> "Beer is the reason we get up each afternoon."
> -- Ray McNeill
>
>
27;re back to where we were. I've re-tagged the file for RC1, rebuilt, the
tests are passing, so keep your fingers crossed!
--
Martin Cooper
On Sat, 22 Feb 2003, Rob Leland wrote:
> After fixing the DTD reference in the struts-config.xml it appears that
> all tests passed,
> un
mehow messed up my system. (I have been able to
run the Cactus tests in the past.) Therefore, I'd appreciate it if someone
else could take the tests for a spin, and let me know the results.
Thanks!
--
Martin Cooper
-
To
e listing betas under the release section. This is
> misleading and confusing to new users.
Being that this is open source and all, you're welcome to submit a patch to
make milestone builds available via mirror sites as well (binary and
source).
--
Martin Cooper
>
> David
>
&
coming soon to a
mirror site near you!
--
Martin Cooper
>
>
> --
> James Mitchell
> Software Engineer/Struts Evangelist
> http://www.open-tools.org/
>
> "The man who does not read good books has no advantage over the man who
> cannot read them."
> - Mark
mirror system. Only the Release
section of the download page references mirror sites at this time.
--
Martin Cooper
"James Mitchell" <[EMAIL PROTECTED]> wrote in message
006401c2d82b$5fcd5240$1f64f80a@atlanta">news:006401c2d82b$5fcd5240$1f64f80a@atlanta...
> Because
have
(yet ;). Still, you could do it like this, although it's a bit ugly:
--
Martin Cooper
>
> So the only place is in the bean, inside the getStartDate() {}.
>
> The other alternative is to copy.
>
> And I must have misunderstood what you were saying, but I think I no
>
> So as you point out, I can format and localize both in the bean. (Ex:
> formBean.setLocale(x) )
Um, I didn't point that out at all.
--
Martin Cooper
> So probably a better choice.
>
> But... since I like how the FMT tag works not sure what "best"
> app
), etc in the bean class. If the
> page is read only, I would format in JSP.
I guess I don't understand. Why do you need to do formatting in the bean,
and why is it different if the page is read-only? You should be able to use
JSTL to do this in either case.
--
Martin Cooper
> So far
tAttribute("foo", "1234567890");
%>
- cut here -
To avoid any question of what other JSTL tags might be doing, I've
explicitly stored a string in a request attribute. The output from the above
page is:
$1,234,567,890.00
The tag did its job just fine when passed
101 - 200 of 682 matches
Mail list logo
