Oh, dang! Forgot to actually change it.
On Jan 19, 2008 9:03 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- James Mitchell <[EMAIL PROTECTED]> wrote:
> > (I renamed the subject to attract the attention of any devs who would
> > likely have something to say about increasing the size of the distr
Am Samstag, 19. Januar 2008 21:01:58 schrieb Brian Pontarelli:
> It seems to be a bug. I have a large complex application up and that
> uses namespaces and it appears to be working well. Therefore, I'm
> assuming it must be an environment or configuration bug inside the
> convention plugin that is
--- James Mitchell <[EMAIL PROTECTED]> wrote:
> (I renamed the subject to attract the attention of any devs who would
> likely have something to say about increasing the size of the distribution,
> but are probably not following this discussion)
Looks the same.
> I could be wrong (it's happened
(I renamed the subject to attract the attention of any devs who would likely
have something to say about increasing the size of the distribution, but are
probably not following this discussion)
I could be wrong (it's happened in the past, rarely :) , but that setting is
not an out-of-the-box confi
Piero Sartini wrote:
The results should be the same as smarturls, codebehind, etc. In your
case they should be login-success.jsp or login.jsp and
register-success.jsp or register.jsp. If you turn on some fine or finest
logging in the convention package it should print out the results it is
mappin
You asked that the discussion be moved to struts-dev, so I did.
S2 *does* have an out-of-the-box configuration; it's in default.properties.
It uses commons-fileupload, and it won't fail until runtime when using
.
While your comment added to the upload interceptor is useful, it should be in
a {not
My comments on this can be found here:
https://issues.apache.org/struts/browse/WW-2446
On Jan 19, 2008 11:29 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
> The tag depends on an upload dependency being in place.
>
> The default S2 configuration uses commons-fileupload, which won't work with
> the
The tag depends on an upload dependency being in place.
The default S2 configuration uses commons-fileupload, which won't work with
the standard distribution, because we don't include fileupload.
If we don't want to ship fileupload, then we should not make the default S2
configuration use it, be
