Yeah, it is REST plugin related. At the moment a result is mandatory
(enforced by xwork) even though many of the restful operations its
meaningless to declare a result.. In those cases its also inappropriate
to use to ServletRedirectResult so a NullResult can be used.
However, you're right
My guess would be it's because the absolute default for default results
is undefined, it's just that many people include struts-default.xml in
their config which defines ServletDispatcherResult with default set to
true and thus it becomes the global default.
Musachy Barroso wrote:
I am guessi
I am guessing(wild guess) it is somehow related to REST.(output xml, json etc)
musachy
On Thu, Jun 12, 2008 at 10:55 AM, dusty <[EMAIL PROTECTED]> wrote:
>
> +1 for identical default behavior between XML and Annotations.
>
> Mr. Don, do you remember why you came up with the NullResult?
>
> -D
>
>
+1 for identical default behavior between XML and Annotations.
Mr. Don, do you remember why you came up with the NullResult?
-D
James Holmes-2 wrote:
>
> Not sure why there is a difference. Perhaps there's good reason? But if
> not,
> I'm in favor of consistency and making things the same.
Not sure why there is a difference. Perhaps there's good reason? But if not,
I'm in favor of consistency and making things the same.
Good catch.
On Thu, Jun 12, 2008 at 8:31 AM, Al Sutton <[EMAIL PROTECTED]> wrote:
> Is there any reason why the default result type in struts.xml is
> ServletDispa
