Hi All,
I remember a while back that there was quite a bit of discussion
which Java version to make the primary version supported by SAF2 and
if it's 5, then how to support 1.4. Retrotranslator was mentioned as
one of the ways to support 1.4 without having to stay source-compatible.
I'd
I don't often reply to messages on these lists, but I feel like I
have to offer a (relatively) outside perspective here.
There's been a lot of confusion external to apache about what's going
on with Struts. With Shale moving to a TLP, that's helped, but I
think a lot of people are still co
It's a gentle slide for WebWork 2.2 developers now, and some of us
would like to keep it that way.
Forever? Or just for the Struts 2.0 release? Because if you guys
are talking about making sweeping changes some time ... can you keep
doing this?
Now, if the current 2.0.0 doesn't represent
While it might imply that, Stripes actually uses
@HandlesEvent
Which can take an optional String parameter which is the name of the
handled event (which is defaulted to the method name otherwise)
I was going to chime in on this, so I may as well now. Stripes,
through it's default w
Being able to return Result instances from Actions doesn't
necessarily mean the lack of reuse of Results. This is equivalent to
saying that because it's Java code you can't reuse it. I didn't
realize that XML was the solution to lack of reuse in OO ;)
Seriously though, it's not uncommon i
On Jul 26, 2006, at 11:00 AM, Jason Carreira wrote:
I understand that there are different ways to skin the cat, but
what if I want to reuse my actions in different contexts? What if I
want to call my action from a JBPM workflow? Do I need to subclass
it to override the result that's returne
I can't agree enough with using var-args for logging. Stripes has,
from the start, done something very similar to Seam. The main
difference is that instead of putting placeholders into the message,
you just provide things in the order you want appended. I find that
convenient because you
To add a little weight to Don's comments, the cost of allocating an
array really is *very* minor. To quote Brian Goetz[1], the cost of
allocating a new object in 1.4.2 and above is approximately 10
instructions (maybe more for an array, but remember that var-arg
calls are optimized at comp
On Aug 22, 2006, at 5:11 PM, Martin Cooper wrote:
if (isDebugLoggingEnabled()) {
log.debug("And the answer is: " + expensiveMethodCallHere());
}
I don't know about you, but I'm very thankful for that guard when
debug
logging is disabled (e.g. in production). Without it, I'm going to
make
Why does a difference of opinion always have to lead to someone
saying "I don't think you get what I'm saying"? Sigh. I get it just
fine, I just disagree.
So what you're saying effectively is that developers who are smart
enough/well trained enough to know to wrap expensive logging
stat
I feel like I should jump in and clear up my position here since the
"Stripes" position is essentially what I wrote in a blog entry ;)
Stripes very happily supports both the push and pull ways of doing
this (and Jason pointed out to me earlier, that WebWork has similar
functionality but I
11 matches
Mail list logo
